(Sorry, didn't mean to ignore this... See below...) On 11/4/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
On Sat, November 4, 2006 5:29 pm, Martin Cooper wrote: > It's not a question of which one has the most widgets. Prototype, and > hence > script.aculo.us, is fragile, especially in a portlet environment, so we > cannot, in good conscience, encourage people to use that to build robust > enterprise-ready applications. Since Struts supports portlet development, > we > don't want to have to say "oh, but you shouldn't use our AJAX tags if > you're > building portlets". Many people are rather fond of Prototype, so I think it might be a good thing to explain why Martin calls it "fragile", for those that might not be aware...
<snip>Nice Explanation</snip>
I'm not sure why you say you can't write valid XHTML with Dojo; you can. > There are three ways of adding Dojo widgets to your apps. Yes, not all of > them will give you XHTML that will validate, but at least one of them > does. I think Angelo is clearly referring to the markup approach to widget creation... correct me if I'm wrong Martin, but isn't it in fact true that with that approach you cannot write valid XHTML because of widgetId, dojoType, etc? Of course your right, that's not the only way to use widgets... but you mentioned three ways... out of curiosity, what's the third, aside from markup and programmatic creation?
I was referring to the markup approach as well. There are 3 different ways that you can add Dojo widgets to your apps using markup. The one that most people know is along the lines of this: <div dojoType="foo" ... /> which, as has been pointed out, is not valid XHTML markup "in flight", although it results in a valid DOM on arrival. However, if you need to have XHTML markup that can be validated, you can also achieve exactly the same result by doing this: <div class="dojo-foo" ... /> Of course, you can add other CSS classes in there as you normally would. Alternatively, you can also use Dojo's own namespace to add your widgets, like this: <dojo:foo ... /> So, take your pick. There's a lot more to Dojo than meets the eye. -- Martin Cooper
And as for effects, they're getting better all the time. Have you tried > 0.4yet? Indeed... with Dojo, it's important to realize that it's still relatively early in its lifecycle... with each new versions comes pretty big improvements... I looked at it for the first time roughly a year or so ago, and it looked interesting, but very immature (I in fact wrote a warning because of this in my AJAX book)... note that this isn't just a quality of code concern, or a functionality concern, it also includes documentation, support, examples, etc... looking at it now though, you can see a really vast improvement compared to where it was just a short time ago... there's still things to not be thrilled with, but most people tend to agree that the pluses outweigh the minuses by a good margin at this point. > Martin Cooper Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
