Roadmap - Integration with Bases #497
Replies: 16 comments 20 replies
-
|
This may be the best way to proceed for the medium term, but I think it may be months until it is feasible? |
Beta Was this translation helpful? Give feedback.
-
|
HI @callumalpass , As I mentioned in another discussion, it is a good direction for the plugin's maintainability and reliability. Before using Tasknotes I was already using bases and it was a huge friction remover. However, if the UI interactions become more basic by adhering to Bases, I don't thing it would be worth it to invest on setting up another plugin. The experience with Bases-Powered Tasknotes must be a significant improvement over using Bases alone. These are just initial thougths. I'll think of more specific items to discuss in a near future.. |
Beta Was this translation helpful? Give feedback.
-
|
That sounds like a positive convergence. I would be happy to re-write my TaskNotes filters in the familiar Bases syntax. A migration wouldn't be necessary. Being able to embed a task view in a note would be ideal. I do sometimes find the current TaskNotes filter system awkward. I end up with multiple versions of filters with the same name. The key challenge is to retain the Kanban, Agenda and Calendar views. Thanks for seeking our opinions on this. |
Beta Was this translation helpful? Give feedback.
-
|
I agree with this plan, merging with base by adding custom views to it once the API is released would be ideal. |
Beta Was this translation helpful? Give feedback.
-
ℹ️
|
Beta Was this translation helpful? Give feedback.
-
|
Hello. Thanks for your work. It will be useful to change the name of the properties/sections in YAML marking to its taste so that the Tasknotes plugin in the settings can choose your own option. Then the tasks in the BASs will be more individual and convenient. And also, add your categories/sections to YAML tasks. |
Beta Was this translation helpful? Give feedback.
-
|
Moving core of TaskNotes into bases is wise decision... it is maybe painful for dev team but long term this is correct direction... |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
As long as advanced calendar view, and other TaskNotes views are not effected it seems like it makes sense. But I don't know how feasible this is as I can't even get basic sorting for the priority property in bases. (see my reddit post about the issue). I don't know If you could help with this? I have not done extensive testing but it seems like bases is somewhat limited compared to say the Dataview plugin. For this reason it may make sense to keep TaskNotes separate from bases to ensure the specific views and custom features won't be limited by Bases. But you will know more than me, so IDK. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not a developer, but it does seem to me to be a sensible move to integrate with the Obsidian ecosystem as much as possible so that maintenance of the plugin is manageable. I can see real promise with Bases, and from a user perspective, if I can concentrate my efforts learning the ins and out of Bases well because of increased integration, it's a win. |
Beta Was this translation helpful? Give feedback.
-
|
Great job, I was waiting for this plugin, as Tasks is a mature and well documented work, but I've long been thinking the right approach is 'task per note' , either for calendar integration, md extension of tasks, Obsidian (bases) best integration. |
Beta Was this translation helpful? Give feedback.
-
|
Bases integration is brilliant! On Kanban view ... is there a way to group by something other than status at this point? I'd like to group by tag (where I keep contexts like "Work", "Home", etc.). |
Beta Was this translation helpful? Give feedback.
-
|
Love this work! Out of the box in my vault, the Kanban view seems to order the status columns alphabetically, but the screenshot above is clearly not ordered A-Z. Since we can manually set the order of statuses in Tasknotes, shouldn't that order be replicated in the Bases view? If not, how is it done? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Yoohoo! @callumalpass |
Beta Was this translation helpful? Give feedback.
-
|
If you use the Tasks Lists view and group by project, is there a way to get the project names to render as links if they are existing notes? |
Beta Was this translation helpful? Give feedback.
-
|
speaking purely as a user: yes please! |
Beta Was this translation helpful? Give feedback.





Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As TaskNotes has matured and Bases has been released, I have been considering TaskNotes future architecture and sustainability. This post outlines a potential path forward, and I'd be curious to hear what users think.
The proposal is to integrate TaskNotes more closely with the Obsidian Bases core plugin. The objective would be to delegate functionality like filtering, grouping, and view rendering from TaskNotes to the Bases engine. The Obsidian team has indicated that features such as grouping and Kanban-style views are on their roadmap for Bases. By leveraging this core functionality, it may be possible to reduce the complexity of the TaskNotes codebase and improve its stability.
This architectural change would mean that a TaskNotes view could be defined within a .base file. A possible implementation could look like the following:
Adopting this direction could result in several positive outcomes. It would allow TaskNotes to use Obsidian's own filtering engine, potentially improving performance and consistency. Task views could become embeddable in any note, similar to other Base queries. Aligning with a core Obsidian feature would also mean that improvements made to Bases by the Obsidian team could directly benefit TaskNotes. Finally, reducing the amount of custom view and filter logic within the plugin should simplify the codebase, making it more straightforward to maintain.
This approach is not without foreseeable challenges. A significant technical hurdle would be representing recurrence rules in a way that is compatible with the Bases property system. Another area of concern would be the implementation of task-specific actions, such as context menus, within the Bases UI. A reliable migration path for users' existing "Saved Views" into the Bases syntax would also be an important requirement.
I am interested in hearing your thoughts on this direction. In particular, it would be useful to understand if there are essential TaskNotes features that you believe might be at risk in such a transition. I am also seeking input on any potential benefits or drawbacks of this approach that I may have overlooked. Please share any thoughts/concerns you might have.
Beta Was this translation helpful? Give feedback.
All reactions