Re: Gnomad2 and libmtp

--- [email protected] wrote:

> Couple of suggestions - now that multiple protocols
> are supported is it necessary to have BOTH libmtp
> and libnjb in order to compile gnomad2? If so, maybe
> that design coukd be reconsidered for a dynamic load
> of the appropriate library based on a command line
> option or a config parameter?
>=20
> Secondly, to save you and the rest of us loads of
> time with having to fit all our apps to two APIs,
> wouldn't it be cleaner to design an abstract API so
> that the apps address this one API (gettrack,
> getmeteadata, putfile, settime etc etc) and  libnjb
> and libmtp are the backend implemetations of it -
> maybe the route to go would be to change libnjb to
> have the same front-facing interface as libmtp?
>=20
> Just suggestions.
>=20
> Martin
>=20
>=20

I'd have thought the issue here might be that libmtp
(or so its name suggests) handles MTP devices in
general, which I don't think are limited to Creative
MP3 players, while libnjb is Creative-specific.=20

One approach to the multiple-API issue might be that
libnjb decides when to use libmtp in place of its own
code, hiding this from the app? So apps wanting to
access Creative MP3 players would continue to use
libnjb as before. Not sure how practical that would
be.=20

You'd still need both libraries present, but you'd
hope that in due course libmtp would become a standard
part of most distros anyway, like libptp.

Steve



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
that extends applications into web and mobile media. Attend the live webc=
ast
and join the prime developer group breaking into this new coding territor=
y!
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D=
121642