Hi Christian,
thanks for your post and for the suggestion! I really appreciate your feedback!
You are correct, in that the plugins page will have many items on it, if someone uses many Extensions. However, for me, that’s actually an advantage: I don’t have to duplicate code that is already there. If I would now add a separate tab for managing Extensions in TablePress, things would get bloated even more, in my opinion.
Also, putting the Extensions in a subfolder has one major problem: One would lose flexibility in editing them, as an automatic plugin update would erase all modifications. So, this is not really an option. If at all, one would need a new “meta” plugin (which is then the only Extension showing on the plugins page), that can be used to manage all of the TablePress Extensions. But that’s exactly what I mean above: It would be extra/redundant work, that I’d rather spend on the plugin or the Extensions themselves.
For putting the Extensions on GitHub: I actually have them in a repository there, but that’s a private repo, as it contains some custom stuff for some people. I’ll need to find the time to clean up that repo, before I can publish it.
Regards,
Tobias
Thanks for the fast answer. Your support for the plugin here at WP.org is really impressive.
All you are saying is logical and I see why your current way is the most suitable.
What do you think about the project I mentioned in the end of my post?
Hi Christian,
sure, no problem, you are very welcome!
About your project idea: That does indeed sound interesting, but I’m not really sure that you would get a whole lot of adoption.
I’m using git/GitHub myself for the TablePress development, and then manually push to the wp.org SVN plugin repository whenever I want to release a new version (via git-svn in SourceTree).
That doesn’t happen that often for me (only once in a few weeks), so that I don’t really need this to be automatic. Also, I don’t think that I would be comfortable with giving someone push access to the plugin’s main repo.
What I would like however would be the automatic translation management of the plugin on wp.org. Right now (for TablePress and WP-Table Reloaded), I managed the translation files manually, and always have to write an email to the translators and ask them to update the translations before a release. This is tedious, and as a few translators are no longer interested, translations get abandoned. Also, doing the actual translation in poedit or the CodeStyling Localization plugin is not always trivial. Have that in a real open-source manner/community approach would be much better. I have thought about hosting a custom GlotPress installation for TablePress, but then was reluctant as that’s again another service to administer and maintain. I have seen that you are engaged in GlotPress as well, and maybe that could be a first starting point, especially as the WP core team has shown some interest into better plugin translations in the past (mostly Nacin). So, a translate.wp-plugin-repository.org (or whatever) would be really cool and I would love to see that integrated into the WP plugin repo.
Regards,
Tobias
Thanks for the input.
I will take your points into consideration and keep you in the loop.
Hi,
sure, no problem! You are very welcome!
I’ll be following your project. All the best for it!
Best wishes,
Tobias
