Apache OpenOffice Wiki - User contributions [en]

Certification/Student

2010-10-07T18:46:34Z

SpamKiller: Undo revision 186304 by Janet19 (Talk)

{{DISPLAYTITLE:Student Book Structure}}

Student book will give the outline of the content of the OpenOffice.org suite and give a series of exercises and practices for the student to perform. The activities will be mapped to the syllabus and should provide cross references between the teacher's book and the student's book.

Testing policy will be determined by the certification committee. Yet a basic draft could be developed before the decision takes place.

==Layout==
The layout of the content should cover the important parts of the training since the book is restricted to the course. The book should be coordinated between the times for practice, for discussion and for theory. The overall layout should include the Cornell note taking style for optimized layout. Also the amount and depth of topics to cover.
* Theory 20%
* Discussion 30%
* Practice exercise 50%

===Theory===
The book should explain the purpose and practice of the topic. Theory should be conceptualized and summarized in an easy to follow way in the document.

===Discussion===
Encourage debate and Q&A period between the instructor and the students. Note talkings would be important to get extra information and clearing specific questions derived from the discussion.

=== Practice ===
Should be coordinated between activities and follow the different modules from the syllabus. The book should suggest a section to provide time for the exercise solving period and suggest a time in minutes to solve it.

Example:

'''Chapter 3 exercises (40 minutes)'''
[[Category:Certification]]

Uno/Cpp/Test/Bootstrap

2010-10-07T18:45:46Z

SpamKiller: Undo revision 186309 by ShirleyG (Talk)

[[Uno/Meta/Organization#Types|Type]]: [[Uno/Meta/Test|Test]] [[Uno/Meta/Organization#States|State]]: Finished Availability: URE 1.3 (SRC680_m212)

==Tests==
bootstrap_InitialComponentContext
* without client purpose
* from within client purpose

==Execute==
# Mac OS X setenv DYLD_LIBRARY_PATH "../lib":$DYLD_LIBRARY_PATH
<platform>/bin/bootstrap.test

==Files==
* {{Uno/UDKlink|cppuhelper/test/bootstrap/bootstrap.test.cxx}}
* {{Uno/UDKlink|cppuhelper/test/bootstrap/TestEnv.cxx}}
* {{Uno/UDKlink|cppuhelper/test/bootstrap/TestEnv.def}}
* {{Uno/UDKlink|cppuhelper/test/bootstrap/bootstrap.test.cxx}}

==Depends on==
* [[Uno/Cpp/Tester/TestComponent]]

[[Category:Module:CPPUhelper]]
[[Category:Test]]
[[Category:Uno]]
[[Category:Uno:Cpp]]

OOoSCM Minutes

2010-03-13T13:40:53Z

SpamKiller: Undo revision 158721 by Veronica90 (Talk)

On every Friday 2pm UTC (15:00 CET) there is a meeting (#oooscm on irc.freenode.net) to discuss a new SCM (<u>S</u>oftware <u>C</u>onfiguration <u>M</u>anagement) system for OpenOffice.org.

== 2008/02/7 ==

Participants: Jan Holesovsky, Matthias Klose, Jens-Heiner Rechtien

Topics:
* work on "lazy cloning" for git by Jan, shows promising results
* gathering numbers mostly finished, there is no clear winner/looser just from the numbers
* next face-2-face steering council meeting is on Feb 18th, Jan and Heiner will deliver a coauthored paper for it.

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2008-02-07_IRC_log]].

== 2008/02/1 ==

Participants: Jan Holesovsky, Jens-Heiner Rechtien

Topics:
* work on "lazy cloning" for git by Jan.
* gathering numbers ongoing, hopefully to be finished next week
* next face-2-face steering council meeting is on Feb 18th, we'll need to deliver a statement for it.
* next meeting: Do., Feb. 14th, 14 UTC

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2008-02-01_IRC_log]].

== 2008/01/25 ==

Meeting cancelled.

== 2008/01/18 ==

Participants: Jan Holesovsky, Jens-Heiner Rechtien

Topics:
* templates are now ready: [[SCM_Migration]]
* bzr import still missing, we will proceed with Subversion and git

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2008-01-18_IRC_log]].

== 2008/01/11 ==

Canceled due to lack of attendance.

== 2008/01/04 ==

Participants: Jan Holesovsky, Jens-Heiner Rechtien

Topics:
* no news due to Xmas/New Year vacation
* bzr import still missing

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2008-01-04_IRC_log]].

== 2007/12/21 ==

Participants: Jan Holesovsky, Jens-Heiner Rechtien

Topics:
* no news due to Xmas vacation, next meeting Jan. 4th 2008

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2007-12-21_IRC_log]].

== 2007/12/14 ==

Participants: Matthias Klose, Jens-Heiner Rechtien

Topics:
* no news

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2007-12-14_IRC_log]].

== 2007/12/07 ==

Participants: Jan Holesovsky, Matthias Klose, Jens-Heiner Rechtien

Topics:
* we've got imports for svn and git, bzr import still missing
* we will wait until bzr-1.0 is released for bazaar evaluation
* Heiner will provide some work flow templates

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2007-12-07_IRC_log]].

== 2007/11/30 ==

Participants: Matthias Klose, Eike Rathke, Jens-Heiner Rechtien

Topics:
* some open questions regarding bzr import and performance

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2007-11-30_IRC_log]].

== 2007/11/23 ==

Participants: Jan Holesovsky, Martin Hollmichel, Matthias Klose, Eike Rathke, Jens-Heiner Rechtien

Topics:
* transfer issues regarding the SVN repository o3-build.services.openoffice.org
* bzr "shared repositoires", git "shallow clones"
* exchanged arguments for and against splitting the code repository in a number of repositories
* local disk space occupied by working copy / local repository

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2007-11-23_IRC_log]].

== 2007/11/16 ==

Participants: Martin Hollmichel, Petr Mladek

Cancelled because of too few participants this week (Jan and Heiner could not attend), see dev@tools mailing list: http://tools.openoffice.org/servlets/ReadMsg?list=dev&msgNo=6395)

== 2007/11/9 ==

Participants: Jan Holesovsky, Martin Hollmichel, Matthias Klose, John Arbash Meinel, Maximilian Odendahl, Martin Pool, Eike Rathke, Jens-Heiner Rechtien

Topics:
* setup a weekly IRC meeting, on Fridays, 14 UTC
* how to proceed to obtain a meaningful comparison between the SCM candidates
** we agreed to first create a comparable import for Bazaar, Subversion and Git along the lines of the "migration recipe" in [[SCM_Migration]].
** after that we'll try to create optimized migrations which play on the strength of the SCM systems.

IRC log: [[http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes_2007-11-09_IRC_log]].
[[Category:SCM]]

Help:Editing

2009-01-03T23:06:36Z

SpamKiller: Undo revision 105681 by Kholo chel40 (Talk)

[http://meta.wikimedia.org/wiki/Help:Editing Editing Overview] and
[http://meta.wikimedia.org/wiki/Help:Contents#For_editors Help for Editors]

The OOo Documentation project's [[Documentation/Dashboard/Wiki_Editing_Policy | Wiki Editing Policy]], of which some is nice to know for general editing tasks as well.

'''Some installed MediaWiki extensions'''
* [http://www.mediawiki.org/wiki/Extension:DynamicPageList DynamicPageList (DPL) extension] used for example in many [[Uno]] pages and the [[Calc|Calc/...]] subhierarchies. See [http://semeb.com/dpldemo/index.php?title=Dynamic_Page_List overview, manual and FAQ].
* [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi]
* Help on [http://meta.wikimedia.org/wiki/Help:ParserFunctions ParserFunctions]
For other parser hooks and extensions and specific versions installed see the [[Special:Version|Version]] page.

[[Category:Help]]

User talk:Feilsky

2008-08-24T22:17:04Z

SpamKiller: removed SPAM

Category:ODF

2008-08-24T20:28:50Z

SpamKiller: what the .... was User:Batesbn up to?

Extensions

2007-06-28T16:43:02Z

SpamKiller:

__NOTOC__
{{Extensions}}

[[Extensions de|de]]
[[Extensions es|es]]
[[Extensions fr|fr]]
[[Extensions it|it]]
[[Extensions zh|中]]

All translated pages may not be up to date - Main language remains English

=== OpenOffice.org Extensions ===

OpenOffice.org offers the possibility to develop independent 3rd party extensions. The categories of extensions reach from Basic libraries, packages with Java/JavaScript or Python macros to more sophisticated extensions in form of UNO components implemented in Java, C++ or Python. Even the last category of extensions subdivide in general UNO components providing new implementations for existing functional areas or specialized components like Calc Add-Ins, Add-Ons, DataPilots, Chart Add-Ins or linguistic components (e.g. Spellchecker, Hyphenator or Thesaurus).

The Extensions project provides
* <b>[[Extensions development|Tools, guidelines and starting information]]</b> to develop new functionality for OpenOffice.org
* <b>[[Extensions repository|Repository of existing Extensions]]</b>: listing and classification
* <b>[[Extension Deployement|Deployment to end-users]]</b>

You can join us at
* #ooo-ext [[IRC_Communication|IRC channel]]
* dev@extensions.openoffice;org mailing list for building the extensions ecosystem

=== Translating these pages ===

The Extension project has to be strongly bound to Native-Lang communities to relay any local third party development. So we warmly welcomed people interested in providing translations for the Add-ons and also for the documentation and pages of this site.

The naming convention proposed is to
* Create a new page taking the English page and add your language code as suffix (eg. Extensions_repository_fr)
* Put a link to this translated page at the top of the English page, with the language code
* Be aware that if you start a translation, it would be good to monitor it so that it remains as much in sync as possible

=== Some extension categories ===

* Calc Add-Ins provide new Calc built in functions which can be directly used over the normal function dialog in the Calc application.
* [[Add-ons]] describe components providing some new functionality and normally coming with an UI integration (e.g. new menu entries or complete new menues, new toolbars).
* DataPilots provide a new kind of data pilot which can be used directly over the DataPilot dialog in the Calc application.
* Chart Add-Ins provide a new chart type
* Linguistic components provide new implementations of known interfaces which can be used directly over the normal UI.
* Starting with OOo 2.0.4 we have support for [[non-code_extensions|non-code extensions]] (e.g. templates, autotexts)

=== References/Articles ===

* [http://api.openoffice.org/docs/DevelopersGuide/Components/Components.xhtml#1_7_3_Add-Ons OpenOffice.org Developers Guide]

* [http://www.linuxjournal.com/article/7802 Linux Journal: "Off the Wall: Macros and Add-ons"]

* In this Wiki: [[SimpleCalcAddIn|a simple Calc AddIn]] and [[CompleteAddIn|a complete AddIn]]

[[Category:Extensions]]
[[Category:Source directories]]

Talk:Http://www.google.com/accounts/RP?c=CK-a v2ivt nkwEQuJ7l3OOzlpVu&hl=lt

2007-06-12T22:02:38Z

SpamKiller: revert spam

Hi,

I just wanted to thank Jean Hollis Weber and whoever else created this wiki site. It's a great job, and I have linked to it from the Digital Tipping Point links page. 2005/12/20 Christian Einfeldt

Christian, I had nothing to do with setting up this wiki, though I'm flattered that you think I did. :-) When I have time, I'll be contributing to it. --Jean Hollis Weber

== Suggestion for some re-organization ==
Dudes. We -so- need a main page/everything else cleanup .. :) Looking at the Scribus wiki and the [http://developer.mozilla.org Mozilla Developer Center] just makes me salivate. Currently the main page is more or less a link farm without much structure. How about adding some layout and thinking a bit more about entry points to different regions of the wiki/main site? We could probably initially borrow the MDC style sheet to get us started? (or design our own?) --[[User:KaiB|KaiB]] 19:09, 26 March 2006 (CEST)

Just a little suggestion, do you guys think the current Wiki need a bit of cleanup and re-organization? I also contributed to the [http://wiki.scribus.net/index.php/Main_Page Scribus Wiki] and I think the Scribus wiki-doc authors are doing a nice job of placing content in a well organized manner. -- [[User:Zero0w|Wily Yuen]], Feb 13, 2006

: Reply to myself: if this is a good idea, give me a nod. I'll try to move things around a little and hope that I won't mess things up ;) ---- [[User:Zero0w|Wily Yuen]], Feb 13, 2006

: Yes, it does. The Marketing section wants all of its pages named <nowiki>[[Marketing--pagename]], although they would interact better with the wiki software if they were [[Marketing/pagename]]</nowiki>. I've made a suggestion to switch this. Further organization should be done through the use of categories. Categories are very easy to use, just add the tag <nowiki>[[Category:XXXX]]</nowiki> to the page. I have done this for all of the marketing pages that I could find. Actually, if you view [[Marketing]], you will see the template I created for marketing pages. The development section has a lot of miscellaneous pages. View [[Special:Uncategorized pages]]. Also, there are a number of pages that look like they are simply Wikipedia entries. I don't think they belong here. If we do have a glossary, it should be in a page like [[Glossary]] or [[List of OpenOffice.org-related terms]]. Contact me if you need help with creating templates, etc. --[[User:RealGrouchy|RealGrouchy]] 07:15, 21 February 2006 (CET)

::I'm admittedly coming in late on this, but then I only found the site earlier this week. I actually think that Marketing has sort of the right idea, except that is should be Marketing:pagename. That would, in effect, be claiming their own [[Help:Namespace|Namespace]]. Mediawiki does come with its own predefined namespaces, however custom namespaces can be defined as well. And I think both Marketing and Development would benefit from such. Possible benefits of having their own name space:

#Pages can be searched for and organised independently
#Feature separation is possible
#Background colors and other special formatting can be restricted to a specific project group.
Example.
{|Border=1 align="center"
|----
|Bgcolor="Ivory"|<BR>Main Page Space<BR>
|Bgcolor="Cyan"|<BR>Development Page Space<BR>
|Bgcolor="Red"|<BR>Marketing Page Space<BR>
|}

Yet even as each project maintained its separate page formatting, the main body format would still be the same so as to maintain a common overall identity, even though we would now know which project we were looking at.
--[[User:Kirk|Kirk]] 00:46, 1 June 2006 (CEST)

Kirk, thanks for your proposal for a [[User:Kirk/test|revised main page]]. I fully agree with you and others that some re-organisation would be good. I earlier thought of a [[User:St/Main Page|page with some graphical elements]]. --[[User:St|stx12]] 14:36, 3 June 2006 (CEST)

== Spamming ==

There are repeated attempts by the same poster to spam the [[Main Page]] with links to advertising sites. Should the Wiki admin do something about it? --[[User:Zero0w|Zero0w]] 16:37, 25 March 2006 (CET)

The user has been blocked. Thanks for the heads-up.
--[[User:St|stx12]] 16:55, 25 March 2006 (CET)

== Let us add XML and other file formats for upload<->download only ==

Hi! I have made a web page in my NLC project that uses data from a XML file. Now I have tried to put it on some open for user-editing page, like Wiki, so they could download it, edit it and upload without accessing CVS, using the Wiki and the effects would be seen in my NLC project page. But I am getting some "xml is a wrong file type for Wiki" message :( I think it is a very useless limitation that user can not upload any file type. I have tried some other wikis, like wikosource, wikimedia, wikibooks, and everywhere the same strange problem with uploading other various types. Let's be the first to get rid of unnatural limitations. Software that uses XML for writing files should allow users to edit XML pages through Wiki or in some other way. --[[User:Konradst|Konrad]] 14:45, 2 April 2006 (CEST)
: Well I have found the needed functionality in "documents&files" section of the project, but still it would be great if uploading xml files would be available in Wiki --[[User:Konradst|Konrad]] 15:00, 2 April 2006 (CEST)

== Unable to upload files ==

Hello,
Why are we not allowed to upload files on this wiki?
I would like to upload 2 images.
Thanks,
[[User:Val1984|Val1984]] 10:07, 28 April 2006 (CEST)

: uploads have been unintentionally disabled during the last upgrade. Give it a try now. --[[User:St|stx12]] 21:49, 2 May 2006 (CEST)

== link to OpenOffice.org_Solutions? ==

Would anyone object if I put a link on the main page for http://wiki.services.openoffice.org/wiki/OpenOffice.org_Solutions? This page is new and is currently not linked anywhere, basically making it impossible to find. Pending a re-org of the main page, I was thinking it might be good to put a link for that page under "Finding general OpenOffice.org user help".

: thanks for asking; that's fine with me, go ahead. The main page needs some serious work though...; --[[User:St|stx12]] 20:38, 10 May 2006 (CEST)

== Category Indexing ==

Hello, I'm trying to get the Category Index setup and have run into a question. For the moment I am inclined to subcategorize '''Writer''', '''Calc''', and '''Database''' under '''Documentation'''. I currently got '''Writer Issues''' placed under '''Writer''' in '''Documentation'''. But now I'm thinking the Issue Categories should be under '''Development''' instead. Any thoughts, guidance?--[[User:Kirk|Kirk]] 20:27, 1 June 2006 (CEST)

: I agree that the "xxx issues" categories are related to Development. --[[User:St|stx12]] 14:28, 3 June 2006 (CEST)

== Example Base File ==

There has recently been a discussion under way on the users@dba.openoffice.org mailing list regarding the production of an [[example Base database]] for contribution. It has been suggested to use this wikipedia as a resource for defining and developing this project. --[[User:DrewJensen|DrewJensen]] 15:41, 9 June 2006 (CEST)

== language template / box ==
Please add Bangla (bn) in the laguage template (or box) in the main page, since we've created our page [[bn.openoffice.org]] and almost localized 80% of the main page. '''Bangla''' in ''Bangla'' script '''বাংলা''' --[[User:Mak|mak]] 22:36, 12 September 2006 (CEST)

== Copyrights ==
Hi, what is the [http://en.wikipedia.org/wiki/Wikipedia:Copyrights copyright] of this wiki ? I suggest [http://en.wikipedia.org/wiki/Wikipedia:Text_of_the_GNU_Free_Documentation_License GNU Free Documentation License] like Wikipedia, the free encyclopedia, allowing me to share this wiki. ;-)

== Incorrect translations in the Welcome box ==

Kudos for the great MediaWiki site. It might really be a good idea to talk with some native speakers about the welcome text in the Welcome box on the Main Page that includes the date and a welcome message in several languages. Spanish and German are both wrong. Spanish should be "'''Bienvenidos''' a OpenOffice.org" and German should be "Willkommen '''bei''' OpenOffice.org". I'm guessing the translations are from some template that is being pulled in since I can't figure out how/where to fix the problem.

== Dynamic Page List ==

Your website is using a rather outdated version of a mediwiki extension named DynamicPageList. There is a new version with plenty of improved functionality available. Perhaps you may want to have [http://semeb.com/dpldemo a look?] --[[User:Algorithmix|Algorithmix]] 17:12, 20 February 2007 (CET)

Impress multiple display specification

2006-04-07T14:26:15Z

SpamKiller:

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719]. (Other specifications can be created using the [[Specification template]])

This specification has been split into two - [[Impress simple multiple display specification]] and [[Impress presenter mode specification]].

Any discussion of the specification should happen in the issue, or on the discussion pages for those specifications.

Current status of the implementation is at [[Impress multiple display support]].

[[Category:Specification]]

User talk:Npower

2006-01-18T12:37:53Z

SpamKiller:

Help talk:Contents

2006-01-18T12:37:33Z

SpamKiller:

Talk:Writing warning-free code

2006-01-18T12:37:24Z

SpamKiller:

Porting to x86-64 (AMD64, EM64T)

2006-01-18T12:37:14Z

SpamKiller:

== Current status ==

The x86-64 port is work in progress. It is not ready for use yet, but it compiles (with quite large set of patches), and performs basic operations. '''It is of no use for non-developers.'''

Help is appreciated, join the project! :-)

The work is based on ''ooo64bit02'' [[CWS|Child Workspace (CWS)]], and most of the patches are committed back there now. The problem is that this CWS is too huge to be integrated - it would be an incredible task for the QA. The idea is to split it to smaller CWSes and get them integrated one by one.

More info:
* [http://artax.karlin.mff.cuni.cz/~kendy/ooo/OOoCon-2005/ OOoCon2005 presentation about the port]
* [http://artax.karlin.mff.cuni.cz/~kendy/blog/ Jan Holesovsky (Kendy)'s blog]
* [http://blog.janik.cz/ Pavel Janik's blog]

== How to get it ==

All the available and the most recent patches are in [[ooo-build]]; you can see them [http://cvs.gnome.org/viewcvs/ooo-build/patches/64bit/ here]. See the general [[Getting It]], [[Building]], [[Installing]], [[Running]] sections for ooo-build.

Be sure to specify one of the 64bit distros (like ''NLD64'', ''Debian64'', etc.) during the ''./configure'' time (''--with-distro='' configure switch), it will apply the 64bit patches then.

== How to help ==

Generally

* Compile it
* Find a bug (crash, missing functionality, ...)
* Fix it ;-) It might be either in the ooo-build patches, or up-stream
* [http://qa.openoffice.org/issue_handling/submission_gateway.html#code_module File] the problem & the solution to the IssueZilla if it is up-stream, or send it to openoffice@lists.ximian.com if it is in the ooo-build patches
** Ensure that you CC 'kendy' and 'pjanik' on the report to get a quick response
* If the underlying problem is a new problem archetype - try to find & fix all other instances of it

The most important task now is to isolate fixes from ''ooo64bit02'', and get them up-stream. Once the official OpenOffice.org builds on x86-64, it will be much easier to get more people involved, and to fix bugs more effectively.

The other task is to get it work with a JVM - for example with Sun Java 1.5.0 for x86-64, or any other.

Should you have questions, please contact ''kendy'', ''martink'', or ''paveljanik'' on [[IRC_Communication|IRC]].

== Java related issues during porting==
* First, remove the --without-java line in distro-config/NLD64.conf.in file, and give the option of --with-distro=NLD64 while configuring.
* Encountered problem & solution
{| border="1" cellspacing="1"
!|OSD
!|Source tag
!|Configuration Option
!|Phenomenon
!|Solution
!|Note
|-
|SuSe9.3
|m136
| --with-distro=NLD64 --with-tag=src680-m136
|xmlhelp module failed because the Berkeley DB 4.2 on suse9.3 doesn't have db.jar instlled, ie. the java option isn't turned on when the db42 rpm package is builded, and this causes some java programs which use the calss of com.sleepycat.db.Db fail.
|manually recompile the BerkeleyDB 4.2 with java option turned on and configure --with-db-jar=/usr/local/BerkeleyDB.4.2/lib/db.jar;remove the --with-system-db line in distro-config/NLD64.conf.in file; add /usr/local/BerkeleyDB.4.2/lib/db.jar to $CLASSPATH; finally re-configure the whole building process.
|BerkeleyDB.4.4 changed the API of java, please DON'T use the 4.4 version of Berkeley DB.
|-
|}

Talk:ES/Desarrollo/Syndication

2006-01-18T12:37:05Z

SpamKiller:

Talk:Mono Integration

2006-01-18T12:36:55Z

SpamKiller:

Product Release

2006-01-18T12:36:45Z

SpamKiller:

== Product Releases of OpenOffice.org ==

For detailed release information please see http://development.openoffice.org/releases/

=== Ongoing OpenOffice.org 2.0.x ===

* [[OOoRelease201|OpenOffice.org 2.0.1]]
* [[OOoRelease202|OpenOffice.org 2.0.2]]

Change & transition to more regular time-based releases is
underway here; checkout Martin's
[http://development.openoffice.org/releases/OpenOffice_org_2_x.html#plan mail]
on the releases list.

=== Released OpenOffice.org 2.0.x ===

* [[OOoRelease200|OpenOffice.org 2.0.0]]

=== OpenOffice.org 1.1 ===

* OpenOffice.org 1.1.5
* OpenOffice.org 1.1.4
* OpenOffice.org 1.1.3
* OpenOffice.org 1.1.2
* OpenOffice.org 1.1.1
* OpenOffice.org 1.1.0

=== OpenOffice.org 1.0 ===

* OpenOffice.org 1.0.3 (2003-04)
* OpenOffice.org 1.0.2 (tag OpenOffice_1_0_2) (2003-01)
* OpenOffice.org 1.0.1 (tag OpenOffice_1_0_1) (2002-07)

Talk:SVG Import Filter

2006-01-18T12:36:35Z

SpamKiller:

Talk:FAQ

2006-01-18T12:35:43Z

SpamKiller:

Talk:Tips

2006-01-18T12:35:33Z

SpamKiller:

Commit Rights

2006-01-18T12:35:22Z

SpamKiller:

The procedure which will result in you having your OpenOffice.org account upgraded to '[[DomainDeveloper]]' is currently a bit fuzzy. If you are an active participant in discussions on the mailing list governing the piece of OpenOffice.org which interests you, and you intend to contribute source code to the OpenOffice.org project, chances are that you will need CVS commit rights.

The biggest advantage to having such rights is, of course, the ability to contribute code yourself directly into the CVS repository, without having to attach patches to issues and badger another developer into incorporating your changes.

There are a number of steps required to receive CVS commit rights, and to then activate them so that they are useful to you.

'''Step 1'''. Sign a JCA (downloadable from http://www.openoffice.org/licenses/jca.pdf). Some of the reasons why you must do this are listed at http://www.openoffice.org/FAQs/faq-licensing.html#jca1.

'''Step 2'''. Do stuff which results in your account being upgraded to '[[DomainDeveloper]]' status - submitting a couple of quality patches should do the trick.

'''Step 3'''. Follow the instructions here: http://www.openoffice.org/docs/ddSSHGuide.html on how to set up and create an SSH tunnel.

'''Step 4'''. Create a CWS (Child WorkSpace) for the area of work you intend to do. Directions on how to do this can be found here: http://tools.openoffice.org/dev_docs/ooo-cws-tools-doc.sxw. Note that without CVS commit rights, you cannot create CWSs. Also, if you have already got a specific milestone build, you can avoid the lengthly 'Update' process initiated by 'cwscreate' by using the -f option. This means, for example, if you are working on the OpenOffice 2.0.0 branch, you might already have the SRC680 m130 source. To avoid the CWS toolset updating you to a milestone you already have, you can enter 'cwscreate -f SRC680 m130 <cws name>'.

More details on creating CWSs can be found here: http://tools.openoffice.org/dev_docs/child_workspace_policies.html and here [[CWS]].

'''Step 5'''. Go to the 'Environment Information System' at http://eis.services.openoffice.org/EIS2/servlet/Logon. Browse through the CWSs until you have found the CWS you just created. Once you've found it, click on the link at the top of the page, something like 'SRC680/<cws name>'. Fill in the relevant details and set yourself to be the owner of the CWS (enter your name into the textfield on the left of the dropdown combo box if you aren't already listed).

'''Step 6'''. Commit your code. Find someone on the relevant mailing list to QA your code, assign the issues to them (note that IssueZilla will reset their status to 'New' upon reassignment), then set the QA representative in EIS.

'''Step 7'''. As QA personnel generally don't have the expertise or time necessary to apply your changes and build a patched version of Office, it is necessary to supply them with a build containing your changes. Do a full build of Office, and upload the single download file from your instsetoo_native directory (for example: OOo_2.0_windows_install_en-US.exe) to: http://ooomisc.services.openoffice.org/pub/OpenOffice.org/cws/upload/. You can obtain details on how to upload files to this server from the project lead of of your project, or from one the release engineers.

'''Step 8'''. The QA person will test the bugs you have fixed on a standard milestone build, and on your patched version and confirm that the bugs are fixed and that no new bugs have been introduced. Once the QA process is finished, the QA person will merge your changes into the MWS, and you should see them in the next milestone build, and hopefully the next release.

Happy hacking!

Development Tutorials

2006-01-18T12:35:12Z

SpamKiller:

<h1>OO.o hackers tutorials</h1>

''' See also [[Helper Class Implementations]]'''

<p>
Since there are a number of common tasks that people want
to get done, and looking at these in detail can be instructive
generally - we've provided a set of annotated patches to help
people get stuck into the code.
</p>
<p>
This is aimed as an extension to [[Building]] and [[Hacking]] OOo
so you might want to check them out first if you haven't already
</p>
<ul>
<li>
[[Tutorial Start]]
( [http://go-oo.org/tutorials/accelerator-about.diff.txt diff] )
- adding / changing the default K/B accelerators.
</li>

<li>
[[Tutorial Toolbar]]
( [http://go-oo.org/tutorials/add-about-toolbar.diff.txt diff] )
- adding / changing the default toolbar items.
</li>
<li>
[[Tutorial About]]
( [http://go-oo.org/tutorials/ok-ok-about-button.diff.txt diff] )
- adding items to & altering the about dialog
</li>

<li>
[[Tutorial Charmap]]
( [http://go-oo.org/tutorials/new-button-charmap.diff.txt diff] )
- adding a widget & i18n string & callback.
</li>
<li>
[[Tutorial Writer]]
( [http://go-oo.org/tutorials/sw-save-image-context-menu.diff.txt diff] )
- adding a new menu command & its implementation.
</li>
<li>
[[Tutorial Impress]]
( [http://go-oo.org/tutorials/sd-save-image-context-menu.diff.txt diff] )
- adding a new menu command & its implementation.
</li>

</ul>
<h2>The build procedure</h2>
<ul>
<li>
[[Tutorial Build]]
( [http://go-oo.org/tutorials/helloworld-ooo-style.diff.txt diff] )
- creating a skeleton project / toplevel.
</li>
<li>
[[Tutorial Library]]
( [http://go-oo.org/tutorials/helloworld-ooo-style.diff.txt diff] )
- Making up a new library of the toplevel project.
</li>
<li>
[[Tutorial Client]]
( [http://go-oo.org/tutorials/helloworld-ooo-style.diff.txt diff] )
- Using the library from a different toplevel project.
</li>
</ul>
<h2>You know ? :-D</h2>

<ul>
<li>
[[Tutorial UNO Library]]
( [http://go-oo.org/tutorials/helloworld-uno-style.diff.txt diff] )
- Making a UNO component out of the new toplevel project.
</li>
<li>
[[Tutorial UNO Client]]
( [http://go-oo.org/tutorials/helloworld-uno-style.diff.txt diff] )
- Using our shiny new UNO component from a different top-level project.
</li>

<li>
[[Tutorial UNO IDL]]
( [http://go-oo.org/tutorials/helloworld-idl-style.diff.txt diff] )
- Creating an own idl file for our new UNO component to implement.
</li>
</ul>
<h2>All together now! :-)</h2>
<ul>
<li>
[[Tutorial Locate UI]]
- Getting to the associated code from the UI pointers.
</li>
<li>
[[Tutorial Locate Functionality]]
- Getting to the associated code from the functionality.
</li>
<li>
[[Tutorial Locate Misc]]
- Pointers on locating code, reading UNO code, which couldn't go in the other two parts. :-)
</li>
</ul>
<p>
If you're looking for whom to beat up for these, that would be [mailto:rsiddhartha/at/novell/dot/com me]. :-)
</p>
<h2>Further Resources</h2>
<ul>
<li>
Mailing list at: [http://lists.ximian.com/mailman/listinfo/openoffice ooo-build mailing list]
</li>
<li>
IRC: #go-oo on Freenode
</li>
</ul>
<p>
All the best! :-)
--Raul
</p>

Talk:Debugging

2006-01-18T12:35:02Z

SpamKiller:

Talk:Running

2006-01-18T12:34:53Z

SpamKiller:

Windows

2006-01-18T12:34:23Z

SpamKiller:

== Welcome to OOo development for Windows ==

This is an initial attempt to fill out information for building on Windows.
If it ends up being complete, this notice can be removed! At the moment you'll have to piece together information from [[#See also|other pages]] with the changes here for doing it on Windows.

Most of this wiki assumes that you'll be using a reasonably current Linux system, as a time saving feature. While real hackers prefer [http://www.gnu.org Free software], if you're forced to build stuff for Windows, this is the place to be.

== Development Tools ==

There have been several different ways of building with more or less success...

The reference page to look at is [http://tools.openoffice.org/dev_docs/build_windows_tcsh.html Building under Windows with tcsh]

Other ways to build are documented below, the official way requires Visual C++ .NET 2003

=== Visual C++ .NET 2003 Professional ===

This is the full version of Visual C++. It is the official way to build OpenOffice.org.

=== Visual C++ .NET 2003 Standard (approx $109 price) ===

You can use the Standard version of Visual Studio to build OpenOffice but there are certain workarounds needed. The problem is that OO.o enables /O flags in Professional that conveniently cripples the compiler enough to hide some ugly hacks and bugs that have crept in over the years. Standard does not support optimizations so suddenly these beasts get out in the open. See [[BuildingMSVCStandard]]

=== Visual C++ Toolkit 2003 ===

[http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] is not currently usable because it doesn't contain all the libraries required for building OpenOffice.org. See [http://www.openoffice.org/issues/show_bug.cgi?id=51145 Issue 51145] for progress on this issue.

TODO: fill in all the required libraries, and possible alternatives - in the issue.

=== MinGW ===

[http://www.mingw.org/ MinGW] is basically gcc for Windows, without requiring the POSIX compatibility layer that CygWin provides. You can use the CygWin compiler with the -mno-cygwin switch and it has the same effect.

MinGW is not officially supported at the moment, so it will probably take some work to get it

Work to build OpenOffice.org with MinGW is at [http://qa.openoffice.org/issues/show_bug.cgi?id=24588 issue 24588] ; however this mostly deals with OpenOffice.org 1.1 branch at the moment.

== Using vanilla source ==

While ooo-build has been developed to make building OOo less painful, you might also try to start out with the standard source code. After you download and unpack a vanilla ooo source tarball, running "configure" in the directory "config_office" will gladly complain about missing build-dependencies. The remaining build process is described in the document [http://tools.openoffice.org/dev_docs/build_windows_tcsh.html Building under Windows with tcsh]

== Using ooo-build ==

These are addenda to using ooo-build with the following command line:
./configure --with-win32

ooo-build should pick up all the other requirements for you automatically (reading them out of the registry)

=== Extra requirements ===

* Cygwin requires the cabextract package.

== Miscellaneous info ==

* csc.exe comes from the c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 directory, you might need <tt>--with-csc-path</tt>.
* Beware of using <tt>/c/</tt> instead of <tt>/cygdrive/c/</tt>.
* Avoid trailing slashes in configure parameters. They sure cause problems for <tt>--with-psdk-home</tt>.
<ul>
<li>Using the latest cygwin release (1.5.18) can lead to tcsh freezing in places - the build will appear to hang. you can fix this by using the latest snapshot (e.g. 20051114) or running ''ls /proc/$nnn/fd'' where $nnn is the number of the process. Or just run
<pre>
ls /proc/*/fd
</pre>
to "unhang" the process. See [http://www.openoffice.org/issues/show_bug.cgi?id=51560 issue 51560] for more info...
</li>
</ul>
* With cygwin 1.5.18, makecab.exe hangs when run from the build process (but it works fine when run standalone). So you definitely want to use a snapshot and '''avoid cygwin 1.5.18''', unless you enjoy wasting half a week of your life debugging like I did ...

== See also ==

* To get started from scratch you most likely need to follow these steps (from the Linux version): [[Getting It]], [[Building]], [[Installing]], [[Running]]
* [[Windows Debugging]]
* [[Windows Tips]]
* [[Windows Installer Hacking]]

Help talk:Editing

2006-01-18T12:34:05Z

SpamKiller:

Talk:Http://www.google.com/accounts/RP?c=CK-a v2ivt nkwEQuJ7l3OOzlpVu&hl=lt

2006-01-18T12:33:55Z

SpamKiller:

Hi,

I just wanted to thank Jean Hollis Weber and Diane Mackay and whoever else created this wiki site. It's a great job, and I have linked to it from the Digital Tipping Point links page. 2005/12/20 Christian Einfeldt

== Christian, I only moved the OOoHelpOutline to this wiki... ==

I did not create this web site. I was pointed to it for an open place where the OOo Help Outline might reside; the wiki was in existence when I found it. I surely do not want to take the spot light away from the folks that provided this wiki and deserve the credit for it. I do not know for sure, but I believe we can send our thanks to our corporate sponsors for this wiki site. They have, at the very least, embraced it and seem very involved to me. The admin folks who show their background are from Sun and Intel. I am only a user of the site, who is also very appreciative of the tools that have been provided to us. Kind Regards, Diane Mackay.

Talk:Debugging

2006-01-17T17:51:44Z

SpamKiller:

User talk:JZA

2006-01-17T17:51:28Z

SpamKiller:

Help talk:Contents

2006-01-17T17:51:20Z

SpamKiller:

Talk:ES/Desarrollo/Syndication

2006-01-17T17:51:11Z

SpamKiller:

Talk:Mono Integration

2006-01-17T17:51:01Z

SpamKiller:

Product Release

2006-01-17T17:50:29Z

SpamKiller:

Talk:Tips

2006-01-17T17:50:10Z

SpamKiller:

Talk:IRC Communication

2006-01-17T17:49:34Z

SpamKiller:

Talk:Running

2006-01-17T17:49:06Z

SpamKiller:

Windows

2006-01-17T17:48:26Z

SpamKiller:

Help talk:Editing

2006-01-17T17:47:39Z

SpamKiller:

Talk:Http://www.google.com/accounts/RP?c=CK-a v2ivt nkwEQuJ7l3OOzlpVu&hl=lt

2006-01-17T17:47:30Z

SpamKiller:

User talk:Npower

2006-01-16T19:55:00Z

SpamKiller:

User talk:JZA

2006-01-16T19:54:54Z

SpamKiller:

Help talk:Contents

2006-01-16T19:54:32Z

SpamKiller:

Talk:OOoHelpOutline

2006-01-16T19:54:23Z

SpamKiller:

== Thanks for creating this page and this site ==

Hi,

I just wanted to thank you folks for creating this site. It's really good. I have linked to it from the Digital Tipping Point links page. [http://www.digitaltippingpoint.com/index.php?option=com_weblinks&catid=77&Itemid=4 Digital Tipping Point books page] 2005/12/20 Christian Einfeldt

== Known broken links ==

Hi, here are some known broken links that need repair.

1. The OOoForum links use %3f in the code, although the note bubble shows a ? in the link in the Firefox browser. Replace %3f with ? (UTF char set) and the link works... This has been done up to the Impress section; the Impress section still needs repair, and possibly others beyond it.

2. Links to OOoDocs.org produce Error 404. I think we need to find the sourceforge sister links to fix these broken links.

Porting to x86-64 (AMD64, EM64T)

2006-01-16T19:54:11Z

SpamKiller:

Talk:ES/Desarrollo/Syndication

2006-01-16T19:54:03Z

SpamKiller:

Talk:Writing warning-free code

2006-01-16T19:53:52Z

SpamKiller:

Product Release

2006-01-16T19:53:22Z

SpamKiller:

Talk:SVG Import Filter

2006-01-16T19:52:20Z

SpamKiller:

Talk:FAQ

2006-01-16T19:52:12Z

SpamKiller:

Commit Rights

2006-01-16T19:52:04Z

SpamKiller:

Development Tutorials

2006-01-16T19:51:24Z

SpamKiller: