RE: New View Mode: docked

Hi Guys,

My five cents about docked mode.

HP webOS has a concept called "Exhibition Mode" that is basically another view of the application when the device is docked.
The way it works is the "Manifest" of the application allows the developer to set "dockMode": true|false  and the app can use JavaScript to implement the behavior using the following way:
AppAssistant.prototype.handleLaunch = function(params) {
  if (params) {
      if(params.dockMode){ //launch the touchstone theme}
  }
}

I am not sure if this is the best approach. Perhaps if the developer could specify in the Manifest an alternative index.html to be used on dock mode would be better.

You can see more information in the following links:
https://developer.palm.com/content/api/dev-guide/mojo/exhibition.html

https://developer.palm.com/content/api/design/enyo/guidelines/system-features/exhibition-mode.html

Facebook app exhibition mode: http://www.youtube.com/watch?v=0Qeet1g9LWc



Android has the concept of "Car Mode" that can be used thought the API UiModeManager:
http://developer.android.com/reference/android/app/UiModeManager.html

It broadcasts an event that the app should handle for dock mode.

So, I agree with Charles that would be great to have a standard spec for this mode.

Best Regards,
Juliano

Juliano Moraes
Hewlett-Packard Company
Innovation Program Office, PSG
+1 (408) 873-5122

-----Original Message-----
From: Marcos Caceres [mailto:w3c@marcosc.com] 
Sent: Friday, May 11, 2012 8:55 AM
To: Charles McCathieNevile
Cc: public-native-web-apps@w3.org
Subject: Re: New View Mode: docked




On Friday, May 11, 2012 at 3:07 PM, Marcos Caceres wrote:

> 
> 
> 
> On Friday, 11 May 2012 at 11:07, Charles McCathieNevile wrote:
> 
> > Hi,
> > 
> > The View Modes spec currently conflates the idea of a minimised and 
> > a docked application. Opera has a concrete use case for extending 
> > the spec to add a "docked" View mode which is seperate, and we have 
> > seen another one in usage.
> > 
> > 1. Extensions / Speed Dial Extensions (concrete requirement):
> > 
> > Opera's Speed Dial Extensions are pretty much minimised 
> > applications, running in a small region, but still providing the app 
> > with full control over the rendering, via HTML/CSS/SVG/etc etc. By 
> > contrast, when an extension is on a toolbar, it gets an icon and a 
> > short text "badge", both of which can be changed, but it does not have a real rendering surface.
> > 
> > We are looking to extend the functionality of our extensions 
> > platform, still basing it on the widget standards including View 
> > Mode, but we really need to have this distinction. We could 
> > implement it anyway (and probably will), but it would be useful to have it as part of the standard stack.
> 
> 
> 
> Sure, it's trivial to define a "badge" mode. The problem is that both views can be present simultaneously - or two documents are being presented out of the same widget at the same time (better, IMO). This means that the view mode model might be wrong as it applies to individual documents and not to the widget itself.

Actually, I think the model is ok. It's been a long time since I looked at view modes.

Received on Sunday, 13 May 2012 20:39:45 UTC