When the user wants to save the data (snapshot), Clouseau requests from
every running extension the data that is "exported".
All the data are then encapsulated into one single file.
The first idea was to use EET to store the extensions blobs as basic var
arrays. But it was taking so much time that is has been chosen that the
data itself is appended in the file after the EET blob. This one only
contains the app name/pid and the number of bytes of the blob, per
extension.
Additionnally, the objects introspection extension has been modified to
behave as the first Clouseau, i.e taking all the objects information in
one shot and using it during the interaction with the user.
The Save/Load button is now a part of the main toolbar.
It has been removed when the extentions feature has been introduced.
Now, when -f is used in the command line, a list of extensions is
displayed to request the user to choose the extension that needs to
handle this file.
The objects introspection, that has always been as a core part, is now
an extension, and can be not used.
The directories structure allows other extensions to be developed inside
the Clouseau tree, even if they can be developed outside.
Other extensions will be added and the extensions feature will be
adapted to fit all their requirements.
This wasn't really a public header. It exposed a lot of stuff it shouldn't have and it was just confusing.
We'll just create a public header when we'll be ready, i.e know
exactly what we need to expose.
SVN revision: 83492
The Clouseau client is compatible with old Clouseau applications
supporting EcoreConnEet.
Signed-off-by: Aharon Hillel <a.hillel@samsung.com>
SVN revision: 83412
Daniel Zaoui
Jérémy Zurcher
Tom Hacohen
Aharon Hillel
Daniel Zaoui
Cedric BAIL