locus-actions:// and www bookmarks tiny enhancements

joeloc shared this idea ago

Gathering feedback

My goal is still to "tap a single button" and have custom data appear in Locus instantly. No "imports", no web browsers, no navigating through menus or directory structures, no rubbish user interface, just a single tap.

Locus has everything for that builtin already, it's all just a question of tying together a few lose ends here and there. Quick WWW Bookmarks could work together with locus-actions to accomplish that goal. Imagine the following action:

<download><source>http:x.x/getmydata.php?type=kmz&lat={lat}&lon={lng}</source><dest>/mapItems/{bookmarkname}.kmz</dest><after>enableMapItem</after></download>

To make this work, three tiny enhancements are required in Locus:

(1) locus-actions <after> command needs to implement an enableAsMapItem switch.

(2) Quick www bookmarks should allow specifying a complete locus action XML string instead of a simple URI. No user interface change is required. If the definition is an URI, you launch it just like now. But if the definition starts with "<", you treat is as xml and simply hand it over to your locus-action-engine.

(3) Quick www bookmarks needs a {bookmarkName} parameter.

I like this idea 0

Replies (1)

Menion ●

Hello Stefan,

I think you may already accomplish this task, but little bit different.

1. define bookmark to own server over locus-actions, like this:

locus-actions://http/myserver.com/getmydata.php?type=kmz&lat={lat}&lon={lng}

2. tap on this link should forward action to Locus itself (in next version this should already work) and Locus should then call link http://myserver.com/getmydata.php?type=kmz&lat=Y&lon=X and download XML from there

3. on your server, handle received request and generate XML with all actions you require. <after>displayData</after> should work.

If something won't work in method above, let me know.

Reply URL

joeloc ●

Well... it might work that way. But you force this extra XML burden thingy on everybody who wants to add custom data too Locus... wouldn't one single IF command to Locus instead of having every server guy return two files? In fact... the XML is highly Locus specific and belongs into Locus config (imho), whereas the geodata is simply kml/gpx and should come from a server.

Plus... I still need the bookmark name as parameter.

Also... is the DisplayOnly thing really equivalent to mapitems? How long does it stay? Will it survive restarts? Will I get a pretty sidebar to enable/disable? Why do you hate mapitems anyway? :)

URL