W3C home > Mailing lists > Public > public-ddr-vocab@w3.org > June 2007

Re: Height vs Width when a screen can rotate

Date: Thu, 21 Jun 2007 21:03:28 +0200
To: Rotan Hanrahan <rotan.hanrahan@mobileaware.com>
Cc: public-ddr-vocab@w3.org
Message-id: <f834dfb48e64.8e64f834dfb4@tid.es>

wouldn't be two properties / pseudo-properties whose names are
currentWidth and currentHeight?? 

Best Regards

José Manuel Cantera Fonseca
Telefónica I+D

----- Mensaje original -----
De: Rotan Hanrahan <rotan.hanrahan@mobileaware.com>
Fecha: Jueves, Junio 21, 2007 8:59 pm
Asunto: Height vs Width when a screen can rotate
Para: public-ddr-vocab@w3.org

> The Height and Width properties were contributed as candidates to the
> DDR Core Vocabulary. However, the description of these notes that they
> are interpreted based on a screen being in its normal/default
> orientation.
> Does this mean that if I want to get the width of a display that I 
> firsthave to check if it can be rotated, and then if it can, I must 
> check if
> it is rotated, and if it is, then instead of retrieving the width, I
> should retrieve the height?
> As I'd probably want to do this in all cases, it means I have to be
> aware of such relationships and processes just to figure out the width
> of the screen so I can resize my logo banner. Surely we could also
> suggest a set of convenience functions so that we can have a
> CurrentWidth() and CurrentHeight() method. One could imagine that such
> methods would be empowered to figure out if getting the state from the
> client is possible, and if not, then to use some default, like getting
> the width directly from the DDR and hoping that because this is the
> default that this is the most likely correct answer.
> There's nothing in the charter about the DDWG suggesting convenience
> functions. But they'd be nice to have anyway.
> ---Rotan.

Received on Thursday, 21 June 2007 19:03:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:38:13 UTC