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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/freemind-developer > > ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/freemind-developer
