Hi Kanat, most bugs should be fixed in less time, I would say, 10min for the easy ones and 1h for grave bugs. There should be only few bugs that need more time, but this is a very rough estimation.
Thanks for your ideas concerning the paste-issue. I'll post it to the developer list, too. HTH, Chris kanat schrieb: > Message body follows: > > Hi, > > I'm a Computer Science PhD student at Syracuse University, > in USA. My research topic is using dynamically inserted > assertions to: > + trace methods > + understand how a program runs > + discover bug origins > + create reusable assertions that can avoid same bug in > the future > > As my tool is not very stable and has a complicated UI and > no documentation, I will be using it myself. > > I would like to help you with tracking bug origins in > freemind. If I can, I would suggest a solution, or point to > where I think the problem is. I hope to do many experiments > on Thursday. > > I would appreciate if you can in return give me an estimate > on how long each bug may take to resolve. If you say 3 - 5 > hours, for example, I will find my rate factor compared to > your estimate, so I can compare efficiency of my tool to > Eclipse (as I can't use them on the same bug). I need your > estimates as soon as possible, for about 20 bugs you could > pick or I could pick. More careful estimates would be > better, if possible. > > I hope you can help. I'm attaching something I found out > (but didn't resolve) without debugging; I hope it helps... > > > Freemind Bug 2020246 HTML is pasted as source text (linux) > > This appears to be due to endianness (big-endian vs > small-endian, which flips pairs of bytes). > > http://en.wikipedia.org/wiki/Replacement_character > http://en.wikipedia.org/wiki/Byte-order_mark > > FEFF is byte-order-mark. When endianness is mixed up, this > is read as FFFE, which is beyond unicode. This would then be > converted to FFFD, replacement character, representing > "unknown/unprintable char" that you see as boxes. As I > followed the other chars in my test, they also seemed to be > 16-bit Unicode, but with the ASCII chars on the high-order > bytes (they should have been low-order bytes): > http://www.scribd.com/doc/3976156/HTML-paste-error-example > > Probably fixing/being flexible about endianness would solve > the inability to parse the html. Once unicode can be parsed, > freemind may style it properly. (pasting directly into node > being edited may remain unstyled) > > > -- > This message has been sent to you, a registered SourceForge.net user, > by another site user, through the SourceForge.net site. This message > has been delivered to your SourceForge.net mail alias. You may reply > to this message using the "Reply" feature of your email client, or > using the messaging facility of SourceForge.net at: > https://sourceforge.net/sendmessage.php?touser=1242254 > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freemind-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freemind-developer
