Re: WOComponent children
Re: WOComponent children
- Subject: Re: WOComponent children
- From: Mike Schrag <email@hidden>
- Date: Wed, 16 Jan 2008 19:08:54 -0500
I've heard of scriptaculous :-) In plain text scriptaculous.js has the following comment:
"inserting via DOM fails in Safari 2.0, so brute force approach" That comment is saying that direct dom manipulation (via the dom _API_) does not work in Safari, which is why they don't use it and instead the next line after the comment you're quoting is:
document.write('<script type="text/_javascript_" src=""color: #000000">+libraryName+'"></script>');
... which DOES work.
All I'm saying is that while I agree that your proposed DOM manipulation solution is the best given the current architecture of WO, it is still working around a flaw in the base architecture. Also, the DOM manipulation should be tested on a range of browsers and implemented carefully. It will probably work on most of them in the end... but why can't we just do it the right way, by stating the requried resources between the head tags on initial page load?
I'm completely a fan of doing things "the right way," but what you're proposing just isn't right. It doesn't work, and you can't make it work. It's not enough to say "it seems to work on everything but WOSwitchComponent". WOSwitchComponent is a _really_ important component. You are completely ignoring Direct2Web here, which it would not work on, as well as components that dynamically generate their choice of _javascript_ file in code instead of statically generating it. This is not a flaw in the WO base architecture -- you're just asking WO to do something that is impossible. In parting, I hope you do get that DOM manipulation working and we can all benefit from it. I really do believe that dynamic loading is the only way to make this work properly in all cases ... Scriptaculous is basically already doing this, and it is tested on all the browsers that matter. I know we have tested on IE 6, IE 7, Opera, Safari 1 (I did this just now -- wow Safari 3 is SOOo much faster), Safari 2, Safari 3, FireFox 1.5, FireFox 2 -- I don't recall if we tested on IE 5, but I /think/ so. This is not to say there won't be some wackiness we have to work out, but Wonder's all about secret wacky ugliness that you're not supposed to see.
ms |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden