Chad Smith wrote:
*PRE-2.0
"We don't need a database program! It's useless bloat that takes away
choice from the end user!"
Considering that OOo 1.0.x and above contained a databse, adding a
second one can be equated to adding bloat to the program.
*POST 2.0
"The latest addition of our new Database program is far superior to the
*ahem* other guy. It makes our free, open source, cross-platform office
Actually, OOo 2.x contains _two_ database programs, and can be a
frontend to umpteen others. [At least one of the customized versions of
OOo contains three database programs.]
We're even in the midst of a contradiction shift as we speak. Check out
the PIM discussion in the "[discuss] Regarding OpenOffice Suite" thread.
The original code for OOo included a PIM.
A PIM was available as an add on for OOo 1.0.
[Guess what, it even works with 2.0!]
What has changed is that instead of the user havingto add the line in
the menu to access the PIM, it will be included in the codebase.
The pattern is:
1) (When functionality X is absent.) "The way it is now is PERFECT. Its
Most of the requested functionality for Ooo either is present, or can be
done by adding a third party utility/addon. For the rest, the user
might have to write their own macro, or source code.
2a) Something changes, something is added or improved... "We *ALWAYS*
planned on doing X. We just didn't have the resources."
I am not going to wander over to Issuezillla, and the other locations
that list features that are requested for future versions. Resource
allocation is a _major_ issue for OOo.
I willgrant that most of the maps do not contain a list of each and
every feature that is planned for future inclusion in OOo. They focus
on the version of OOO that they are written for.
2b) The truly devoted, those not even wishing to admit any potential
problems with the open source way of doing things. "We *ALWAYS* planned on
One of the fundamntal principles of FLOSS, is that if a feature
scratches an itch, it will be created.
Now I will grant that most users never comprehended how to use the PIM
that was an add on for OOo 1.x, or is part of OOo 2.0. In that respect
the learning curve might be described as being "too steep" for non-geeks.
The UI for some of the requested features (that are present as add ons)
is, to put it mildly, klunky. Other parts of the UI require learning a
bizarre set of command keys, that offers major dysfunctionality in
comparison to the Worstar command set.
xan
jonathon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
