Bob Something tells me the packer proposal might be very useful. To package GWT apps for offline Android execution, Android demands that various artifacts be placed in precise directories on disk before being packaged into an APK. Maybe Thomas can comment about how this would impact his GWT-in-the-Air library.
-Ray On Tue, Nov 11, 2008 at 11:09 AM, BobV <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 11, 2008 at 2:02 PM, Lex Spoon <[EMAIL PROTECTED]> wrote: >> One big question: why a separate packer step? My naive understanding >> is that the point of a linker is to decide where the various bits of >> compiler output will go on disk. Is there a reason to discontinue >> that? It sounds possibly quite confusing to have both packers and >> linkers that the user must choose. > > The idea of a packer is separable (the thing that actually writes bits > to disk), but not currently separate. I'm just calling it out as an > affirmation that we don't want to do this. > > -- > Bob Vawter > Google Web Toolkit Team > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
