Heya Fellahs,
To store plugin settings, and also as a backend for the lvavs preset
storage. I'd like to introduce a subsystem that is capable of
serializing VisParamEntries, and for what it matters. Complete
VisParamContainers.
I'd like to discuss about the following:
Where do we store our param registry ? "~/.libvisual/settings" ?
And what kind of format do we want.
We can go for a binair format, which obviously is fast, and
easy to implement. Also using a binair system (and some
hacking) we can easily serialize and deserialize objects.
We could have a 'serialize, deserialize' method in VisObjects.
that supports (de)serialization from binair data, that is. When
the interface is implemented for the object. This could be nice
with VisPalette, VisColor and the such. Of course we should
be careful with not bloating our object system, But I think
the (de)serialize optional interface on VisObject, to (de)serialize
objects is quite a legal thing to do.
I personally favor the following:
A binair file in "~/.libvisual/settings". What do you
people thing ?
Cheers,
Dennis
|
