hm, if SoC is the argument, then shouldn't we consider the who is doing what discussion?
my feeling is that touching the xconf is out of question to a lot of users? They could easily write up a custom-binding and be glad they never need to learn about the xconf in the first place?
I don't know if I follow this argumentation. Having configuration splitted over multiple files might help the user at the beginning, but can lead to a nightmare at the end. But maybe I just want to do anything to perfect :)
the only config part that would make sense on the xconf level is the class-name, the rest would be local config that needs to be in the binding file anyway (like you say: why scatter it around in different places?)
Ok, this convinces me at least partly ;-)
Joerg
