any further development activities planned?

[nnako]

Hi Lukas. I like your Python application which seems similar to what was developed by Igor. Both your solutions have stopped further development, though. Do you intend to continue the development of your Python version? What would you need to do so? I could support if you like, as I am close to Freeplane development and Python usage.

[lu-kas]

Hi!

Thanks for your interest in this tool. Currently the development stagnated because the tool does everything that I need for my talks and lectures. So, as long as there is nobody else using it, there will be just minor adjustments.

In contrast do the development, I use this tool on a daily basis for lecture.

If you would like to contribute, please feel free to do so. I would be very happy about that. However, I am not sure about a potential integration of the tool into Freeplane. Although it might work out nicely, the tool would become more complex.

What do you think? Do you miss any features? Would it make sense do to more dissemination in the Freeplane community?

Btw, before I started this tool, I have tried Igor's application. For reasons I do not remember, it was not the tool I was looking for.

Best, Lukas

On 19 Jun 2016, at 16:23, nnako notifications@github.com wrote:

Hi Lukas. I like your Python application which seems similar to what was developed by Igor. Both your solutions have stopped further development, though. Do you intend to continue the development of your Python version? What would you need to do so? I could support if you like, as I am close to Freeplane development and Python usage.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[nnako]

Hi Lukas,

my intention would not be to integrate it into the Freeplane runtime application. Using it as an external tool would generally suit my surrounding technology infrastructure. Now, your concept is based on a mix of control sequences within the node's core (like "#FIG ...#", "#SC#",...) and attributes to control the output styling. My view would be this:

• I would rather clearly separate the control from the content. Content would go into the node's core (everything visible will be regarded as content) and control would go into the node's attributes (hiding the display of attributes prevents distraction from content). With no attributes set, a standard style would become active. This would make copying / pasting of standard text to and from the mindmap less complex, I think.
• this approach would also support a "built-in" presentation in any mindmap. So, a presentation could be a small subset of a bigger mindmap. Rather than using absolute (static) node levels (you use levels 1 to 4 counted from the root node), any node could be a "virtual presentation root" e.g. when it has set the "mm2bramer__root" attribute to "1" or so. From here, the relative level distance could determine the function of the node's content (e.g. chapter, sub-chapter or content). You could even have multiple presentations (for different themes) in one big map.
• ...

Regarding Igor's application, I would like to include those additional level-dependent features (like squeezed style, background pictures, ...)

What do you think?

Best, Nnamdi

[lu-kas]

Sry, I am currently travelling without connection to the internet. I'm back in a few weeks and will continue our discussion.

[nnako]

no problem. I'm on vacation as well ;-) .

Just for clarification: I don't intend to make eyerything new and different. I'd like to add functionalities and input features without disturbing / removing the existing ones. I think, by creating a kind of "modular toolbox" where people can set any of their desired styles either within the node core or within the attributes would facilitate multiple different applications. This might be attractive for many users.

Am 29. Juni 2016 21:54:34 MESZ, schrieb Lukas notifications@github.com:

Sry, I am currently travelling without connection to the internet. I'm back in a few weeks and will continue our discussion.