Chad wrote: >(5) OOo can already do it if you write this macro, hack this code, download this patch, compile this completely unrelated program, build this bridge in Perl, and it only works on Linux -- plus it's not gonna work exactly like you think it should.. (NOTE: #5 is an exaggeration to prove a point,
That is _not_ an exaggeration, if you want to edit PDFs in OOo. >Kinda like what happened with Base. The argument against Base was slightly different. For starters, OOo 1.x included a dBase clone, and had (some) hooks for SQL interactivity. The big issue was which SQL database implementation was going to be Incorporated into OOo. ****** _If_ the hooks for an email client are included in OOo, then the questions are: i) Can a bridge to an existing email client be written? or ii) is it "better" to compile an existing email client into OOo? However, if what people mean by "outlook" is _not_ an email client, but a calendar function, or a PIM, then solution is much different: To wit: i) Find/replace/update the dBase templates, and document how to use them. ii) Document how to read/write/edit data in _thisPIM_ using OOo. [Where "thisPIM" is a PIM. Write one document for every known PIM.] iii) Document how to read/write/edit data in _thisCalenderFunction_ using OOo. [Where "ThisCalenderFunction" is a Calendar. Write one document for every known Calendar.] xan jonathon -- Does your Office Suite conform to ISO Standards?
