Hi Ian,
My example is not a nebulous hyper-pathelogical theoretical case meant to stymie the group and prove something about GWT. It is the real world environment/problem that I have in front of me - almost exactly as I have described (although, actually more pathological than I have indicated IMO, this is the crux). So given all of these things I have no control over, I think to myself "You know... Given the problem, it seems somehow contrary to GWT's whole notion to me. Maybe GWT just wouldn't be the right tool for this kind of thing - OR - perhaps I'm missing something... Let's ask the GWT list - more specifically the GWT team - and see what they think. They ought to know." Anyway, I think I've gotten my answer a few times over now - but thanks :) BTW - I'm not sure which part of my posts have made it sound like I don't understand GWT. Is it just the title? The nature of the question? Ironic if so given the above. I kind of feel like I understand it pretty well - this isn't the first time I'm seeing it or anything, in fact, it's what I know about GWT that makes me question whether it's the right tool for this problem in the first place. On Dec 16, 12:44 pm, Ian Bambury <ianbamb...@gmail.com> wrote: > Hi bkardell, > > I think the simple answer is that in extreme cases such as the one you cite, > GWT is not a good fit. > > The easiest response is to ask you to give it a bit of time and wait until > you understand what GWT is before you ask these questions :-) > > But quickly: > > * GWT came into being in order to make JavaScript easier to write by > allowing you to write in Java instead and therefore be able to use all the > tools that are available to Java developers. > > * Obviously this means come sort of conversion from the Java-syntax plain > text into a JavaScript script > > * In doing so, the Google chaps went a bit beresk in trying to optimise the > code produced. And well done them, they have done a fantastic job at it. > > * One of the aims was to produce a monolith that could be uploaded (at a > time-price) initially, but thereafter would be, like a desktop app, already > on the client's machine and only gets re-uploaded if it changes (i.e. an > update) > > * Due to the take-up of GWT and the scale of projects people tried to > produce (e.g. a corporate web site in one .js file) code splitting was added > so that not all the code (pages, whatever) was uploaded unless needed. > > Basically, though, GWT is aimed at creating a one-page (as in HTML) web > site, not at producing little live-alone gadgets to stick into an existing > page. > > I don't think there will, in the near future, be any way to allow tens of > GWT gadgets to access core GWT functionality via a DLL-like common library. > For one thing, my tiny 25kb (currently) gadget, on first use, if it were the > first gadget to be used (and maybe the only one, too) would have to download > a library with code for every single thing that GWT can do, including all > deprecated, outdated and weird widgets. The overhead is pointless. > > On the other hand, ten 30k (before compression) widgets is nothing these > days with internet speeds being what they are (and what they will be soon). > > So yep, if you have a hundred medium to large sized gadgets that get updated > on a daily basis, GWT is probably not for you unless you write some kind of > gadget-framework in GWT and use some kind of meta-code to control it. > > You are very good at coming up with corner cases of a theoretical nature. > May I humbly suggest that you tell us what you are actually trying to do so > that the people in this community can address a concrete problem you have > rather than 'yes but what if...' scenarios. > > Specific is good :-) > > Ian -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
