I’ll just add these thoughts to Christoph’s reply, Frank. These are just thoughts about expectations and what might be possible for Andrey to implement - I don’t mean them to sound critical of the comments ir difficulties you’ve raised, or of your idea that it might be possible to incorporate a simple RTF editor.
While you may be satisfied with a tiny RTF editor, there will always be other people who will argue for more and more word-processing features, so that they can write and format comprehensive notes. However, Andrey’s concept (unless it’s changed) was always to produce a fast and light task manager, with the ability to jot quick, unformatted notes. With the resources and budget available, I expect it will never be a full project management programme (like a multi-platform Microsoft Project) or a full word Processor. Inclusion of Markdown was offered as a simple way to add the formatting that many users had asked for, without breaking that concept. If you really want to produce notes with detailed formatting, good enough to publish, then MLO is probably not the right place for those. Other options would be to (1) stay with plain text notes, which you format after copying them into your publishing tool, (2) use Markdown formatting, then use an external converter or record a macro in Word to convert the code characters to RTF / .docx formatting, or (3) Keep the notes in another app such as Evernote, OneNote or MS Word documents and just put links into your related MLO tasks. For things like notes formatting, parsing and date formatting, Andrey relies on software components from other authors, as he has a small company, trying to support and develop MLO on multiple platforms. This will limit what changes he can make (or persuade other developers to make) in some of the features if his software. I expect that implementing rtf would be a bit trickier. Unlike Markdown, the editor might have to be implemented on every platform (Windows, iOS, Android) at the same time, to keep the notes legible. That would make it a lot harder to develop. We should definitely request features which we think are important and comment on where a feature doesn’t work as hoped or meet our needs. However, I don’t think we should get too upset if our needs can’t be met or are not considered to fit with the author’s plan for development. Overall, I think it’s really important that this discussion takes place, so thanks for stating your view. There have been a few people who have challenged the Markdown implementation with various concerns, so we’ll see what other options or improvements Andrey explores. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/70d6fea3-5df4-44e5-8329-0cf54b44b885%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
