I created an issue for the filtering problem: http://code.google.com/p/gwt-google-apis/issues/detail?id=280
Feel free to come over to the gwt-google-apis group and discuss a proposal for other changes to the gadget API that might help with the app you are building. -Eric. On Thu, Jun 11, 2009 at 9:56 AM, Thibault Pouget<tpou...@gmail.com> wrote: > It would be great :) ! > I was saying at the end of my previous message that I still could get my > local server to serve and I think I found why. > I am also using GXT which needs its image folder to be in the war one. And > looking at the generated manifest, it seems that files outside the > "projectname" folder are not included in the list. > So I am trying to do my own manifest by hand and to download all needed > files including specific css and images. > And I was thinking that some convenient methods to manually build the > manifest would be awesome. For example, directly including an entire > folder... I am going to try and write these. But for now I 'd like to get my > local serve do what he is intended to. :) > By the way, thanks for the quick reply. > > 2009/6/11 Eric Ayers <zun...@google.com> >> >> My thought on this is that we should modify the manifest generator to >> filter out these files, and also add a config option to allow users to >> specify files to exclude in case something else like this comes up - >> maybe through (yet another) annotation on the Gadget class? >> >> On Thu, Jun 11, 2009 at 5:19 AM, Tibo<tpou...@gmail.com> wrote: >> > >> > Hello, >> > >> > I am currently developping an app using both GWT and GAE. I'd like >> > this app to use Gears mostly to used offline and also to improve >> > performance. >> > >> > Taking first steps with gwt-gears API I found quite convenient to have >> > an automatically generated manifest for files needed to be downloaded. >> > >> > However I am using RPC and the Gears manifest generation includes the >> > gwt.rpc files to the list of files to download. Unless I missed >> > something, these files are useless to Gears localserver and over all >> > the default configuration of App Engine doesn't allow to serve gwt.rpc >> > files which results in a HTTP 404 error when trying to download them. >> > >> > I would like to know what solution could be found. >> > >> > I tried to let the rpc files being served which allowed Gears to >> > dowload all the files listed in the manifest but I guess this would be >> > quite unsecure to let this that way. >> > >> > Could we change the folder where the rpc files are generated ? >> > >> > I guess it is possible to make the manifest file manually but it seems >> > to me it goes against a certain spirit of convenience GWT brought to >> > me. >> > >> > Note that even with all files donwloaded I still have trouble in >> > having my local server being able to serve. But this will be for >> > later. >> > >> > Thanks for your interest. :) >> > >> > > >> > >> >> >> >> -- >> Eric Z. Ayers - GWT Team - Atlanta, GA USA >> http://code.google.com/webtoolkit/ >> >> > > > > > -- Eric Z. Ayers - GWT Team - Atlanta, GA USA http://code.google.com/webtoolkit/ --~--~---------~--~----~------------~-------~--~----~ 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-Toolkit@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 -~----------~----~----~----~------~----~------~--~---
