Regarding the prefs.xml and queue.xml files:
It would be very handy if these files used some newlines so that they were human readable.
For example, instead of storing them as a single line of text like they are now:
<MediaCoderPrefs><node key="overall.generic.priority">Idle</node><node key="overall.generic.ignoredBuild">5588</node><node key="overall.ui.mode">Advanced</node><node key="overall.ui.expertView">Audio Command</node>
It would make it easier read and to troubleshoot things if they had some formatting:
<MediaCoderPrefs>
<node key="overall.generic.priority">Idle</node>
<node key="overall.generic.ignoredBuild">5588</node>
<node key="overall.ui.mode">Advanced</node>
<node key="overall.ui.expertView">Audio Command</node>
This would also allow the use of line-based text file comparison tools, for quickly finding what's changed between two copies of the same file, like prefs.xml.
Thanks
Fin
Human Readable xml files
-
- Amateur
- Posts: 68
- Joined: Fri Dec 21, 2012 6:56 am
Re: Human Readable xml files
I second that
I use the very lightweight xml editor from http://www.firstobject.com/ to prettify all my saved presets. Makes it easier also to use WinMerge afterwards to figure out differences.
I notice this website also promotes a c++ library (and maybe some other languages). Perhaps of use to Stanley, although I admit I didn't look deeply into it.
I use the very lightweight xml editor from http://www.firstobject.com/ to prettify all my saved presets. Makes it easier also to use WinMerge afterwards to figure out differences.
I notice this website also promotes a c++ library (and maybe some other languages). Perhaps of use to Stanley, although I admit I didn't look deeply into it.
Re: Human Readable xml files
Changing a XML library takes lots of work. I will look at libxml to see if there is an option.
When things work together, things work.