Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - menion

Pages: [1] 2 3 ... 7
1
Discussion/New features / Re: What's the "Next Big Thing" in 2018?
« on: February 08, 2018, 21:16:57 »
Sure, I like to keep you at least informed :).

There is few major problems. Except fact that current screen where you write logs has problems with rotation of device, it stuck in case of any internet problem during logging etc. , it also do not allow to prepare offline logs with images, it complicates live when logging trackables , it miss display of logs with images (even that images are stored in config/fieldnotes.db file and so on ...
The following users thanked this post: tbkrtz

2
Discussion/New features / Re: What's the "Next Big Thing" in 2018?
« on: February 08, 2018, 17:39:13 »
Good topic :).
Let's discuss basic plans for year 2018

I'll give here, at least, current state in our small team.

Little history:
I had (still have) large hope in live tracking system. Two years ago, I've hired one guy who wrote for me server side solution in nice Clojure language (after more then year of work!). And when first part was finished, he stopped to communicate. Nice .. btw. no one know Clojure :). My mistake ...

In November, some of you probably noticed, that our team had increased to 6 person. Milan > finally developer who should help me with Android. His first task was (still is) Wear add-on. Nice work I think ...
Since January, he work on 1:1 conversion of old Live tracking system to something, we may continue work on it and improve. ETA till middle of March. Then, Milan will work on new UI & various stuff around Live tracking system, also based on feedback. I expect, it will be work on few more months. And then ... sync server? ( most probably ).

Because number of people involved in work on Locus increased and for my suprise, all wants their monthly salary, and also because of number of sold Locus Map is still +- same ( slowly growing ), we needs to invest more work into interesting content, that may bring additional income. Because of this was created and published new Store, because of this I now needs to work on new system for login, new Start screen and third bigger thing will be new Map manager ( which is currently terrible user-experience ).

Most wanted feature: synchronisation. Some users wrote, it's now easy task with some existing stuff. Well, with Petr and Milan, we spend on discussions around this many many hours and we still do not have simple universal solution, that may be done within few weeks. Anyway few ideas are in our heads ... EDIT: and we also have it in list of top priorities!

Except few priorities, that I wrote before and that have to do ( even it's not kind of developement I like ), I really wants to focus in first half of year on:
  • better logging system for geocaching
  • fine-tune route planner
  • fine-tune track editor

And in second half of year
  • new design for main map screen ( close to what is visible in Route planner)
  • new track detail screen with better stats, chart, weather, etc.
  • improve Dashboard system & custom "dashboard" for track screen

My time estimates are really bad, so be aware of it ...
Uff, too long post ... sorry :).
The following users thanked this post: Leeds Tyke, Andrew Heard, Viajero Perdido, Žajdlík Josef, tbkrtz

3
Versions / Re: [APP] - version 3.29.+ ( 1. 2. 2018 )
« on: February 01, 2018, 17:44:37 »
Hi guys,
believe you have fine time  and that a new version won't cause any serious troubles. Anyway I'm ready for some bugfixing!

But, I have one idea. Is here anyone, who use fullscreen mode and never had any troubles with it? Probably not. I'm, since Android 5.0, trying to make it work perfectly and it seems, it is not possible. Anyway fullscreen mode is most useful on main map screen, or generally screen with full screen map (also like Route planner). On these screens usually problem isn't. So, what about full screen mode, that will work on these screens as now and on all other screens, bottom software buttons will be visible? Can you imagine it? Let me know. For me, it looks like ideal solution.
The following users thanked this post: 0709

4
Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: February 01, 2018, 13:52:54 »
Hurray, another new version is out. I'm ready for bug-fixing.

Thanks for help to all ;).
The following users thanked this post: Andrew Heard

5
Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: January 29, 2018, 16:56:47 »
guys, issue in training found. Recorded track was really incorrectly stored so some post-process and also upload to Strava was not working correctly. Issue fixed ... next version (final) in Wednesday ;)
The following users thanked this post: jajaballard, Žajdlík Josef

6
Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: January 29, 2018, 10:52:31 »
Hmm thanks for a test. It seems that Locus needs to report to strava, that it's an indoor training. I see there should be an option ... will check it.
The following users thanked this post: jajaballard

7
Wear for Locus Map / Re: Wear for Locus Map beta testing
« on: January 12, 2018, 15:08:57 »
Hello,
this definitely looks like a problem in Locus Map itself, not an add-on. I'll check it, thanks.
The following users thanked this post: milan.cejnar

8
Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: January 10, 2018, 16:17:22 »
Hi guys,
sorry for a delay in answers! Hope you had also nice time over last weeks ;).

@T-mo
- route planner currently does not have a "Reverse route" function
- list of points: hmm some kind of "Itinerary" similar to what you see in navigation sound interesting
- problem with texts in vector maps is a long therm problem in Locus that definitely needs to be solved this year!

@Viajero Perdido
thanks, I'll look at it with @voldapet . If I remember correctly, we had to improve generation of maps itself and add small hack into them. So issue is probably fixed in LoMaps, but not in other map from different sources.
The following users thanked this post: Viajero Perdido

9
V pohodě :). Do budoucna alespoň víš co je a není možné ...
The following users thanked this post: wlashack

10
Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: December 23, 2017, 12:12:03 »
Thanks, nice to You too, better .. to you all ;).
The following users thanked this post: Andrew Heard, Žajdlík Josef, freischneider

11
Troubles & Questions / Re: Can slope filtering be improved?
« on: November 24, 2017, 08:29:21 »
Good day Andrew,
thank you for a precise description of a problem.

Unfortunately only what I may do now, is to create an new task in our "task system", that will collect problems related to filtering of measured variables with a small promise, that I'll look at it more completely during next year. Thanks for understanding.
The following users thanked this post: Andrew Heard

12
Good day Andrew,
thanks for a report. I see main problem here that chart does not match to statistics tab. In statistics is visible that around 31 minutes, there was "no movement" and it's not correctly reflected on chart, agree.

So I hope this will be better


The following users thanked this post: Andrew Heard

13
Versions / Re: [APP] - version 3.27.+ ( 8. 11. 2017 )
« on: November 11, 2017, 22:31:07 »
@tapio:
version tomorrow .. sorry for a delay.

@Andrew Heard:
sorry to hear you had such problems with obtain of logs. It's perfect, just in this case, this method is not useful. There are two common types of problems ... crash and ANR.
Crash is when app really crash and you get dialog with "Application was terminated" (or something like this). In this case, log is useful, because in log is directly information where app crashed (not why).
ANR means "application not responding". This happen when app do too much work on background (longer then 5 seconds). Then you see dialog "Application is not responding" with option "wait" or "close". This should be your case here and log is not useful, because app did not crash, it just do something ... if you leave app for some time, it should start working again.
So thanks for a log, it did not helped for now, but I believe I've found thanks to your information a source of troubles! And now you at least know, how to create useful log (for cases when app "crash"). ;)
The following users thanked this post: Andrew Heard

14
Versions / [APP] - version 3.27.+ ( 8. 11. 2017 )
« on: November 08, 2017, 22:41:33 »
Important links
- blog post about major version
- list of news of public versions

Versions
8. 11. 2017 - Locus 3.27.0
12. 11. 2017 - Locus 3.27.1
21. 11. 2017 - Locus 3.27.1.2 - BETA version
26. 11. 2017 - Locus 3.27.1.4 - BETA version
28. 11. 2017 - Locus 3.27.1.5 - BETA version
4. 12. 2017 - Locus 3.27.1.6 - BETA version
8. 12. 2017 - Locus 3.27.1.7 - BETA version
15. 12. 2017 - Locus 3.27.1.8 - BETA version
The following users thanked this post: Bucky Kid

15
Versions / Re: [APP] - version 3.26.+ ( 11. 10. 2017 )
« on: November 03, 2017, 22:56:58 »
Oki, thanks Michael. I'm surprised, there is any difference as I expected, results will be exactly same. I'll check it ...
The following users thanked this post: michaelbechtold, erfi

Pages: [1] 2 3 ... 7