FreeMind

> web.sourceforge.net:/home/groups/f/fr/freemind/htdocs/testversions/
> 
> (Currently, it is still under way). (How to access this directory from 
> outside?)

Hi Chris,

congratulations to the release!

the directory can be accessed as

http://freemind.sourceforge.net/testversions/

after I uploaded there file .htaccess which is also attached to this mail.

Regards,
Dimitry

Hi Dimitry,

thank you.

Regards, Chris

Dimitry Polivaev schrieb:
>> web.sourceforge.net:/home/groups/f/fr/freemind/htdocs/testversions/
>>
>> (Currently, it is still under way). (How to access this directory 
>> from outside?)
>
> Hi Chris,
>
> congratulations to the release!
>
> the directory can be accessed as
>
> http://freemind.sourceforge.net/testversions/
>
> after I uploaded there file .htaccess which is also attached to this 
> mail.
>
> Regards,
> Dimitry
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hi Chris

it is good to see a solid version of FreeMind 0.9.0, the version RC6.
Many errors reported for the previous RCs have been fixed.
Congratulations!

There are nevertheless some issues open to which I would like to draw
your attention. The issues that I have reported and are open are still
available in the trackers:

* http://freemind.sourceforge.net/wiki/index.php/Finishing_0.9.0
** http://sourceforge.net/tracker/?group_id=7118&atid=107118&status=1&submitter=danielpolansky&submit=Filter
** http://sourceforge.net/tracker/?group_id=7118&atid=1006953&status=1&submit=Filter

I understand that you consider some of these issues to be of low
priority, so I will pick those that I think are important and explain
a bit why I think they are important.


SELECTED BUGS
=============

Selected bugs, in the order of estimated priority:

1. Feedback on conversion
http://sourceforge.net/tracker/?func=detail&aid=1820886&group_id=7118&atid=1006953
This is the single most important outstanding issue. Users updating to
the version 0.9.0 are not notified that their maps have been converted
to a format that the version 0.8.0 cannot read. Either a warning
should be implemented, one that appears per default, or an additional
function should be added to FreeMind 0.9.0 that saves a mind map in
the file format of 0.8.0; this could be one of the export functions.
If such an export function were there, it would be no longer that
critical that FreeMind does not warn about converting a mind map to an
incompatible file format.

2. Zoom: no zooming effect on node editors
http://sourceforge.net/tracker/?func=detail&aid=2800933&group_id=7118&atid=107118
Zooming set for the mind map does not apply to the rich text node
editor; the bug has been fixed in part, in that zooming at least
applies correctly to plain text long node editor. On one hand, this
does not cause a data loss, so is not of the absolutely utmost
urgency. But it is a conspicuous usability error, one that makes the
zoom fuction only half-usable in combination with rich text editing.
Some of the users of the zoom function use it because small letters
are tiring to their eyes; this can be especially true on some notebook
displays with high PPI (pixel per inch). The bug is quite easy to fix;
I do not have this bug in my personal version of FreeMind.

3. Long node editor not below node
http://sourceforge.net/tracker/?func=detail&aid=2540600&group_id=7118&atid=107118
Long node editor is still sometimes opened above the node instead of
below it. I have added to the bug a scenario that should make it
easier to reproduce the bug. This is not a showstopper or a crash; it
is an annoyance. How severe this annoyance is I am not sure. It is in
any case an unneeded deviation from the behavior of FreeMind 0.8.0 and
0.7.1, one that should not therefore be too difficult to fix.

4. Option for plain text in notes
http://sourceforge.net/tracker/?func=detail&aid=1884362&group_id=7118&atid=1006953
I do not really hope that you will implement an option for having
plain text notes, but I am mentioning this anyway. This is a
regression against FreeMind 0.8.0, one whose fixing has been requested
by various people as documented in the tracker.

5. Hyperlinks - opening not working in long nodes - 0.9.0 RC6
http://sourceforge.net/tracker/?func=detail&aid=2908233&group_id=7118&atid=107118
This is a minor issue, but it seems very easy to fix, and worth it. It
suffices to add the handler for opening of hyperlinks that is added to
rich text notes also to rich text nodes.

There are more open issues that I have left out from this list,
agreeing that they are likely either not all that important or too
hard to fix and can be fixed after 0.9.0.


PASSED TESTS
============

I have tested the opening or following of various hyperlinks on my
Vista machine, without having found any errors. I have not tested the
network "//..." hyperlinks, though. There is a bug report in the bug
tracker for the network hyperlinks in which you say that problems with
their opening are fixed in Java 1.6.0. I assume that to be the case,
otherwise the users of FreeMind 0.9.0 RC series would have likely
complained.

There were three data format errors that I have checked to no longer
appear in FreeMind 0.9.0 RC6:
* http://sourceforge.net/tracker/?func=detail&aid=2844139&group_id=7118&atid=107118
* http://sourceforge.net/tracker/?func=detail&aid=2797009&group_id=7118&atid=107118
* http://sourceforge.net/tracker/?func=detail&aid=2705587&group_id=7118&atid=107118

I have done no performance testing.

I have done no further creative testing other than verifying whether
the issues and bugs that I have already reported have been fixed.

I have tried hard to consider what is important and what is secondary,
and selected the bugs to report here accordingly.

Best regards,

Dan

All right, here comes another bug worth fixing:

6. Switching between maps marks them as modified
https://sourceforge.net/tracker/index.php?func=detail&aid=2852882&group_id=7118&atid=107118
This is not a showstopper, but it makes the function that marks mind
maps with "*" unusable, as switching between several opened mind maps
is a very common and repeatedly done operation, and this operation
leads to a false marking with "*".

Dan

Dear Dan,

this can't be verified by me. I can switch using mouse, menu and 
CTRL+6/7 without problems.
Can you please reproduce the bug with the given freemind.jar and send me 
the output of the log file in your .freemind directory.
Something actually changes your maps, which will be included in the 
logfile.

TIA, Chris

Dan Polansky schrieb:
> All right, here comes another bug worth fixing:
>
> 6. Switching between maps marks them as modified
> https://sourceforge.net/tracker/index.php?func=detail&aid=2852882&group_id=7118&atid=107118
> This is not a showstopper, but it makes the function that marks mind
> maps with "*" unusable, as switching between several opened mind maps
> is a very common and repeatedly done operation, and this operation
> leads to a false marking with "*".
>
> Dan
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>

Hi Dan,

according to your "main" issue:

> 1. Feedback on conversion
> http://sourceforge.net/tracker/?func=detail&aid=1820886&group_id=7118&atid=1006953
> This is the single most important outstanding issue. Users updating to
> the version 0.9.0 are not notified that their maps have been converted
> to a format that the version 0.8.0 cannot read. Either a warning
> should be implemented, one that appears per default, or an additional
> function should be added to FreeMind 0.9.0 that saves a mind map in
> the file format of 0.8.0; this could be one of the export functions.
> If such an export function were there, it would be no longer that
> critical that FreeMind does not warn about converting a mind map to an
> incompatible file format.
>   
I implemented (but not activated) the following warning:

really_convert_to_current_version=<html>This map was created with an 
older version of FreeMind. <br>Should it be converted (recommended)? 
<br>(Otherwise it is taken as it is without guarantee.) </html>

I can activate this warning without problems, but it is hard to change 
it (as all other translations are unchanged then).

If you have a very much better comment here, I can try to have a quick 
translation session.

According to the others, I wrote something below.

Regards, Chris


Dan Polansky schrieb:
> Hi Chris
>
> it is good to see a solid version of FreeMind 0.9.0, the version RC6.
> Many errors reported for the previous RCs have been fixed.
> Congratulations!
>
> There are nevertheless some issues open to which I would like to draw
> your attention. The issues that I have reported and are open are still
> available in the trackers:
>
> * http://freemind.sourceforge.net/wiki/index.php/Finishing_0.9.0
> ** http://sourceforge.net/tracker/?group_id=7118&atid=107118&status=1&submitter=danielpolansky&submit=Filter
> ** http://sourceforge.net/tracker/?group_id=7118&atid=1006953&status=1&submit=Filter
>
> I understand that you consider some of these issues to be of low
> priority, so I will pick those that I think are important and explain
> a bit why I think they are important.
>
>
> SELECTED BUGS
> =============
>
> Selected bugs, in the order of estimated priority:
>
> 1. Feedback on conversion
> http://sourceforge.net/tracker/?func=detail&aid=1820886&group_id=7118&atid=1006953
> This is the single most important outstanding issue. Users updating to
> the version 0.9.0 are not notified that their maps have been converted
> to a format that the version 0.8.0 cannot read. Either a warning
> should be implemented, one that appears per default, or an additional
> function should be added to FreeMind 0.9.0 that saves a mind map in
> the file format of 0.8.0; this could be one of the export functions.
> If such an export function were there, it would be no longer that
> critical that FreeMind does not warn about converting a mind map to an
> incompatible file format.
>
> 2. Zoom: no zooming effect on node editors
> http://sourceforge.net/tracker/?func=detail&aid=2800933&group_id=7118&atid=107118
> Zooming set for the mind map does not apply to the rich text node
> editor; the bug has been fixed in part, in that zooming at least
> applies correctly to plain text long node editor. On one hand, this
> does not cause a data loss, so is not of the absolutely utmost
> urgency. But it is a conspicuous usability error, one that makes the
> zoom fuction only half-usable in combination with rich text editing.
> Some of the users of the zoom function use it because small letters
> are tiring to their eyes; this can be especially true on some notebook
> displays with high PPI (pixel per inch). The bug is quite easy to fix;
> I do not have this bug in my personal version of FreeMind.
>
>   
I tried, but this bug isn't easy to fix IMHO. Perhaps in a future 
version of SimplyHTML.

> 3. Long node editor not below node
> http://sourceforge.net/tracker/?func=detail&aid=2540600&group_id=7118&atid=107118
> Long node editor is still sometimes opened above the node instead of
> below it. I have added to the bug a scenario that should make it
> easier to reproduce the bug. This is not a showstopper or a crash; it
> is an annoyance. How severe this annoyance is I am not sure. It is in
> any case an unneeded deviation from the behavior of FreeMind 0.8.0 and
> 0.7.1, one that should not therefore be too difficult to fix.
>
>   
I prefer not to change this now. I can look at it directly after 0.9.0, 
but as this is tricky inside Java to find its window and dialog positions,
I would like to have a longer testing phase with every constellation of 
monitors and screens.
> 4. Option for plain text in notes
> http://sourceforge.net/tracker/?func=detail&aid=1884362&group_id=7118&atid=1006953
> I do not really hope that you will implement an option for having
> plain text notes, but I am mentioning this anyway. This is a
> regression against FreeMind 0.8.0, one whose fixing has been requested
> by various people as documented in the tracker.
>
>   
Don't know. I don't think, that this is necessary. Perhaps, somebody 
implements it in the future.

> 5. Hyperlinks - opening not working in long nodes - 0.9.0 RC6
> http://sourceforge.net/tracker/?func=detail&aid=2908233&group_id=7118&atid=107118
> This is a minor issue, but it seems very easy to fix, and worth it. It
> suffices to add the handler for opening of hyperlinks that is added to
> rich text notes also to rich text nodes.
>
>   
Perhaps, Dimitry wants to look into it, but I prefer to leave it as it 
is for this version.
> There are more open issues that I have left out from this list,
> agreeing that they are likely either not all that important or too
> hard to fix and can be fixed after 0.9.0.
>
>
> PASSED TESTS
> ============
>
> I have tested the opening or following of various hyperlinks on my
> Vista machine, without having found any errors. I have not tested the
> network "//..." hyperlinks, though. There is a bug report in the bug
> tracker for the network hyperlinks in which you say that problems with
> their opening are fixed in Java 1.6.0. I assume that to be the case,
> otherwise the users of FreeMind 0.9.0 RC series would have likely
> complained.
>
> There were three data format errors that I have checked to no longer
> appear in FreeMind 0.9.0 RC6:
> * http://sourceforge.net/tracker/?func=detail&aid=2844139&group_id=7118&atid=107118
> * http://sourceforge.net/tracker/?func=detail&aid=2797009&group_id=7118&atid=107118
> * http://sourceforge.net/tracker/?func=detail&aid=2705587&group_id=7118&atid=107118
>
> I have done no performance testing.
>
> I have done no further creative testing other than verifying whether
> the issues and bugs that I have already reported have been fixed.
>
> I have tried hard to consider what is important and what is secondary,
> and selected the bugs to report here accordingly.
>
> Best regards,
>
> Dan
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>

Hello Chris,

in this email I focus on the issue 1. Feedback on conversion. I hope
to be able to have a look at the other issues during the coming week,
and see whether further input from my side is needed on them.

I mention only in passing regarding the issue "6. Switching between
maps marks them as modified" that it was reported by Eric Lavarde,
likely on Linux, and that I have easily reproduced the issue on a
Windows Vista machine, so it is surprising that you cannot reproduce
the issue. In the tracker there is also a comment by user "freyi" who
asks us to fix the issue, which means that he too has experienced this
problem.


Now to 1. Feedback on conversion:

To the proposed text of the warning: I don't understand what is meant
by the sentence "(Otherwise it is taken as it is without guarantee.)".

The text that I could propose is the following:

"The mind map you are trying to open was created with an older version
of FreeMind, stored in an old format.<br>FreeMind is about to convert
this mind map into its current format. <br>After the mind map is
converted and saved by this version of FreeMind, it can no longer be
opened in older versions of FreeMind.<br>Should FreeMind convert and
open the mind map?"

I wonder whether the "<br>" are needed, though. Possibly, there should
be only one "<br>", before the question "Should FreeMind convert and
open the mind map?" I don't think the confirmation of the question
should be marked as "recommended", but I admit that I do not know how
other model applications proceed.

If the user accepts, the mind map should be converted and opened, as
in the current prerelease versions. If the user rejects, the mind map
should be neither converted nor opened by FreeMind.

I am aware that the warning will need to be translated, which would,
were this not a critical issue, be a motivation to postpone such a
modification to a next release.

An alternative to this warning is to offer an export function that
stores 0.9.0 mind maps as 0.8.0 mind maps. The export function would,
in the exported mind map, drop these parts of the mind map that are
unsupported by the 0.8.0 version, including attributes and scripts.
This alternative would probably generate translation and documentation
effort too, though. This alternative, much more costly to implement,
would actually be better it seems, as it would make it possible for
people to convert their mind maps to an old format before sending them
to people who still use an old version of FreeMind. But having a
warning is still better than having nothing.

Best regards,

Dan

Dear Dan,

simply, I can't fix a bug, that I can't reproduce. Do you support me in 
trying the jar I sent to you?
Or Eric: can you help me?
TIA, Chris

Dan Polansky schrieb:
> Hello Chris,
>
> in this email I focus on the issue 1. Feedback on conversion. I hope
> to be able to have a look at the other issues during the coming week,
> and see whether further input from my side is needed on them.
>
> I mention only in passing regarding the issue "6. Switching between
> maps marks them as modified" that it was reported by Eric Lavarde,
> likely on Linux, and that I have easily reproduced the issue on a
> Windows Vista machine, so it is surprising that you cannot reproduce
> the issue. In the tracker there is also a comment by user "freyi" who
> asks us to fix the issue, which means that he too has experienced this
> problem.
>
>

An addition to the bug "6. Switching between maps marks them as modified":
it is not in 0.9.0 RC3; it has appeared in 0.9.0 RC4. --Dan

An addition to the bug "2. Zoom: no zooming effect on node editors"

http://sourceforge.net/tracker/?func=detail&aid=2800933&group_id=7118&atid=107118

> I tried, but this bug isn't easy to fix IMHO. Perhaps in a future  version
of SimplyHTML.

This has nothing to do with the version of SimplyHTML. This has to do with
how SimplyHTML is called from FreeMind. I am using basically the same
version of SimplyHTML, yet in my FreeMind the fonts are shown in SimplyHTML
zoomed correctly.

The critical part is the following one in the class "EditNodeWYSIWYG":

            Font font = node.getTextFont();
  191 //            font = Tools.updateFontSize(font,
this.getView().getZoom(), font.getSize());
  192             final Color nodeTextBackground = node.getTextBackground();
  193             rule += "font-family: "+font.getFamily()+";";
  194             rule += "font-size: "+font.getSize()+"pt;";

Here, it matters that the font added to the style rules is the zoomed one.

What I have in my FreeMind is the following:

rule += "font-size: "+node.getFont().getSize()+"pt;";

I call "node.getFont" instead of "node.getTextFont()", where "node" is a
NodeView.

node.getFont is the native method of the JLabel, which returns the font in
which JLabel is actually shown; this should be already zoomed. By contrast,
"node.getTextFont()" is likely a method that returns the non-zoomed font of
nodeview.

So the first thing I would try is to replace "node.getTextFont()" with
"node.getFont()".

If that won't work, you can adjust the font in the code for zooming using
the following code snippet, presuming you have a reference to "map":

 if (map.getZoom() != 1F) {
                font = font.deriveFont(font.getSize()*map.getZoom()); }

--Dan

There is another error that seems worth fixing:

7. Crypted root's childnodes order error
http://sourceforge.net/tracker/index.php?func=detail&aid=2912427&group_id=7118&atid=107118

The bug report was not created by me, but I have posted to the bug
report a detailed procedure on how to reproduce the bug, and I have,
of course, reproduced the bug myself. The bug does not lead to a data
loss but is rather annoying for the users of the encryption function:
the encryption function does not keep the order of the children of the
encrypted node. The bug is a regression bug, not present in FreeMind
0.8.1, but present in FreeMind 0.9.0 RC1 and later.

--Dan

Hi Chris,

I just found at last the time to check the jar file you sent, but it 
breaks with an error message:
$ freemind
Exception in thread "main" java.lang.NoClassDefFoundError: 
freemind/main/FreeMindStarter
Caused by: java.lang.ClassNotFoundException: freemind.main.FreeMindStarter
         at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336)
Could not find the main class: freemind.main.FreeMindStarter. Program 
will exit.
and the size seems quite wrong:
/usr/share/freemind/lib$ ll
total 2920
-rw-r--r-- 1 root root  319619 2009-11-07 13:15 bindings.jar
-rw-r--r-- 1 root root  327186 2009-12-12 10:26 freemind.jar
-rw-r--r-- 1 root root 2323079 2009-12-12 10:25 
freemind.jar.0.9.0~rc6+dfsg-1

It's with the version I packaged, but I checked against the "official" 
download version and it's the same.

Eric

Christian Foltin (GMX) wrote:
> Dear Dan,
> 
> this can't be verified by me. I can switch using mouse, menu and 
> CTRL+6/7 without problems.
> Can you please reproduce the bug with the given freemind.jar and send me 
> the output of the log file in your .freemind directory.
> Something actually changes your maps, which will be included in the 
> logfile.
> 
> TIA, Chris
> 
> Dan Polansky schrieb:
>> All right, here comes another bug worth fixing:
>>
>> 6. Switching between maps marks them as modified
>> https://sourceforge.net/tracker/index.php?func=detail&aid=2852882&group_id=7118&atid=107118 
>>
>> This is not a showstopper, but it makes the function that marks mind
>> maps with "*" unusable, as switching between several opened mind maps
>> is a very common and repeatedly done operation, and this operation
>> leads to a false marking with "*".
>>
>> Dan
>>
>> ------------------------------------------------------------------------------ 
>>
>> Join us December 9, 2009 for the Red Hat Virtual Experience,
>> a free event focused on virtualization and cloud computing. Attend 
>> in-depth sessions from your desk. Your couch. Anywhere.
>> http://p.sf.net/sfu/redhat-sfdev2dev
>> _______________________________________________
>> Freemind-developer mailing list
>> Freemind-developer@...
>> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>>
>>

Be it as it may, there is another bug that seems worth fixing.

8. Node navigation using the arrow keys does not work
http://sourceforge.net/tracker/index.php?func=detail&aid=2918427&group_id=7118&atid=107118
The node navigation using arrow keys is broken after the user presses
escape while editing a new node. This is not a showstopper; there is
an easy workaround; it cannot lead data loss. However, it is a
regression against 0.9.0 RC4, newly appearing in 0.9.0 RC6.

Dan

One more bug worth fixing:

9. Errors after exporting a branch as a new map
http://sourceforge.net/tracker/index.php?func=detail&aid=2932322&group_id=7118&atid=107118
The error that I can reproduce actually consists in (a) the cursor
disappearing after an export to PNG; (b) the cursor disappearing after
an export to JPEG.

--Dan

Another error worth fixing, not reported and discovered by me, but
confirmed by me:

10. RC4 regression: incorrect viewing of UTF-8 map
http://sourceforge.net/tracker/?func=detail&atid=107118&aid=2810535&group_id=7118
The error is still there in RC6. An UTF-8 encoded mind map, attached
to the bug report, is shown in weird characteres in RC4 and RC6, but
not in RC3.

--Dan

I have discovered another bug in RC6:

11. Wrong node selection after moving node left - 0.9.0 RC6
http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118
After I move node left by pressing control + left, it is not selected and
its parent is selected instead.

--Dan

Hi Dan,

this bug can't be reproduced by me. Is there any special, or does it 
occur with every map?
Which java version do you use?

TIA, Chris

Dan Polansky schrieb:
> I have discovered another bug in RC6:
>
> 11. Wrong node selection after moving node left - 0.9.0 RC6
> http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118 
> <http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118>
> After I move node left by pressing control + left, it is not selected 
> and its parent is selected instead.
>
> --Dan
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hi Chris,

I have reproduced the bug in FreeMind 0.9.0 RC6 and also 0.9.0 beta 16, Java
version "1.6.0_17", Windows Vista. The bug occurs in any mind map that I
create. It appears first in 0.9.0 beta 16; it is not there in 0.9.0 beta 15.

Let me rephrase the bug description: if I move a node "A" with control +
left or control + right, the same node "A" should be selected after the
move; in fact, it is not selected and another node is selected instead.

Best regards,
Dan


On Fri, Feb 19, 2010 at 11:19 PM, Christian Foltin (GMX) <
christian.foltin@...> wrote:

>  Hi Dan,
>
> this bug can't be reproduced by me. Is there any special, or does it occur
> with every map?
> Which java version do you use?
>
>
> TIA, Chris
>
> Dan Polansky schrieb:
>
> I have discovered another bug in RC6:
>
>
> 11. Wrong node selection after moving node left - 0.9.0 RC6
>
> http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118
> After I move node left by pressing control + left, it is not selected and
> its parent is selected instead.
>
> --Dan
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOWhttp://p.sf.net/sfu/solaris-dev2dev
>
> ------------------------------
>
> _______________________________________________
> Freemind-developer mailing listFreemind-developer@... href="nethttps://lists.sourceforge.net/lists/listinfo/freemind-developer" target="_new">nethttps://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>

Hello Chris and Dan,

yesterday we found one bug which is relevant for both Freeplane and FreeMind. If you insert an image 
  as a link to the external file and its name contains non ascii characters, they are saved in the 
default system encoding and as a consequence the linked image can not be found if the map with the 
image are opened on another OS.

I attach an example map and one image file linkmÄp.png to this mail.

I am currently fixing the issue for Freeplane. Please let me know if you want me to make the fix for 
FreeMind too.

Kind regards,
Dimitry Polivaev

Dear Dan,

this issue is still mysterious for me. I would like you to look into the 
log messages whether or not there is an exception (or anything else). 
Moreover, can you please try it without any preferences (ie. move your 
auto.properties file temporarily away).

TIA Chris

Dan Polansky schrieb:
> Hi Chris,
>
> I have reproduced the bug in FreeMind 0.9.0 RC6 and also 0.9.0 beta 
> 16, Java version "1.6.0_17", Windows Vista. The bug occurs in any mind 
> map that I create. It appears first in 0.9.0 beta 16; it is not there 
> in 0.9.0 beta 15.
>
> Let me rephrase the bug description: if I move a node "A" with control 
> + left or control + right, the same node "A" should be selected after 
> the move; in fact, it is not selected and another node is selected 
> instead.
>
> Best regards,
> Dan
>
>
> On Fri, Feb 19, 2010 at 11:19 PM, Christian Foltin (GMX) 
> <christian.foltin@... <mailto:christian.foltin@...>> wrote:
>
>     Hi Dan,
>
>     this bug can't be reproduced by me. Is there any special, or does
>     it occur with every map?
>     Which java version do you use?
>
>
>     TIA, Chris
>
>     Dan Polansky schrieb:
>>     I have discovered another bug in RC6:
>>
>>
>>     11. Wrong node selection after moving node left - 0.9.0 RC6
>>     http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118
>>     <http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118>
>>     After I move node left by pressing control + left, it is not
>>     selected and its parent is selected instead.
>>
>>     --Dan
>>
>>     ------------------------------------------------------------------------
>>
>>     ------------------------------------------------------------------------------
>>     SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>>     Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>>     http://p.sf.net/sfu/solaris-dev2dev
>>
>>     ------------------------------------------------------------------------
>>
>>     _______________________________________________
>>     Freemind-developer mailing list
>>     Freemind-developer@... <mailto:Freemind-developer@...>
>>     https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>     ------------------------------------------------------------------------------
>     Download Intel&#174; Parallel Studio Eval
>     Try the new software tools for yourself. Speed compiling, find bugs
>     proactively, and fine-tune applications for parallel performance.
>     See why Intel Parallel Studio got high marks during beta.
>     http://p.sf.net/sfu/intel-sw-dev
>     _______________________________________________
>     Freemind-developer mailing list
>     Freemind-developer@...
>     <mailto:Freemind-developer@...>
>     https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hi Dan,

ok, I've found the problem. You use the "Save only used IDs" option, and 
this causes all node ids to disappear, even within copy and paste. But 
the move+left/right action uses the ids to find the previous selected 
nodes after being copied. Thus, in your case, they can't be found and 
thus the selection is wrong.

I've made a workaround for this case.

Regards, Chris


Dan Polansky schrieb:
> Hi Chris,
>
> I have reproduced the bug in FreeMind 0.9.0 RC6 and also 0.9.0 beta 
> 16, Java version "1.6.0_17", Windows Vista. The bug occurs in any mind 
> map that I create. It appears first in 0.9.0 beta 16; it is not there 
> in 0.9.0 beta 15.
>
> Let me rephrase the bug description: if I move a node "A" with control 
> + left or control + right, the same node "A" should be selected after 
> the move; in fact, it is not selected and another node is selected 
> instead.
>
> Best regards,
> Dan
>
>
> On Fri, Feb 19, 2010 at 11:19 PM, Christian Foltin (GMX) 
> <christian.foltin@... <mailto:christian.foltin@...>> wrote:
>
>     Hi Dan,
>
>     this bug can't be reproduced by me. Is there any special, or does
>     it occur with every map?
>     Which java version do you use?
>
>
>     TIA, Chris
>
>     Dan Polansky schrieb:
>>     I have discovered another bug in RC6:
>>
>>
>>     11. Wrong node selection after moving node left - 0.9.0 RC6
>>     http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118
>>     <http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118>
>>     After I move node left by pressing control + left, it is not
>>     selected and its parent is selected instead.
>>
>>     --Dan
>>
>>     ------------------------------------------------------------------------
>>
>>     ------------------------------------------------------------------------------
>>     SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>>     Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>>     http://p.sf.net/sfu/solaris-dev2dev
>>
>>     ------------------------------------------------------------------------
>>
>>     _______________________________________________
>>     Freemind-developer mailing list
>>     Freemind-developer@... <mailto:Freemind-developer@...>
>>     https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>     ------------------------------------------------------------------------------
>     Download Intel&#174; Parallel Studio Eval
>     Try the new software tools for yourself. Speed compiling, find bugs
>     proactively, and fine-tune applications for parallel performance.
>     See why Intel Parallel Studio got high marks during beta.
>     http://p.sf.net/sfu/intel-sw-dev
>     _______________________________________________
>     Freemind-developer mailing list
>     Freemind-developer@...
>     <mailto:Freemind-developer@...>
>     https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hi Chris,

you are right; thank you for discovering the dependence on "Save only used
IDs".

Can you also make sure there is no hourglass cursor during the control +
left operation? There is no hourglass cursor with control + up and control +
down, which are closely analogous functions, and there is no hourglass
cursor in drag and drop operation, which also moves branches around.

Best regards,
Dan


On Mon, Feb 22, 2010 at 6:10 PM, Christian Foltin (GMX) <
christian.foltin@...> wrote:

>  Hi Dan,
>
> ok, I've found the problem. You use the "Save only used IDs" option, and
> this causes all node ids to disappear, even within copy and paste. But the
> move+left/right action uses the ids to find the previous selected nodes
> after being copied. Thus, in your case, they can't be found and thus the
> selection is wrong.
>
> I've made a workaround for this case.
>
>
> Regards, Chris
>
>
> Dan Polansky schrieb:
>
> Hi Chris,
>
>
> I have reproduced the bug in FreeMind 0.9.0 RC6 and also 0.9.0 beta 16,
> Java version "1.6.0_17", Windows Vista. The bug occurs in any mind map that
> I create. It appears first in 0.9.0 beta 16; it is not there in 0.9.0 beta
> 15.
>
> Let me rephrase the bug description: if I move a node "A" with control +
> left or control + right, the same node "A" should be selected after the
> move; in fact, it is not selected and another node is selected instead.
>
> Best regards,
> Dan
>
>
>  On Fri, Feb 19, 2010 at 11:19 PM, Christian Foltin (GMX) <
> christian.foltin@...> wrote:
>
>> Hi Dan,
>>
>> this bug can't be reproduced by me. Is there any special, or does it occur
>> with every map?
>> Which java version do you use?
>>
>>
>> TIA, Chris
>>
>> Dan Polansky schrieb:
>>
>> I have discovered another bug in RC6:
>>
>>
>> 11. Wrong node selection after moving node left - 0.9.0 RC6
>>
>> http://sourceforge.net/tracker/?func=detail&aid=2953495&group_id=7118&atid=107118
>> After I move node left by pressing control + left, it is not selected and
>> its parent is selected instead.
>>
>> --Dan
>>
>>

Dear Dan,

according to

16. Scripts do not work if file operations are not permitted[5] 
<http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118> (/http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118/) 
- no progress so far

I tried it out with ="Hello", and it worked without file permissions.

Could you try, please?

TIA, Chris

Hello Chris,

regarding 16. Scripts do not work if file operations are not permitted
(http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118):

I have tried to run the script '="Hello"', and it gave me an
exception, as described in the bug report.

My testing environment: FreeMind 0.9.0 RC10, Java version "1.6.0_21",
Windows Vista.

The bug was originally reported by Dimitry, who I think also used some
version of MS Windows.

In the email "Scripts do not work if file operations are not
permitted" from 11.5.2009, you yourself have written:

"The problem is known, but AFAIK this is only valid for the first time
a script is executed as the class files are then hold inside the
cache, or the like."

Thus, back then you must have been able to reproduce the bug, right?
Could it have been that you have tested the issue on Windows rather
than on Mac OS X, back then?

In the same email thread from 11.5.2009, Dimitry has proposed some
sort of fix for the bug.

>From a web interface, the thread is available here:

http://sourceforge.net/mailarchive/forum.php?thread_name=4A089EEB.1080207%40gmx.de&forum_name=freemind-developer

Best regards,
Dan



On Sat, Nov 6, 2010 at 11:01 PM, Christian Foltin (GMX)
<christian.foltin@...> wrote:
> Dear Dan,
>
> according to
>
> 16. Scripts do not work if file operations are not
> permitted[5] (http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118)
> - no progress so far
>
> I tried it out with ="Hello", and it worked without file permissions.
>
> Could you try, please?
>
> TIA, Chris

Hello Chris,

as regards 18. "Conversion from 0.8.0 to 0.9.0 drops indentation in
notes" and the proposed bug fix by adjusting the file
"freemind_version_updater.xslt":

I have downloaded the XSLT, placed it into freemind.jar, and tested
the result. It seems to do what it should, with one exception.

What is does correctly: It converts indentation in notes correctly,
and it converts "a b" as "a b" instead of "a&#160b", as it should.

What is does erroneously: I have a test mind map "Notes and encryption
after conversion", which it fails to load; it gives the exception
"Error while parsing file:java.io.IOException: Stream closed" placed
to a root node. I attach the test mind map "Notes and encryption after
conversion" to this email. In 0.9.0 RC9, the test mind map gets opened
without a failure, albeit with conversion mistakes such as missing
newlines in notes. In 0.9.0 RC10 with the new XSLT, the mind map does
not get opened at all.

Best regards,
Dan

Dear Dan,

recently, I published 0.9.0 RC11. IMHO, it solves every issue from

http://freemind.sourceforge.net/wiki/index.php/Finishing_0.9.0

Regarding the problem you described: the stack size is too small to
let the replacement function work properly (there are too many
recursions, that can't be reduced inside XSLT due to the nature of this
language).
So, the map gets converted
correctly, if you start the .bat (this includes -Xss8M) or on a Mac.
Otherwise, it is now opened without conversion, but with a loss of data
and an error message in the status bar.
Can you integrate the stack option into the freemind.c?

TIA, Chris

Am 08.11.10 15:52, schrieb Dan Polansky:
> Hello Chris,
>
> as regards 18. "Conversion from 0.8.0 to 0.9.0 drops indentation in
> notes" and the proposed bug fix by adjusting the file
> "freemind_version_updater.xslt":
>
> I have downloaded the XSLT, placed it into freemind.jar, and tested
> the result. It seems to do what it should, with one exception.
>
> What is does correctly: It converts indentation in notes correctly,
> and it converts "a b" as "a b" instead of "a&#160b", as it should.
>
> What is does erroneously: I have a test mind map "Notes and encryption
> after conversion", which it fails to load; it gives the exception
> "Error while parsing file:java.io.IOException: Stream closed" placed
> to a root node. I attach the test mind map "Notes and encryption after
> conversion" to this email. In 0.9.0 RC9, the test mind map gets opened
> without a failure, albeit with conversion mistakes such as missing
> newlines in notes. In 0.9.0 RC10 with the new XSLT, the mind map does
> not get opened at all.
>
> Best regards,
> Dan
>
>
> ------------------------------------------------------------------------------
> The Next 800 Companies to Lead America's Growth: New Video Whitepaper
> David G. Thomson, author of the best-selling book "Blueprint to a 
> Billion" shares his insights and actions to help propel your 
> business during the next growth cycle. Listen Now!
> http://p.sf.net/sfu/SAP-dev2dev
>
>
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hello Chris,

I have just closed three bugs, out of the five listed in Finishing 0.9.0.

Regarding the note conversion and the stack size: Increasing the stack
size of a thread to get the thing working makes me really nervous. It
seems it would be much better to implement the part that converts
notes in Java, and call the Java method from XSLT. If XSLT is not up
to the task, it should better get a little help from Java I think.

Regarding the bug with scripting, I can still reproduce problems. I
have posted a description of the latest behavior to the bug:

------------------------------------
16. Scripts do not work if file operations are not permitted
http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118

In 0.9.0 RC11, an attempt has been made to fix the problem. But the problem
persists, albeit in a slightly different form.

I have a mind map with a script '="hello"'.

When I press Alt + F8 the first time after loading the mind map, the
script gets correctly executed: the text of the node with the script gets
overwritten with "hello". This is an improvement over 0.9.0 RC10.

Then I rewrite the text of the node with "world", to be able to see the
effect of the script again.

Then I press Alt + F8 again, and the script does nothing; in addition, I
see the hourglass cursor signifying waiting, as if the operation were still
in progress.

When I repeatedly press Alt + F8, I get the same result: nothing happens.

Then, I cannot close FreeMind normally and have to end it using the task
manager instead, which means something got quite wrong.

I emphasize that I am on Windows Vista.
------------------------------------

What do you think causes the problems with scripting? What is the
solution that you are trying to implement?

Best regards,
Dan


On Sat, Nov 27, 2010 at 1:45 PM, Christian Foltin (GMX)
<christian.foltin@...> wrote:
> Dear Dan,
>
> recently, I published 0.9.0 RC11. IMHO, it solves every issue from
>
> http://freemind.sourceforge.net/wiki/index.php/Finishing_0.9.0
>
> Regarding the problem you described: the stack size is too small to
> let the replacement function work properly (there are too many recursions,
> that can't be reduced inside XSLT due to the nature of this language).
> So, the map gets converted
> correctly, if you start the .bat (this includes -Xss8M) or on a Mac.
> Otherwise, it is now opened without conversion, but with a loss of data and
> an error message in the status bar.
> Can you integrate the stack option into the freemind.c?
>
> TIA, Chris
>
> Am 08.11.10 15:52, schrieb Dan Polansky:
>
> Hello Chris,
>
> as regards 18. "Conversion from 0.8.0 to 0.9.0 drops indentation in
> notes" and the proposed bug fix by adjusting the file
> "freemind_version_updater.xslt":
>
> I have downloaded the XSLT, placed it into freemind.jar, and tested
> the result. It seems to do what it should, with one exception.
>
> What is does correctly: It converts indentation in notes correctly,
> and it converts "a b" as "a b" instead of "a&#160b", as it should.
>
> What is does erroneously: I have a test mind map "Notes and encryption
> after conversion", which it fails to load; it gives the exception
> "Error while parsing file:java.io.IOException: Stream closed" placed
> to a root node. I attach the test mind map "Notes and encryption after
> conversion" to this email. In 0.9.0 RC9, the test mind map gets opened
> without a failure, albeit with conversion mistakes such as missing
> newlines in notes. In 0.9.0 RC10 with the new XSLT, the mind map does
> not get opened at all.
>
> Best regards,
> Dan
>
>
> ------------------------------------------------------------------------------
> The Next 800 Companies to Lead America's Growth: New Video Whitepaper
> David G. Thomson, author of the best-selling book "Blueprint to a
> Billion" shares his insights and actions to help propel your
> business during the next growth cycle. Listen Now!
> http://p.sf.net/sfu/SAP-dev2dev
>
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
>

Hello Chris,

I have discovered another regression bug and have posted a bug fix to
the bug report:

19. Find next fails to end the search
http://sourceforge.net/tracker/?func=detail&aid=3123873&group_id=7118&atid=107118

It is quick to fix and does not require any investigation on your side.

Best regards,
Dan

Hello Chris,

I have had a look at the scripting bug, and have proposed a bug fix,
one that you need to review, though. I have posted the fix to the bug
report:

Scripts do not work if file operations are not permitted
http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118

The last comment to the bug report, for your convenience:

I get the undesirable behavior described with 0.9.0 RC11 removed by
performing the following change in ScriptingEngine.executeScript method:

// setting the same security manager the second time causes it to be
// removed.
//securityManager.setFinalSecurityManager(scriptingSecurityManager); //
Commented out. --Dan
securityManager.setFinalSecurityManager(null); // Inserted: be explicit
about setting it to null. --Dan

At that location, the security manager should be disabled; if it is not,
it causes problems with loading of some classes later. Setting an object
two times to disable something seems like a bug-prone idea. I am setting
the final security manager as null, as that is the intended effect. I am
not the author of the code, so I am not sure whether it matches the
intention.

As regards the method securityManager.setFinalSecurityManager, I do not
understand why it is implemented the way it is:

public void setFinalSecurityManager(SecurityManager
pFinalSecurityManager) {
if(pFinalSecurityManager == mFinalSecurityManager) {
mFinalSecurityManager = null;
return;
}
if(mFinalSecurityManager != null) {
throw new SecurityException("There is a SecurityManager installed
already.");
}
mFinalSecurityManager = pFinalSecurityManager;
}

I would implement the method as follows:

public void setFinalSecurityManager(SecurityManager pFinalSecurityManager)
{
mFinalSecurityManager = pFinalSecurityManager;
}

The method should not worry about whether there is already a security
manager set. When the caller wants to get the security manager removed, the
caller should be very explicit about it, by passing "null".

--Dan

Hello Chris,

scripting: I have updated the bug report with a further comment:

Further comment to my previous comment: It seems that the thing with
setting the security manager two times to get it removed is intentional;
there is a note to that effect at the top of FreeMindSecurityManager class.

The key thing is that, after the recent bug fix, the security manager is
being removed twice (as it should not): once in the method "evaluate", and
once before the line "System.setOut(oldOut)". It seems that it should
suffice that the line
"securityManager.setFinalSecurityManager(scriptingSecurityManager);" before
"System.setOut(oldOut)" is commented out.

http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118

Best regards,
Dan


On Wed, Dec 1, 2010 at 12:24 AM, Dan Polansky <dan.polansky@...> wrote:
> Hello Chris,
>
> I have had a look at the scripting bug, and have proposed a bug fix,
> one that you need to review, though. I have posted the fix to the bug
> report:
>
> Scripts do not work if file operations are not permitted
> http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118
>
> The last comment to the bug report, for your convenience:
>
> I get the undesirable behavior described with 0.9.0 RC11 removed by
> performing the following change in ScriptingEngine.executeScript method:
>
> // setting the same security manager the second time causes it to be
> // removed.
> //securityManager.setFinalSecurityManager(scriptingSecurityManager); //
> Commented out. --Dan
> securityManager.setFinalSecurityManager(null); // Inserted: be explicit
> about setting it to null. --Dan
>
> At that location, the security manager should be disabled; if it is not,
> it causes problems with loading of some classes later. Setting an object
> two times to disable something seems like a bug-prone idea. I am setting
> the final security manager as null, as that is the intended effect. I am
> not the author of the code, so I am not sure whether it matches the
> intention.
>
> As regards the method securityManager.setFinalSecurityManager, I do not
> understand why it is implemented the way it is:
>
> public void setFinalSecurityManager(SecurityManager
> pFinalSecurityManager) {
> if(pFinalSecurityManager == mFinalSecurityManager) {
> mFinalSecurityManager = null;
> return;
> }
> if(mFinalSecurityManager != null) {
> throw new SecurityException("There is a SecurityManager installed
> already.");
> }
> mFinalSecurityManager = pFinalSecurityManager;
> }
>
> I would implement the method as follows:
>
> public void setFinalSecurityManager(SecurityManager pFinalSecurityManager)
> {
> mFinalSecurityManager = pFinalSecurityManager;
> }
>
> The method should not worry about whether there is already a security
> manager set. When the caller wants to get the security manager removed, the
> caller should be very explicit about it, by passing "null".
>
> --Dan
>

Hi Dan,

recently, I published 0.9.0 RC12 which solves every known issue (IMHO).
Even the string conversion has been moved from XSLT to a java method
without memory problems.
Moreover, commons-lang was removed.

I hope, that you are able to test it, soon.

Best regards, Chris


Am 01.12.10 09:05, schrieb Dan Polansky:
> Hello Chris,
>
> scripting: I have updated the bug report with a further comment:
>
> Further comment to my previous comment: It seems that the thing with
> setting the security manager two times to get it removed is intentional;
> there is a note to that effect at the top of FreeMindSecurityManager class.
>
> The key thing is that, after the recent bug fix, the security manager is
> being removed twice (as it should not): once in the method "evaluate", and
> once before the line "System.setOut(oldOut)". It seems that it should
> suffice that the line
> "securityManager.setFinalSecurityManager(scriptingSecurityManager);" before
> "System.setOut(oldOut)" is commented out.
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118
>
> Best regards,
> Dan
>
>
> On Wed, Dec 1, 2010 at 12:24 AM, Dan Polansky <dan.polansky@...> wrote:
>> Hello Chris,
>>
>> I have had a look at the scripting bug, and have proposed a bug fix,
>> one that you need to review, though. I have posted the fix to the bug
>> report:
>>
>> Scripts do not work if file operations are not permitted
>> http://sourceforge.net/tracker/index.php?func=detail&aid=2789907&group_id=7118&atid=107118
>>
>> The last comment to the bug report, for your convenience:
>>
>> I get the undesirable behavior described with 0.9.0 RC11 removed by
>> performing the following change in ScriptingEngine.executeScript method:
>>
>> // setting the same security manager the second time causes it to be
>> // removed.
>> //securityManager.setFinalSecurityManager(scriptingSecurityManager); //
>> Commented out. --Dan
>> securityManager.setFinalSecurityManager(null); // Inserted: be explicit
>> about setting it to null. --Dan
>>
>> At that location, the security manager should be disabled; if it is not,
>> it causes problems with loading of some classes later. Setting an object
>> two times to disable something seems like a bug-prone idea. I am setting
>> the final security manager as null, as that is the intended effect. I am
>> not the author of the code, so I am not sure whether it matches the
>> intention.
>>
>> As regards the method securityManager.setFinalSecurityManager, I do not
>> understand why it is implemented the way it is:
>>
>> public void setFinalSecurityManager(SecurityManager
>> pFinalSecurityManager) {
>> if(pFinalSecurityManager == mFinalSecurityManager) {
>> mFinalSecurityManager = null;
>> return;
>> }
>> if(mFinalSecurityManager != null) {
>> throw new SecurityException("There is a SecurityManager installed
>> already.");
>> }
>> mFinalSecurityManager = pFinalSecurityManager;
>> }
>>
>> I would implement the method as follows:
>>
>> public void setFinalSecurityManager(SecurityManager pFinalSecurityManager)
>> {
>> mFinalSecurityManager = pFinalSecurityManager;
>> }
>>
>> The method should not worry about whether there is already a security
>> manager set. When the caller wants to get the security manager removed, the
>> caller should be very explicit about it, by passing "null".
>>
>> --Dan
>>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>

Hello Chris,

I have closed two bugs fixed in 0.9.0 RC12.

There is still at least one issue with the conversion, newly so:

Each converted note now starts with the following text:

<html xmlns:HtmlTools="xalan://freemind.main.HtmlTools"><head/>

This seems to be a side effect, which should be removed. This was not
there in 0.9.0 RC10 and seems undesirable. This "xalan" text is not
only shown in the source code pane but
also saved to the mind map file.

http://sourceforge.net/tracker/index.php?func=detail&aid=3096369&group_id=7118&atid=107118

Another thing: in RC11 you have introduced some quiet failure when
some issues occur duing the conversion. This failure is really quiet
and inconspicuous, which is not good. The behavior of RC10 was much
better IMHO: when there was a conversion problem, FreeMind failed as
conspicuously as possible without crashing. In RC11, FreeMind says in
the status line "Error on conversion. Continue without conversion.
Some elements may be lost!", but this is really easy to overlook; at
first, I have overlooked this message and only wondered why a
converted mind map has missing notes. The thing is, the status line is
quickly erased: it suffices that I select another node and the status
line gets erased. I think it would really be much better to revert to
RC10 behavior in this regard. The conspicuousness of the conversion
problem in RC10 was good: it helped me discover a problem that I would
otherwise be much more likely to overlook. The conversion problem was
due to the stack problem, one that should no longer be there.

Best regards,
Dan


On Sat, Dec 4, 2010 at 10:38 PM, Christian Foltin (GMX)
<christian.foltin@...> wrote:
>  Hi Dan,
>
> recently, I published 0.9.0 RC12 which solves every known issue (IMHO).
> Even the string conversion has been moved from XSLT to a java method
> without memory problems.
> Moreover, commons-lang was removed.
>
> I hope, that you are able to test it, soon.
>
> Best regards, Chris

Hello Chris,

when we are at the HTML text of converted notes, a minor issue that I
estimate is easy to fix: The text of notes contains '<p align="left">'
instead of '<p>'. What is this good for? Can this be removed so that
the notes contain plain "<p>"? I do not see any visible difference of
adding 'align="left"'; it seems to be needless cruft. If this is risky
or difficult to fix, then just forget this email. I just thought this
could be handled in one batch of work with the removal of
'xmlns:HtmlTools="xalan://freemind.main.HtmlTools"'.

Best regards,
Dan


On Sun, Dec 5, 2010 at 11:57 AM, Dan Polansky <dan.polansky@...> wrote:
> Hello Chris,
>
> I have closed two bugs fixed in 0.9.0 RC12.
>
> There is still at least one issue with the conversion, newly so:
>
> Each converted note now starts with the following text:
>
> <html xmlns:HtmlTools="xalan://freemind.main.HtmlTools"><head/>
>
> This seems to be a side effect, which should be removed. This was not
> there in 0.9.0 RC10 and seems undesirable. This "xalan" text is not
> only shown in the source code pane but
> also saved to the mind map file.
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=3096369&group_id=7118&atid=107118
>
> Another thing: in RC11 you have introduced some quiet failure when
> some issues occur duing the conversion. This failure is really quiet
> and inconspicuous, which is not good. The behavior of RC10 was much
> better IMHO: when there was a conversion problem, FreeMind failed as
> conspicuously as possible without crashing. In RC11, FreeMind says in
> the status line "Error on conversion. Continue without conversion.
> Some elements may be lost!", but this is really easy to overlook; at
> first, I have overlooked this message and only wondered why a
> converted mind map has missing notes. The thing is, the status line is
> quickly erased: it suffices that I select another node and the status
> line gets erased. I think it would really be much better to revert to
> RC10 behavior in this regard. The conspicuousness of the conversion
> problem in RC10 was good: it helped me discover a problem that I would
> otherwise be much more likely to overlook. The conversion problem was
> due to the stack problem, one that should no longer be there.
>
> Best regards,
> Dan
>
>
> On Sat, Dec 4, 2010 at 10:38 PM, Christian Foltin (GMX)
> <christian.foltin@...> wrote:
>>  Hi Dan,
>>
>> recently, I published 0.9.0 RC12 which solves every known issue (IMHO).
>> Even the string conversion has been moved from XSLT to a java method
>> without memory problems.
>> Moreover, commons-lang was removed.
>>
>> I hope, that you are able to test it, soon.
>>
>> Best regards, Chris
>

Hi Dan,

the <p align...> comes from the way, SimplyHTML stores everything.
Here, there is a note with content "bla" stored:

<node CREATED="1291927734954" ID="ID_1326457101"
MODIFIED="1291927740859" POSITION="left" TEXT="asdfadsf">
<richcontent TYPE="NOTE"><html>
  <head>
   
  </head>
  <body>
    <p>
      bla
    </p>
  </body>
</html>
</richcontent>
</node>

In order to have the same in the converted notes, the align was added by me.

Best regards, Chris

Am 05.12.10 12:09, schrieb Dan Polansky:
> Hello Chris,
>
> when we are at the HTML text of converted notes, a minor issue that I
> estimate is easy to fix: The text of notes contains '<p align="left">'
> instead of '<p>'. What is this good for? Can this be removed so that
> the notes contain plain "<p>"? I do not see any visible difference of
> adding 'align="left"'; it seems to be needless cruft. If this is risky
> or difficult to fix, then just forget this email. I just thought this
> could be handled in one batch of work with the removal of
> 'xmlns:HtmlTools="xalan://freemind.main.HtmlTools"'.
>
> Best regards,
> Dan
>
>
> On Sun, Dec 5, 2010 at 11:57 AM, Dan Polansky <dan.polansky@...> wrote:
>> Hello Chris,
>>
>> I have closed two bugs fixed in 0.9.0 RC12.
>>
>> There is still at least one issue with the conversion, newly so:
>>
>> Each converted note now starts with the following text:
>>
>> <html xmlns:HtmlTools="xalan://freemind.main.HtmlTools"><head/>
>>
>> This seems to be a side effect, which should be removed. This was not
>> there in 0.9.0 RC10 and seems undesirable. This "xalan" text is not
>> only shown in the source code pane but
>> also saved to the mind map file.
>>
>> http://sourceforge.net/tracker/index.php?func=detail&aid=3096369&group_id=7118&atid=107118
>>
>> Another thing: in RC11 you have introduced some quiet failure when
>> some issues occur duing the conversion. This failure is really quiet
>> and inconspicuous, which is not good. The behavior of RC10 was much
>> better IMHO: when there was a conversion problem, FreeMind failed as
>> conspicuously as possible without crashing. In RC11, FreeMind says in
>> the status line "Error on conversion. Continue without conversion.
>> Some elements may be lost!", but this is really easy to overlook; at
>> first, I have overlooked this message and only wondered why a
>> converted mind map has missing notes. The thing is, the status line is
>> quickly erased: it suffices that I select another node and the status
>> line gets erased. I think it would really be much better to revert to
>> RC10 behavior in this regard. The conspicuousness of the conversion
>> problem in RC10 was good: it helped me discover a problem that I would
>> otherwise be much more likely to overlook. The conversion problem was
>> due to the stack problem, one that should no longer be there.
>>
>> Best regards,
>> Dan
>>
>>
>> On Sat, Dec 4, 2010 at 10:38 PM, Christian Foltin (GMX)
>> <christian.foltin@...> wrote:
>>>  Hi Dan,
>>>
>>> recently, I published 0.9.0 RC12 which solves every known issue (IMHO).
>>> Even the string conversion has been moved from XSLT to a java method
>>> without memory problems.
>>> Moreover, commons-lang was removed.
>>>
>>> I hope, that you are able to test it, soon.
>>>
>>> Best regards, Chris
>>
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly 
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus 
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Dear Dan,

both is fixed in CVS. The first, you can verify by exchanging the xslt
script.

Best regards,

Chris

Am 05.12.10 11:57, schrieb Dan Polansky:
> Hello Chris,
>
> I have closed two bugs fixed in 0.9.0 RC12.
>
> There is still at least one issue with the conversion, newly so:
>
> Each converted note now starts with the following text:
>
> <html xmlns:HtmlTools="xalan://freemind.main.HtmlTools"><head/>
>
> This seems to be a side effect, which should be removed. This was not
> there in 0.9.0 RC10 and seems undesirable. This "xalan" text is not
> only shown in the source code pane but
> also saved to the mind map file.
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=3096369&group_id=7118&atid=107118
>
> Another thing: in RC11 you have introduced some quiet failure when
> some issues occur duing the conversion. This failure is really quiet
> and inconspicuous, which is not good. The behavior of RC10 was much
> better IMHO: when there was a conversion problem, FreeMind failed as
> conspicuously as possible without crashing. In RC11, FreeMind says in
> the status line "Error on conversion. Continue without conversion.
> Some elements may be lost!", but this is really easy to overlook; at
> first, I have overlooked this message and only wondered why a
> converted mind map has missing notes. The thing is, the status line is
> quickly erased: it suffices that I select another node and the status
> line gets erased. I think it would really be much better to revert to
> RC10 behavior in this regard. The conspicuousness of the conversion
> problem in RC10 was good: it helped me discover a problem that I would
> otherwise be much more likely to overlook. The conversion problem was
> due to the stack problem, one that should no longer be there.
>
> Best regards,
> Dan
>
>
> On Sat, Dec 4, 2010 at 10:38 PM, Christian Foltin (GMX)
> <christian.foltin@...> wrote:
>>  Hi Dan,
>>
>> recently, I published 0.9.0 RC12 which solves every known issue (IMHO).
>> Even the string conversion has been moved from XSLT to a java method
>> without memory problems.
>> Moreover, commons-lang was removed.
>>
>> I hope, that you are able to test it, soon.
>>
>> Best regards, Chris
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly 
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus 
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hello Chris,

I have tested your changes by updating my version of FreeMind 0.9.0 in
Eclipse from CVS, and running FreeMind from Eclipse.

Re removing of the "Xalan" string: works fine.

Re conspicous failure: it works. I have tested the thing by placing
"throw new Exception("Artificial exception");" before the line
"successful = true" in the class "TransformerRunnable" in Tools.java.

Re '<p align="left">': I do not understand your explanation. There is
no '<p align="left">' in the HTML source of rich text long nodes, so I
do not see why there should be '<p align="left">' in the HTML source
of notes. When you create a long plain text node, then switch it to
rich text, and then look at the HTML source, there is no
'align="left"'; and that is how it should be, if you ask me. I do not
see any useful function that 'align="left"' serves, nor do I see any
technical necessity for it being there. I have looked at HTML
paragraph tags generated by MediaWiki, and they are plain ones, having
no 'align="left"'. So no matter how I think about it, I do not
understand the need.

Best regards,
Dan

Hi Dan,

to end up this discussion, I've removed the align=left in the CVS
version of the updater script.

I you don't mind, I'm going to release the 0.9.0 version.
Do you have any important objections?

Best regards,

Chris

Am 10.12.10 19:55, schrieb Dan Polansky:
> Hello Chris,
>
> I have tested your changes by updating my version of FreeMind 0.9.0 in
> Eclipse from CVS, and running FreeMind from Eclipse.
>
> Re removing of the "Xalan" string: works fine.
>
> Re conspicous failure: it works. I have tested the thing by placing
> "throw new Exception("Artificial exception");" before the line
> "successful = true" in the class "TransformerRunnable" in Tools.java.
>
> Re '<p align="left">': I do not understand your explanation. There is
> no '<p align="left">' in the HTML source of rich text long nodes, so I
> do not see why there should be '<p align="left">' in the HTML source
> of notes. When you create a long plain text node, then switch it to
> rich text, and then look at the HTML source, there is no
> 'align="left"'; and that is how it should be, if you ask me. I do not
> see any useful function that 'align="left"' serves, nor do I see any
> technical necessity for it being there. I have looked at HTML
> paragraph tags generated by MediaWiki, and they are plain ones, having
> no 'align="left"'. So no matter how I think about it, I do not
> understand the need.
>
> Best regards,
> Dan
>
> ------------------------------------------------------------------------------
> Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
> new data types, scalar functions, improved concurrency, built-in packages, 
> OCI, SQL*Plus, data movement tools, best practices and more.
> http://p.sf.net/sfu/oracle-sfdev2dev 
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>

Hello Chris,

thank you for your removing align=left.

>From the point of view of a clean process, there should IMHO better be
a version 0.9.0 RC13. Then I can close the bugs in the bug tracker
against this version, and after a week or so after the release of
0.9.0 RC13, a final version can be released that is identical to 0.9.0
RC13.

My understanding of a good process of final release is that the the
final release should be identical to the last published RC version. As
our recent experience shows, an RC version sometimes contains bugs
that were thought to be fixed in the RC version, or contains new bugs
or issues. I do not really think that there are going to be any
problems with RC13, but my estimation can turn wrong, hence it would
be better to keep this process, I think.

Best regards,
Dan


On Fri, Dec 17, 2010 at 9:51 PM, Christian Foltin (GMX)
<christian.foltin@...> wrote:
>  Hi Dan,
>
> to end up this discussion, I've removed the align=left in the CVS
> version of the updater script.
>
> I you don't mind, I'm going to release the 0.9.0 version.
> Do you have any important objections?
>
> Best regards,
>
> Chris
>
> Am 10.12.10 19:55, schrieb Dan Polansky:
>> Hello Chris,
>>
>> I have tested your changes by updating my version of FreeMind 0.9.0 in
>> Eclipse from CVS, and running FreeMind from Eclipse.
>>
>> Re removing of the "Xalan" string: works fine.
>>
>> Re conspicous failure: it works. I have tested the thing by placing
>> "throw new Exception("Artificial exception");" before the line
>> "successful = true" in the class "TransformerRunnable" in Tools.java.
>>
>> Re '<p align="left">': I do not understand your explanation. There is
>> no '<p align="left">' in the HTML source of rich text long nodes, so I
>> do not see why there should be '<p align="left">' in the HTML source
>> of notes. When you create a long plain text node, then switch it to
>> rich text, and then look at the HTML source, there is no
>> 'align="left"'; and that is how it should be, if you ask me. I do not
>> see any useful function that 'align="left"' serves, nor do I see any
>> technical necessity for it being there. I have looked at HTML
>> paragraph tags generated by MediaWiki, and they are plain ones, having
>> no 'align="left"'. So no matter how I think about it, I do not
>> understand the need.
>>
>> Best regards,
>> Dan

Hi Dan,

done, although ...

Best regards, Chris

Am 18.12.10 07:54, schrieb Dan Polansky:
> Hello Chris,
>
> thank you for your removing align=left.
>
> From the point of view of a clean process, there should IMHO better be
> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker
> against this version, and after a week or so after the release of
> 0.9.0 RC13, a final version can be released that is identical to 0.9.0
> RC13.
>
> My understanding of a good process of final release is that the the
> final release should be identical to the last published RC version. As
> our recent experience shows, an RC version sometimes contains bugs
> that were thought to be fixed in the RC version, or contains new bugs
> or issues. I do not really think that there are going to be any
> problems with RC13, but my estimation can turn wrong, hence it would
> be better to keep this process, I think.
>
> Best regards,
> Dan
>

Hello Chris,

unfortunately, I have discovered a conversion bug that was already
fixed in 0.9.0 RC5 and reappeared in 0.9.0 RC11, and persist in 0.9.0
RC13 (the bug is not there in 0.9.0 RC10). I am sorry I did not
discover the bug earlier; possibly, I have failed to notice the
problem because of the too quiet failure on conversion to 0.9.0 that
was introduced in 0.9.0 RC11 and removed in 0.9.0 RC13.

21. Byte-order mark for UTF-8 (BOM) produces failure to load
http://sourceforge.net/tracker/?func=detail&aid=3141875&group_id=7118&atid=107118

Best regards,
Dan


On Sun, Dec 19, 2010 at 10:09 PM, Christian Foltin (GMX)
<christian.foltin@...> wrote:
>  Hi Dan,
>
> done, although ...
>
> Best regards, Chris
>
> Am 18.12.10 07:54, schrieb Dan Polansky:
>> Hello Chris,
>>
>> thank you for your removing align=left.
>>
>> From the point of view of a clean process, there should IMHO better be
>> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker
>> against this version, and after a week or so after the release of
>> 0.9.0 RC13, a final version can be released that is identical to 0.9.0
>> RC13.
>>
>> My understanding of a good process of final release is that the the
>> final release should be identical to the last published RC version. As
>> our recent experience shows, an RC version sometimes contains bugs
>> that were thought to be fixed in the RC version, or contains new bugs
>> or issues. I do not really think that there are going to be any
>> problems with RC13, but my estimation can turn wrong, hence it would
>> be better to keep this process, I think.
>>
>> Best regards,
>> Dan
>>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>

An afterthought: my error: I have failed to notice the problem because
I have failed to test Cars.mm in the first place. When I open Cars.mm
in 0.9.0 RC11, the failure is conspicuous. I have no clue why I have
omitted Cars.mm from the test. --Dan


On Wed, Dec 22, 2010 at 8:21 PM, Dan Polansky <dan.polansky@...> wrote:
> Hello Chris,
>
> unfortunately, I have discovered a conversion bug that was already
> fixed in 0.9.0 RC5 and reappeared in 0.9.0 RC11, and persist in 0.9.0
> RC13 (the bug is not there in 0.9.0 RC10). I am sorry I did not
> discover the bug earlier; possibly, I have failed to notice the
> problem because of the too quiet failure on conversion to 0.9.0 that
> was introduced in 0.9.0 RC11 and removed in 0.9.0 RC13.
>
> 21. Byte-order mark for UTF-8 (BOM) produces failure to load
> http://sourceforge.net/tracker/?func=detail&aid=3141875&group_id=7118&atid=107118
>
> Best regards,
> Dan
>
>
> On Sun, Dec 19, 2010 at 10:09 PM, Christian Foltin (GMX)
> <christian.foltin@...> wrote:
>>  Hi Dan,
>>
>> done, although ...
>>
>> Best regards, Chris
>>
>> Am 18.12.10 07:54, schrieb Dan Polansky:
>>> Hello Chris,
>>>
>>> thank you for your removing align=left.
>>>
>>> From the point of view of a clean process, there should IMHO better be
>>> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker
>>> against this version, and after a week or so after the release of
>>> 0.9.0 RC13, a final version can be released that is identical to 0.9.0
>>> RC13.
>>>
>>> My understanding of a good process of final release is that the the
>>> final release should be identical to the last published RC version. As
>>> our recent experience shows, an RC version sometimes contains bugs
>>> that were thought to be fixed in the RC version, or contains new bugs
>>> or issues. I do not really think that there are going to be any
>>> problems with RC13, but my estimation can turn wrong, hence it would
>>> be better to keep this process, I think.
>>>
>>> Best regards,
>>> Dan
>>>
>>
>> ------------------------------------------------------------------------------
>> Lotusphere 2011
>> Register now for Lotusphere 2011 and learn how
>> to connect the dots, take your collaborative environment
>> to the next level, and enter the era of Social Business.
>> http://p.sf.net/sfu/lotusphere-d2d
>> _______________________________________________
>> Freemind-developer mailing list
>> Freemind-developer@...
>> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>>
>

Dear Dan,

we've encountered a long known java bug:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058

I've fixed it the usual way and, currently, RC14 is publishing on SF.
(By the way, now some other (UTF) encodings should be supported, too.)

HTH, Chris

PS: Mery christmas!

Am 22.12.10 20:21, schrieb Dan Polansky:
> Hello Chris,
>
> unfortunately, I have discovered a conversion bug that was already
> fixed in 0.9.0 RC5 and reappeared in 0.9.0 RC11, and persist in 0.9.0
> RC13 (the bug is not there in 0.9.0 RC10). I am sorry I did not
> discover the bug earlier; possibly, I have failed to notice the
> problem because of the too quiet failure on conversion to 0.9.0 that
> was introduced in 0.9.0 RC11 and removed in 0.9.0 RC13.
>
> 21. Byte-order mark for UTF-8 (BOM) produces failure to load
> http://sourceforge.net/tracker/?func=detail&aid=3141875&group_id=7118&atid=107118
>
> Best regards,
> Dan
>
>
> On Sun, Dec 19, 2010 at 10:09 PM, Christian Foltin (GMX)
> <christian.foltin@...> wrote:
>>  Hi Dan,
>>
>> done, although ...
>>
>> Best regards, Chris
>>
>> Am 18.12.10 07:54, schrieb Dan Polansky:
>>> Hello Chris,
>>>
>>> thank you for your removing align=left.
>>>
>>> From the point of view of a clean process, there should IMHO better be
>>> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker
>>> against this version, and after a week or so after the release of
>>> 0.9.0 RC13, a final version can be released that is identical to 0.9.0
>>> RC13.
>>>
>>> My understanding of a good process of final release is that the the
>>> final release should be identical to the last published RC version. As
>>> our recent experience shows, an RC version sometimes contains bugs
>>> that were thought to be fixed in the RC version, or contains new bugs
>>> or issues. I do not really think that there are going to be any
>>> problems with RC13, but my estimation can turn wrong, hence it would
>>> be better to keep this process, I think.
>>>
>>> Best regards,
>>> Dan
>>>
>>
>> ------------------------------------------------------------------------------
>> Lotusphere 2011
>> Register now for Lotusphere 2011 and learn how
>> to connect the dots, take your collaborative environment
>> to the next level, and enter the era of Social Business.
>> http://p.sf.net/sfu/lotusphere-d2d
>> _______________________________________________
>> Freemind-developer mailing list
>> Freemind-developer@...
>> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>>
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and, 
> should the need arise, upgrade to a full multi-node Oracle RAC database 
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hello Chris,

thank you for the rapid bug fix! I have tested 0.9.0 RC14 against all
the mind maps that I use to test the conversion from 0.8.1 to 0.9.0,
and everything looks good, ready for the final release. Nonetheless,
please give me some more time to once more thoroughly test 0.9.0 RC14;
this test that I have made has been hasty and without my full
attention, performed under time pressure.

Merry Christmas!

Best regards,
Dan


On Fri, Dec 24, 2010 at 12:08 AM, Christian Foltin (GMX)
<christian.foltin@...> wrote:
>  Dear Dan,
>
> we've encountered a long known java bug:
>
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058
>
> I've fixed it the usual way and, currently, RC14 is publishing on SF.
> (By the way, now some other (UTF) encodings should be supported, too.)
>
> HTH, Chris
>
> PS: Mery christmas!
>
> Am 22.12.10 20:21, schrieb Dan Polansky:
>> Hello Chris,
>>
>> unfortunately, I have discovered a conversion bug that was already
>> fixed in 0.9.0 RC5 and reappeared in 0.9.0 RC11, and persist in 0.9.0
>> RC13 (the bug is not there in 0.9.0 RC10). I am sorry I did not
>> discover the bug earlier; possibly, I have failed to notice the
>> problem because of the too quiet failure on conversion to 0.9.0 that
>> was introduced in 0.9.0 RC11 and removed in 0.9.0 RC13.
>>
>> 21. Byte-order mark for UTF-8 (BOM) produces failure to load
>> http://sourceforge.net/tracker/?func=detail&aid=3141875&group_id=7118&atid=107118
>>
>> Best regards,
>> Dan
>>
>>
>> On Sun, Dec 19, 2010 at 10:09 PM, Christian Foltin (GMX)
>> <christian.foltin@...> wrote:
>>>  Hi Dan,
>>>
>>> done, although ...
>>>
>>> Best regards, Chris
>>>
>>> Am 18.12.10 07:54, schrieb Dan Polansky:
>>>> Hello Chris,
>>>>
>>>> thank you for your removing align=left.
>>>>
>>>> From the point of view of a clean process, there should IMHO better be
>>>> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker
>>>> against this version, and after a week or so after the release of
>>>> 0.9.0 RC13, a final version can be released that is identical to 0.9.0
>>>> RC13.
>>>>
>>>> My understanding of a good process of final release is that the the
>>>> final release should be identical to the last published RC version. As
>>>> our recent experience shows, an RC version sometimes contains bugs
>>>> that were thought to be fixed in the RC version, or contains new bugs
>>>> or issues. I do not really think that there are going to be any
>>>> problems with RC13, but my estimation can turn wrong, hence it would
>>>> be better to keep this process, I think.
>>>>
>>>> Best regards,
>>>> Dan
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Lotusphere 2011
>>> Register now for Lotusphere 2011 and learn how
>>> to connect the dots, take your collaborative environment
>>> to the next level, and enter the era of Social Business.
>>> http://p.sf.net/sfu/lotusphere-d2d
>>> _______________________________________________
>>> Freemind-developer mailing list
>>> Freemind-developer@...
>>> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>>>
>>
>> ------------------------------------------------------------------------------
>> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
>> to consolidate database storage, standardize their database environment, and,
>> should the need arise, upgrade to a full multi-node Oracle RAC database
>> without downtime or disruption
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Freemind-developer mailing list
>> Freemind-developer@...
>> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>

Hello Chris,

I have found two more bugs related to data loss, by extending a test
mind map with even more cases in which something could go wrong in
conversion from 0.8.0 to 0.9.0.

22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links
http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118

23. Drag and drop of two connected nodes drops arrow link
http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118

I am sorry, again, that I did not discover these bug earlier.
Unfortunately, my brain seems to be much more eager to think about
what can go wrong when there are no more bugs on the list to be fixed.

Best regards,
Dan

Hi Dan,

sorry, if we continue like this, we'll never publish 0.9.0.

IMHO, these bugs are not that dramatic.
Let's postpone them.

Best regards, Chris

Am 27.12.10 10:33, schrieb Dan Polansky:
> Hello Chris,
>
> I have found two more bugs related to data loss, by extending a test
> mind map with even more cases in which something could go wrong in
> conversion from 0.8.0 to 0.9.0.
>
> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links
> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118
>
> 23. Drag and drop of two connected nodes drops arrow link
> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118
>
> I am sorry, again, that I did not discover these bug earlier.
> Unfortunately, my brain seems to be much more eager to think about
> what can go wrong when there are no more bugs on the list to be fixed.
>
> Best regards,
> Dan
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and, 
> should the need arise, upgrade to a full multi-node Oracle RAC database 
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>

Hello Chris,

the ultimate decision is up to you, as you are the project director.
Whatever I decide or propose, you can override it. Nonetheless, within
the constrained and subordinate role of the unofficial quality manager
of FreeMind, I feel uncomfortable giving go ahead to a version that
contains known bugs that lead to data loss.

Both bugs 22 and 23 are related to data loss. Especially bug 22 is
rather insidious, easy to be overlooked by the affected user. Bug 23
is rather unlikely to be overlooked by the user, so it could really be
postponed for 0.9.1, but it is a data loss bug nonetheless.

I am fully aware of the time pressure to release final FreeMind 0.9.0,
which is why I do not report here some regression bugs that are less
serious. From where I am standing, we seem to be really close to final
release.

Best regards,
Dan


On Mon, Dec 27, 2010 at 5:53 PM, Christian Foltin (GMX)
<christian.foltin@...> wrote:
>  Hi Dan,
>
> sorry, if we continue like this, we'll never publish 0.9.0.
>
> IMHO, these bugs are not that dramatic.
> Let's postpone them.
>
> Best regards, Chris
>
> Am 27.12.10 10:33, schrieb Dan Polansky:
>> Hello Chris,
>>
>> I have found two more bugs related to data loss, by extending a test
>> mind map with even more cases in which something could go wrong in
>> conversion from 0.8.0 to 0.9.0.
>>
>> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links
>> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118
>>
>> 23. Drag and drop of two connected nodes drops arrow link
>> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118
>>
>> I am sorry, again, that I did not discover these bug earlier.
>> Unfortunately, my brain seems to be much more eager to think about
>> what can go wrong when there are no more bugs on the list to be fixed.
>>
>> Best regards,
>> Dan

Dear Dan,

bug 22 is fixed in CVS. Bug 23 is not going to be fixed immediately as
this involves lot of work.
It is definitively left for 0.9.1.

Best regards,

Chris.

PS: Do you get the CVS version on your own?


Am 27.12.10 20:22, schrieb Dan Polansky:
> Hello Chris,
>
> the ultimate decision is up to you, as you are the project director.
> Whatever I decide or propose, you can override it. Nonetheless, within
> the constrained and subordinate role of the unofficial quality manager
> of FreeMind, I feel uncomfortable giving go ahead to a version that
> contains known bugs that lead to data loss.
>
> Both bugs 22 and 23 are related to data loss. Especially bug 22 is
> rather insidious, easy to be overlooked by the affected user. Bug 23
> is rather unlikely to be overlooked by the user, so it could really be
> postponed for 0.9.1, but it is a data loss bug nonetheless.
>
> I am fully aware of the time pressure to release final FreeMind 0.9.0,
> which is why I do not report here some regression bugs that are less
> serious. From where I am standing, we seem to be really close to final
> release.
>
> Best regards,
> Dan
>
>
> On Mon, Dec 27, 2010 at 5:53 PM, Christian Foltin (GMX)
> <christian.foltin@...> wrote:
>>  Hi Dan,
>>
>> sorry, if we continue like this, we'll never publish 0.9.0.
>>
>> IMHO, these bugs are not that dramatic.
>> Let's postpone them.
>>
>> Best regards, Chris
>>
>> Am 27.12.10 10:33, schrieb Dan Polansky:
>>> Hello Chris,
>>>
>>> I have found two more bugs related to data loss, by extending a test
>>> mind map with even more cases in which something could go wrong in
>>> conversion from 0.8.0 to 0.9.0.
>>>
>>> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links
>>> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118
>>>
>>> 23. Drag and drop of two connected nodes drops arrow link
>>> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118
>>>
>>> I am sorry, again, that I did not discover these bug earlier.
>>> Unfortunately, my brain seems to be much more eager to think about
>>> what can go wrong when there are no more bugs on the list to be fixed.
>>>
>>> Best regards,
>>> Dan
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and, 
> should the need arise, upgrade to a full multi-node Oracle RAC database 
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hello Chris,

I have just tested 0.9.0 RC15 from CVS against the bug 22; the test
showed that bug 22 is fixed. Thank you.

Postponing fixing bug 23 to 0.9.1 is suboptimal but acceptable IMHO.
Given that you say that fixing the bug is too much work, given that
the bug is fairly easy to spot (hard to overlook) for the user, and
given how late 0.9.0 already is, it seems excusable to leave the bug
in the final release in spite of the bug being a data loss one.

I know of no other serious bugs that block final release 0.9.0. I
would have one last thorough look at 0.9.0 RC15 after it is released
at SourceForge, and then I would give it a go ahead.

Best regards,
Dan


On Sun, Jan 9, 2011 at 10:24 PM, Christian Foltin (GMX)
<christian.foltin@...> wrote:
>  Dear Dan,
>
> bug 22 is fixed in CVS. Bug 23 is not going to be fixed immediately as
> this involves lot of work.
> It is definitively left for 0.9.1.
>
> Best regards,
>
> Chris.
>
> PS: Do you get the CVS version on your own?
>
>
> Am 27.12.10 20:22, schrieb Dan Polansky:
>> Hello Chris,
>>
>> the ultimate decision is up to you, as you are the project director.
>> Whatever I decide or propose, you can override it. Nonetheless, within
>> the constrained and subordinate role of the unofficial quality manager
>> of FreeMind, I feel uncomfortable giving go ahead to a version that
>> contains known bugs that lead to data loss.
>>
>> Both bugs 22 and 23 are related to data loss. Especially bug 22 is
>> rather insidious, easy to be overlooked by the affected user. Bug 23
>> is rather unlikely to be overlooked by the user, so it could really be
>> postponed for 0.9.1, but it is a data loss bug nonetheless.
>>
>> I am fully aware of the time pressure to release final FreeMind 0.9.0,
>> which is why I do not report here some regression bugs that are less
>> serious. From where I am standing, we seem to be really close to final
>> release.
>>
>> Best regards,
>> Dan
>>
>>
>> On Mon, Dec 27, 2010 at 5:53 PM, Christian Foltin (GMX)
>> <christian.foltin@...> wrote:
>>>  Hi Dan,
>>>
>>> sorry, if we continue like this, we'll never publish 0.9.0.
>>>
>>> IMHO, these bugs are not that dramatic.
>>> Let's postpone them.
>>>
>>> Best regards, Chris
>>>
>>> Am 27.12.10 10:33, schrieb Dan Polansky:
>>>> Hello Chris,
>>>>
>>>> I have found two more bugs related to data loss, by extending a test
>>>> mind map with even more cases in which something could go wrong in
>>>> conversion from 0.8.0 to 0.9.0.
>>>>
>>>> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links
>>>> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118
>>>>
>>>> 23. Drag and drop of two connected nodes drops arrow link
>>>> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118
>>>>
>>>> I am sorry, again, that I did not discover these bug earlier.
>>>> Unfortunately, my brain seems to be much more eager to think about
>>>> what can go wrong when there are no more bugs on the list to be fixed.
>>>>
>>>> Best regards,
>>>> Dan

Hi,

0.9.0 RC15 is published at sf.

Best regards, Chris

Am 11.01.11 19:40, schrieb Dan Polansky:
> Hello Chris,
>
> I have just tested 0.9.0 RC15 from CVS against the bug 22; the test
> showed that bug 22 is fixed. Thank you.
>
> Postponing fixing bug 23 to 0.9.1 is suboptimal but acceptable IMHO.
> Given that you say that fixing the bug is too much work, given that
> the bug is fairly easy to spot (hard to overlook) for the user, and
> given how late 0.9.0 already is, it seems excusable to leave the bug
> in the final release in spite of the bug being a data loss one.
>
> I know of no other serious bugs that block final release 0.9.0. I
> would have one last thorough look at 0.9.0 RC15 after it is released
> at SourceForge, and then I would give it a go ahead.
>
> Best regards,
> Dan
>
>
> On Sun, Jan 9, 2011 at 10:24 PM, Christian Foltin (GMX)
> <christian.foltin@...> wrote:
>>  Dear Dan,
>>
>> bug 22 is fixed in CVS. Bug 23 is not going to be fixed immediately as
>> this involves lot of work.
>> It is definitively left for 0.9.1.
>>
>> Best regards,
>>
>> Chris.
>>
>> PS: Do you get the CVS version on your own?
>>
>>
>> Am 27.12.10 20:22, schrieb Dan Polansky:
>>> Hello Chris,
>>>
>>> the ultimate decision is up to you, as you are the project director.
>>> Whatever I decide or propose, you can override it. Nonetheless, within
>>> the constrained and subordinate role of the unofficial quality manager
>>> of FreeMind, I feel uncomfortable giving go ahead to a version that
>>> contains known bugs that lead to data loss.
>>>
>>> Both bugs 22 and 23 are related to data loss. Especially bug 22 is
>>> rather insidious, easy to be overlooked by the affected user. Bug 23
>>> is rather unlikely to be overlooked by the user, so it could really be
>>> postponed for 0.9.1, but it is a data loss bug nonetheless.
>>>
>>> I am fully aware of the time pressure to release final FreeMind 0.9.0,
>>> which is why I do not report here some regression bugs that are less
>>> serious. From where I am standing, we seem to be really close to final
>>> release.
>>>
>>> Best regards,
>>> Dan
>>>
>>>
>>> On Mon, Dec 27, 2010 at 5:53 PM, Christian Foltin (GMX)
>>> <christian.foltin@...> wrote:
>>>>  Hi Dan,
>>>>
>>>> sorry, if we continue like this, we'll never publish 0.9.0.
>>>>
>>>> IMHO, these bugs are not that dramatic.
>>>> Let's postpone them.
>>>>
>>>> Best regards, Chris
>>>>
>>>> Am 27.12.10 10:33, schrieb Dan Polansky:
>>>>> Hello Chris,
>>>>>
>>>>> I have found two more bugs related to data loss, by extending a test
>>>>> mind map with even more cases in which something could go wrong in
>>>>> conversion from 0.8.0 to 0.9.0.
>>>>>
>>>>> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links
>>>>> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118
>>>>>
>>>>> 23. Drag and drop of two connected nodes drops arrow link
>>>>> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118
>>>>>
>>>>> I am sorry, again, that I did not discover these bug earlier.
>>>>> Unfortunately, my brain seems to be much more eager to think about
>>>>> what can go wrong when there are no more bugs on the list to be fixed.
>>>>>
>>>>> Best regards,
>>>>> Dan
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand 
> malware threats, the impact they can have on your business, and how you 
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Freemind-developer mailing list
> Freemind-developer@...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer

Hello Chris,

I have tested 0.9.0 RC15 and have found no errors that would block
final release. All remaining bugs seem acceptable for final release,
given how late the release already is. From the role of the unofficial
quality manager of FreeMind, I am herewith giving go ahead to the
final release of 0.9.0.

You have rejected to fix some bugs or issues, for various reasons.
Rejected bugs include "3. Long node editor not below node", "4. Option
for plain text in notes", and "23. Drag and drop of two connected
nodes drops arrow link".

I would recommend that we watch for new critical bugs after the final
release of 0.9.0, which is expected to be used by many more people
than betas and RCs. If new critical bugs are discovered, there can be
a bug-fix release 0.9.1.

Thank you for all your effort in this marathon.

Best regards,
Dan