+1.

-- Adam


On 8/2/06, Joseph Rozier <[EMAIL PROTECTED]> wrote:

Hello,

Piyush Hari and I are planning to work on adding additional PDA
support in Trinidad.

Specifically, we intend to help maintain the Pocket IE 2003 support as
well as add support for Mobile IE 5.0 (the successor to Pocket IE
2003) and the BlackBerry Browser 4.0.

To start us off, I would like to propose the addition of Agent support
for BlackBerry Browser 4.0.

Specifically, this change would involve:

1)  The addition of the BlackBerry Agent and Platform contants in
org.apache.myfaces.trinidad.context.Agent.  The BlackBerry Browser 4.0
runs on BlackBerry devices.  Therefore, the Agent and Platform will
both be "blackberry."  (Compare to Pocket IE, where the agent is "ie"
and the platform is "ppc" for PocketPC.)

2) The specifcation of BlackBerry specific capabilities values (in a
blackberry.xml file in
trinidad-impl\src\main\resources\META-INF\agent).  The capabilities
values will be quite similar to the Pocket IE 2003 capabilities
values, except at this point it looks like no PPR will be supported
(-adfinternal-partialRendering will be false and -adfinternal-xmldom
will be false).

3) The detection of the BlackBerry User-Agent string in
org.apache.myfaces.trinidadinternal.agent.AgentFactoryImpl.

One question I have is the use of the hardwareMakeModel property of
the Agent interface.  It appears that no Agents currently support
this.  I would like to support this for the BlackBerry.

The BlackBerry User-Agent string starts with
BlackBerry<model>/<version>, where <model> is the device model.  For
example, for the BlackBerry 8700 running the BlackBerry Browser 4.1.0,
the value is BlackBerry8700/4.1.0.

Does it make sense to others that the hardwareMakeModel for the
BlackBerry agent should be the String "BlackBerry<model>" (e.g.
"BlackBerry8700")?  Since no other Agent sets the hardwareMakeModel, I
have no convention on which to rely.

Please let me know your opinions on this proposal so that I may open a
JIRA (and provide the patch).

Take care,

Joey

Reply via email to