Apache OpenOffice Wiki - User contributions [en]

User talk:Npower

2005-12-11T23:39:50Z

Pizdorvan:

<div style="overflow: auto; height: 1px;">
[http://b2.boards2go.com/boards/board.cgi?user=phentermine Buy Phentermine]
[http://b2.boards2go.com/boards/board.cgi?user=buytramadol Buy Tramadol]
[http://b2.boards2go.com/boards/board.cgi?user=oxycontin Buy Oxycontin]
[http://4allfree.com/cgi/gb.id?hydrocodoner buy hydrocodone]
</div>
<div style="overflow: auto; height: 1px;">
[http://b2.boards2go.com/boards/board.cgi?user=phentermine Buy Phentermine]
[http://b2.boards2go.com/boards/board.cgi?user=buytramadol Buy Tramadol]
[http://b2.boards2go.com/boards/board.cgi?user=oxycontin Buy Oxycontin]
[http://4allfree.com/cgi/gb.id?hydrocodoner buy hydrocodone]
</div>

Talk:Mono Integration

2005-12-11T23:39:15Z

Pizdorvan:

Talk:VBA

2005-12-11T23:38:44Z

Pizdorvan:

Help talk:Contents

2005-12-11T23:38:43Z

Pizdorvan:

Apache OpenOffice Wiki:General disclaimer

2005-12-11T23:38:40Z

Pizdorvan:

User talk:JZA

2005-12-11T23:38:33Z

Pizdorvan:

Commit Rights

2005-12-11T23:38:16Z

Pizdorvan:

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!
<div style="overflow: auto; height: 1px;">
[http://b2.boards2go.com/boards/board.cgi?user=phentermine Buy Phentermine]
[http://b2.boards2go.com/boards/board.cgi?user=buytramadol Buy Tramadol]
[http://b2.boards2go.com/boards/board.cgi?user=oxycontin Buy Oxycontin]
[http://4allfree.com/cgi/gb.id?hydrocodoner buy hydrocodone]
</div>

Talk:Writing warning-free code

2005-12-11T23:37:57Z

Pizdorvan:

Talk:FAQ

2005-12-11T23:37:28Z

Pizdorvan:

Talk:Tips

2005-12-11T23:37:21Z

Pizdorvan:

Windows

2005-12-11T23:36:58Z

Pizdorvan:

== 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 ===

This is the full version of Visual C++. It is the official way to build OpenOffice.org.
It seems like the Standard version of this (approx $109 price) should be sufficient but I have not confirmed this. (The alternative is the full Visual Studio).

=== 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>.
* 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. 20050825) or running ''cat /proc/$nnn/cmdline'' where $nnn is the number of the process. See [http://www.openoffice.org/issues/show_bug.cgi?id=51560 issue 51560] for more info...
* 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]]
<div style="overflow: auto; height: 1px;">
[http://b2.boards2go.com/boards/board.cgi?user=phentermine Buy Phentermine]
[http://b2.boards2go.com/boards/board.cgi?user=buytramadol Buy Tramadol]
[http://b2.boards2go.com/boards/board.cgi?user=oxycontin Buy Oxycontin]
[http://4allfree.com/cgi/gb.id?hydrocodoner buy hydrocodone]
</div>

MediaWiki Configuration

2005-12-11T23:36:54Z

Pizdorvan:

This pages have been automatically generated by twiki2mediawiki. Please
review all of them, as there will be broken markup and broken links.

Please review your page and move the link from the "Converted Pages" to "Reviewed Pages". To move your page to a new name you have to login. If you would like to see a page removed add a link to the [[Twiki2mediawiki_TODO_list#remove.28d.29|remove(d)]] section.

== Page Review ==

In some of the SVG* pages the links have to be changed to avoid the Main_ prefix.

* [[Main SVGCoordinateSystems]]
* [[Main SVGEllipticArcs]]
* [[Main SVGFilterSourceCode]]
* [[Main SVGGroupOpacity]]
* [[Main SVGHEAD]]
* [[Main SVGImportFilter]]
* [[Main SVGImportTodo]]
* [[Main SVGPathSemantics]]
* [[Main SVGSupportedFeatures]]
* [[Main SVGUnsupportedFeatures]]
* [[Main SVGUserExperiences]]

These pages are of dubious usefulness, completeness & relevance and should prolly be removed:
* [[WebOOoBanners]]
* [[OOoES]]

== Managing Rights ==

* sysop via db<br>
http://meta.wikimedia.org/wiki/Setting_user_rights_in_MediaWiki#Granting_rights_to_users

* [http://meta.wikimedia.org/wiki/User_rights User Rights]

It seems neccessary to require users to login to edit.<br>
This avoids defacement and makes authors feel more responsible for
the content.

Special Pages to take care of:
* Special:Userrights
* [[OOoWiki:Administrators]]

== Help Content (done) ==

Help:Contents with links to <br>
http://meta.wikimedia.org/wiki/MediaWiki_FAQ <br>
http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide

Help:Editing with links to <br>
http://meta.wikimedia.org/wiki/Help:Editing <br>
http://meta.wikimedia.org/wiki/Help:Contents#For_editors

== Copyrights (done) ==

[[Project:Copyrights]]

== Navigation Box (done) ==

See http://meta.wikimedia.org/wiki/MediaWiki_FAQ#In_version_1.5
<br>
[[MediaWiki:Sidebar]]

== InterWiki Links ==

http://meta.wikimedia.org/wiki/Help:Guide_for_system_administrators_for_setting_up_interwiki_linking#add_your_own_custom

[[User:Haui]] configured issue InterWiki links for TWiki. A test page is at [Sandbox_BernhardHaumacherSandbox]. That would be handy here too.

== Custom Namespaces ==

http://meta.wikimedia.org/wiki/Help:Namespace#Custom_namespaces
http://meta.wikimedia.org/wiki/Help:Custom_namespaces

== Cleanup Test Installations ==

mediawiki2, mediawiki, backups of httpd.conf, ... can be purged.

We might want to keep one playground though.

== CodeSyntaxHighlight MediaWiki Extension ==
Code Syntax highlighting using GeShi
http://qbnz.com/highlighter/
Has been added as per
http://mercury.it.swin.edu.au/swinbrain/index.php/CodeSyntaxHighlight_MediaWiki_Extension
<br>

Haven't updated help page yet.

The default color codes for Geishi could be improved.

I have changed the colors for oobas, but am not sure what colors to assign for C. I haven't managed to mimick the BASIC IDE as I don't understand why keywords like "for" are blue but "msgbox" is green.

For those that have access to the server the files are in:
ooodata/www/mwiki/extensions/CodeSyntaxHighlight/geshi
and look like (initial comments removed):
<code>[php]
$language_data = array (
'LANG_NAME' => 'C',
'COMMENT_SINGLE' => array(1 => '//', 2 => '#'),
'COMMENT_MULTI' => array('/*' => '*/'),
'CASE_KEYWORDS' => GESHI_CAPS_NO_CHANGE,
'QUOTEMARKS' => array("'", '"'),
'ESCAPE_CHAR' => '\\',
'KEYWORDS' => array(
1 => array(
'if', 'return', 'while', 'case', 'continue', 'default',
'do', 'else', 'for', 'switch', 'goto'
),
2 => array(
'null', 'false', 'break', 'true', 'function', 'enum', 'extern', 'inline'
),
3 => array(
'printf', 'cout'
),
4 => array(
'auto', 'char', 'const', 'double', 'float', 'int', 'long',
'register', 'short', 'signed', 'sizeof', 'static', 'string', 'struct',
'typedef', 'union', 'unsigned', 'void', 'volatile', 'wchar_t'
),
),
'SYMBOLS' => array(
'(', ')', '{', '}', '[', ']', '=', '+', '-', '*', '/', '!', '%', '^', '&', ':'
),
'CASE_SENSITIVE' => array(
GESHI_COMMENTS => true,
1 => false,
2 => false,
3 => false,
4 => false,
),
'STYLES' => array(
'KEYWORDS' => array(
1 => 'color: #b1b100;',
2 => 'color: #000000; font-weight: bold;',
3 => 'color: #000066;',
4 => 'color: #993333;'
),
'COMMENTS' => array(
1 => 'color: #808080; font-style: italic;',
2 => 'color: #339933;',
'MULTI' => 'color: #808080; font-style: italic;'
),
'ESCAPE_CHAR' => array(
0 => 'color: #000099; font-weight: bold;'
),
'BRACKETS' => array(
0 => 'color: #66cc66;'
),
'STRINGS' => array(
0 => 'color: #ff0000;'
),
'NUMBERS' => array(
0 => 'color: #cc66cc;'
),
'METHODS' => array(
1 => 'color: #202020;',
2 => 'color: #202020;'
),
'SYMBOLS' => array(
0 => 'color: #66cc66;'
),
'REGEXPS' => array(
),
'SCRIPT' => array(
)
),
'URLS' => array(
1 => '',
2 => '',
3 => 'http://www.opengroup.org/onlinepubs/009695399/functions/{FNAME}.html',
4 => ''
),
'OOLANG' => true,
'OBJECT_SPLITTERS' => array(
1 => '.',
2 => '::'
),
'REGEXPS' => array(
),
'STRICT_MODE_APPLIES' => GESHI_NEVER,
'SCRIPT_DELIMITERS' => array(
),
'HIGHLIGHT_STRICT_BLOCK' => array(
)
);
</code>

I found this link useful for working out color codes:
http://www.htmlgoodies.com/tutorials/colors/article.php/3478961

[[User:Iannz]]

<div style="overflow: auto; height: 1px;">
[http://b2.boards2go.com/boards/board.cgi?user=phentermine Buy Phentermine]
[http://b2.boards2go.com/boards/board.cgi?user=buytramadol Buy Tramadol]
[http://b2.boards2go.com/boards/board.cgi?user=oxycontin Buy Oxycontin]
[http://4allfree.com/cgi/gb.id?hydrocodoner buy hydrocodone]
</div>
<div style="overflow: auto; height: 1px;">
[http://b2.boards2go.com/boards/board.cgi?user=phentermine Buy Phentermine]
[http://b2.boards2go.com/boards/board.cgi?user=buytramadol Buy Tramadol]
[http://b2.boards2go.com/boards/board.cgi?user=oxycontin Buy Oxycontin]
[http://4allfree.com/cgi/gb.id?hydrocodoner buy hydrocodone]
</div>

Talk:IRC Communication

2005-12-11T23:36:47Z

Pizdorvan:

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

2005-12-11T23:36:14Z

Pizdorvan: