I've been looking at web development tools such as Flex and as of recent, GWT.
So is this accomplished by routing through a different runtime library specific to the browser or simply adding the conditional scripting scratch to work around differences when compiled?
From my understanding of how GWT works, it takes the GWT Java code and "compiles" it into the JS equivalent page code. Or is there more to it?
Bear Bibeault wrote:it's a well-known and well-defined problem.
Maybe so, but wouldn't it be a better model to encapsulate such differences through the use of a runtime library (as does Flex) in the case that either browser related bugs arose and/or new functionality was added? In GWT and like models it would seem that a regeneration of JS against an upgraded sdk would be necessary and regression tests and other safeguards to insure reliable code. I'm not a huge Adobe fan by any means, but their approach makes more sense to me.
[SCBCD in process]
Yeah, but does being a ninja come with a dental plan? And what about this tiny ad?