Thanks all for the clarification. Regards,
Fang Wang Solution Architect, Conversational Speech Solutions IBM Certified IT Specialist IBM Software Services for Websphere e-mail: [email protected] ******************************************** Cell: (214)394-4757 **NEW NUMBER** ******************************************** ______________________________ Certified Nuance Technical Associate Nuance Enterprise Technologies From: "Rees, Kevron" <[email protected]> To: "Hanchett, Paul" <[email protected]>, Cc: Fang Wang/West Palm Beach/IBM@IBMUS, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Date: 01/31/2014 11:41 AM Subject: Re: [Dev] mismatch in vehicle data from AMB DBus plugin API and the HVAC web application? In addition to what Paul said, the web api has a "zone" attribute that should correspond with the DBus API zone. You can find out which zone a given objectName is in with the listZones call: https://review.tizen.org/gerrit/gitweb?p=profile/ivi/wrt-plugins-ivi.git;a=blob;f=src/Vehicle/Vehicle.idl;h=324b09a996c0da0c7d794bdbd803702bf4320f09;hb=refs/heads/tizen#l122 -Kevron On Fri, Jan 31, 2014 at 8:23 AM, Hanchett, Paul <[email protected]> wrote: > Fang-- > > AMB defines a base set of property types (like the SeatHeater setting you > mention). At initialization time, a plugin instantiates storage for the > property and assigns it to a Zone (names like Zone::None, Zone:Front, > Zone:Left, Zone::Right, Zone::LeftFront which is a sort of logical OR > between Zone::Front and Zone::Left-- Look for the Zone class...) > > So, in the case you mention a plugin would declare that there's a SeatHeater > in Zone::LeftFront and another in Zone::RightFront. > > Paul > > > > Paul Hanchett > ------------------- > Infotainment Engineer > MSX on behalf of Jaguar Land Rover > One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, > Oregon, 97204 > > Email: [email protected] > ------------------- > > Business Details: > Jaguar Land Rover Limited > Registered Office: Abbey Road, Whitley, Coventry CV3 4LF > Registered in England No: 1672070 > > > On Fri, Jan 31, 2014 at 3:43 AM, Fang Wang <[email protected]> wrote: >> >> Hi, >> >> I looked through the vehicle data in the AMB DBus API. There are some >> mismatches between the data at DBus layer and the representation at the web >> application. For example, for HVAC, the web app shows seat heater for left >> side and right side. But the api layer only shows one SeatHeater property. >> Similarly for TargetTemperature. How would these be mapped out? For the Auto >> and Max buttons on HVAC web application, my understanding is that the logic >> is in the web application to turn on a few other properties based on >> different scenarios. But not sure how these two sides properties at HVAC web >> app mapped to the single properties at DBus layer. Did I miss anything. I >> did see the latest change to move defrost property in to windows object so >> can specify the rows for the defrost button, which would distinguish the >> front and back defrost? thanks. >> >> >> Regards, >> >> Fang Wang >> Solution Architect, Conversational Speech Solutions >> IBM Certified IT Specialist >> IBM Software Services for Websphere >> e-mail: [email protected] >> ******************************************** >> Cell: (214)394-4757 **NEW NUMBER** >> ******************************************** >> ______________________________ >> Certified Nuance Technical Associate >> Nuance Enterprise Technologies >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> https://lists.tizen.org/listinfo/dev >> > > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi >
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
