new span database format

[tmays]

So, do you really want the info key on the root level of span? It should probably be included in the system key under span, with the other project keys. By the way, I'm not sure what your plan is for organizing those project keys in system, but we'll talk about that.

As for the info key, which is really a "projectinfo" key, I think we could easily include it in system. We should probably also condense the time and date format to not have all of those sous-keys... :)

[reno-]

• 1 for the datetime format… I guess we should have it in a condensed way…

About the info root-key, I agree that it should be in system.

What do you think about

system::span::project::name system::span::project::filename system::span::project::path system::span::project::creation system::span::project::lastopen system::span::project::appversion

I changed a bit the actual name in system::span::project:: from "name" to "filename". Like that, we will be able to change the name of a project without changing its filename.

PS : I re-used "appversion" and not "version" because I think about using version for the project's versionning in the future.

[tmays]

Excellent!

a couple details: I had changed "creation" to "created" (i.e. when the project was "created") and "lastopen" is actually "lastopened" (i.e. when the project was "last opened")

ok for name and file name. I agree totally.

But what about appname? isn't it good to know what app made the project?

[reno-]

ok for the modifications, I just named them from my memory…

why not appname, it could be nice, I tagg this issue as a todo to remember it