[Freemind-developer] xml (was images, comments,...)

[<OSE...@st...>]

Hello,

> | If we want to change, we could change the suffix file name for the new
> | file and keep the mm file type for import old model. The ealier is
better
> | because xml will be more complex.
> Actually it is quite irrelevant which format is used
[...]
> because both formats are xml an can easily be transformed
> into each other (old one to new one and vice versa).

You right.
Just thinking how to help common user who don't know anything on xml and
that have already lot of old file type.
I add recently in freemind a import/export feature. It is based on file
extension.
If a user open an mm file (actual extension), this file will be imported
with a import xslt filter for exemple. And so he could read old file type
without any problem.

> I have written a simple xslt transformation sheet

As you seem expert in xml, would you integrate a xslt filter in freemind ?
Import/export filter are plugins so you could add one more easily (I
hope).


> You/we

we :))

> (I'm not sure yet ;-) should switch to the standard JAXP (Java
> API for XML Processing) API which is supported by most parsers

That the first time I see JAXP (I am new to xml). It seems interesting.

If we use that, it will change some core files. So I think that Joerg have
to take the decision (I am sure he read all mails but I know that he has
no time yet to answer).

> | > put the text into an element, not an attribute, which is
> | > more flexible (but that's another story ;-)
> Citing Brett McLaughlin, Java & XML (O'Reilly):

Thanks for this quote.

> By the way, TouchGraph is really cool! I looked a long time for a
> flexible open source layouter for another project I'm working on,
> Thanks for the link!

So you have an other task on freemind :-) that to adapt TouchGraph into
freemind.

a+
Vincent