I also agree with this proposal

> 
> Benoit  Suzanne
> Widget Factory Project Manager - Orange Labs - FT/RD/SIRP/SOL/SLAM
> t. +33 (0)145 298  198 - m. +33 (0)680 287 553
> benoit.suza...@orange-ftgroup.com
> 
 



> From: Arthur Barstow <art.bars...@nokia.com>
> Date: Fri, 13 Mar 2009 07:12:06 -0400
> To: "marc...@opera.com" <marc...@opera.com>
> Cc: public-webapps <public-webapps@w3.org>
> Subject: Re: [widgets] Screenshots and case sensitive file names
> Resent-From: <public-webapps@w3.org>
> Resent-Date: Fri, 13 Mar 2009 11:13:33 +0000
> 
> Marcos - I prefer your 2nd proposal. Unless contrary views are
> expressed in the next few days, I recommend adding your proposal to
> the ED.
> 
> -Regards, Art Barstow
> 
> On Mar 12, 2009, at 12:53 PM, ext Marcos Caceres wrote:
> 
>> Hi,
>> I've decided that having the screenshots at the root of the widget (or
>> at the root of localized folders) is just messy. Also, the naming
>> convention will probably confuse authors, so I've created a screenshot
>> element for consideration.
>> 
>> [[
>> 
>> The screenshot Element
>> A screenshot is a file inside the widget resource that graphically
>> represents the widget in a running state.
>> 
>> Context in which this element may be used:
>>  In the widget element.
>> 
>> Occurrences:
>>  Zero or more.
>> 
>> Expected children:
>>  none.
>> 
>> Attributes
>> src: Required. A valid path that points to a file inside the widget
>> resource.
>> 
>> Usage Example
>> 
>> <widget xmlns="http://www.w3.org/ns/widgets";>
>> <screenshot src="/screenshots/mainscreen.jpg"/>
>> <screenshot src="/screenshots/level1.jpg"/>
>> </widget>
>> ]]
>> 
>> I considered adding a "preferred" attribute, but then decided that
>> it's first declared is most preferred, and so on. This will be
>> reflected in the order in which the screenshots are stored in the
>> configuration defaults (i.e., I'll make it explicit that screenshots
>> should be stored and presented in the order they appear in the
>> document).
>> 
>> WDYT?
>> 
>> Kind regards,
>> Marcos
> 


Reply via email to