Skip to content

Things for Next Release

davidbannon edited this page Feb 16, 2021 · 30 revisions

Release Plan

With v0.32 out now, I expect tomboy-ng release cycles to be a little longer. Given that basic functionality is almost all there now, we can afford the luxury of a beta release cycle before formal release, the extra testing period will ensue a quality release and avoid bugs that sometimes creep in that require an unexpected (to me) combination to demonstrate.

So, watch the github release page, you may see some beta or pre-release packages.

New Features

Any, all or even none of these may make it into v0.33.

Run auto sync and snapshot in separate thread

Will avoid a few seconds of non responsiveness, particularly at startup.

Ctrl N

When focus is on the Search Window, seems that a Ctrl-N can go to a number of controls with being acted on, that is, a new note please. Done in v0.32b

Sorting of Notebook List

Hmm, just alphabetical I guess ?

Exporting (and importing ?)

Better to use the CommonMark markdown exporter I wrote for the NextCloud experiments (done in v.32b), nice to be able to export a Notebook full of notes too.

Makes sense to tidy up Tomboy Tools for this purpose, much of whats needed is already there. While it has a clunky interface, that can be improved over time too. Still need to escape the new titles while importing.

Should not be too hard.

Nextcloud Notes

I am still unconvienced that their API is suitable. So, this one is likely to be on hold. https://github.com/nextcloud/notes/issues/627

Tomdroid sync

While working nicely for Linux user (who don't have too many notes), would be good to extend to Windows.

Selective Sync

Useful if we could associate (each separate) sync with a Notebook. Especially so now that we have a function (for Linux) users Tomdroid sync. That way, a user can declare a sync only involves certain notes. Need to model this a bit to ensure its safe.

PO tools

It would be nice to be able to manage the Help Notes via the .po system. This would make maintaining them a lot simpler for translators. But there are some issues. While a start has been made, did not make it it to 0.32.

  • Add an export in .po format.
  • Add an import from .po format.
  • Add an export to man page, html.....
  • But must have some means of merging existing translated content with new content, ie what happens to *.es.po when *.po is overwritten ? That is starting to sound like an implementation of POEdit. Can we find a way to use POEdit to do that syncing ?

It appears msgmerge, part of gettext, might do it all. So, I propose a workflow to make / manage help notes like this -

  • I add a dumb .po import/export capability.
  • create a (disposable) tomboy note, either from scratch or by importing the appropriate (English) .po file.
  • edit as required.
  • Export that content from tomboy-ng to a .po or .pot file containing a limited sub set of common mark. This file becomes part of git distro.
  • Use msgmerge to generate new *.XX.po files for each supported language. Normally, little will have changed, most of existing translations will be valid. New content will be, of course, by default in English.
  • Translators will, at some stage, pull down their .po file, edit some or all and return it.
  • At package time, I 'import' (cli desirable) each *.XX.po file generating a regular Tomboy format help note to distribute in the package.
  • Man pages, pdf, html can be generated in the same way, to broaden appeal. Maybe ??

Progress Report : I have added (to TomboyTools) the ability to export a note in a sort of .pot file. It still has the xml markup in there so is quite hard to read IMHO. aguador is looking at some other tools that might be more suited to flowing, marked up text than poedit.

Clone this wiki locally