I also agree, with regards to the documentation side of things at
least (the site and wiki)
I remember when I was first making my way into the community, I was a
little confused when I started reading about Infusion vs. Fluid.
On the homepage at fluidproject.org it reads:
"Fluid is a community, a product, and a collection of tools created
by an international team of partner academic institutions. Fluid is
open source software that..."
which does imply that Fluid itself is a collection of tools forming a
library or "product" but on the download page for infusion ( http://fluidproject.org/index.php/downloads
) it reads:
"Fluid Infusion is a collection of rich, reusable, accessible user
interface components built for the Web."
which to me is sounds like a description for a library as well..
so Is fluid a family of open source libraries? is Infusion the
codename for the current fluid library that we're developing?
On 18-Dec-08, at 11:09 AM, Anastasia Cheetham wrote:
On 18-Dec-08, at 10:50 AM, Jonathan Hung wrote:
I would like
to bring up the opportunity for us to use more of the "Infusion"
name.
"In the header of the file, link to the Javascript files with
<script> tags:
<script type="text/javascript"
src="fluid-0.6/fluid-components/js/Fluid-all.js"></script>"
In situations like this, I think we should be using "infusion-0.6".
Jon, these are good thoughts. I agree that we should try to do a
better job of referring to the Infusion bundle as Infusion, and not
as Fluid. Page headers, etc. can easily be updated to include
Infusion where appropriate.
The example you gave is a sample folder name, and was selected
because currently, our zipped release bundles do extract to a folder
with the 'fluid' name and not 'infusion'. Do we want to consider
changing the actual name of the bundle files to 'infusion-0.6.zip'
instead of 'fluid-0.6.zip'? What about the Fluid-all.js file name?
Good questions...
--
Anastasia Cheetham [email protected]
Software Designer, Fluid Project http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
