Thanks, for your feedback, my additions are not carved in stone
Sure, there’s a difference - sorry about the CSS Framework, this has to be clarified. And with jQuery you’re also hitting the point!
But jQuery is part of the core and therefore treated in another way than bootstrap. Bootstrap may become part of the core, but what’s about Zurb Foundation, mootools, etc. then? @jacmoe: Right
That said, I sometime stumbled upon incompatibilities with jQuery versions in Yii 1.x. With scriptMap you can overcome this problem, but wouldn’t it be nicer just to define the version of “yii2-jquery” you want to have or just download it and place it into your app? You could also remove “yii2-bootstrap” and include “yii2-zurb-foundation” - without composer, may do this by hand, but the code has to be structured in a certain way.
And on the other hand, that an extension must not include existing (PHP, Yii) extension code, take YiiBooster and yii-boostrap for example.
In the first releases YiiBooster included a slightly modified version of yii-bootstrap, which would have lead to incompatibility issues. That must not happen.
I am inspired by the Unix philosophy Rule of Composition and Rule of Separation.
If such a thing happens, we should use the composer.json file to define either a require(ment) or conflict(s).
Please, you don’t need to actually use(!) composer. This file would just contain a very basic set of meta information in JSON format, which would make it also very easy to create a custom Yii2 package repository. I would make this a requirement , not just for the sake of composer, more because it would take a ton of load off the core-devs maintaining the extension platform.
Don’t has to be src/, but as far as I understand the PSR-0 Examples you have to have kind of an entry point for autoloading your classes via a namespaces. Note: I am not experienced with namespaces, so I may overlook something here.
But to give you also an example here, this one line enables me to use any class from packages, which support autoloading via namespaces, without adding an alias or import - even in Yii 1.x.
How will we "install" an extension in Yii2?
I also totally agree here. btw: I tried to use the word SHOULD instead of MUST on the “debatable” points .
And for sure we should provide something like a downloadable extension template to start with.
Ah, that would be a very nice yiic command or gii module!
Sure sorry, like in PSR-0: \<Vendor Name>\(<Namespace>\)*<Class Name>