Depending on what you use for development you could look at using an app like cyberduck for mac or on Linux there's the fish protocol in KDE and Gnome has a way to mount directories over ssh or ftp. I think Filezilla might get some similar functionality (noticing when files change and uploading) on Windows. Any of these methods get close to a local server. It's almost the same problem as general web development except that gadgets always have to be served on the web during development.
Rob Russell Google Developer Relations On Tue, May 4, 2010 at 9:13 PM, Marcelo de Moraes Serpa <[email protected] > wrote: > Thanks for the useful information Rob ;) > > I ended up publishing the gadget through a virtualhost on my local machine > and setting up iGoogle with caching disabled. Works, although a local server > would be faster. > > Cheers, > > Marcelo. > > On Tue, May 4, 2010 at 5:27 PM, Rob Russell <[email protected]> wrote: > >> Hi Marcelo, >> GGE is meant to be a quick way to get started. More experienced developers >> generally come up with their own workflow, as it sounds like you've started >> to. We're definitely interested in how people do version control and >> improving the workflow for developers as they get more experience with good >> software development practices. >> >> For your immediate problem, caching, add the developer gadget at >> http://www.google.com/ig/adde?moduleurl=www.google.com/ig/modules/developer.xml. >> This gadget allows you to quickly add and remove other gadgets. It also >> lets you turn off caching so you can refresh the page and see changes >> immediately. >> >> Personally, I use a mercurial repository for a lot of my testing gadgets. >> It's light-weight and gives easy access to the latest version through the >> /raw-file/tip/ path.Subversion allows similar development. Both are >> available through Google Code as long as your project fits in one of the >> Open Source licences they support. I haven't tried github but that might >> also be an option. Of course you can also run your own server. I don't think >> a version control system is a good host for a gadget in the long term but it >> can be a helpful part of the workflow (and of course version control is >> important independent of deployment). >> >> >> Rob Russell >> Google Developer Relations >> >> >> >> On Tue, May 4, 2010 at 3:09 PM, Marcelo de Moraes Serpa < >> [email protected]> wrote: >> >>> Hello list, >>> >>> I'm brand new to Gadgets development, and, while I've found the >>> documentation pretty good at boostrapping one into getting a gadget up >>> and running, I didn't find any references on how to setup a >>> development enviroment for gadgets. >>> >>> What do I mean? >>> >>> Well, I noticed that using the online editor can be good for simple >>> gadgets (and or for the experienced iterationless gadget developer), >>> but using it brings several limitations IMO: >>> * You can't version control the file(s); >>> * Publishing it manually everytime is a pain. >>> >>> What I did was to publish my gadget directory under subdomain of mine. >>> Then, I published this URL as a gadget on iGoogle. So far, so good. I >>> then came back to good old emacs, hacked in some gadget-XML and came >>> back to Firefox, pressed F5 and... still the old gadget. Tried several >>> times and also on other browsers and got the same result. >>> >>> Now, I would definetly expect at least an iGoogle developer mode, >>> where gadgets are reloaded on refresh. Am I missing something? >>> >>> The best, though, and I would leave it as a suggestion for future >>> releases, would be to have a local google gadget toolchain to test >>> them without the need to be connected to the internet. Much faster. >>> >>> Thanks in advance, >>> >>> Marcelo. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "iGoogle Developer Forum" group. >>> To post to this group, send email to [email protected] >>> . >>> To unsubscribe from this group, send email to >>> [email protected]<google-gadgets-api%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/Google-Gadgets-API?hl=en. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "iGoogle Developer Forum" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-gadgets-api%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/Google-Gadgets-API?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "iGoogle Developer Forum" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-gadgets-api%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/Google-Gadgets-API?hl=en. > -- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
