Artifact component sketch + Mobile FSS

[Jess Mitchell]

I'm working on edits to the Q2 roadmap page and it occurs to me that  
what are represented as independent streams of work will soon blend  
and overlap and coordinate nicely.  As our thinking in Fluid Engage  
moves from the modular to the full solution we can expect our streams  
to do the same -- mixing.  It actually nicely will demonstrate some of  
the early goals of Fluid -- modular pieces that taken individually or  
together can make up an exciting chunk of UI functionality.

Sounds like good stuff to me.

Best,
Jess



~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
jess at jessmitchell.com
/ w / 617.326.7753  / c / 919.599.5378
jabber: jessmitchell at gmail.com
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~




On Jun 2, 2009, at 3:51 PM, Jacob Farber wrote:

> So Heidi and I had an interesting conversation about this email, how  
> it will pertain to Mobile FSS work, and how we can contribute.
>
> The first thing we needed to do was get a clearer picture about what  
> exactly a Artifact Component sketch was. After pinging Michelle,   
> she explained it was literally an Infusion Component based on  
> presenting artifacts (whereas we thought it might have meant  
> something slightly different). Either way, the Mobile FSS ideas for  
> the sketch remain relevant: transforming material from the desktop  
> browser environment to the mobile space with minimal effort.
>
> Heidi and I were thinking of breaking down a feature list for  
> identifying important blocks of UI and information, and having FSS  
> transform those into the appropriate look 'n feel for the target  
> device. I think an artifact component would still need to work  
> within these ideas. One idea we were toying with was working  
> backwards from Claytons demo for McCord (http://spot.colorado.edu/~clayton/fluid%20stuff/mccordhackip.html 
> ). Based off this demo, it would be nice to see how the original  
> page might be quickly and easily transformed via FSS, UIOptions, etc  
> into his mobile-friendly demo.
>
> Basically, we're taking the core concept behind FSS, adding more  
> semantics into the core to allow for even better descriptions of  
> what content is and how it should be treated. This will probably be  
> important for the artifact component's development too.
> What do you think?
> Jacob
>
> ________________________________________
> From: fluid-work-bounces at fluidproject.org [fluid-work-bounces at fluidproject.org 
> ] On Behalf Of Michelle D'Souza [michelle.dsouza at utoronto.ca]
> Sent: Tuesday, June 02, 2009 1:42 PM
> To: fluid-work List
> Subject: Fwd: Artifact component sketch
>
> I don't think Armin's reply showed up on list so I'm forwarding it.
>
> Begin forwarded message:
>
>
> Hello,
>
> For those who don't know me, my name is Armin Krauss and I am a  
> student working part time over the summer at the ATRC for the Fluid  
> Engage project.
>
> I will start trying to sketch out an artifact component that can  
> display the test data we got from McCord. This data might soon be  
> available in a Database. I think Yura is working on this right now.
>
> I also got a email of Clayton forwarded and I will look at work he  
> already did in order to understand the iPhone platform better.
>
> Once I start I will post thoughts and links on JIRA. I am happy  
> about any comments and suggestions.
>
> Best,
>
> Armin
>
> --
>
>
>
> On Tue, Jun 2, 2009 at 12:18, Michelle D'Souza <michelle.dsouza at utoronto.ca 
> <mailto:michelle.dsouza at utoronto.ca>> wrote:
> Hi everyone,
>
> As you know, we are aiming to build something concrete in time for  
> the face to face meeting to help to focus our conversations and our  
> work together. As part of this, it would be useful to have an  
> artifact component sketch that we can play with. As with all our  
> first sketches, this initial thing will likely have very little  
> resemblance to the component that we will eventually build and ship,  
> but it will give us a starting point. To get this work started, I'm  
> going to create a space in the sandbox to house it.
>
> I've created a parent JIRA issue for this and Armin is going to  
> start in on it:  http://issues.fluidproject.org/browse/FLUID-2889
>
> Michelle
>
>
> ------------------------------------------------------
> Michelle D'Souza
> Software Developer, Fluid Project
> Adaptive Technology Resource Centre
> University of Toronto
>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org<mailto:fluid-work at fluidproject.org 
> >
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>
>
> ------------------------------------------------------
> Michelle D'Souza
> Software Developer, Fluid Project
> Adaptive Technology Resource Centre
> University of Toronto
>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090602/6ecc9186/attachment.html>