Re: Magic file: splash.[png,gif,jpeg,etc...]

On Wednesday, 7 December 2011 at 08:52, Scott Wilson wrote:

> 1. Is it necessary to define both a magic file and a content attribute?

I personally don't like being locked-in: I like to have the choice to call the file whatever I want and put it wherever I want inside the package.   
> I can see the UC for maybe wanting to use a different filename, but is it a big enough UC? Is there another reason for it?

Might be annoying to type on non-english keyboard (and to remember another english word?… I guess it would be like you and I having to learn some strange Chinese word). It's probably not a huge pain, but if we can make someone's life a little easier, I think it's a good thing.    
> Or is it more that we are following the pattern of the <content> and <icon> elements where we have both default magic files that can be overridden by the author?

There is that too, yes.  
> 2. While SVG is one of the standard formats we habitually list in images, Brian indicated that it isn't currently supported in device OSs for displaying splash screens.

Right. I've put in the spec: "It is OPTIONAL for a user agent to support the media types listed in the default splash-screen table."
> Its probably worth including in the top spot as if it does get supported it gets around the scaling issues, however perhaps we need an Authoring Guideline suggesting widget authors shouldn't rely on SVG alone and always include a non-SVG splash image.

Agreed.  

Added:  

[[
Authoring Guideline: At the time of writing, there is limited support on devices for displaying SVG as a splash screen. As such, if you do include an SVG-based splash screen file, it is strongly recommended that you also include a splash screen file in one of more of the other formats listed in the default splash-screen table.  
]]

--  
Marcos Caceres
http://datadriven.com.au

Received on Wednesday, 7 December 2011 18:09:01 UTC