Many thanks for your comments
Petr
--
You received this message because you are subscribed to the Google Groups "zotero-dev" group.
To post to this group, send email to zoter...@googlegroups.com.
To unsubscribe from this group, send email to zotero-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/zotero-dev?hl=en.
Another option is to communicate via MozRepl, which will give you
access to the Zotero JavaScript object and methods. This amounts to an
additional dependency, but it should work fine and not run into
locking issues. For an example of using MozRepl with emacs, see:
http://people.internetconnection.net/2009/02/interactive-html-development-in-emacs/
.
I haven't used MozRepl for more than exploring the JavaScript innards
of Zotero, but this should be feasible.
Avram
Well, you can disable the lock with the
extensions.zotero.dbLockExclusive hidden pref, but MozRepl (or a custom
Zotero plugin with a trivial HTTP server) is still likely a better
option. There's no guarantee that the database schema won't change at
any time.
There are no plans to restore the integration HTTP server. The current
integration plugins do use XPCOM from Java/Python/C++, but that's a
pretty complex route to go.
The integration server was specific to the integration plugins, but
we've considered a more general server that third-party apps could use.
It's unclear what real benefit that would provide over MozRepl,
though�we already use the JS API internally, and any abstraction of that
API in a server would require additional work and maintenance.
We use MozRepl ourselves to generate previews for the style repository
(which was set up before citeproc-js existed). There's an actual
Firefox+Zotero+MozRepl instance running in a VNC session on a server,
and the repo gets the previews from there.