On May 19, 2006, at 12:10 PM, Jose R wrote:
> I just want to add that this is my opinion as a begginner in this > javascript framework stuff, and as a begginner i can (and certainly i > am) wrong in some areas as in the visual effects... i dont know > what is > the "trunk", what does it mean. > its my desire to let others to choose the best one, i think prototype > is also a good choice. It's definitely my desire that people choose the best toolkit for the job, which is why MochiKit goes pretty far out of its way to ensure interoperability. Using another toolkit doesn't mean you can't also use MochiKit (or vice versa). As for trunk, that's Subversion terminology. The trunk is where development is currently taking place, which implies a certain level of incompleteness and instability. The equivalent CVS terminology would be the HEAD, and others call it top of tree. MochiKit doesn't currently have the features you're looking for and the target audience is more or less expected to have a fair amount of programming experience with something similar like Python, at least to the point where they can read and understand the reference documentation. Prototype with Scriptaculous does what you've said you wanted to do, and it does it now. There are most definitely downsides to that stack, but practically speaking it's probably the best choice for you at the moment. -bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
