Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release on WordPress.org #5

Open
mpeshev opened this issue Sep 9, 2013 · 3 comments
Open

Release on WordPress.org #5

mpeshev opened this issue Sep 9, 2013 · 3 comments

Comments

@mpeshev
Copy link
Contributor

mpeshev commented Sep 9, 2013

Have you considered releasing the plugin on WordPress.org?

@topdown
Copy link
Owner

topdown commented Sep 9, 2013

I have been using it for a couple years, as a simple benchmark solution and decided to put it here on Github to see if it would get any attention.

I have thought about it, but was holding off because of trying to make decisions on internal business models.
A couple weeks ago I spent a couple days on a more robust version that removes the need for settings and abstracts all of the data into a large array. This array is then formatted for display, the main purpose is so it can be stored for record and exported for clients.

It also uses simple jquery on the front end to hide and show sections, removing the need for settings.
And has a new section for counting HTTP resources on page load, images, JS, CSS, and listing the locations.
Basically lowering the requirement of having to use browser tools like FireBug to see what static files are loaded by plugins.

Long story short, I have not decided what I am going to do between the 2 plugins.

@mpeshev
Copy link
Contributor Author

mpeshev commented Sep 9, 2013

Okay, I'd appreciate letting me know when you decide (just to know if what I'm poking would be buried in the ground).

There are quite a few debugging/benchmark plugins really and I'm not certain which is the most active, but this one came handy and doing what I need as well. I would take a look at the other, extended one, if you plan to release it and not sell it.

@topdown
Copy link
Owner

topdown commented Sep 9, 2013

I tested a lot of those plugins, wasn't happy with them, so I wrote this one to do what I needed at the time.
This one would not get dropped or buried.
I would keep this one public and add the more advanced one as a paid/upgrade option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants