It would be a titanic effort to rebuild so many standars. And most of the big enterprises doesn't accept an app with push- comunications or corba or rmi. Security departments are very strict. And the new releases distribution problem has been mentioned. I think that something shoud be change, but the minimun one to reduce the effort.
GWT is a big step but before you have to deal with a bit of HTML and a lot of CSS. HTML+CSS has a lot of historical issues and was created thinking in an higienic paper model: you have a page width but you don't have a height. It's difficult to fit the panel to the screen (javascript, window resize events, ...) and the elements to a fixed height. And the elements are very basic: divs, tables, ... Things as usual menues and tab panels are a lot of javascript. HTML+CSS was not developped thinking in panels or to fit in a screen (specially the height). GWT is affected by this problems. If a panel is rendered as a TABLE you have to use table-styles but if it's rendered as a DIV you have other styles. And GWT has to generate code for each browser because CSS is not a strong standard followed by all browsers. The solution could be a new standard for browsers with layout-elements like DockPanels, VerticalPanels, ... that automatically fits all the window. And with some commons controls: tables (confortable tables like in swing), menuBar, trees, canvas, ... Years ago, if was really easy and fast to create apps that fills the app window and that resize automatically using nested DockPanels in Delphi, for example. And without coding, only using properties like align left, center, ... On Sep 24, 10:24 pm, ddyer <[email protected]> wrote: > I think this discussion is off the track. If you have a specific > application, for a specific class of customers, > by all means bypass the middle man. > > That's not what browsers and web protocols are intended for. Web > protocols and browsers were invented > to allow arbitrary content providers to easily provide rich content to > arbitrary users, and conversely for > users to accept content from unknown providers, with reasonable > assurance that it is safe to do so. > > Considering Java, Flash, and GWT as alternative engines for providing > untrusted desktop-like content; > it all comes down to different sets of tradeoffs among availability, > download/setup time, and capability. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
