Hi

Both 'usableDisplayWidth' & 'usableDisplayHeight' are good and needed but both have potential problems. The width value can vary on devices that support portrait/landscape browsing options. The height value is problematic as some devices allow full screen browsing so the height changes.

For height I'm happy to live with the default, but for the landscape/portrait devices we need to know both sizes (and probably the default orientation).

For Environment I find the proposed values a bit limiting, is osSymbian useful if it doesn't indicate S60 vs UIQ (or will that be in osVersion). Why no osMacOSX ... you can write applications for it and it is as open as S60, UIQ or RIM? It would seem better to just use osType with defined values rather than osSymbian, osLinux, osWindows, osRim and osProprietary.

Regards

Scott

Very good points Scott.

WRT default orientation and devices that are capable of also using a different orientation, it is something we should track in the future. As things stand we do not have this information, but I agree with you it is valuable and we should add it to the top of our list of properties.

In your experience, would a single boolean property be enough to track full screen mode support? We could create one extra property along the lines of "canDoFullScreen" and the designer can act appropriately.

Of course, both orientation and full screen mode are dynamic and with today's technology in your average device, does not offer access to this information to the designer/developer.
This is one of the reasons why I am pushing back these properties a bit. You might or might not know that the OMA is working in this direction, Vodafone is also doing something similar in their labs (you can read about this on Betavine) and there is at least one commercial solution already on the market. I think these properties will become much more interesting once these technologies are deployed.

Lastly, I take your points about operating systems. OS X can be added to the list, of course, no point not to. The reason why we were suggesting 1 property for every OS was to keep consistent with the other properties we have where we tried to stay with booleans, much easier to manage in an application rather than text that needs to be parsed. For a moment we even considered having the boolean properties and one generic property that would be a string and would hold the name of the OS. If that was the case we could drop the osProprietary and just have one along the lines of osType or osName.
osVersion was more for a version number so "8.0", "9.0" and so on. The S60 and UIQ problem is interesting. I wonder if we will have Gnome and KDE on mobile devices! :)
Correct me if I'm wrong, but aren't S60 and UIQ frameworks that provide a set of API's built on top of the core Symbian implementation?

Is it still possibile to propose new properties?

We would LOVE to hear more suggestions for new properties.

I would like to propose a property to detect if a device can stream video.

I believe WURFL and UAProf both have this attribute, so it would be nice if it was implemented into DA.

Streaming is high in our list of properties that we want to add.

There are quite a few properties that would help about streaming such as HOW the file is delivered, video codec, the audio codec, the framerate. Do you have any ideas about what you would need for your application? Want to share some thoughts?

Is there anywhere I can find out the definitions for the properties.

Whilst we can work out the vast majority, it would be nice to see a list of ALL available properties and their respective description - i.e. aacInVideo = Supports AAC in video, midip = ???

Regards

http://deviceatlas.com/properties/
Here you can find the properties supported by Device Atlas at this moment.

For instance, instead, http://wurfl.sourceforge.net/help_doc.php here you can see all properties supported by Wurfl (there are a lots of item!)

Bye!

I know the system is geared towards the mobile web, but messaging capabilities would be useful.
Can the handset recieve MMS, Nokia Smart Messaging, EMS and WAP Push.

HTML 4.01

JavaScript

JScript

XMLHTTP

XMLHttpRequest

Christian Louboutin Sale dryrty