1785 is junk. Use 1783, I have run into no bugs with it as of yet. You have to "build" an .svg filter
Now, a friend of mine did this (his first rpm) but we can't seem to figure out why it does not work. I have retrieved all the required depnedancies through synaptic, but... something is still missing....

To build a new filter based on the XPFilter project will require creating a new copy of the source directory called something sensible for your filter, renaming (and editing) the configuration XML file and modifying some parts of the configure.in script and Makefile.am
As the example filter is still under development (various extensions will be added to it as time goes by) it is recommended that you try to alter as little of the build framework as possible to make merging in new versions as painless as possible.
For a hypothetical SVG filter that uses XarLib, the necessary changes would be as follows:
Copy the XPFilter-0.2 directory as SVGFilter.
Copy the xpxlfilter.xml file as svgfilter.xml and edit the contents appropriately. E.g.
<FilterConfig>
<Filter name="SVGFilter">
<DisplayName>SVG Filter</DisplayName>
<Extensions>svg</Extensions>
<CanImport>svgfilter -c -f %IN%</CanImport>
<DoImport>svgfilter -i -g -f %IN%</DoImport>
<PrepareExport>svgfilterui -f %OUT% -x %XML%</PrepareExport>
<DoExport>svgfilter -e -g -f %OUT% -x %XML%</DoExport>
</Filter>
</FilterConfig>
Edit configure.in
  • Change the name of the project in the AM_INIT_AUTOMAKE line from XPFilter to SVGFilter
Edit Makefile.am
  • Change the names of the programs being compiled in bin_PROGRAMS. One is set directly in bin_PROGRAMS as both filters use the same xpfilterui program for the PrepareExport stage. The other is added conditionally as it needs to be a different program for each filter. You can delete the conditional setting of bin_PROGRAMS and set your new filter program names directly in bin_PROGRAMS.
  • Change the variables that start either xpfilterui_ or xpxlfilterui_ to be svgfilterui_ and svgfilter_ respectively. Delete those variables that start xpfilter_.
  • Change the relevant part of the install-data-local rule to copy the correct xml file.
The top of Makefile.am would then look something like this:
bin_PROGRAMS = svgfilter svgfilterui
svgfilter_SOURCES = xpfilter.cpp xarlibfilter.cpp
svgfilter_CPPFLAGS = $(XARLIB_CFLAGS)
svgfilter_LDADD = $(XARLIB_LIBS)
svgfilterui_SOURCES = xpfilterui.cpp
install-data-local:
mkdir -p $(DESTDIR)/usr/share/xaralx/filters/
$(INSTALL_DATA) $(srcdir)/svgfilter.xml $(DESTDIR)/usr/share/xaralx/filters
The implementaion would then be done by replacing the content of the functions in xarlibfilter.cpp and xpfilterui.cpp. If additional source files are required then they are simply added to the relevant _SOURCES line. The framework handles all the command line parsing, XarLib initialisation etc, leaving you to concentrate just on reading and writing Xar format records.



I also have the RPM which my friend DidouPH built but I will need to ask him first. It's not public yet so bare with me on that. I'm sure if I ask him he'll be fine with it.?? Let me check and hopefully Ill post it very soon