as I said I did not really read it all as it was late and I was on my way to bed so appologies on the first part. As for the JS improvements anything to reduce load times and externalize the JS/CSS from the theme will be benifitial wether your code is used exactly or as something to base it off of is stil extremely benifital.
K'ay, appologies accepted.
hanakin wrote:Possibly a new RFC should be made for 3.2 to completely externalize all the JS/CSS within the theme via jquery. Probably do not need to worry about the already external files for now other than to insure not to break their functionality.
You mean... Not until the jQuery is loaded all js is blocked and stopped?
I think we should use jQuery only for the hard stuff. Like an appear/disappear with animation where the animation is something like a fade in or a fold. Hard stuff, you see... Another good use for jQuery is modal windows. Those "windows" (that are actually divs) that appear above everything else, with a tab(like) thingy. That is hard stuff and jQuery is good to work with that.
Example bad uses of jQuery are:
AJAX, simple appear and disappear (just changing the class will do), control CSS in any way (except if it's part of its animations), most string manipulations, scrolling (when there are no fancy algorithms here like easing), etc... When it's simple stuff, use the API.
hanakin wrote:Their are other features of the refered to software such as support for reading and rendering less and saas files as well as running the code through http://prefixr.com/ to fix or append all the correct vendor prefixes. Woild make creating and editing the themes alot simpler for authors exspecially if they do not have complete understanding of the CSS3 stuff
They have external access system!
We can use php's curl system to access their server and get the correct CSS with the browser prefixes.