W3C home > Mailing lists > Public > public-appformats@w3.org > November 2006

Re: [Widgets] Restriction to index.html

From: Ed Voas <voas@yahoo-inc.com>
Date: Wed, 15 Nov 2006 18:34:15 -0800
Message-Id: <09A2FD4D-A5DF-4236-9CBA-0C7DFEA79C93@yahoo-inc.com>
To: public-appformats@w3.org

I was thinking something similar, having the 'config/metadata/info'  
file (currently config.xml) name the main file to load, as you've  
done with your src attribute. The name of the file should totally be  
freeform. Having it specified though is something I'd personally like  
for our stuff as we currently have to troll the folder to find the  
first .kon file we have. ick.

On Nov 15, 2006, at 4:45 PM, Marcos Caceres wrote:

>
> Hi Chris,
> Thanks for the suggestion. Like you said, despite what is currently  
> said in the spec, it will not be a requirement that a widget  
> package contain an 'index.html' file anywhere. The manifest format  
> will provide a (yet-to-be-specified) mechanism to allow authors to  
> declare which file launches first. This will overcome the is issues  
> related to having an "index.<extension>" and accommodate  
> implementations, such as Yahoo!'s Widget Engine, that don't use  
> HTML to as the UI language. That way, developers can name their  
> "index" file whatever they want. However, we should nevertheless  
> recommend that developers name their main widget file  
> "index.<extension>" for the sake of consistency. I personally would  
> not like to formally specify "index.<extension>" as the required  
> file name, particularly in an internationalized context.
>
> Here is a hypothetical example of the launching mechanism:
> <widget src="/calendar/funkyCal.svg" xmlns="http://www.w3.org/ns/ 
> widgets">
>    ...other metadata...
> </widget>
>
> Kind regards,
> Marcos
>
> Chris Lilley wrote:
>> Hello public-appformats,
>>
>> In the interesting Widget specification in section 2.2. Widget Files
>> http://www.w3.org/TR/widgets/#widget0
>>
>> it says that an index.html is required.
>>
>> This seems to preclude having an index.htm, index.xhtml, index.svg -
>> why are these ruled out? The following comment seems to indicate that
>> this is under review:
>>
>>   Need to address other formats, such as SVG and XHTML, as well.
>>   Probably in a way by making this a whole lot more abstract, so that
>>   you can use any language you want.
>>
>> I therefore suggest instead:
>>
>>   index.<extension>
>>     The main document for the actual widget, and is displayed in a
>>     viewport whose main properties are established by the config.xml
>>     file. This document can reference external content,
>>     including, but not limited to scripts, CSS files and images the
>>     same way regular web pages can. The extension depends on the
>>     format, for example index.html or index.svg.
>>
>>
>
>
>
Received on Thursday, 16 November 2006 03:01:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:10:20 GMT