> Gears provides a ton of useful pieces [snip]
> [We want to] create our own new install of Gears that
> contains the additional UltraLite Gear. And, as you requested, we
> would like to work with you to make sure the installs "don't clobber
> each other in the wild".
>
> So as a starting point for discussion, from your perspective, what
> things will we need to change to ensure they can co-exist?
I can think of two possible paths:
(1) Use Gears technology to create plugin that exposes (only) the
UltraLite DB, with a Gears-compatible interface.
(2) Create and distribute a parallel "iAnywhere Gears" distribution.
Have you thought of which you want to pursue?
In both cases, you'll need to do some things to prevent "iAnywhere
Gears" from colliding with the "Google Gears" distribution.
* Split PRODUCT_FRIENDLY_NAME ("Google Gears")
into PRODUCT_VENDOR ("Google" / "iAnywhere")
and PRODUCT_FRIENDLY_NAME ("Gears").
* Change any hard-coded "Google" strings to PRODUCT_VENDOR.
* Check places in the code marked "[naming]" and update those.
* Update GUIDs to avoid conflicts. (Maybe all GUIDs??)
There are probably more things that need to be changed, but this
should be a good start toward letting "google.gears.factory" and
"ianywhere.gears.factory" coexist.
--Chris
