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

RE: Height vs Width when a screen can rotate

From: Rotan Hanrahan <rotan.hanrahan@mobileaware.com>
Date: Thu, 21 Jun 2007 20:17:23 +0100
Message-ID: <D5306DC72D165F488F56A9E43F2045D3011C7080@FTO.mobileaware.com>
To: <public-ddr-vocab@w3.org>

In reality the DDR on its own is for cases where you can only access static properties, so for currentX you have to use defaultX instead.

Outside of this simple DDR use case, you have the possibility of client-side queries where you have direct access to client state so you can get currentX without concern. On the server side, you *might* be able to get the current values (e.g. via an Ajax callback to the client) so what you really need is a convenience method that looks at all the possible ways it might get the answer and uses the best way.

But who would suggest these convenience methods? The DDWG? The UWAWG? The OMA? Somebody else?

It's digressing from the narrow focus of the DDWG's DDR, which is about holding static properties for others to use in their adaptation solutions, but overall there should be some agreement on what methods (not just properties) might be useful for adaptation.

To be clear: I don't see such methods being in the DDR API.

My problem was not about the dynamic nature of width and height, but about the interpretation of the words "width" and "height". In the suggested description of the Width and Height properties for the DDR Core Vocabulary, these terms are explicitly defined in terms of the *default* orientation of the screen. However, the words "width" and "height" have a different meaning when you think of currentWidth and currentHeight, because in this situation the words are interpreted with respect to the *current* orientation.

It has potential for confusion, I think.


-----Original Message-----
From: JOSE MANUEL CANTERA FONSECA [mailto:jmcf@tid.es] 
Sent: 21 June 2007 20:03
To: Rotan Hanrahan
Cc: public-ddr-vocab@w3.org
Subject: Re: Height vs Width when a screen can rotate


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:19:58 UTC

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