Draft DHTML Developer's Checklist
colin.clark at utoronto.ca
Thu Sep 13 13:48:23 UTC 2007
Thanks for your suggestions, these are great. I've improved labelling
in Item 3, and will include a code snippet illustrating how to create
Examples sound good; I'll see what I can dig up and what Eli has in
mind as well.
I'm planning to distribute this checklist more widely in the Sakai and
uPortal communities later this week.
Quoting Aaron Zeckoski <aaronz at vt.edu>:
> This is a great start. Would it be possible to link over to examples
> of each of your 3 main points? They don't have to be great examples
> but it helps a lot to see this stuff in the context of real code.
> I would also recommend code snippets for item 2. For example, how
> would I create a bit of custom JS code that is namespaced? What would
> a few sample prefixes look like?
> Item 3 would benefit from clearer labelling. It is not completely
> clear to me that opaque is bad so maybe tweak the wording or just put
> something like "this is bad".
> Nice job!
> On 9/11/07, Colin Clark <colin.clark at utoronto.ca> wrote:
>> Hi everyone,
>> user interfaces, and would like to get the community's feedback on it.
>> The checklist is an attempt to provide developers with a quick overview
>> of a few of the most important issues to watch out for, and real
>> techniques for how to address them.
>> Thoughts? Suggestions for improvements?
>> Colin Clark
>> Technical Lead, Fluid Project
>> Adaptive Technology Resource Centre, University of Toronto
>> fluid-work mailing list
>> fluid-work at fluidproject.org
> Aaron Zeckoski (aaronz at vt.edu)
> Senior Research Engineer - CARET - Cambridge University
> Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
More information about the fluid-work