mobile FSS update

[Heidi Hazelton]

hi all,

Just a little update from the mobile FSS crew. We had a chat this  
morning on Breeze about different ways mobile FSS could work, and how  
it will tie into the Artifact component Armin is starting work on, and  
the existing UIOptions component.

We're going to explore a few different things, to get a sense of  
what's possible and what works. In preparation for the all-hands  
meeting in a couple of weeks, we'll explore the following methods:

- Markup for the mobile is authored from scratch. Try to make the  
authoring process as quick/easy as possible by having stuff ready in  
nice useable chunks. Each component has a template and stylesheet for  
mobile display.

- Markup exists in one html page, but is parsed, if necessary, before  
being delivered to the user's device (desktop/mobile/other). This is  
done by tagging contextual elements of a page via css classes that can  
help explain a section's meaning or layout - the thought being that in  
addition to properly styling sections for the particular device's  
experience, extra/less important stuff will be left out for a stripped- 
down mobile version. We've been calling this our "fantasy" as we're  
not sure how possible/useful it will be. A nice benefit would be using  
existing html pages but can an automated approach really provide a  
nice mobile experience? We shall see...

----
Scenarios we aim to create that will flesh out the above ideas:

A) Simple.
Provide iPhone-like UIs for a path to the artifact component, possibly  
rolling styles from an existing framework into mFSS. Artifact  
component also styled with mFSS.

B) Fantasy?
Start with a complex website and pare down to something like Clayton's  
example via semantic tagging of markup.

We'll be starting on scenario A on monday.
-----

One more thing, we've been talking about how iPhoney to make the look  
and feel. I found this neat link that shows how non-iPhoneyness can  
still look pretty slick and be very functional: http://cssiphone.com/

As always, questions/comments welcome.


heidi