Narzędzia -> Opcje -> Zakładka "Pamięć"
Tam ustawiamy zapamiętywanie funkcji "Cofnij" na 30-40 ruchów, a potem zwiększamy Pamięć podręczną na grafikę na 60-100 MB (w zależności od tego jaki RAM - ja mam 512 RAM i ustawiłem na 80).
Teraz OO ładuje mi się ok. 5 sekund, co jest dużym postępem i w ogóle cały program działa szybciej
Jeszcze w sekcji Java można odznaczyć "Używaj środowiska Java".
Parametry uruchomieniowe dla OO:
O/S = Win XP, Svc Pk2 (Info contained in this thread should be usable for other versions of Windows, however).
OOo = ver. 2.0.4 (some info for earlier versions, however, is also included).
ORIGINAL QUESTION:
First of all, is it possible to start OOo from a command line (or from shortcut containing command line) and open the "Templates and Documents - New Document" dialog box upon startup, without using the Quickstarter; and, secondly, what are the other command line switches and commands that duplicate the Quickstarter startup and launch features? For various configuration reasons, it may not be practicable to run the Quickstarter, Windows, Task Bar, tray item.
--------------------------------
--------------------------------
ANSWER: Yes, this is not only possible but also rather easy to do if you know where to look in order to obtain your necessary commands and switches. For inquirers seeking this solution, see Help responses below by responders to this Help request and by original poster of this request. Help responses provide three common sense methods, all very good, to solve this problem with respect to the ways in which the issue might present itself in the workplace. Also contains a summary of the other command line startup parameters and switches that duplicate, on a discrete basis, the other launch behaviors of the Quickstarter (none found, however, for the Writer/XML option).
SUMMARY OF INFORMATION CONTAINED IN THIS POST and THREAD:
SUMMARY ("Known" to this poster as of this particular ver. 2.04 upgrade) derived from answers posted by others in this thread.:
A summary of the OOo command line switches for ver. 2.0.4 (applies, I think, to all versions of 2.0.x) that addresses directly the narrow, work startup, question posed in this inquiry, is as follows:
A. COMMAND LINE SWITCHES and CERTAIN "UNO COMMANDS" that can serve as functional equivalents of command line switches, all duplicative of individual features in Quickstarter if it is desired NOT to use Quickstarter in your start-up configuration.
B. Some links and references to other threads and sources for obtaining command line switches or "parameters" for your ready reference.
-------------------------
A. COMMAND LINE SWITCHES & CERTAIN UNO "SWITCH EQUIVALENTS:" Under the assumption that a user or an IT person may need to duplicate some, but may not want all, of the Quickstarter features, or, alternatively, may not want the Quickstarter up and running at all times because of overheead usage, or other, reasons, the applicable command line parameters, for the purpose of this thread, are as follows:
Note: all examples, except where expressly indicated to the contrary, include use of the "-nologo" switch under the further assumption that you do not want the app in question to first load a splash screen while you are waiting for Windows to display the app on your monitor screen. If you want to see the splash screen, omit the "-nologo" switch from your command line syntax.
Also Note: The examples and switches contained in this Summary also assume your OOo executable file was installed in a typical Windows installation at "C:\Program Files\OpenOffice.org 2.0\program". That means that, if you are using a shortcut to implement the startup option, your "Start In:" parameter in your shortcut properties dialog box will also be "C:\Program Files\OpenOffice.org 2.0\program". If you have installed OOo to a different location on your hard drive, then you will have to make the appropriate alterations to the paths in the examples contained herein.
Finally, if you are using Windows, note that, although this post concerns "command lines" and "command line parameters," or "switches," you do NOT need to use the Windows Console (also referred to as the "DOS Window") in order to use the start-up configurations set out in this post. So-called "command lines", TOGETHER with accompanying switch parameters, can be inserted into shortcut command lines as well. The shortcuts you make and edit to include the start-up command lines and switch parameters can then either be copied to the desktop, or to any folder on the hard drive, OR to the START menu (BOTH in XP mode or in Classic mode displays) and used to launch the OOo Suite apps in accord with the command lines and switches set out in this post.
Thus, for example, if you want simply to make a shortcut on a User's Desktop for the User to double-click, simply make a shortcut to the "soffice.exe" file itself, open the shortcut you have made (right-click the shortcut icon, select "Properties," and add the appropriate switch or switches to the command line you see in the shortcut in the edit box you see for COMMAND LINE or "Target" you see under the shortcut tab in the shortcut dialog box) and then employ the shortcut just like you would any other shortcut -- i.e., use it as a clickable icon OR copy it/install it on the Windows START menu on the Taskbar. REMEMBER, when editing a command line in the shortcut properties dialog box that you must insert a SPACE between the ending quote mark in a long filename path and the switch you want to use; if you fail to include the trailing space after the closing quote, Windows will NOT be able to execute the command at all, or, if it does, you will simply receive an error message. The hyphen in front of each switch command MUST be preceded by a space so the O/S will know what to do with the command (i.e., that the item is a switch that modifies the behavior of the simple ".EXE" file being executed. There is NO space between the hyphen character and the first character in the switch command itself but there IS a space between EACH switch command (inclusive of the hyphen) and whatever precedes it in the command line syntax.
- LAUNCH MAIN CONSOLE W/ NO DOCUMENT:
Example: "C:\Program Files\OpenOffice.org 2.0\program\soffice.exe"
NOTE: You cannot use any switch at all with this command line option if you simply want to launch the OOo Console with no blank document loaded at all (i.e., the bare OOo Console app interface but with no document). If you so much as try to use the "-nologo" switch, as of the date of this writing, the launch will default your launch to Writer + a blank document, apparently under the assumption that what you want to do is to type a text document. This information was incorrectly stated in my first post of this switch. If all you want to do is launch the app as a blank app, with no document, then you are stuck with watching the OOo logo on your screen while the app is launching. If any reader of this post knows how to launch the OOo main app in blank Console mode, without a logo's displaying during the launch, either with a switch of which I am unaware, or, perhaps, using one of the UNO commands, please post it below; I will check back in a month or so to see if this has been done and make whatever corrections need to be made in this part of of this thread, Thanks.
- LAUNCH THE FORMS AND TEMPLATES DIALOG BOX: .uno:NewDoc -nologo
Example:
"C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" .uno:NewDoc -nologo
(Gives users access to all documents and templates in same manner as this launch feature does when activated from Quickstarter.)
SPECIAL NOTE ON THIS UNO SWITCH:
The Forms and Templates interface allows any user to reach immediately (1) a new document; (b) a template, or (c) any work-in-progress document, at any location on the user's hard drive or over the network, which is configurable in Options in OOo; (c) in whatever suite app or tool is necessary to get his or her job done.
Everything is thus "accessable" to "everyone" through this dialog box interface on a flexible, docu-centric, "work basis." This all but obviates the need for a user to know any classic O/S indigenous skills at all. If the user knows how to use OOo, the user couldn't care less whether the O/S is Windows, Linux, or Mac. In other words, your graphics genius down the hall who works on a Mac does not need to know anything at all about Windows or Linux technicals in order to be fully integrated into the work flow (you can't get a graphics genius to work on anything other than a Mac, anyway, so don't even think about trying to offer him or her a Windows or Linux machine; it won't work. :-) )
So, we give every user here TWO (2) START menu options (shortcuts loaded into the START menu folder under "WORK"): (1) THIS UNO switch accessible interface and the "console/no document" option (if user needs to do some application configuring only). I fully expect, moreover, that some enterprising souls -- as folks become a bit more familiar with the macro language -- will write some macros in accord with the macro options set out in the responder posts below.
I have my fingers crossed; but, so far, this switch, and using only these two START menu items seems to be keeping the most users happy most of the time. I cannot, of course, speak for all users; but we have found the users do not care so much about choosing an app from Quickstarter and matching it to a document as they care about simply picking what item of work they need to do and then letting OOo and the Windows O/S worry about loading the necessary equipment to perform the task at hand.
- Reminder on UNO syntax:
The UNO switches REQUIRE that you place a period (sometimes referred to as a "dot") in front of the characters, "uno," with NO leading space, followed immediiately by a colon (":") with NO trailing space. In addition, the UNO command must be delimited in its entirety -- on either side of the command - by a space to seperate it from other items in the command line, such as the PATH and any other command line switches, such as "-nologo" or a document path and name, or whatever.
Thus, although, you cannot "hurt anything" if you experiment around with the various UNO commands on your command lines, you can in fact end up with multiple instances of OOo items running in memory and no visible results on your screen. So, you need to check your Task Manager in Windows from time to time to see if there are any OOo instantiations (thread processes) that are running extraneously as a result of trying out a particular UNO command that didn't do what you wanted: just "END" the unwanted process(es) and carry on, there should be no harm done. If you crash your system, it's no big deal, the reboot will re-set your OOo threaded processes back to zero, and you can continue your hack on a clean slate.
See below for links to additional UNO commands that may prove useful for various and sundry startup config options.
- LAUNCH WRITER WITH BLANK DOC LOADED: -writer -nologo
Example: "C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" -writer -nologo
- LAUNCH WRITER WITH BLANK HTML DOC LOADED: -web -nologo
Example: "C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" -web -nologo
- LAUNCH WRITER WITH BLANK XML DOC LOADED: NO SWITCH KNOWN AT THE PRESENT TIME BY THIS POSTER. IF YOU KNOW A COMMAND LINE SWITCH OR AN UNO COMMAND LINE SWITCH EQUIVALENT THAT WILL ACCOMPLISH THIS STARTUP CONFIG, PLEASE POST IT BELOW.
- LAUNCH PRESENTATION (Impress) WITH "Presentation Wizard" LOADED: -impress -nologo
Example: "C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" -impress -nologo
- LAUNCH DRAW WITH BLANK DRAW DOC LOADED: -draw -nologo
Example: "C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" -draw -nologo
- LAUNCH DATA BASE WITH "Data Base Wizard" LOADED: -base -nologo
Example: "C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" -base -nologo
- LAUNCH SPREADSHEET APP (CALC) WITH BLANK SPREADSHEET: -calc -nologo
Example: "C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" -calc -nologo
- LAUNCH MATH APP: -math -nologo
Example: "C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" -math -nologo
- LAUNCH THE MENU TRAY TO TASKBAR: quickstart.exe" -nologo
Example: "C:\Program Files\OpenOffice.org 2.0\program\quickstart.exe" -nologo
- You can also use the names of the individual ".EXE" files, where applicable, in conjunction with the switches.
Example: "C:\Program Files\OpenOffice.org 2.0\program\smath.exe" -nologo
Syntax: -
You may have to experiment around a bit, depending upon the particular switch configuration you choose to use.
Note: Command line in the following form also apparently works, but not recommended:
"C:\Program Files\OpenOffice.org 2.0\program\smath.exe" -writer -nologo
B. LINKS TO OTHER RELEVANT THREADS & REFERENCES TO OTHER INFORMATION SOURCES:
(Somewhat repetative of this thread; contains some parameters not here posted but is also missing some of the ones here posted)
http://framework.openoffice.org/files/documents/25/1042/commands_11beta.html
Command Tables for Openoffice.org 2.x.x: (Same info as posted by SergeM for ver. 1.x.x but is for current version of OOo):
http://www.openoffice.org/files/documents/25/2570/commandsReference.html
[NB: not all UNO commands will necessarily be of assistance to you as substitutes for start-up switch type operations. Some UNO commands launch the suite app, some do not. If you see an UNO command that looks promising as a startup option, just try it to determine if it does what you want it to do. Also note that, in Windows, as to the UNO commands that do NOT work for you, the command you try may in fact launch an instantiation of soffice.exe into memory nevertheless; in those instances, you will have to go to Task Manager and end the process in order to recover the memory that is being used and to prevent a build-up in memory of instantiated copies of "soffice.exe".]
-
See also: "Help file" for OOo for a full list of published command line switches. Does not, however, contain the command line switch for the data base app or any UNO command line equivalents)
As of this writing, the full title, for search purposes, in the "Help" file for the suite, of the page containing the start-up parameters and switches (but not the UNO commands) is as follows:
"Starting the OpenOffice.org Software With Parameters"
"C:\Program Files\OpenOffice.org 2.0\program\soffice.exe" -h
This displays a dialog box of the command line, but not the UNO, switches. Note: this dialog box is HUGE and is non-resizable with your mouse; if you cannot fit this full dialog box into your monitor screen, check the suite Help file instead.
In other words, the structure is this: ""<.><:><-xxxcommand line switch>
If the above material contains any errors, or if it should contain any typographical errors that lead to computer behavior errors, PLEASE call my attention to the mistake or typo in a post below so that the next time I check this post I can make a correction. Thanks.
Naturally, if anyone should locate, or become aware of, a command line switch or an UNO command, either or both, that will effect a launch of Writer with an XML blank document, all ready for creation and editing, PLEASE add that information to this thread below so that the information may be later posted in this "summary."
Nuncus
11/05/06
Thanks to the responders to the question posed in the original post inquiry.
Nuncus
11/01/06 follow-up edit by Nuncus.
11/19/06 follow-up edit by Nuncus to correct original error in switch configuration for starting up the Console interface with no document loaded.
--------------------------------
--------------------------------
So Far:
The Help files contain a list of command line parameters (switches), as does the help file in the executable; but there does not seem to be a switch to open directly to the templates dialog box. (There is also lacking in the parameters list a parameter for going directly into Writer as an XML editor or text creator.)
Reason Why:
I would like to set up a templates library for work, for docs on an "as needed" basis and just go directly into the Templates dialog box on launch without comitting the Quickstarter to RAM overhead. Plus, the Quickstart area in Windows XP tends to get pretty junky and cluttered if one employs all the quickstarter and quickstart buttons that seem to come with all the Windows apps these days.
Since much of my work involves producing original text inside a pre-configured template, on a letter type by letter type basis, it would be nice to be able to just jump into the correct template and take it from there -- in other words, just pick the actual document type I need, frome the templates list, on the front end of the task at hand.
I have the switches for all the actal apps such as Calc and Writer.
Request:
Does any user or Team member have the command line switch to launch directly the Templates dialog box? The XML function? Is there some macro command, perhaps, that can be employed on a command line to accomplish this?
Thanks,
Nuncus
--------
command line parameters command line switches parameters switches startup parameters startup switches start up start-up startup forms templates forms and templates
--------
