Difference between revisions of "Documentation/Dashboard/DocOOo Structure"
(→HOW_TO) |
(→HOW_TO) |
||
Line 219: | Line 219: | ||
[1] as per CVS statistics | [1] as per CVS statistics | ||
− | + | ||
− | + | ===HOW_TO=== | |
− | + | ||
− | + | {| border=1 cellpadding=1 style="border-collapse:collapse;" | |
− | + | |- style="background-color: #DADAFF;" | |
− | + | ! Document | |
− | + | ! Title | |
− | + | ! Format(s) !! Size !! Age[1] !! License | |
− | + | ! Owner/Author | |
+ | ! Notes | ||
+ | ! Up-to-date? | ||
+ | ! Recommendation | ||
+ | |- style="background-color: #DDDDDD;" | ||
+ | | colspan=10 | Section '''data_source''' | ||
+ | |- | ||
+ | | SQLite | ||
+ | | Using SQLite Database with OpenOffice.org | ||
+ | | PDF, SXW || 27p || 2.8 y || PDLv1 | ||
+ | | Yves Chaufour (French version) | ||
+ | | translated by Gerry Singleton | ||
+ | | | ||
+ | | | ||
==Issuetracker== | ==Issuetracker== |
Revision as of 14:02, 13 July 2007
Contents
Website Content
The documentation web site repository contains a total of around 5700 files organized into different subdirectories. The following list is an incomplete tree of the documentation/www repository:
. |-- HOW_TO |-- Samples_Templates |-- articles |-- book_reviews |-- contests |-- faqs |-- id |-- it |-- manuals |-- online_help |-- quickstart |-- setup_guide2 |-- testdir |-- tutorials |-- user_faq `-- zh
HOW_TO
Document | Title | Format(s) | Size | Age[1] | License | Owner/Author | Notes | Up-to-date? | Recommendation |
---|---|---|---|---|---|---|---|---|---|
Section data_source | |||||||||
SQLite | Using SQLite Database with OpenOffice.org | PDF, SXW | 27p | 2.8 y | PDLv1 | Yves Chaufour (French version) | translated by Gerry Singleton | ||
data1_EN | How to Create a Data Source from Scratch | HTML, SXW | 11p | 2.5 y | PDLv1 | Scott Carr | |||
how_to_link_tables_ using_named_parameters | How to Link Tables Using SQL Named Parameters | PDF, SXW, HTML | 42 | 4.6 y | PDLv1 | Scott Carr | |||
Section drawing_graphics | |||||||||
documentationdraw_en | How to get to grips with OpenOffice.org Draw | PDF, SXW | 125p | 1.7 y | none specified | Michel Pinquier | PDF is corrupt | ||
draw1_EN | How To Compose a Document with Simple Geometric Shapes, to Change their Attributes (color, size, position, ...) and to Print the Result. | PDF, HTML | 13p | 5 y | none specified | Gianluca Turconi | |||
Section drawing_graphics | |||||||||
Formula_CommandRef0_4_1 | Formula Command Reference | PDF, SXW | 15p | 2.6 y | LGPLv2.1 | Fred Saalbach | |||
Formula_HowTo_1_0 | Formula | PDF, SXW | 18p | 1.9 y | LGPLv2.1 | Fred Saalbach, Harald Schilly (German original) | |||
Section impress | |||||||||
HowToInsertNotes | How to Insert Notes In an Impress Presentation | PDF, SXW, ODT | 8p | 2 y | PDLv1 | Steven Allen | |||
InsertNewSlide | How to Insert a New Slide in Impress | PDF, SXW, ODT | 9p | 2 y | PDLv1 | Steven Allen | |||
NewImpressUsingTemplate_revised | How To Create a New Impress Document Using a Template | PDF, SXW, ODT | 11p | 2 y | PDLv1 | Steven Allen | |||
fs_impress2_0 | First Steps in Impress | PDF, ODT | 39p | 1.5 y | PDLv1 | Andreas Mantke | |||
movies_without_java | Using Movies in Impress on Linux without the need for Java Software | PDF, ODT | 39p | 1.4 y | PDLv1 | Max Weber | |||
Section misc | |||||||||
AverCrossRef | Label Format Cross-Reference | 11p | 10.6 mo | PDLv1 | Russell Ossendryver | no source available | get source or remove | ||
Troubleshooting_guide | Troubleshooting Common Problems | PDF, HTML | 21p | 10.4 mo | PDLv1 | Gerry Singleton | no source available | get source and move content to Troubleshooting wiki section (to be created) | |
cygwin_tortoise_cvs | Installing and using CVS under Windows | PDF, HTML | 9p | 4.7 y | none specified | Miljenko Williams | no source available | remove, misplaced, no source | |
email_change_v0.2 | Changing Your Email Address: OpenOffice.org Mailing Lists | PDF, SXW | 10p | 2.2 y | PDLv1 | Tim Kampa | |||
multiple_screens | How to Setup Multiple Screens under Linux Using Xinerama | PDF, ODT | 10p | 1.6 y | none specified | Chris Tyler | remove, link to Linux Web resource instead | ||
Section spreadsheet | |||||||||
Section various_topics | |||||||||
Section word_processing | |||||||||
[1] as per CVS statistics
HOW_TO
Document | Title | Format(s) | Size | Age[1] | License | Owner/Author | Notes | Up-to-date? | Recommendation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Section data_source | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SQLite | Using SQLite Database with OpenOffice.org | PDF, SXW | 27p | 2.8 y | PDLv1 | Yves Chaufour (French version) | translated by Gerry Singleton |
IssuetrackerThe master issue list has a total of 151 issues, 129 (85%) of which are owned by issues@documentation, i.e. no-one.
Organize By the Most Transparent Way of Approaching a ProgramIt is tempting to organize the same way Microsoft Office does because people are very familiar with Microsoft Office. The advantage is people will understand and use features more quickly if they are already familiar with concept and location. The disadvantage is there may be a completely new way to doing something which is far more efficient and intuitive then the way Microsoft Office handles a feature. All of your various ways of learning (multimedia, etc.) can be incorporated into the following wiki structure.
Collaborative Wikis
Structured LearningMost users approach a program by looking at what they can see first. If they can make sense of what they see, they will gradually learn more advanced concepts from this starting point. So the best way to teach a program is to start with what the user sees and explain it in every way possible (text, spoken, multimedia, etc.). If you want to reinforce concepts even more, then include exercises so the user gets hands-on experience. Do a review of each concept covered as a way of adding repetition - a summary of the material. After you've covered what a learner sees, then begin to take them into what they don't see (the menu items and what they mean and do). This is a thorough approach for non-emergency users and will result in a thorough understanding of OpenOffice. As a training mechanism for a company or educational institution, organizing information this way would be ideal. In addition because the information is organized in line with actual program components, updating information and placing it correctly will become much easier. Your other common type of user will be the emergency user who just has to get something done right away and needs to know how to do it. To my mind, this information can be incorporated into the wiki structure discussed above and made searchable.
Outline of Wiki Concept for OpenOfficeOpenOffice Base/Calc/Draw/Impress/Math/Writer
Adding Value to OpenOffice.orgThere are other people who are working on projects which will add value to OpenOffice. Clipart and templates are two of these areas. I would suggest perhaps someone be asked to collect all of these together onto a page of links. Put a link in OpenOffice that connects to these pages, so a user can rapidly find new resources instead of hunting for them on the OpenOffice.org website. This will have the added utility of simplifying the website as well. Maybe put a template link and a clipart link under the “Help” Menu? As a user, one of the first things I looked for was templates and clipart. It took some digging to find the following:
I'm helping a lot of people with OpenOffice right now. I've set up several businesses with it and I also install it by default for everyone who is not interested in buying Microsoft Office. There are a couple of things which I think could be changed to give more visibility to OpenOffice. Automatically delete installation files from desktop after installation Place folder with shortcuts in it on desktop as well as in Program Folder Menu. This will make OpenOffice far more visible and easier to access for new users. If they want to delete the folder containing the shortcuts from their desktop they can. In the meantime it makes OpenOffice.org far more visible. Question: Firefox is making money for Mozilla by starting with a Firefox Google search page. I'm not sure what kind of mandate OpenOffice has in this area, but what if there was an additional link under the help menu to “Search for Resources” for OpenOffice which takes the user to an OpenOffice Google search page? This would generate additional income for the project without being obnoxious or useless. |