> So independent of the fact that you might not be able to imagine > reasons, it doesn't mean that there aren't any ;-) >
Oh no, I wasn't suggesting that at all - quite the opposite. It's precisely because I *don't* have the imagination that I need help :-) For example, if you are writing applications where browsers are forbidden, then why would you write it as a browser-based application and then convert to a desktop app and never use the browser version? And if you have a PIM, then surely there's a better way of presenting things than putting the whole darn lot in one tree - you can't *see* the whole tree in one go, so what is the point? And if you *do* have to, then as above, what is the point of building it as a browser-based app, converting it, and not being able to use the browser version? Ian http://examples.roughian.com 2008/10/28 Lothar Kimmeringer <[EMAIL PROTECTED]> > > Ian Bambury schrieb: > > > I can't actually think of a single situation where I myself would design > > a web app (or even a desktop app) with 10,000+ tree nodes open at the > > same time, and I don't think I've ever come across one while surfing the > > web, but if I'm ever forced to build one that the general public might > > stumble across, before Firefox fixes its bug, then I now know there is a > > solution :-) > > 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. > > When developing team-enabled B2B-applications you very often run > into this specific kind of problem. Another example is PIM where > product-informations should be presented in a structured way. This > tree can become much bigger than the one described above and even > if you only show the nodes that are actually used, this will very > soon exceed the 10.000-number e.g. when creating a catalog with > thousand pages. > > There are other reasons why you want a local installation instead > of a browser-based, e.g. OSI-levels 8 and 9 (politics and religion), > where browsers are forbidden by company-regulations, etc. > > So independent of the fact that you might not be able to imagine > reasons, it doesn't mean that there aren't any ;-) > > > Regards, Lothar > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
