I've opened ADFFACES-110 for this issue. https://issues.apache.org/jira/browse/ADFFACES-110
We are planning on supporting BlackBerry Browser 4.0, which supports XHTML MP, plus some additional features. We do not plan on providing full support for earlier BlackBerry Browsers. For example, versions 3.2&3.3 (which support compact HTML) and 3.6&3.7 (which support XHTML Basic). I am making two assumptions, and would welcome any input on them: 1) The capabilities we specify should match what the browser actually supports, not what the documentation says it supports. For example, the 4.0 browser documentation does not mention support for the "readonly" attribute of the input element, but the browser does in fact support it, so I'm setting -adfinternal-readonlyFormElements to true. It feels dirty to rely on an undocumented feature, but I figure we are targeting the "real world" device, not some specification. 2) It is okay/desirable to provide an Agent/capabilities for the earlier BlackBerry browsers even if we are not planning on supporting them explicitly (that is, not verifying that all Trinidad features work on them). This way the developer can still detect that it is a BlackBerry and the version number if they so choose. I'm planning on adding two entries to capabilities.xml: "blackberry" for pre-4.0 with the most basic set of capabilities, and "blackberry4" for 4.0+ capabilities. Would it be preferable to only define an Agent/capabilities for browsers for which we are explicitly providing support? Take care, Joey On 8/2/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
+1 for the proposal +1 for going ahead with the jira ticket 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 > -- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
