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@gmail.com>
To: chirp_devel@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@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers