[18:55] <OvenWerks> Eickmeyer[m]: The time has come...
[18:56] <OvenWerks> It looks like it is time to change the config file format
[18:56] <OvenWerks> The xml lib looks easier to use. Th json format looks cleaner to read
[19:03] <OvenWerks> Eickmeyer[m]: I am adding a data base of all the devices in a system to the config file so that people can hide them set rate/buffer/nperiods/i/o per device. With the whole set of loop devices we saw, I think the lines will be too long to do a list of space separated devices names
[19:05] <Eickmeyer[m]> OvenWerks: Yeah, the existing config file keeps crashing if it's formatted incorrectly, so I agree.
[19:05] <OvenWerks> I did not know that. I have not had that happen here
[19:06] <OvenWerks> Or is that old to new...
[19:22] <OvenWerks> All of the examples are too simple, they do not explain adding nodes.
[19:31] <Eickmeyer[m]> Nah, it's people in Fedora mostly. Simply deleting .config/autojack fixes it.
[19:48] <OvenWerks> I may make a small utility that takes autojackrc in and puts out autojack.json if the first exists and the second not. Autojack can run it on startup if it find old and not new.
[19:48] <OvenWerks> That way studio-controls and autojack can be clean, one format only.
[19:59] <Eickmeyer[m]> That might work.
[22:51] <OvenWerks> Eickmeyer[m]: this is going to be a rather large change :P
[23:12] <Eickmeyer[m]> OvenWerks: Are we looking at a 3.0 bump?
[23:33] <OvenWerks> Eickmeyer[m]: it is no wonder setting up json looked so hard. What they don't tell you is it is basically a python dict.
[23:33] <OvenWerks> I was going for a 2.1
[23:34] <OvenWerks> so If I create a python dict to hold all of my config options... one command savs it that way
[23:39] <Eickmeyer[m]> OvenWerks: Ooo! nice.