garden synch

[mwest]

I'd like the dictionary and atlas to be the same type of application as this. can you explain the differences in 1) this app and 2) an app that wants to synch with it...like how the replication works and how it hooks into the dashboard. i also think the dashboard should be called the name of the garden, since that is how users will prob best think of it.

[ryanramage]

Ok here goes:

The idea is your are off-loading a very common thing (in this case tag management) into a central app. So any app that wants to use the common tags would import a common kanso package, and then most of the tag work would be done for them.

There is currently a feature missing in this app, which is when you click on a tag, you should be able to see links to all the places in the apps that that tag is used.

How it works is that each tag is a document, they look like:

{ "_id": "1ed5d7d31b32ecbd3558bd955c011fbe", "_rev": "1-1c6a72d943954f7a07014b87463b40c2", "type": "garden.tag", "name": "idea", "hash": "idea", "description": "An idea" }

And then these get replicated (and now from) all the app dbs. If anyone creates a new tag, they would just mimic this, and it would come back into the tags db.

This has the cost of each app having extra size, but the advantage is that then the apps are independent, and can run offline, or on another server.

[mwest]

thanks,

so it's 2-way sync (an app that uses garden-tags needs only to add a "type": "garden.tag" doc and it will push across all garden-tags enabled app on that server)?

prob smart to add "uri": "value" to keep garden-tag docs somewhat lightweight (in the case of the atlas i am thinking limit places to point and/or bbox) and point to the master app doc (w/ compex polygons, additional names, audio, translations, etc. that may or may not be locally avail.)

...also phones can grab just the synch docs and ignore the full docs.