On Mon, Jan 30, 2012 at 11:49 AM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: >> +<!-- >> + The autopair plugin will match devices, following the order of the XML >> + file [1], on any combination of type, OUI, or name. >> + >> + [1]: So specific devices should be at the top, and generic ones at the bottom, >> + so settings for specific devices are overridden as expected. >> +--> >> + >> +<!DOCTYPE devices [ >> + <!ELEMENT devices (device)+> >> + <!ELEMENT device EMPTY> >> + <!ATTLIST device type (any|mouse|tablet|keyboard|headset|headphones|audio|printer|network) "any"> >> + <!ATTLIST device oui CDATA #IMPLIED> >> + <!ATTLIST device name CDATA #IMPLIED> >> + <!ATTLIST device pin CDATA #REQUIRED> >> +]> > > I think we need to have a discussion on this database format first. I > honestly do not like it at all. It does matching and result handling in > a single XML element. That seems like a bad idea. > > And in addition making pin attribute required and then trying to disable > PIN with "NULL" magic is something that I rather not have. > > I am also wondering why this has to be XML and not simple key-value INI > style files. > I tend to agree ;-) The reason it couldn't be pure INI-style (at least, parseable by glib) though is because you then need unique group names for each match, which is equally urgh to write. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist? -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
