OpenOffice.org Macros Explained

Numerous mailing lists are available for OpenOffice.org users. Information on each mailing list is available from the lists- related Web site. Start from the projects Web page at http://projects.openoffice.org .

• For questions concerning UNO bridges and language bindings, including StarBASIC: http://udk . openoffice.org .

• Use http://framework . openoffice.org/scripting/ for questions about the upcoming scripting framework.

• The site http://xml.openoffice.org deals with questions questions regarding the OpenOffice.org XML file formats.

• The development Web site, http://development.openoffice.org/index.html , references the dev API mailing list. There is also a link to the archives, which are filled with useful questions and answers: http://api.openoffice.org/servlets/SearchList?listName=dev .

When you ask a question on a mailing list, the answers go to the mailing list rather than directly to you. You must subscribe to the mailing list so that you can receive the answers. Instructions are provided to subscribe to each of the mailing lists. Although developers read the mailing lists and answer questions, this is not a support forum in the sense of guaranteed help. If other users or developers have a solution or an idea for a solution, they will post an answer. Answers requiring a lot of work or time are not likely to be answered .

As a user of OOo, the users mailing list ( users-subscribe@openoffice.org ) may be of interest. Be warned , however, that it generates a lot of traffic-about 200 e-mail messages each day. Although this list is primarily for questions regarding usage of the different components such as Writer and Calc, macro-related questions are frequently asked and answered.

The dev mailing list ( dev-subscribe@api.openoffice.org ) can also be a good source for information of interest. The dev list is for API-related questions, but numerous scripting questions are asked and answered here. Although many Sun developers use this list and answer questions, they are not obligated to do so; do not abuse them. The dev list produces a much more manageable number of e-mail messages. Don't be offended if you're directed to another list.

A good first step before asking a question is to subscribe to the mailing list. Remember, the people answering your questions are not paid to do so. It is appreciated if you answer other people's questions if you know the answer. Here are some hints to ensure that you receive answers on the mailing lists.

• Before asking a question, try to find the answer yourself. Search the Web, search the mailing-list archives, search the Developer's Guide, search Google, read a FAQ. Inspect returned objects. The user community members prefer to help people who can help themselves and give back to the community.

• Choose a meaningful message header. I receive hundreds of e- mails every day so I am likely to skip a message that is titled "Please Help," "Urgent," or "Macro Problem." A better title is "How do I run a macro from the command line?" or "Searching macro fails to find attributes." I can then look at questions that I am likely to already understand or that interest me. We all get more e-mail than we need. Vague or misleading subject lines often inspire liberal use of the Delete feature.

• Carefully word your question so that you ask the right question. "My macro has a run-time error" is rather vague. Including a little code certainly helps. Including the run-time error in your message also helps. The fact that your sort macro does not sort as it should might be specific, but I need more information and perhaps some code before I can comment. State the problem precisely, and include how you tried to solve the problem. Specific error messages-and anything you know about the circumstances or likely causes of the problem-are welcome.

• Do not expect someone else to do your work for you. "My client is paying me $2000 to convert this macro; will you do it for free?" is not likely to receive a response. I have translated macros from other systems because they were interesting and of broad scope, and I was allowed to then release them to the user community. If you are really in a bind, someone on the list might be willing to do your work for a fee.

• Do not directly ask a single individual, even if they are knowledgeable. Many people can answer your question using pooled knowledge, and you will often receive a better solution. In other words, ask the question on the list rather than directly to an individual, unless you have a good reason for doing so. The last question that I helped answer on the list generated roughly 10 messages from four different people.

• It's considered bad form to request an answer to be e-mailed to you at a different address. If you don't care enough to check the mailing list for the answer, why should someone else care enough to spend time answering your question in the first place? Again, remember that these folks are volunteers! Also, the answer to your question-an online discussion leading to the understanding of your circumstances and eventual solution-may be of value to others in the community. In this way, the shared pool of knowledge grows larger and better over time.

• When you do have a solution, post it to help others. A polite "thank you" is also appropriate. Again, courtesy and sharing are important to the development of a functioning community that benefits you and all the other members as well. (I feel like a public service announcement when I say these things, just in case you were wondering.)

The mailing list Web page at http://www.openoffice.org/mail_list.html contains links that allow you to search the mailing lists for previously asked questions. Many questions have already been asked and answered. The mailing list Web page also includes instructions on accessing some of the mailing lists as a newsgroup. The users list generates numerous messages that can overwhelm your mailbox, so this is a good option.