Re: libseed-list Making libseed reentrant and some API cleanup modifications proposition

[Alexandre Mazari <amazari igalia com>]

Oh, and one last thing:

Current SeedEngine initialization rely on passing command line arguments
(mostly to set the debug mode). I am not sure this is the right place in
the stack, a boolean property of SeedEngine might be more apropriate.

Anyway, comments from both Seed devs and Seed library users apreciated !

Le lundi 28 mars 2011 à 10:10 +0200, Alexandre Mazari a écrit :
> Hi everyone,
> 
> One of the requirements for the WebKit integration and the
> Evince/poppler js work (PDF specification define a JS API usable within
> a document) is to be able to create multiple SeedEngines, one per
> page/document.
> 
> Seed currently uses a lot of global state in static constants (mostly in
> the importer), disallowing the creation of several engines without
> side-effects.
> 
> I'd like to work on encapsulating those globals per instance, but that
> might imply some API breakage. What do you think about it ?
> 
> In the longer term, we could also make SeedEngine and SeedImporter
> GObjects and using GError in the C API instead of the SeedException.
> 
> Also, the public API could be streamlined by making all the SeedValue
> related symbol private and exposing higher level methods.
> 
> Finally, SeedContext should be hidden to client code, passing around the
> SeedEngine instead.
> 
> What do you think ?
> 
> _______________________________________________
> libseed-list mailing list
> libseed-list gnome org
> http://mail.gnome.org/mailman/listinfo/libseed-list