> You're only going to get a good answer if you state specifically what > you're trying to accomplish. If you just want a filterable table, it's > probably trivial to build one with just MochiKit. However, if it's > easier to do so with Dojo, then maybe you should just use Dojo. > > The goal really is to do the least amount work possible, and worry > about the consequences when they matter. Optimizations require very > specific information, and I don't really see enough here to make a > recommendation one way or the other.
Of course the goal is also to do that which allows less work overall down the line. In the case, I decided that was learning mochikit better, and just dug into the sortable code demo. I think understanding the guts of something minimal that is built elegantly will be more useful to me in the long run. It's really nice, well documented, and was a good way to get exposed to some of the nicer mochikit functional programming features I probably wouldn't have looked at on my own for ages. Kudos to you! Which begs the question, are any of these mochkit demos like that one included as TG widgets, or will they be? I haven't found that yet, but though I should check again here before turning it into a widget. Thanks Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
