jonathon wrote:
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.

If you mean the built-in, flat-file, dBase thing.... That wasn't a database, that was a toy.

BTW, that had nothing to do with the dbase file format. I used Borland dBase for DOS versions 4 and 5 in the 90's and it was a full-fledged, SQL92 compliant relational database system. You could even construct complete applications with it that included menus, forms, tables, reports, etc., that you could compile into a self-standing executable.


*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.]

One database program, one toy program, and approximately the same ability to connect to outside systems as Access.


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.

So far, so good.

A PIM was available as an add on for OOo 1.0.
[Guess what, it even works with 2.0!]

Prove this last statement. I think you're just making crap up out of whole cloth.



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.


Your statement makes no sense. In order for "add the line in
the menu to access the PIM" to work in would already have to 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.


Do you understand the meaning of the word "include"?



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.

Please provide a reference to this Add-on, a link would be nice.

Rod

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to