Thanks, I am trying to get to grips with the database business. The
first thing I noticed was: "Data is stored using the same-origin
security policy, meaning that a web application cannot access data
outside of its domain." So I guess it may not be appropriate after
all, because ...
In layman's terms what I want is for the user to store his data on his
hard disk; some of this data is pointers to other data stored
remotely. For example, a designer selects a table; he stores only the
source (supplier's link) of the table and the position he determined;
the product source supplies a 3D component model (say, a link to a
Sketchup file) and name/value datasheet. Designer's reports including
2d & 3d model assemblies, costs, time and so forth, are generated from
both local and remote sources.
Your advice would be most appreciated.
Chris
On Mar 13, 4:39 am, Brad Neuberg <
bradneub...@google.com> wrote:
> Hi Chris, you should be able to use the Gears Database to store your
> name/value pairs. Just create a SQL table with appropriate columns, and
> write each name/value pair as a row in the column. You can do all of this
> with JavaScript, and the data will be persistent. Do you have a server as
> well? If so, then you will need to do data syncing. Details on the Gears
> Database API here:
>
>
http://code.google.com/apis/gears/api_database.html
>
> Best,
> Brad
>
>
bradneub...@google.com
>
> On Mon, Mar 9, 2009 at 8:57 PM, chrisglasier <
chrisglas...@gmail.com> wrote:
>
> > I am working on a project called "Namesets" which uses html for user
> > interaction, javascript for automation and structured words for
> > content. These three work together as a digital machine to produce an
> > array of names, each representing an entity in the physical world.
> > Each entity also has an array of name/value pairs that identify its
> > physical, financial and temporal parameters. Currently I convert these
> > arrays into comma separated strings and write them to a browser
> > window, from where they are copied/pasted into a text file for reuse.
> > These records belong to the client and are stored locally.
>
> > I learnt sufficient html + Javascript to make this work. I also picked
> > up parts of the Ruby API so that I could have it interact with
> > Google's Sketchup. So I was wondering if I could do something similar
> > with Google's Gears.
>
> > The first question of course is whether Gears is really applicable to
> > the data storage I have described. There is a 3.5min video clip
> > introducing Namesets athttp://
sites.google.com/site/namesets/,