Things for Next Release - tomboy-notes/tomboy-ng GitHub Wiki

Release Plan

With v0.34 out now, tomboy-ng release cycles are 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.

New Features

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

Importing and Exporting. Done, in 0.35

  • import-txt=, import-md=, import-note= will make a new note from the indicated file (or template). First line will become title.
  • adding --title-fname will get the title from file name.
  • in every case, note will be imported, an existing instance of tomboy-ng advised to reindex and this instance exits.
  • The new notes are directed to the Notes repository BUT if you also provide a --config-dir on the command line pointing to a dir with an alternative tomboy-ng.cfg file it will be used to determine where the imported notes end up. You can use tomboy-ng to make that config file for you (just by starting it with eg tomboy-ng --config-dir=my-special-dir and then changing its default note path. Or just make a dummy config file, all it needs is the NoteDir path. eg

[BasicSettings]

NotesPath=/home/dbannon/myspecialdir/

  • the use of a filename on the commandline without switches will be limited to note format only, single note mode, note saved back to same place. This is not an import operation.
  • This is intend as a one note at a time model and is probably only appealing to Linux users, how to cater to Windows and Mac ? , Linux user will also be able to do a shell for loop and process a directory. Might be workable under PowerShell. Technically workable under bash on MacOS but who knows what Apple has put in our way ? TT is still the answer for bulk imports/exports.

Revised Search Model

  • SWYT - Search While You Type, optional (because of the extra memory and compute load).
  • Significantly faster, especially so for users with a large number of notes.
  • Bit kinder on memory, again, especially so for large numbers of notes.
  • Intuitive interaction between a search term and notebooks.
  • A number of search related functions have been speed up slichtly, eg the linking to existing notes while you type.

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 - confirm this, I don't think its working ???

Tomdroid sync

While working nicely for Linux user (who don't have too many notes), clunky and difficult to extend to Windows and MacOS. Unless I hear from users that they need this capability, I will drop it out and save some code. V 0.35 will be the last to have it.

Github Selective Sync

Selective Sync now works with Github Sync and could be extended to work with File Sync reasonably easily. Is there a need ?

PO tools (Deep Blue Sky Stuff)

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.

All seems a lot of work, and may end up too complicated to use anyway......

Roy (who knows far more about translation than I ever hope to) does not seem excited. Very back, back burner.