Question:
What was the original reason for choosing to keep all these many
different formats in the first place (as opposed to, say having everything
HTML)? Wouldn't that ease a lot of maintenance problem and also slim down
the right-click context menu?
Right now, they are being saved in a new "richcontent" tag. This means, if
the new maps are opened in 0.8.0, the notes with formatting would never
show up. Wouldn't it be possible to keep some degree of forward
compatibility by, say, still using the "TEXT=" attribute for node content
like this:
<node TEXT="This is a simple old node"> </node>
<node TEXT="This is a <b>HTML</b> node"> </node>
Here the node content would still be legible in the 0.8.0 versions
(although cluttered by a few tags), while the newer version would
automatically know that tag is of HTML type. That way user would never
have to explicitly choose between tag types.
I understand these decisions have been made years ago, and it is probably
too hard to change now, but I wanted to know the reasons behind such
choices.
Reasamp
On Sat, 26 Jan 2008 03:59:45 +0600, Ray Benjamin <[EMAIL PROTECTED]>
wrote:
>
> I think I made a similar comment some time back. Once someone has
> decided a particular node should be a long node, it should stay that
> way. Although, we should provide a way to change it to a short node
> later. But I agree, once a decision has been made, we shouldn't keep
> asking the question. It goes against the concept of making the use of
> FreeMind as streamlined as possible.
>
> Ray
>
> Dimitry Polivaev wrote:
>> Hi, how shoud we proceed in this question? Dimitry
>>
>> == fwd ==
>>
>> I've switched to FreeMind 0.9.0 beta 15 for my daily work, and I'm
>> rather
>> annoyed by the following behavior (which I consider to be a bug): when I
>> want to edit a node as long node, I get the question if I want
>> bold/italic
>> or not. I can either "remember my decision" but then this decision is
>> valid
>> for all nodes, or I can decide to not "remember my decision" but then I
>> get
>> asked about it even for nodes where I've already taken a decision, i.e.
>> nodes which already are long nodes.
>>
>> The correct behavior should be IMHO that I don't get the question for
>> already existing long nodes, because I've already taken a decision.
>>
>> i.e. in EditAction.java (I think)
>> - // if the node is not already html, we ask if rich text or plain text
>> edit.
>> - if(!isHtmlNode && editDefinitivelyLong) {
>> + // if the node is not already long, we ask if rich text or plain text
>> edit.
>> + if(!node.getIsLong() && editDefinitivelyLong) {
>>
>> Thanks, Eric
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Freemind-developer mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>>
>>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Freemind-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freemind-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freemind-developer
