Rexel Bartolome

I'm not really sure but it's been that way ever since I remember it? But I think I've only used freeplane since 1.9+ so older versions may have behaved differently

That does look impressive for creating tables @sfpcom :D but yes not necessarily what I imagined for a Kanban/Trello board specifically After some thought, maybe this "Trello/Kanban Board" view doesn't necessarily have to be it's own layout but instead it could be it's own node, which I would call the Column Node which is basically a Floating Node but automatically arranges it's children vertically like in the Outline View. Here's how I imagine it would work: https://i.imgur.com/blZ5Xz3.mp4 Of course...

You should add the preview image there too! 😄

Nothing specific if I remember correctly. After the topic was mentioned, lots of people mentioned the benefits of moving to Github which are now mentioned in this thread

After seeing @macmarrum 's demonstration regarding tables, I remember a feature request that I was planning on creating a post for: Trello Board Node Layout Currently we only have the default view/layout: And the outline view And I thought be we could have something in between where a certain level (i.e., Level 1 nodes) organize themselves horizontally with their siblings, and their children organized vertically like this A perfect use case for this is for a To Do list for a GTD system where you...

Yea and we've continued the discussion here cause we want to check in with others in the community that didn't get to attend or stay ( like @quickfold , @edo_f and others ) I personally like it because Github has recently launched the Discussions page which is much more intuitive than SF's (you can upload gifs and videos that can be watched inside Github and you can copy paste images easily in text posts which I think @euu will appreciate ). This is different from the Issues page, which is like the...

I agree with this one, this would be a quality-of-life feature request. It's much more intuitive if a node's location didn't change when it gets converted to free-positioned. It would also solve the problem of multiple overlapping nodes when you convert a bunch of them to free-positioned as I think that's the more common way of creating free-positioned nodes anyway, rather than inserting free-positioned nodes at the start.

Ohhh I see, I never really thought about it that way but yeah it does make sense. I have no clue regarding API's and software development and stuff 😅 But I guess it's kind of like how in Blender there's lots of powerful add-ons that aren't necessarily built inside the program but instead just comes pre-added or pre-installed when you install the base program, so you just need to enable them if you need their functionality (or sometimes if the addon is well maintained, it's pre-enabled already). I...