- From: Chris Lilley <chris@w3.org>
- Date: Fri, 17 Nov 2006 11:27:44 +0100
- To: Marcos Caceres <m.caceres@qut.edu.au>
- Cc: public-appformats@w3.org
On Thursday, November 16, 2006, 1:45:30 AM, Marcos wrote: MC> Hi Chris, MC> Thanks for the suggestion. Like you said, despite what is currently said MC> in the spec, it will not be a requirement that a widget package contain MC> an 'index.html' file anywhere. The manifest format will provide a MC> (yet-to-be-specified) mechanism to allow authors to declare which file MC> launches first. This will overcome the is issues related to having an MC> "index.<extension>" and accommodate implementations, such as Yahoo!'s MC> Widget Engine, that don't use HTML to as the UI language. That way, MC> developers can name their "index" file whatever they want. However, we MC> should nevertheless recommend that developers name their main widget MC> file "index.<extension>" for the sake of consistency. I personally would MC> not like to formally specify "index.<extension>" as the required file MC> name, particularly in an internationalized context. I agree, its even more flexible to allow any file to be specified. I was just going for the minimal change to satisfy my request. Feel free to do more. MC> Here is a hypothetical example of the launching mechanism: MC> MC> <widget src="/calendar/funkyCal.svg" MC> xmlns="http://www.w3.org/ns/widgets"> MC> ...other metadata... MC> </widget> MC> Kind regards, MC> Marcos MC> 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. >> >> -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Friday, 17 November 2006 10:27:55 UTC