[chirp_devel] RFC settings import export

[Jens J.]

Also, I seem to recall some sort of long description field in settings that I attempted to use, but did not do anything.
I was looking for some UI control akin to a label or tooltip (i.e., to provide a longer description or notes about a particular setting) but could not find anything that did that.
If such a thing existed, it would be useful in an export

On the format of csv, seems like the following fields would be useful:
setting_name, group_name, setting_description, type, value


types: boolean, int, float, list, string

Not sure if having a column for the possible values of a setting, such as range or list, would be of any value to the user.

Seems like there would need to be some logic at import time to resolve any conflicts or missing, as I dont think there is a concept of "default values" for settings within chirp at this point.  Along these lines, settings can also change/expand over time with newer versions of software. Conflict/missing resolution would also be needed here.
I guess if it's importing settings over an existing radio image, this may be easier.
But there is still the general idea of how to deal with InvalidValueError exceptions!

-J


________________________________
 From: Jens J. <kd4tjx at yahoo.com>
To: "chirp_devel at intrepid.danplanet.com" <chirp_devel at intrepid.danplanet.com> 
Sent: Sunday, December 29, 2013 6:11 PM
Subject: Re: [chirp_devel] RFC settings import export
 


In my limited dealings with settings on a few radios, they seem very proprietary.
How can you "serialize" these?
Noting that not all radios have settings stored within a single array or struct - there may be multiple places, and then some custom logic on how it's read from and stored to radio image.

Now that I think about it, perhaps you could export just Chirp's view of the settings, as it is more or less a tree structure, with a few fixed types and values.
Seems like it would work ok to import settings between same models, but would get very tricky (if not impossible) to implement across models.

-J


________________________________
 From: IZ3GME Marco <iz3gme.marco at gmail.com>
To: chirp_devel at intrepid.danplanet.com 
Sent: Sunday, December 29, 2013 6:05 PM
Subject: [chirp_devel] RFC settings import export
 

Hi all
from recent comments in users list I'm thinking to implement import-export of settings to cvs.
I'm not going to try any cross model support at first.

Comments?
Do you see any drawback?

73 de IZ3GME Marco
_______________________________________________
chirp_devel mailing list
chirp_devel at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers




_______________________________________________
chirp_devel mailing list
chirp_devel at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20131229/09344dcd/attachment-0003.html