I do feel obliged (and in Texas terms which is where I am from, that just means my heart tells me I have to) say that the switch to SQLite is a bit of a bummer. XML was SO easy to manipluate external to the project, ex. via XSL, shell scripting, etc.

Not sure I understand the logic of it, as it buries the data in a deeper level...?

I do see that Thunderbird has a SQLite manager which I am going to experiment with. So for those of us unfamiliar with SQLite and who want to manipulate the data or extended the funtionality, that would still be an option.

Thanks, for listening and working so "smart" on the project. OSMO is and always will be a great tool.


Scott Vanya
Learn to Love even hate, and the world will be a better place.

Scott Vanya
Scott Vanya's Website - Dedicated to the Proliferation of Unconditional Love

Open Mics Austin (website) - Showcasing the Live Poetry Scene in Austin, TX, USA
On 10/16/2013 09:17 PM, Julien Eula wrote:
Hi all,

so I've been cleaning the feature requests tracker a bit and i'm almost done with it (only one page left of unsorted requests). You can browse the latest updated tickets at http://sourceforge.net/p/osmo-pim/feature-requests/?q={%22status%22%3A+{%22%24nin%22%3A+[%22wont-fix%22%2C+%22closed%22]}}&limit=25&page=0&sort=mod_date%20desc . ALso, I'm almost done moving the issues from https://github.com/nodiscc/osmo-pim/issues

I have added tags to the tickets to help sorting them, and see where the majority of requests have been made. Merged many many duplicates or tickets about the same problem.

As far as I can tell, the most frequent requests are about a new category/tags system (http://sourceforge.net/p/osmo-pim/feature-requests/search?q=labels:tags - I closed many of these without tagging, but there are definitely a LOT of requests about this). There's a main tracking ticket in https://sourceforge.net/p/osmo-pim/feature-requests/19 for tagging, also a proposal for a simple, manual tagging system in https://sourceforge.net/p/osmo-pim/feature-requests/50/ (basically just hashtags)

The second most active topic is a sync system, see http://sourceforge.net/p/osmo-pim/feature-requests/search?q=labels:sync . As I said, CalDAV would be a nice choice for calendar sync as it uses ics which osmo already supports. I've been able to import tasks from a CalDAV server (Owncloud) using the 'cadaver' command line tool and a bit of shell scripting. A plain text, file-system based storage for notes would be a great choice, users just have to use the tool of their choice to sync these files (Owncloud, Dropbox, Ubuntu One, Sparkleshare, Google Drive, Git, Spideroak, whatever...) between machines.

The third most active request seems to be tighter integration between components. Eg, being able to edit events from the calendar, linking to contacts/events from Notes.

The rest are improvements like being able to add images inside notes (some widely used markups like Markdown allow this, maybe use it for Notes?), multiple selection improvements.... Just check out the list of feature requests. I still have to sort some requests (those that have no tags yet, old old ones etc.) but anyone please feel free to update the requests with ideas, report bugs and more feature requests and so on.

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >

Osmo-pim-friends mailing list