The current organization of user files essentially assumes they are
all unrelated. However, they aren't. Micro$oft's project structure is
a move in the right direction allowing you to organize files by
project. But project's isn't the only logical structure. For example I
would like to organize files by version and project. In other words I
might have a report that's issued quarterly. That might be represented
logically as one project (the entire year) with four versions (one per
quarter). Of course then there is support for large documents where
the structure is page > chapter > book > multiple volumes. There is
precious little help for people doing this sort of work. Nor is their
support for teams. Finally there are requirements on companies like
Sarbanes-Oxley impacting records retention. There are requirements for
protecting intellectual property. There are the HIPAA laws that impact
medical records. All of these requirements call out for solutions
beyond the premise that each file is independent.
On Jan 5, 2009, at 4:39 PM, Riley wrote:
You are exactly correct Eberhard. Technically not an Open Office
responsibility. However, #1 as an "open source" right up OO's alley
and #2 if there is a lacking of the program being written correctly
now sold us from store shelves, then it is something imho of OO
concern and also a GREAT OPPORTUNITY to jump into the ring and shine
their opponent's right eye for having dropped the ball to computing
Consumers.
Not to mention that it would increase Open Office desirability and
show OO cares what happens to people using their freeware enough to
pick up the slack. Simply put, it adds several layers of Value...
that would likely result in an increased donation to be shared by
the OO team.
Riley
--
St. Doug, Tigger and Puppy in our memory.
Tir na nOg
Wilton, NH USA
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
