Some ideas for FLUID-1872
colin.clark at utoronto.ca
Mon Jan 19 16:08:12 UTC 2009
On 15-Jan-09, at 1:43 PM, Jacob Farber wrote:
> 1) Could'nt we clean up the samples to become exemplars? They could
> just be more detailed or feature-focused springboards.... as it is
> right now, if I were to come at this for the first time, I would be
> a little confused as to why there are so many different kinds of
> reviewable code.
> 2) As for the semantics for "real-world" perhaps it could be
> something like "implementations" or "partner-demos" or "use-cases".
> I would think a full instance of, say, Sakai wouldnt matter since
> its a demo of client-side functionality with the assumption the
> project implementor has intimite knownledge of their own system (ie.
> a uPortal person doesnt need to see how we set up uPortal proper,
> just whats expected of them on the front-end and they could make the
> necessary changes in their uPortal instance.). Please correct me if
> Im wrong, but as long as the markup is what the app spits out
> normally, then they shouldnt have a problem. The whole system doesnt
> need to be up and running to showcase a small peice of functionality.
> Any thoughts on this? Thanks again
I like this quite a bit, and I agree that newcomers must undoubtedly
find our different types of examples confusion.
So given the semantics you've laid out, can you summarize again what
the directory structure will look like?
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
More information about the fluid-work