On Jul 27, 10:41 am, "Edward K. Ream" <[email protected]> wrote: > Here's something that might be of interest to some Leo users, and > perhaps Leo itself.
>From the first few pages of the docs: >http://doc.fluidinfo.com/fluidDB/objects.html QQQ FluidDB is conceptually very simple: it holds a large number of objects, all of a single flexible kind, and it provides the means to create, modify, and retrieve these objects. A FluidDB object is just a collection of tags, usually with values. As with other tagging systems, tags have names, such as tim/opinion, but unlike most tag systems, tags can also and usually do have values, such as "very exciting". For now, think of an object as a container for tags. When objects are first created, they are completely empty. Each is assigned a unique identifier which can be used to carry out operations on it, such as adding or removing tags. There is no limit on the number of tags on an object. Any application or user may create new objects at any time, and use them for any purpose. QQQ Unique identifier function like Leo's gnx's. It would be easy to represent a Leo outline as a set of FluidDB objects: just assign leo_parent and leo_children tags to objects, for example. Thus, FluidDB could host any collections of Leo outlines. Or anything else :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
