> When thinking of regular pages you might be right but I wasn't making > up the example. This was one of the reasons why we had to switch > from a browser-based application to a local running one. In this > specific case a tree showing all possible segments and fields > of an EDIFACT IFTMIN (one of the most complex structures of EDIFACT) > lead to waiting times of many seconds per mouse-click when working > with a browser on a modern PC.
so, in this specific instance, being able to migrate - pretty much instantaneously and with zero code modifications from a [too-slow] browser-based environment to a [very-fast] desktop-based one would be a definite advantage, yes? especially given that 1) running compiled java instead of interpreted javascript would end up running much faster 2) webkit is _blindingly_ quick. that _would_ have saved your development team a great deal of time and money. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
