"Robert Wittams" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > So I think Dojo could do all of this, at the cost of adopting its heavy > widget framework. MochiKit could also do most of this with the addition > of Drag and Drop and some simple visual effects. I believe there are > efforts to create this functionality in a MochiKit style on the mochikit > mailing list, but as of yet, I have no idea if these things will be > included in MochiKit, as they seem to be derided as 'bling' as often as > possible.
Don't take me wrong but it's a problem with Mochikit as I see it: it's driven mostly by beauty of API and "let's make it like Python" attitude than by real life needs. I would be fired the first day I say to my clients "it's an IE bug, IE is a collection of bugs + a bunch of non-standard features, screw them!" but it is a common theme there. Another problem of almost all low-level toolkits is a design mismatch. Programmers tend to develop tools from the bottom solving some common low-level problems, while applications are formulated in terms of end user functionality. It means that you have to bridge the gap with a layer (layers). And in many cases you will see a mismatch between what's actually needed and what's actually available depending on how comprehensive the toolkit is and what applications have driven its creation. After years in business I was bruised a lot by this problem and now I prefer to start with a big picture. That's why I like seeing a widget/event framework instead of "ooh, look how neat is a creation of <a> element!". Thanks, Eugene
