RE: Metaphor for structuring all information

Sorry for the over long previous post :-)

Just an added note though. In case I didn't make it clear, books and
projects do not have to be simple aggregation types. For instance,
"mail" and "account" books may appear to the user as simple aggregation
types, but what appears to the user as creating content in these books
can be arbitrarily complex behind the scenes.

The key is to keep the interface the same between all of these content
aggregation types. If they learn how to make a simple document in the
system, they automatically know most of how to send a mail message,
insert course content, or enter an expense.

Richard



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/