danialt wrote:
I will try to reduce the JS things here and there in the component. This can be done with a better design that current one (designers are welcome), so we wouldn't need slideDown/Up animations, ...
jQuery by nature is not the trouble (and i think with the latest version there is no conflict with mootools). It is poor programming of other templates, even JS libraries that causes it. Though, if it is really needed i will use it.
I understand that. A jQuery to Mootools conversion is more work than you can ask anybody to do for free, but less JS errors, or less use of jQuery is a great step forward.
And I agree that template designers that don't ensure that their template's work in popular components that uses jQuery (like FB and like) shouldn't do JS in the first place (RT and YT, I'm looking at you). I'm not saying FM should be completely Mootools compliant, but when something is going to be redone anyways, why not do your best? That's my theory on why you take your time on FM. I for one never release anything that I know have bugs.
Good luck with it, I would love to help, but my schedule for the 2 months ahead are completely booked as we are busy setting up our new sites (namely NinjaTheme, NinjaForge and like) but if you still haven't released it by the time I have time on my hands I'll do my best to help you
