-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Implement bootstrap extension #20
Comments
First, this is an extension, meaning optional in downloading. So you shouldn't worry about download size. |
@qiangxue Thanks for explain it. It's good to know that will exist official extensions, this three qualities (ready-to-use|high-quality|continued support) on Yii tools are awesome features. |
Will you separate this extension into an own repository? |
Not this one, I guess. |
Please consider it, we also had this discussion about the zii widgets, it's minimal overhead to include it as a package, but would greatly enhance the modularity of the framework. E.g. if someone wouldn't use bootstrap at all he would not require this package and get a slimmer core. This applies also to any package which depends on other code, eg. zii-widgets depend on jQuery. |
@qiangxue @samdark "officially maintain some commonly used extensions so that developers can have ready-to-use and high-quality tools they need without the worry of code breaks or discontinued support" Bootstrap is an external source, what would happen if bootstrap is in the future replaced in use by, for example, the zurb foundation? I do not think that it should be officially supported but Yii should provide the right standards to avoid the creation of bad and buggy extensions and let developers do the rest. |
@tonydspaniard we'll support one of these bootstrapping frameworks. Most probably it will be Twitter's since Foundation dropped support of IEs except the very latest too soon. |
Yii2 should provide support for any CSS/UI framework and no framework or components should be tied to the core. |
It will not be tied. It will be bundled. |
Chris and I have nearly finished Yiistrap and Yiiwheels. We joined forces to improve its last library and also to stand up over YiiBooster, library that I no longer support, adding Yiiwheels to extend Yiistrap so to keep one and only library from Twitter Bootstrap's. @samdark @qiangxue maybe would you consider adding both as one library to Yii2? |
@tonydspaniard We can certainly consider adding them to Yii 2, provided that you are willing to modify the license terms to follow that of the existing Yii 2 code. Having said that, I think if we decide to move along this way, we need to agree on the design of the base classes first, and then modify the more concrete class implementations. Actually it will be almost like a rewrite. The main difference is that you have much more experience with these bootstrap widgets and probably have better idea than us on how to make them even better. Do you think this is fine with you? We may discuss further details in emails. |
@qiangxue I would love to participate actively with them. My only concern is that I worked with Chris and what we did is a rewrite of his Yii-bootstrap and he asked me to keep the copyright. Nevertheless, Yiistrap is a library built for Yii 1.1.+ and I do not see any issue in building a new that will comply with Yii2 expectations. I will ask Chris, as my ethics force me to do so, if he wishes to work with me in order to integrate Yiistrap + Yiiwheels into Yii2. Whatever his answer is, please count me in. |
Hello, I'm joining in a bit late but I just wanted to say that I'm open for discussion about developing similar functionality as Yiistrap for Yii2. I would love to participate. |
* upstream: Fixes issue yiisoft#320: Module::createController() will fail with a route with trailing slash. Fixed test break about AssetController. requirements css.php twitter bootstrap update to 2.3.2 Twitter bootstrap updated to 2.3.2 Modified the IAssetConvert interface. hashing the key for registerCss and registerJs. Update AccessRule.php refactored code after feedback Fixed framework path. Added support for View::POS_READY. new proposed structure remove from master (update track) made some changes, fix some pitfalls, remove PHP_EOL yiisoft#20 proposed architecture for bootstrap Conflicts: yii/helpers/base/Inflector.php
You use what version of Bootstrap ? v2.x or v3.x ? |
Shouldn't the |
I think it should. |
What's the drawback of keeping |
There are no drawbacks keeping it as official extension. |
There is:
|
|
Nope. The debug toolbar itself won't use any CSS framework. It is the debug module that will display standalone debug pages which will use bootstrap. Gii could be in either core or official extension. If it will be in the core, then that's another positive argument. Basically my argument is that if we have some core code that depends on a CSS framework to work well, then we should keep this CSS framework in the core. |
It's OK for me to keep bootstrap in the core as long as it's used for standalone modules only i.e. not conflicting with any user JS/CSS. As for |
I agree moving Regarding core vs. official extensions: the only advantage of using official extensions is that it makes the size of the core code smaller. Our situation is different from ZF2/SF2 since our extensions are not designed to be reused in other frameworks. |
In the toolbar composer.json:
Then they should be also released as separate extensions and require yii2-bootstrap. That would be much cleaner, IMHO. And if you want to release a complete archive the build process should take care of this. |
Why should we turn the debug toolbar into an extension? This will be used by almost all applications. Turning it into an extension means extra dependency for every application, and the only benefit is that it makes the size of the core code smaller. |
No need to decouple toolbar. It will be used in 99% developer's environments, I think. |
@creocoder is right definitely must be extension and not in the core. |
I'm actually starting to lean towards moving it to the official extensions. I haven't looked that much as Yii2 yet so I'm still getting to know the whole structure. |
@tonydspaniard what's left on this one except the decision to move it to an extension or not? |
Could support for Bootstrap 3 be added? |
@doliver3 we have bootstrap 3 already ;) |
<3 2013/10/22 Carsten Brandt [email protected]
|
Bootstrap support implemented. |
caching-http.md translated. [skip ci]
add runtime-logging.md
The extension contains a set of widgets implementing various features provided by Twitter Bootstrap.
The text was updated successfully, but these errors were encountered: