Google Gemini, Claude, MCP support #2340
Replies: 3 comments 2 replies
|
Hi @LukasWestholt , what would be your idea to do that? |
|
Please don't do that within jtxB. |
|
There's a long term request for an ability to import entries (my interest is solely in Journal entries - but I can imagine there might be need to import notes and tasks as well). The feature request is probably so old it has fallen off the radar as most people I know who use jtxB (ie only me) have found workarounds, but it would still be very useful. It needs to be agnostic as to where the data comes from and use a simple format - the obvious thing is to use CSV file format since you already have CSV export (experimental) and it is simple and the VCALENDAR data is essentially plain text. If someone is using some automated system as the source of data then it is going to have to be presented in a standard format anyway, whether it is coming from an sql database or a random text generator. It should be quite simple to tell the source to generate it as a CSV with specific column headings. Personally I have no use for Automated Information, but I don't care if other people use it - I'd just hate to see jtxB, which is really useful, tie itself to specific data sources apart from VCALENDAR. If there is a genuine need for automation in tasks then perhaps it is time to ditch the tasks stuff from jtxB and spawn a separate jtxT (jtx-Tasks) app which would deal with such things as compatibility and data exchange with the likes of Nextcloud tasks and automated information generators. It seems that the majority of people making feature requests of all sorts are actually using the Tasks functionality rather than the original Journal function. For my point of view all the tasks stuff in jtxB is just bloatware - there are plenty of other tasks apps out there, but this is the best (and only) VJournal app. |
Uh oh!
There was an error while loading. Please reload this page.
Does anyone use AI to create new Tasks and push to CalDAV Server?
All reactions