From my point of view. I would like to see libusb-1.0 go through another iteration or two. Remove the dependency on WinUSB and the other dlls. Get as many of the core functions working cross platform as possible.
We may eventually need to migrate to a 2.0 version. But I would rather not see the developer fragmentation that dual paths would cause right now. One core issue that I see as a need to be addressed. Is a set of tests with baseline devices which exercise all functions of every API on every platform. No final release until all the test boxes are checked. Problems are being fixed, but are we introducing new ones? On 09/29/2012 06:00 PM, Pete Batard wrote: > On 2012.09.29 02:20, Xiaofan Chen wrote: >> The thing is that the fork is now much more popular than the >> existing libusb among Linux distros > Alas, still not Slackware 14.0, which was released yesterday, and turns > out to be the distro I use most of the time. :) > >> My suggestion is to continue new development in 2.0/3.0 >> but keep 1.0.x for a while (1.0.15 can be 1.0.14 + bug fix >> + USB 3.0). > I think that's more or less what we agreed on. I don't have the scope to > maintain 2 branches at once, which is why I indicated that I'd have to > drop 1.0 as we move the API forward, but Hans agreed to pick it up. > >> I do not see an issue of changing to libusbx.h for 2.0/3.0 series. > OK. Let's see if there are other voices against a libusb.h -> libusbx.h > rename in 2.0, or if Hans has some more elements he wants to bring > forward against that. > > > Now, with regards to the 2.0 API, I have created a wiki page, that > points to the 1.0 -> 2.0 diff (bottom link). It can be accessed at: > https://github.com/libusbx/libusbx/wiki/API-2.0 > > Basically, I have created a libusb.h wiki page [1], containing the > header, and I'm just using the history diff from the wiki for link. > You can edit the header, preferably adding your changes in the list from > the API-2.0 page as well, and once you're done, just go to page history, > select the first and latest, and click compare revisions. You should > then update the link from the API-2.0 page with the URL you get. > > I wish there was a way to get a diff that displays the full content of > the page, but haven't been able to get that from github. > > Note that at this stage, not all the changes we discussed are in, so > feel free to go ahead and add the missing ones. > > Regards, > > /Pete > > [1] https://github.com/libusbx/libusbx/wiki/libusb.h > > ------------------------------------------------------------------------------ > How fast is your code? > 3 out of 4 devs don\\\'t know how their code performs in production. > Find out how slow your code is with AppDynamics Lite. > http://ad.doubleclick.net/clk;262219672;13503038;z? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > libusbx-devel mailing list > libusbx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libusbx-devel > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
