-
Notifications
You must be signed in to change notification settings - Fork 113
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
Upgrade to bootstrap 3.0 #4
Comments
Yup, I'll translate it to stylus as soon as its officially out. |
Sweet! Looking forward to it. |
Nice work, I also hope to see the upgrade to stylus :) |
👍 |
A heads up, v3 is moving from CSS reset to normalize.css. I've ported it here, I was porting v3 sometime ago but am moving towards styl and rework instead. Also you will encounter some problems in media queries as stylus does not currently support variables as arguments in media queries (which there is a lot of in v3), there's offcourse a lot of really messy workarounds. |
Thanks for the heads up, do you have any pointers fr the workarounds for supporting the variables in the media queries? |
Sort-off, there's a few workarounds that you can find by browsing issues (which I have attached to this comment) in the Stylus repo. The solution I had was creating a media mixin, however I wasn't really happy with it. My solution
Which can be used like this:
Besides the problem with @media queries Stylus is limited in that you can't write mixins as selectors, I had envisioned something like this:
Relevant Stylus issues:
Final ThoughtsThese issues have been open for a while and the pull requests have largely been ignored. I can only guess that the reason is that TJHolowaychuk is too busy and is more interested in developing Styl and Rework. Being somewhat of a hipster, I decided to abandon my stylus port of v3 to stylus and work on styl/rework projects (plugins and libraries). |
BS 3 is out. |
Very interesting, will try soon |
Where are we on 3.0? Looking to upgrade. |
I'll be back from vacation on August 8th so in the following days. On 2013-08-01, at 15:49, abrkn notifications@github.com wrote:
|
I'll wait a bit for final release before making a translation seeing how the current release seems to be constantly updated. |
Thanks maxmx, can't wait to try it out. |
Will new version make use of nib methods or it will use custom (mixins) functions? |
Allright release candidates are done, expect v3 in a few days. |
I'll try to make it nib-dependent |
Great news ! Thank you |
I'm working on a project that really needs BS3, but it uses stylus. Could you publish your progress with the port in a separate branch so I could pull from it (and maybe contribute)? |
+1 for branch updates, if your lazy just add -A changes. Btw I'm working on a less to stylus 'parser', it uses the less CSS parser if anyone's interested is using or contributing. |
Ssup dudes, I released it, I'm sure there are still some bugs left, but I ran the compiled css on the documentation site and everything looked good so far. Also, I kept the mixins in instead of using nib, it was the easiest way to release this as fast as possible. Please contribute if you find anything. |
@maxmx Could you please tag the release so that bower can resolve the new version? |
@liqweed Done! |
Works! |
Everything fine on our end. Thanks ! I just had a max call stack error in the mixins scale(ratio) {
-webkit-transform: scale(ratio);
-ms-transform: scale(ratio); // IE9+
transform: scale(ratio);
} Guess it'll be the same for rotate and other as well ? |
Right, its probably not used in bootstrap but you used it somewhere, I'll fix these soon. |
@maxmx np, thanks for the heads up. btw, I had a problem importing Bootstrap's theme.styl - would this by any chance address that? |
Yes i gave some love to the overlooked theme.styl file and even gave it a separate build using grunt. On 2013-08-29, at 7:15, liqweed notifications@github.com wrote:
|
Do you have any plans to upgrade to bootstrap 3.0 when it comes out? The rc has been out for a while, and I'm just curious if I can stick to your project.
The text was updated successfully, but these errors were encountered: