On Wed, 2014-04-23 at 16:08 -0400, Tristan Van Berkom wrote: > This is my prerogative and I can accept that it is not shared with the > maintainers of EDS, nevertheless I would still like to caution against > opening up the SQL tables owned by EBookSqlite to be shared with plugins > (it may take a little more time in the beginning to flesh out a well > defined interactive API that satisfies the needs of plugins, but this > will pay off in better long term stability, anyway this is my opinion).
I agree with you, plugins should not make assumptions about the content of sqlite database. This needs to be documented clearly. However, the goal is not to let plugins access the existing tables. Instead, the goal is to let plugins create their own custom tables and update them as part of the same transaction that EBookSqlite uses to update its own tables. Name clashes need to be avoided, but that is a minor issue. We might also want to add hooks for DB updates and locale changes. Does this address your concern? Bye, Patrick _______________________________________________ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
