Hi all,

Thanks for all the advice.

Reading Tizen 3 source has already yielded the following list of objects
exposed in the Javascript namespace:

tizen.alarm
tizen.application
tizen.bluetooth
tizen.bookmark
tizen.calendar
tizen.callhistory
tizen.contact
tizen.Contact
tizen.ContactGroup
tizen.ContactRef
tizen.ContactName
tizen.ContactOrganization
tizen.ContactWebsite
tizen.ContactAnniversary
tizen.ContactAccress
tizen.ContactPhoneNumber
tizen.ContactEmailAddress
tizen.Content
tizen.datacontrol
tizen.datasync
tizen.download
tizen.filesystem
tizen.locale
tizen.mediaserver
tizen.messageport
tizen.messaging
tizen.nfc
tizen.networkbearerselection
tizen.notification
tizen.package
tizen.power
tizen.push
tizen.seService
tizen.speech
tizen.systemsetting
tizen.systeminfo
tizen.time
tizen.vehicle
tizen.websetting

I am struck by the Contact objects all appearing as second-level under
tizen, as opposed to being grouped under tizen.contact; I wonder why they
are different.

Anyway, while the link
https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.web.device.api is
helpful for developer documentation, what I am looking for is more along
the lines of a dependency tree, i.e. something saying that tizen.vehicle
depends on automotive message broker, or that tizen.bluetooth depends on
bluez.  To that end, I appreciate the suggestion to use rpm.  The command:

 rpm -q --requires wrt-plugins-ivi

yields a moderate list of libraries, of which the relevant ones appear to be

libwrt-plugins-tizen-mediaserver-impl.so
libwrt-plugins-tizen-speech-impl.so
libwrt-plugins-tizen-vehicle-impl.so

which provide the interfaces supporting tizen.mediaserver, tizen.speech,
and tizen.vehicle respectively.  (This is the simpler example;
wrt-plugins-tizen has a much longer list of libraries, some of which
support the rest of the namespace.) So far so good, but this is where I get
stuck.  I do not know what commands to give rpm in order for it to tell me
what underlying packages are used by, for example,
libwrt-plugins-tizen-vehicle-impl.so.  I think it relies on the various
automotive-message-broker rpms, but I am unable to find an rpm command
which will tell me that tizen.vehicle is in any way reliant on AMB.  Is rpm
able to do this?  What rpm command should I be using?

Thanks,
Steve Gerken
-------------------
Linux Developer
MSX, as broker for Jaguar Land Rover

One World Trade Center, 121 SW Salmon Street, 11th Floor, Portland, Oregon,
97204
Email: [email protected]
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to