Categories: Elastic
Why so often and why so little increment?
Well in he process of releasing 2.0 we considered the possibility to support calculations based on percentages, but It was dropped, because we believed that it was not necessary, but well it turns out that it is important, and that the current algorithm was not enough, some rounding problems arise mainly it comes from the width reported by the browsers, and the rounding that result from that.
So to not make a long story, this release tries to solve that, as an experiment, maybe its usefull, maybe not we will see.
basically there are no nesting rules, you can nest almost anything. the general usage is this
columns > column
columns > container > column
columns > container > column > container
that is the idea nest at your will
you can check the Elastic 2.0 RC Release http://elasticss.com/releasing-v20-rc/
let me know if that helped
Just started using ElasticSS on portalZINE TV. Love it, still a bit slow when calculating the column sizes on IE.
But as I am a jquery programmer myself, this fits right into my concept
Cheers
Alexander
Any reason why you bind elastic on load and not trigger it when the dom is ready ? Swiched from load to dom ready.
Cheers
Alexander
basically due to a problem on the ready event on safari 4.0 final, it seems to dispatch the ready event twice canceling the previous event, this causes the elastic engine to stop processing
Thanks for your comments on the framework, cool site you have, and good use of the framework, thanks a lot for letting us know about it
Ok, yes heard about the safari problem. I will add an exception for it, allowing the rest of the browsers to use the dom ready event
really good css framework, but really poor document.
No concept explanation for unit, columns and nesting rules, user can hardly learn all the features from the code snippets.
Please enhance that ASAP, or else the google group will see no question askers any more…