Hi Emil, >This is the tricky part - wish I could find my notes they have better >brain-dump. >It's OK to have the library as both front (config tool) and backend >(used by mesa) although: > - special care on splitting and annotating the API is needed > - handling this "extra" dependency would be fiddly for slower moving distros > I'm not sure I get the whole picture of what you are suggesting, so I put some ideas on how I think such API would work [here][1].
>> What about the current configuration files? Do you think there is a better >> way to handle them? >> They are for in a xml format, which is far from optimal. >> >What seems to be the problem with XML? The files are meant to be >read/written to $app. > I dislike XML because it is too ugly. Something more natural and easy to read/write would be more interesting. Like a YML format. Ideally I would like to use JSON, but then it becomes a lot harder for people to write this by hand in case the GUI tools don't offer the options they want/need. Of course this is just my point of view, and not necessarily a real issue. Kind Regards, Jean Hertel [1]: https://github.com/jlHertel/libdriconfig/blob/master/USAGE.md _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
