if i release an official parser i think it would use those methods.
the whole point is to store your CSS in JSON and parse it with JS, the libraries used to do the parsing / assigning are kinda arbitrary.
60 karma · joined November 20, 2009
if i release an official parser i think it would use those methods.
the whole point is to store your CSS in JSON and parse it with JS, the libraries used to do the parsing / assigning are kinda arbitrary.
i'll agree with you that c++ is faster then jQuery....good day
you can try re-reading the comments on this thread but if you've never dealt with really rich javascript apps, i can see why this is hard to grasp.
2. if you cant separate your business logic from your views....you have bigger problems to deal with....
in my rich internet applications i will use traditional CSS for the initial "base" state of the application and then JSSS for all further states which are generated via JS (no page-reload)
this is intended for client-side templating and dynamically assigning CSS classes and properties at run-time.
:-)
Nothing like being able to execute arbitrary x86 code through the browser....