Finishing 0.9.0: Difference between revisions
Dan Polansky (talk | contribs) (→Outstanding bugs: +bug 16) |
Dan Polansky (talk | contribs) (→Outstanding bugs: +status to the bugs) |
||
| Line 10: | Line 10: | ||
==Outstanding bugs== | ==Outstanding bugs== | ||
Outstanding bugs in FreeMind 0.9.0, 2010-07-07[http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTimMOGHl9qP9zSbkfT_KUqwovMk_JQas3zn9c_0l%40mail.gmail.com&forum_name=freemind-developer]: | Outstanding bugs in FreeMind 0.9.0, 2010-07-07[http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTimMOGHl9qP9zSbkfT_KUqwovMk_JQas3zn9c_0l%40mail.gmail.com&forum_name=freemind-developer]: | ||
* 2. Zoom: no zooming effect on node editors[http://sourceforge.net/tracker/?func=detail&aid=2800933&group_id=7118&atid=107118] | * 2. Zoom: no zooming effect on node editors[http://sourceforge.net/tracker/?func=detail&aid=2800933&group_id=7118&atid=107118] - in progress; an almost correct solution implemented in RC8; an adjustment for a strange multiplication factor still missing AFAIK | ||
** <p style="color: gray;">This bug of rich text editing failing to zoom can be fixed with acceptable effort. It does not appear in my private version of FreeMind. Based on my private version of FreeMind, I have posted some suggestions into the bug report on how to fix the bug. If these suggestions did not work, something along the lines of them must work. This is not a hard problem. Importantly, the problem concerns every edit of a rich text node when the mind map is zoomed, which concerns all people who prefer zoomed mind maps be it for their eyesight or for their having high PPI display. It is not a minor usability problem with a rarely used function, but rather it is there right in the middle of the main function that FreeMind offers. --Dan</p> | ** <p style="color: gray;">This bug of rich text editing failing to zoom can be fixed with acceptable effort. It does not appear in my private version of FreeMind. Based on my private version of FreeMind, I have posted some suggestions into the bug report on how to fix the bug. If these suggestions did not work, something along the lines of them must work. This is not a hard problem. Importantly, the problem concerns every edit of a rich text node when the mind map is zoomed, which concerns all people who prefer zoomed mind maps be it for their eyesight or for their having high PPI display. It is not a minor usability problem with a rarely used function, but rather it is there right in the middle of the main function that FreeMind offers. --Dan</p> | ||
* 10. RC4 regression: incorrect viewing of UTF-8 map[http://sourceforge.net/tracker/?func=detail&atid=107118&aid=2810535&group_id=7118] | * 10. RC4 regression: incorrect viewing of UTF-8 map[http://sourceforge.net/tracker/?func=detail&atid=107118&aid=2810535&group_id=7118] | ||
** <p style="color: gray;">I have reproduced the bug in Windows. It is a bug that prevents loading of certain reasonably formatted mind maps not created by FreeMind. FreeMind's format should be open, in that it should be possible to create mind maps in this format outside of FreeMind. This is not the kind of bug over which one should hurry up to get the final release out. It is a regression bug, absent in 0.9.0 RC3. --Dan</p> | ** <p style="color: gray;">I have reproduced the bug in Windows. It is a bug that prevents loading of certain reasonably formatted mind maps not created by FreeMind. FreeMind's format should be open, in that it should be possible to create mind maps in this format outside of FreeMind. This is not the kind of bug over which one should hurry up to get the final release out. It is a regression bug, absent in 0.9.0 RC3. --Dan</p> | ||
* 12. data loss in notes; note conversion[http://sourceforge.net/tracker/index.php?func=detail&aid=3008236&group_id=7118&atid=107118] | * 12. data loss in notes; note conversion[http://sourceforge.net/tracker/index.php?func=detail&aid=3008236&group_id=7118&atid=107118] - in progress by Chris | ||
** <p style="color: gray;">The bug leads to apparent loss of all notes (notes, not nodes) that were within an encrypted node, after a conversion of a mind map saved by FreeMind 0.8.1 to FreeMind 0.9.0. I have reproduced the bug in Windows; the reporter of the bug uses Linux. In fact, the notes are not lost, but merely hidden away from the user. The problem is that the user does not know that the notes have not been lost, and, if he is a non-technical user, has no obvious way of discovering that his notes are in fact safely stored in the mind map. --Dan</p> | ** <p style="color: gray;">The bug leads to apparent loss of all notes (notes, not nodes) that were within an encrypted node, after a conversion of a mind map saved by FreeMind 0.8.1 to FreeMind 0.9.0. I have reproduced the bug in Windows; the reporter of the bug uses Linux. In fact, the notes are not lost, but merely hidden away from the user. The problem is that the user does not know that the notes have not been lost, and, if he is a non-technical user, has no obvious way of discovering that his notes are in fact safely stored in the mind map. --Dan</p> | ||
* 13. Conversion from 0.8.0 to 0.9.0 drops newlines in notes[http://sourceforge.net/tracker/?func=detail&aid=3021953&group_id=7118&atid=107118] | * 13. Conversion from 0.8.0 to 0.9.0 drops newlines in notes[http://sourceforge.net/tracker/?func=detail&aid=3021953&group_id=7118&atid=107118] - in progress by Chris | ||
** <p style="color: gray;">When a mind map created with FreeMind 0.8.1 has notes whose text contains newlines, the newlines are dropped upon the conversion of the mind map to FreeMind 0.9.0 RC8. --Dan</p> | ** <p style="color: gray;">When a mind map created with FreeMind 0.8.1 has notes whose text contains newlines, the newlines are dropped upon the conversion of the mind map to FreeMind 0.9.0 RC8. --Dan</p> | ||
* 15. Freemind cannot find text with Greek characters[http://sourceforge.net/tracker/?func=detail&aid=3035387&group_id=7118&atid=107118] | * 15. Freemind cannot find text with Greek characters[http://sourceforge.net/tracker/?func=detail&aid=3035387&group_id=7118&atid=107118] - in progress; a solution proposed in the text of the bug | ||
** <p style="color: gray;">Searching in unicode rich text nodes fails to find general unicode strings just after a mind map has been opened. --Dan</p> | ** <p style="color: gray;">Searching in unicode rich text nodes fails to find general unicode strings just after a mind map has been opened. --Dan</p> | ||
* 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] | * 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] | ||
** <p style="color: gray;">Even a simple script such as '="Hello"' fails unless file operations are permitted for scripts. Oddly enough, the failure occurs only the first time a script is run.</p> | ** <p style="color: gray;">Even a simple script such as '="Hello"' fails unless file operations are permitted for scripts. Oddly enough, the failure occurs only the first time a script is run.</p> | ||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 07:57, 28 September 2010
The following two trackers track open items as regards the release 0.9.0:
- Bugs reported by Daniel Polansky — those in "open" status
- Issues — those in "open" status
- Bugs in SimplyHTML
Steps after release candidate
- Translation – Is already in process by people spontaneously sending us translations.
- Documentation – Can already be started.
Outstanding bugs
Outstanding bugs in FreeMind 0.9.0, 2010-07-07[1]:
- 2. Zoom: no zooming effect on node editors[2] - in progress; an almost correct solution implemented in RC8; an adjustment for a strange multiplication factor still missing AFAIK
This bug of rich text editing failing to zoom can be fixed with acceptable effort. It does not appear in my private version of FreeMind. Based on my private version of FreeMind, I have posted some suggestions into the bug report on how to fix the bug. If these suggestions did not work, something along the lines of them must work. This is not a hard problem. Importantly, the problem concerns every edit of a rich text node when the mind map is zoomed, which concerns all people who prefer zoomed mind maps be it for their eyesight or for their having high PPI display. It is not a minor usability problem with a rarely used function, but rather it is there right in the middle of the main function that FreeMind offers. --Dan
- 10. RC4 regression: incorrect viewing of UTF-8 map[3]
I have reproduced the bug in Windows. It is a bug that prevents loading of certain reasonably formatted mind maps not created by FreeMind. FreeMind's format should be open, in that it should be possible to create mind maps in this format outside of FreeMind. This is not the kind of bug over which one should hurry up to get the final release out. It is a regression bug, absent in 0.9.0 RC3. --Dan
- 12. data loss in notes; note conversion[4] - in progress by Chris
The bug leads to apparent loss of all notes (notes, not nodes) that were within an encrypted node, after a conversion of a mind map saved by FreeMind 0.8.1 to FreeMind 0.9.0. I have reproduced the bug in Windows; the reporter of the bug uses Linux. In fact, the notes are not lost, but merely hidden away from the user. The problem is that the user does not know that the notes have not been lost, and, if he is a non-technical user, has no obvious way of discovering that his notes are in fact safely stored in the mind map. --Dan
- 13. Conversion from 0.8.0 to 0.9.0 drops newlines in notes[5] - in progress by Chris
When a mind map created with FreeMind 0.8.1 has notes whose text contains newlines, the newlines are dropped upon the conversion of the mind map to FreeMind 0.9.0 RC8. --Dan
- 15. Freemind cannot find text with Greek characters[6] - in progress; a solution proposed in the text of the bug
Searching in unicode rich text nodes fails to find general unicode strings just after a mind map has been opened. --Dan
- 16. Scripts do not work if file operations are not permitted[7]
Even a simple script such as '="Hello"' fails unless file operations are permitted for scripts. Oddly enough, the failure occurs only the first time a script is run.
