That's an understandable viewpoint. Safari hasn't traditionally had very good support/implentation of some of the core JS api . (that is required to be ecma compliant at least). They have fixed this in more recent versions of safari but it's something the dojo dev's are still trying to support as much as possible.
The good news is that no one has to use the new JS features if they don't want to, and the ones that are used by default in some sections are all cross browser compliant. As for standardizations, I know a few companies/projects that might not agree with you; - IBM - Sun Microsystems - AOL - Every web based framework hosted on apache. (if I've missed knowing any then apologies, I'm speaking more to the core JSF/struts/webwork type frameworks) - Many other big wigs that would take too much time to hunt down and list.. The official list of supported browsers can be found here: http://dojo.jot.com/FAQ#Supported%20Browsers. I should also note that the dojo foundation/devs are in direct contact with the mozilla/IE teams to try and ensure more industry wide browser compatibility/improvements in general. That being said, I definitely don't want to ignore browser compatibility issues when they come up and will definitely react quickly to any bugs that are found. (as long as they are humanly reasonable, expecting <= ie 5.0support or any of the earlier safari versions probably isn't going to happen.) People really don't have too much to worry about as any of the more dynamic functionality is something people can choose to "opt in" for. Of course, since tapestry uses hivemind this is all a moot point. If you ~do~ want the dynamic features but would rather use something other than dojo then you have the choice of specifying your own "ResponseBuilder" configuration point. I've re-factored all of this logic and any of the existing javascript handling so that people can plug in their own handles and manage as much of this process as they would like. Choice is always a good thing :) As much as I love dojo I don't want to code myself (or the community) into a hole we can't get out of easily if it's decided to move to a different toolkit someday. Hope that helps :) If anyone would like more answers I can probably pull one of the dojo devs or the sun servlet spec lead people in to answer to things I can't. On 7/1/06, Aslak Grønflaten <[EMAIL PROTECTED]> wrote:
Hi, I'm having trouble with Dojo as well, and especially the fact that it's been chosen for 4.1. Of all the Tacos demos, only the tab component work in Safari (on the Mac). If it's not cross-platform, Dojo is really not a good toolkit to standardize on.... A --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
