On 14.2.2013 2.36, "Pete Batard" <p...@akeo.ie> wrote: >I'm sorry, but I don't get why we seem so hell bent (as it looks to me)
Well, no, it is just difficult to keep one's hands of the keyboard when something 'interesting' surfaces. I'm in no hurry with hotplug, I was just curious and wanted to get reactions to recent libusb progress and that lead to the discussion (more about the usage of words than about the actual API). >And maybe some of you here feel that libusbx should be tied to the >libusb API, but I don't see much point in participating in a fork if we >can't go in our separate direction should we think it'll help our users >better, especially if the reason for a deviation is users reporting that >a first proposal doesn't work that well for them. And yeah, this means >that our users may eventually have to choose between two incompatible >APIs and non interchangeable libraries, but that's really the essence of >forks (and that's alos why I believe we should only introduce hp in 2.x >of libusbx to alleviate the problem). I'm with you there. > >So, to get back to the current point, in case you ask me right now what >kind of cross-platform API we should go with for hotplug and whether we >want to go with DRIVERLESS_WHATEVER events, I'll continue to state "I >don't know". And I'm not gonna know until I have a proposal with some >Windows code, alongside the Linux and OS X one, that we can place in the >end of our users, so that we finally start to receive feedback. That's fine, I just wanted to understand why it might be beneficial to do what was discussed and got educated. cheers Kusti ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
