View Single Post
Posts: 1,548 | Thanked: 7,510 times | Joined on Apr 2010 @ Czech Republic
#1971
Originally Posted by rinigus View Post
@MartinK, thank you for the update, looking forward to test it. ESpeak already amused everyone this morning
Nice!

Originally Posted by rinigus View Post
Its great that you integrated POI support. Other map clients do have the same in TODOs, as far as I remember.
I think it's pretty important to be able to save any points of interest you encounter on your travels and to look them up later.

Originally Posted by rinigus View Post
Regarding POIs, I do wonder if we can keep it in some backend that would be used by all if the same notation is followed.
The funny thing is that the sqlite database schema is actually not an original modRana creation - IIRC it comes from Mappero, which is a long defunct navigation app for the N900. ModRana might still even support sharing the POI database when you run it on the N900.

Originally Posted by rinigus View Post
For example, as a part of our address books with all phone numbers and such. All devices do have address books and they could be easily shared between devices.
If I understand this correctly this would depend on Jolla, which unfortunatelly just means it will most likely get never implemented due to them being too busy. IIRC (can't find the specific question now) they have not even imeplemented a way to set an alternative mapping application to handle location links.

If we can get them to cooperate or the affected area is one where community can effectively contribute (eq. not being blocked by closed components & actually having a maintainer that can review and merge PRs) - that would be less hopeless.

Originally Posted by rinigus View Post
Just an idea that maybe worth of thinking about when we get to the stage where all other issues are resolved ...
Yeah, I'm personally glad I finally got to implement this and it's even still unfinished (you actually can't yet delete points once you add them ).

As for sharing the database, there are a couple issues worth considering:
- who else would be interested in sharing the POI database ? (eq. so unnecessary work is not done if no one will use it)
- the easiest way might be using the same SQL schema and a common location for the database, it might even work with concurrent access
- but that effectively locks the schema in stone - it's really simple at the moment (basically just name, description, coordinates, category) and might use some extending (phone numbers, elevation, address, opening hours, email address, website, twitter handle, etc.)
- it's actually a question if it needs to be an sqlite database at all - it just seems like a pretty big overkill for the few points people are likely to store & enforces IMHO unnecessary rigid schemas

I've had quite a good experience with BlitzDB in my experimental Twitter client - it's basically a pure-Python JSON document database. I've been feeding it with thousands of tweets and it works just fine, so it should be also able to handle a few POI as well. Of course unlike sqlite it kinda expects the app using it is also Python or can talk to Python in some capacity.

I guess alternative solution could be if modRana could work with multiple POI database formats, including one shared with other apps. The user might need to specify where new POIs should be stored (local/shared), but it should be possible to agregate the multiple POI databases to a single view.

Or OSM Scout Server could provide a REST API for storing & retrieving POI that that arbitrary apps could easily use. Now with socket activation it would be more useful than ever. ;-)

I guess we will see, but certainly something to think about.
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
 

The Following 8 Users Say Thank You to MartinK For This Useful Post: