Hi Egon,
some hints:
* If you are looking for a basic usecase, I would recommend implementing
the IExportFormat interface.
* More complicated uses might involve IExportFormatProvider
* The XML Export is currently the only plugin I know which uses
IExportFormat and plugin.xml but you are right that it is too complicated.
What you basically need is a simple plugin.xml like this:
<plugin id="net.sf.jabref.export.xml" version="1.0"
class="net.sf.jabref.export.xml.JabRefXmlPlugin">
<requires>
<import plugin-id="net.sf.jabref.core"/>
</requires>
<!-- Will load code and resources from the home folder -->
<runtime>
<library type="code" path="./" id="code"/>
<library type="resources" path="./" id="resouces"/>
</runtime>
<extension id="YourExportFormat" plugin-id="net.sf.jabref.core"
point-id="ExportFormat">
<parameter id="exportFormat"
value="net.sf.jabref.export.YourIExportFormatClass" />
<parameter id="displayName" value="Name...." />
<parameter id="consoleName" value="......" />
<parameter id="extension" value="..." />
</extension>
</plugin>
This should be everything you need.
For testing you can just add the <extension...> part into the plugin.xml
in the plugins/net.sf.jabref.core folder and put your class beside the
other export format classes.
Alastair has recently worked on a plugin and might help you with getting
additional library dependencies into a plugin.
Take care,
Christopher
On Mon, 04 Jan 2010 16:04:48 +0100, Egon Willighagen
<egon.willigha...@gmail.com> wrote:
> Hi all,
>
> I am seeking to work a bit more on BIBO support, and XHTML+RDFa in
> particular. I want to write an export plugin using the XOM library,
> and am looking for source code of a good export plugin that is
> written/updated against the 2.6 beta.
>
> I found plugin source code in SVN, but the xml export uses XSLT, and I
> am not sure what classes to keep and what plugin.xml to keep to write
> a new export plugin with a new independent export format (and I don't
> want to use XSLT). And the RISExport plugin uses templates which I do
> not want to do either, as it makes it easier to cause XML
> invalidity...
>
> Pointers are very much appreciated!
>
> Egon
>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Jabref-devel mailing list
Jabref-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jabref-devel
