Re: c++ linktypes

Martin Bayer <[email protected]>
Newsgroups gmane.comp.video.gephex.devel
Message-ID <[email protected]>
[Georg Seidel]:
> ~   * functions for binary serialization which must be implemented
> ~     (with them the core can save the state of the graph)
> 
> ~   * maybe make the ascii serialisation optional by moving them
> ~     into an "AsciiSerializableLink" subclass (images and audio
> ~     data maybe wont allow serialization to ascii)

I think a textual representation of all linktypes is necessary. We need 
a way to specify the initial value for all link types from the scheme 
scripting layer.

The binary serialization can be optional because the ascii serialization 
is also a binary one. Datatypes like audio and video should have simple 
and small textual representations for reasonable initial values like 
e.g. a black image and should provide additional optimized binary 
representation methods.


What do you think about a textual encoding scheme as s-expressions? This 
allows us a very simple integration in the highlevel scripting layer.

The first element in the list is the type identifier of the unit type 
and the other elements of the list represent the value.

Examples:

(color 0.5 0.1 0.4)
(number 3.74)
(position 0.1 0.7)
(string "text")
(image (1 1) ((color 0.0 0.0 0.0)))

Martin

_______________________________________________
gephex-devel mailing list
[email protected]
http://lists.gephex.org/mailman/listinfo/gephex-devel
signature.asc (application/pgp-signature, 256 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBqmZDCm3i57PRsbsRAlDWAKCbiFKJEUDY3RM8Em25Nt72bBO9HgCeKDil
DYiv+61otw/NDyeTD4/DCd0=
=d3fu
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.