hello Артём, thank you very much for your input! i kept on thinking about the idea. i had to realise that even if one could compile the plugin code (java) to javascript the _real_ problem still remains:
- how can you load this plugin code at runtime? - what are the implications on the development process (i.e. the way plugins are developed/tested) when plugins are loaded dynamically? - what must (not) be part of the plugin javascript source (e.g. to avoid doing gwt initialisation twice (?))? i think there are two ways to build an appstore-ish application using gwt: (1) static plugins: plugins are part of the codebase i.e. they are already "installed". thus they are already part of the platform and users might (in-)activate them using the application itself. for more details about my idea see http://code.google.com/p/honeycrm/wiki/PluginsStaticApproach. (2) dynamic plugins: everyone can potentially create plugin files and publish them somewhere on the net. users will upload them to the (plugin-aware) application. this has to extract the plugin, put the js source into the database and perhaps has to update the configuration. from my point of view (1) is the preferred way of doing it because of the simplicity of a potential implementation. for some sample code see http://honeycrm.googlecode.com/svn/branches/PlatformTest/. (1) simplifies a lot of things - especially the live of the plugin developer. how should plugins be developed and _extracted_ from the development system (for publishing them)? if you want to create external repositories where people can download plugins, they have to be self- contained. how could this be achieved for (2)? however, the most important thing i would like to discuss is: what you think about (1) static plugins http://code.google.com/p/honeycrm/wiki/PluginsStaticApproach kind regards, ingo On 10 Okt., 10:14, Артём <artem...@gmail.com> wrote: > The first problem I see is that the GWT compiler calls System.exit, > therefore you can't easily call it's "main" function from your > program. And you can't execute it as an external program via a command- > line either. I suppose you'll have to use a modified version of GWT to > do that. Then there's the question of GWT compiler execution time: it > usually takes 25-35 seconds to run GWT on my hardware, I doubt > AppEngine will allow the request to run this long. > > On Oct 4, 5:51 pm, Ingo Jaeckel <ingo.jaec...@googlemail.com> wrote: > > > hello everyone, > > > i want to build an app store for a GWT application. users should open > > the app store from within the application, browse through apps and > > install them like they are used to it from other app stores e.g. apple > > app store or android market. i outlined my ideas about it in the wiki > > of my projecthttp://code.google.com/p/honeycrm/wiki/Plugins > > (including a more detailed description of the store, apps and sequence > > diagrams of the installation process). > > > - has something like this been done before? > > - are there any best practices on this topic? > > - is it realistically i.e. a good idea to put source code into the > > plugin package (e.g. a zip file) and do the transformations > > (compilation of .java -> .class using javac and .java -> .js using > > GWTs compiler)? > > seehttp://code.google.com/p/honeycrm/wiki/Plugins#installation_of_plugins > > - can i do this within google app engine or do i have to use another > > servlet container e.g. for compilation. > > > kind regards, > > ingo > > -- 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.
