W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: [widgets] Screenshots and case sensitive file names

From: Marcos Caceres <marcosc@opera.com>
Date: Thu, 12 Mar 2009 17:53:06 +0100
Message-ID: <b21a10670903120953p395ff557w4a57970344704807@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>
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

On Wed, Mar 11, 2009 at 3:11 PM, Marcos Caceres <marcosc@opera.com> wrote:
> Might be good if we allow multiple screenshots in a widget. One
> screenshot is just not enough to show off all aspects of a widget that
> would motivate someone to download a widget. The file naming
> convention would be identical to the Widgets Signatures file naming
> convention:
>
> thumbnail.jpg
> thumbnail1.png
> thumbnail2.png
> thumbnail3.png
>
> etc.
>
> Also, I think not having case sensitivity on file names is going to be
> a PITA. I propose we make all file names case sensitive (particularly
> because there is a possibility of file names being encoded in UTF-8,
> in which case we enter a world of hurt when it comes to distinguishing
> between character cases). This mildly affects the i18n, where we will
> recommend language tags be in lower-case form (i.e., en-us, not
> en-US).
>
> I can add authoring and conformance checker requirements to suit.
>
> Kind regards,
> Marcos
>
> --
> Marcos Caceres
> http://datadriven.com.au
>



-- 
Marcos Caceres
http://datadriven.com.au
Received on Thursday, 12 March 2009 16:53:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:30 GMT