This object is in archive!
Optimize speed of core functions (viewing maps)
Declined
Locus has many of functions a new funcions are adding. But there are space for optimizing core functions as download and view maps which all users use. Not all IO (network, DB, file, ...) operations are in the background threads, optimized for multicore devices etc. Critical functions can be in native code. Some competitors are faster.
I like this idea 
These are very common statements matching almost any piece of Android software (and other software as well).
I guess you need to become much more focussed if you want to get support for your idea.
These are very common statements matching almost any piece of Android software (and other software as well).
I guess you need to become much more focussed if you want to get support for your idea.
these topic are general, but
1. I`m trying to constantly improve speed at all possible places. It`s not like I created one system before two years and it`s still same. Truth is that I still try to measure some memory leaks, CPU problematic parts etc etc. and improve them. That`s also why every new version of Locus has problems on places which previously worked fine. Every single line of code is in danger, that I create better one :))
2. current system is by me, almost on top of it`s possibilities. All is stuck on native code and OpenGL as you suggested. Both these things are still too much out of my knowledge range and I still see better places where invest time.
When I compare half an year spend on improving speed of maps by using OpenGL and half an year on creating some GUI improvements and useful features, I always end at second choice.
But when I look back, when all began, I can never imagine that after few years will exists such complex tool. And same it`s with these speed improvements. I think there is no need for special topic. These improvements will come for sure, it just need some time till I learn something more about it.
these topic are general, but
1. I`m trying to constantly improve speed at all possible places. It`s not like I created one system before two years and it`s still same. Truth is that I still try to measure some memory leaks, CPU problematic parts etc etc. and improve them. That`s also why every new version of Locus has problems on places which previously worked fine. Every single line of code is in danger, that I create better one :))
2. current system is by me, almost on top of it`s possibilities. All is stuck on native code and OpenGL as you suggested. Both these things are still too much out of my knowledge range and I still see better places where invest time.
When I compare half an year spend on improving speed of maps by using OpenGL and half an year on creating some GUI improvements and useful features, I always end at second choice.
But when I look back, when all began, I can never imagine that after few years will exists such complex tool. And same it`s with these speed improvements. I think there is no need for special topic. These improvements will come for sure, it just need some time till I learn something more about it.
Replies have been locked on this page!