After 4.3 is out...
Anton Lundin
glance at acc.umu.se
Wed Dec 17 15:03:46 PST 2014
On 17 December, 2014 - Robert Helling wrote:
> … what are people planning to spend time on?
>
> For me that would be (not necessarily in that order)
>
> 1) pSCR (as just explained in a different mail)
>
> 2) Making image integration more portable between the devices, in a way to be determined: paths relative to a (configurable) image_root, relative paths from home etc, images from the web… We talked about this before.
>
> 3) Increasing responsiveness of the planner (doing some profiling, maybe splitting the replot into smaller tasks that not all need to be redone upon changes of data etc)
>
> And of course there is the big elephant in the room (but I probably cannot really contribute due to lack of ideas/understanding): Coming up with a UI to utilize the git save/load.
>
> Other ideas?
>
I have a stack of fixes i found with valgrind. They are mostly minor
leaks and i figured rather a leaky and working subsurface than a
non-leaky potentially crashing subsurface when we are cutting a release.
The configure-dc/fwupdate-dc code needs a progressbar and a bit better
fault handling.
Figure out how and what can be configured in the OSTC Sport and build
some configure code for that one too.
Some auto-discovery of new firmwares for OSTC/OSTC3/OSTC Sport's and hook
that up with the firmware-updating code so the user can get a "Hey, your
fw is OMG OLD!, click here to update" dialog.
Saving separate o2-cell-values for more computers than just the MkVI,
and build some cell-validation-analysis? Tracking o2-cell performance
over time to be able to do pre-fail-warnings?
Finish off the android downloader code and get that app actually
working.
Build a android-planner based on the subsurface planner?
//Anton - END-OF-IDEAS
--
Anton Lundin +46702-161604
More information about the subsurface
mailing list