Notes on Current Infusion Demos
Current public demos
build.fluidproject.org
Integration Examples
Demo uPortal site
Sakai mock-up
uPortal mock-up
Other infusion demos
Uploader server demo
Infrastructure
Continuum Build Server
Unit Tests
Manual Tests
Infusion Builder
Builder: Daily Build
Unit Tests: Javascript (client side)
Unit Tests: PHP (server side)
Continuum
build.fluidproject.org/infusion/src/demos/
Production
Preview
Sneak Peek
Really Rough Notes:
demos copies and pasted
simple and complex demos
snippets vs demos
demonstrate proper use of fluid principles like proper use of DOM binder and framework.
example: the keyboard a11y plugin demo
http://build.fluidproject.org/
Integration examples: useful? text?
uportal and Sakai mock-ups
"other infusion demos"
uploader server demo
A big priority for me with the demo portal is getting rid of the iFrames
(2:40:15 PM) colinclark: we will have to dig up our Screen Navigator code from Engage to do so
(2:40:32 PM) colinclark: The visual space we provide the demos is too constrained for them to look hot
(2:40:43 PM) colinclark: they always look squeezed or even wrap unpleasantly sometimes
(2:40:54 PM) colinclark: A diversity of examples of how you can configure a component will be cool to have
(2:41:02 PM) colinclark: rather than having to guess from the API documentation
(2:41:38 PM) colinclark: And a consistently high level of visual hotness would cool, too
(2:41:58 PM) jessm: and consistency across them wrt instructions, explanations, etc.
presentation:
builder
demo portal
documentation
readme
website
wiki
Builder:
descriptions
status - subcomponents
Layer up demos
underpants up to top0hat and tails
how do we deliver the message that we have the same thing but different packaging.
–
Demo page to become a component page.
demo page to become a component
status
easy demos
code snippets
builder
no status
super easy