[gephex-devel] serialisation in gephex-0.5

[Georg Seidel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Some more thoughts how to handle link serialisation in 0.5...

We already talked about removing the (de)serialisation functions in the 
link interface.
Instead we wanted to add (de)serialisation units, which take an osc 
value as input
and write into a link (or the other way round).

A problem that came up was the following: Imagine a serialisation unit 
has mor input ports
(e.g. image serialisation has parameters for quality level and 
resolution of serialised frame).
Then a link has to be attached to each of these input ports, which in 
turn needs a serialization
unit to set its initial value, which in turn need links for inputs, 
which in turn...

I propose the following solution to this recursive serialisation unit 
problem:

  * (de)serialisation modules must only have one input and one output 
port
    (osc + the type to (de)serialise)

  * additional parameters (quality, etc) can be set by a mechanism 
similar to that
    proposed by martin for generic link types (lists, arrays, etc)
   Think of it like int template parameters in C++

An open issue is the serialisation of osc links themselves...

Comments?

Regards,

Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)

iD8DBQFCQ9qf/rP0cdKF/ToRAjsUAKCxCZkJ4WirjnMQCiyTn7o93idWwQCeJWMr
E+wup214fUSyjbPjsXtm0CY=
=h55/
-----END PGP SIGNATURE-----