Ok, scratch that idea then. I suppose it's not too plausible. My original intent for posting was lack of literature on writing cross- library javascript. Do you have any other techniques for that besides writing plain old javascript and my now dead idea of writing a compatibility layer?
The original issue I wanted to solve was when we are unable to use all our MooTools code and plugins because they conflict with another library. Is there no way to prevent that from happening? On Oct 15, 4:00 pm, "Iván N Paz" <[EMAIL PROTECTED]> wrote: > Personally, Im tackling on my spare time the "easy-ness" of some stuff > in jQuery (what really makes it popular among designers [which are not > supposed to be hi-tech people]) and bring it to mootools as an > abstraction layer on top of it..... > > If I find my code to be over 5K or 10K uncompressed, I will give > up.... no use in trying to BLOAT smth, just for the sake of it.... > > I will be focusing mainly on bringing mootools to non-tech-savy > people... more friendly to newbies (no one feels offended plz, Im newb > to mootools myself!!!) which will use that layer first, and then get > rid of it and go on tackling more difficult stuff such as their own > classes, implement, extend, etc... > > All that, after I give my last touches to the bezier stuff that I > havent finished it to make it production-state yet.. :-P
