Sounds nice, but on the long run, why not including a PHP class for extensions into core. This would already make quite some code you need for new extensions obsolete. I'd like to see a base class for all extensions which offer simple information such as the extensions name, version, file path, etc.
2012/7/2 Andrew Garrett <[email protected]>: > Ooh, I like this. > > On Thu, Jun 28, 2012 at 7:37 AM, Ori Livneh <[email protected]> wrote: > >> >> >> On Monday, June 25, 2012 at 9:06 AM, Derric Atzrott wrote: >> >> > Would anyone be interested in a program that generates Skeletons for new >> > extensions? I've noticed that when I make extensions I generally go >> through >> > the exact same process (with minor variations) each time. >> > >> > >> >> [ snip ] >> >> I've been working on something similar, so I decided to throw it up on >> GitHub, in case it's useful. It's a skeleton extension for >> JavaScript-centric MediaWiki extensions. >> >> https://github.com/atdt/skeljs >> >> Out of the box, you get: >> >> * QUnit test scaffold >> * ResourceLoader integration >> * MediaWiki-compatible JSHint config >> * Command-line build tool (grunt) for linting and running Qunit tests >> using phantomjs >> >> I've only recently started developing on MediaWiki so this definitely >> needs to be reviewed. (*cough* Krinkle / Roan / Trevor?) >> >> Derric (& others): feel free to use this in any way you want. I'll >> migrate this to Gerrit when I get the chance. >> _______________________________________________ >> Wikitech-l mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l >> > > > > -- > Andrew Garrett > Wikimedia Foundation > [email protected] > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
