Using the PEAR class Net_UserAgent_Mobile as a starting point, how
about the following:
Common class methods:
getCarrierLongName
getCarrierShortName
getDisplay
getHeader
getName
getUserAgent
getVersion
isAirHPhone
isDoCoMo
isError
isEZweb
isJPhone
isNonMobile
isTUKa
isVodafone
isWAP1
isWAP2
makeDisplay
noMatch
parse
raiseError
Display class methods:
calcSize
getDepth
getHeight
getHeightBytes
getSize
getWidth
getWidthBytes
isColor
EZWeb class methods:
getDeviceID
getModel
getServer
isEZweb
isTUKa
isXHTMLCompliant
There are more, but I'll spare you. See the PEAR docs for more details:
http://pear.php.net/package/Net_UserAgent_Mobile/docs/0.25.0/classtrees_Net_UserAgent_Mobile.html
These are the method calls for the various Classes, and give an idea
on what kind of meta data people use. For instance the getWidth is
useful to calculate if an image should be/can be displayed. Other
useful info I would like to see is image file formats that are
supported: JPEG, GIF, PNG. Maybe even format versions ...
I haven't played w/ video or audio, but I'm sure with the new batch of
mobiles the ability to know the device capability will come in handy
in your next mobile web project. Also, QRCode and Felica capability
doesn't seem too far off.
chriskk
On 11/2/05, Kyle Barrow <kyle@pukupi.com> wrote:
> I think a WUFL patch would be a the best way to incorporate Japanese
> mobile capabilities into WUFL and am prepared to lend a hand on this
> front but what extra information are developers looking for?
>
> It would be great if we could build a list of these before anyone
> starts work on a patch? DC?
>
> Cheers
>
> Kyle
>
> --
>
> mobile web gear | pukupi.com | 34°40'n 135°30'e
--
b: http://moblog.oreno.org/
e: chriskk@gmail.com
Received on Wed Nov 2 10:48:33 2005