Map View Feature

[tu2-atmanand]

In this topic will discuss everything about the Map view feature released in the version 1.7.0 as an experimental feature. This feature can be better understood and efficiently used after understanding the Dependency Flow Planning methodology which was born while implementing this feature in Task Board.

Will keep you all updated everything regarding this feature and its improvement in upcoming versions in this discussion topic.

[tu2-atmanand]

How to use Map View Feature

Here are some points you will need to keep in mind while/for using Map view feature :

• In the current version, 1.7.0, you will be only able to use this feature if you have enabled the "Experimental features" setting under the General tab of Task Board settings.

• You can only show a certain task on the canvas (map view), if that task has an ID property to it. For example : 🆔 4.
  • The ID property to tasks are important because IDs play a very crucial role in real world to refer any item quickly and it wont be possible for any plugin to give a smooth experience like, storing the state(size and position) of the task-node, if its data is not stored for the task. And Task Board does it my mapping the data with its ID and store it in the localStorage. In future, it might be possible to show all tasks without an ID on them, once optimizations to this feature has been implemented.
• To make the process of applying ID to a task simpler, a new setting has been added, "Auto add unique id", which will help to automatically apply an incremental numeric id when you will interact with the task. So, please enable this feature as well, it will be really useful in future, if you like to use the upcoming features as mentioned in the setting.

• Furthermore, there is also a button inside the "Edit task modal" to quickly show any task on the canvas. If the task is not present on the Map view, you can use this button, which will apply an ID to the task inside the note and then your task will be automatically visible on the Map view.

[tu2-atmanand]

Enhancement Suggestions

For now, will simply put down all the enhancements which can be made to improve this feature. If it looks a valid request, then will create an issue and start its implementation.

• Different UI for resizing : Only on hover, the parameter of the node can light-up, then user can select its edges to resize the node horizontally or vertically. The current UX of first clicking on the node and then using the corner markers to resize is not a good experience.
• Edge connectors : Either a setting to decide whether to have the edge connectors on only top-bottom or left-right. OR have them on all four sides but only show them on node hover.

[medo0o0o0]

To make the process of applying ID to a task simpler, a new setting has been added, "Auto add unique id", which will help to automatically apply an incremental numeric id when you will interact with the task. So, please enable this feature as well, it will be really useful in future, if you like to use the upcoming features as mentioned in the setting.

is it possible to auto add id that is dataview compatible ? , like [id:: dcf64c]

[tu2-atmanand]

Ahh! Forgot to add it. Actually, since for last few versions, the focus was mainly on Tasks plugin compatibility, thats why didnt paid much attention to Dataview side. But will implement all the missing things now. Ill also will start the testing from my end.

This will be implemented in the upcoming version 1.8.0. Thank you @medo2132112 for reporting this.

[medo0o0o0]

great @tu2-atmanand that's nice to hear

[tu2-atmanand]

Hi
I realized that this integration of dataview format for all the task properties will require a considerable amount of time for both development and testing. Hence for now, in the upcoming version, will only try to implement the 'id' and 'dependsOn' properties, Since they are necessary for Map view feature. In the next version, 1.9.0, a complete integration of dataview formats will be implemented. The development can be tracked here : #449

[medo0o0o0]

will only try to implement the 'id' and 'dependsOn' properties

those are the most important two ,that great