Issue 7152 - macro examples
Summary: macro examples
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Windows 2000
: P3 Trivial
Target Milestone: ---
Assignee: petergottlieb
QA Contact: issues@api
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-08-20 17:40 UTC by petergottlieb
Modified: 2013-02-24 21:08 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description petergottlieb 2002-08-20 17:40:54 UTC 
I have done a number of macros, ranging from simple things like changing text 
color, or subscript/superscript, to more complex like removing double spaces 
between words throughout a document.  I would be happy to supply some as 
examples, if someone would tell me where to send them and provide some guidance 
as to which ones would be of most interest.  Also, it appears that OOo does not 
have any track changes capability (such as is found in Microsoft Word).  I 
would like to try that, if I could find source code and the ground rules for 
making such contributions.  As a first step in that direction, I would like at 
least this question answered: The Developer's Guide, Chapter 7, appears to 
refer to a Java package "com.sun.star.text.TextDocument" which contains all the 
functions on which this chapter of the Developer's Guide is based.  Where can I 
find this package?  I can't find it anywhere on the sun website.
Comment 1 ooo 2002-12-19 10:48:17 UTC 
Thanks for your support. Sorry for the late answer, there was
something wrong in IssueZilla, I simply did not get this issue before
today, it was kinda hidden to me.

Regarding your examples contribution: You can send documents to
publish, simply as an attachment to this issue.  You have follow some
instructions on http://www.openoffice.org/contributing.html to enable
us to actually publish such contributions.  If somebody makes regular
contributions and the contributions prove to be of quality, we can
grant cvs rights.

Regarding your "change tracking capability":  It does not look like an
API issue.  Such a feature could not even be implemented just using
the official API, you would need to change internals. Anyways, are you
talking about versioning or redlining? Such features exists!  If not,
find the right mailinglist for your issue and disuss it there.
IssueZilla is the wrong place for such effords.

We will issue a new SDK with an improved IDL documentation and a first
final version of the DevGuide in January.  Please check this out when
it is available, it will have documentation for TextDocument too.
Comment 2 utomo99 2003-10-08 04:29:16 UTC 
Utomo . mi:
I think we can close this ?
Comment 3 ingenstans 2003-10-22 09:11:48 UTC 
This really should be closed by now. There are plenty of examples, a 
complete SDK document, and it was raised for version 614.
Comment 4 ooo 2003-10-23 09:19:17 UTC 
closing