[development] Google Gears

[Scott Trudeau]

Theoretically, a way to "sync" Drupal site instances (Google Gears
aside) would be awesome.  Practically, it is a very hard problem to
solve since most Drupal sites are in constant flux "in the wild" and
therefor, once you "copy" a local version of the site and make
changes, you have two separate branches with many potential
opportunities for collision.  You can handle some sync collisions
intelligently but there will always be weird cases.  Also, I can't
even begin to imagine how much more effort it would take to build
modules that can handle a sync framework.

That said, if there were a reasonably reliable and functional tool for
"syncing up" two sites forked from the same parent copy, it could lay
a nice foundation for a better staged development process for large,
active sites.

Scott

On 5/31/07, Michelle Cox <mcox at charter.net> wrote:
> Actually, I would love the ability to have my site offline synched easily to
> my site online. There aren't a lot of hotspots in my town, especially at the
> places that have kiddie stuff to keep my son entertained. I made a local
> copy of my site, but it's a PITA to keep it updated so I usually don't
> bother. Something like what has been talked about here would be awesome. Not
> something I'm in a position to help create, though, so it's just a wish on
> my part.
>
> Michelle
>
>
> On 5/31/2007 7:16:58 AM, Robin Monks (robin at civicspacelabs.org) wrote:
> > The weird thing is, with the dawn of cheap broadband, and wifi-covered
> > cities, planes, trains and buses, noone is actually offline to enjoy this
> > now.
> >
> > Robin
> >
> > On 5/31/07, Victor Kane <victorkane at gmail.com> wrote:
> > >
> > > well, one possibility is php gtk, see http://gtk.php.net/  (there is a
> > > data persistence layer in gears)
> > > But I
> > wasn't speaking only of using Gears itself, but rather of the
> > > paradigm shift to rich clients, with offline support.
> > > On the one hand stuff like Apollo, on the other ... if we have Drupal on
> > > a
> > > stick, we can have Drupal on a rich client.
> > > The paradigm shift of web apps recycled as rich client apps can be seen
> > > on
> > > many fronts, for example in the world of light, agile J2EE, the Spring
> > > Framework has the Rich Client sub-project (see
> > > http://www.springframework.org/spring-rcp).
> > >
> > > Victor Kane
> > > http://awebfactory.com.ar
> > >
> > > On 5/31/07, adrian rossouw <adrian at bryght.com> wrote:
> > > >
> > > >
> > > > On 31 May 2007, at 11:05 AM, Victor Kane wrote:
> > > >
> > > > use case is manage content, prepare a new edition of a site all ready
> > > > to
> > > > synchronize with on line edition...
>
>