Hi Steven,

It turns out there is already an issue open for this:

  http://code.google.com/p/gwt-google-apis/issues/detail?id=208

Be sure to 'star' it and add comments if you like.

On Fri, Feb 6, 2009 at 12:49 AM, Steven <steven.pul...@gmail.com> wrote:
>
> I noticed in the comiled code a lot of calls using: _IG_GetCachedUrl()
>
> that's excellent! and just the way I want it.
>
> However - that does then leave something to be desired when you are
> developing and making changes frequently.
>
> In those case it would be nice to have { refreshInterval: 0 } passed
> to the function.
>
> Ideally you would be able to set some sort of DEBUG_P = 1 flag in the
> file that control this behavior.
>
> Any suggestions?
>
> And if I may be so forward - if there isn't yet a straightforward
> solution - maybe this can be a request for future versions of the GWT
>
> On Feb 3, 1:48 pm, Steven <steven.pul...@gmail.com> wrote:
>> thanks for the info!  especially the note about -PRETTYoutput (I
>> should have thought of that!)
>>
>> On Feb 3, 5:41 am, Eric Ayers <zun...@google.com> wrote:
>>
>> > On Mon, Feb 2, 2009 at 9:40 PM, Steven <steven.pul...@gmail.com> wrote:
>>
>> > > I have a question regarding using the GWT to create gadgets for
>> > > iGoogle.
>>
>> > > I have 
>> > > seenhttp://code.google.com/docreader/#p=gwt-google-apis&s=gwt-google-apis...
>> > > which details how you can now use the legacy gadgets API with GWT to
>> > > create gadgets.
>>
>> > > I also noticed that the way the GWT seems to achieve cross browser
>> > > compatibility is to create multiple javascript files and dynamically
>> > > include the right ones.
>>
>> > > I am worried about the performance hit of hosting uncached files on my
>> > > webserver.
>>
>> > > My question is this: does the GWT cache requests to these javascript
>> > > files?
>>
>> > No, GWT doesn't actually cache them.  It routes the request for your
>> > compiled resources through a proxy which is supposed to cache them
>> > (for up to 1 hour, I believe)
>>
>> > > Historically my process has been to have the entiregadgetinline as
>> > > type "html" and where necessary only include external resources after
>> > > using a call to _IG_GetCachedUrl so that they are proxies by google.
>>
>> > > So to clarify, my question is: When GWT spans it's code across
>> > > multiple files does it use _IG_GetCachedUrl to cache the request of
>> > > external javascript - or if not does it at least do something to
>> > > ensure that the javascript will not be requested (from my webserver)
>> > > every time a user loads thegadget.
>>
>> > Turn onprettymode when you compile, and then look at the generated
>> > .gadget.xml file (add -stylePRETTYto the command line) and you'll
>> > see that this is exactly the strategy used in the compiledgadget.
>>
>> > > just curious because on of the things I love about the wholegadget
>> > > space is that it has let me develop interesting projects in a way that
>> > > doesn't put much load on my puny server.
>>
>> > There are things you need to watch out for.  Make sure you load your
>> > .css files through a <script> take in your module definition
>> > (.gwt.xml).  Also, images could be an issue, but you can translate the
>> > urls to images to go through the proxy with the same _IG_GetCachedUrl
>> > call manually, or you can use the new GadgetImage class (in the next
>> > public update, due out very shortly).
>>
>> > > thanks!
>>
>> > --
>> > Eric Z. Ayers - GWT Team - Atlanta, GA 
>> > USAhttp://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
-~----------~----~----~----~------~----~------~--~---

Reply via email to