You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by wa...@apache.org on 2020/11/01 20:54:36 UTC
[openoffice-org] branch main updated (cd5fca1 -> a95beeb)
This is an automated email from the ASF dual-hosted git repository.
wave pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git.
from cd5fca1 Migration of modularization html content
new 71b9499 Migration of framework/scripting/release-0.3/SFrameworkInstall.jar large asset
new 1539f72 Migration of framework assets
new a95beeb Migration of framework html content
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
assets/framework/documentation/devmanual/draft.sxw | Bin 0 -> 42590 bytes
.../documentation/filters/configstructure.gif | Bin 0 -> 16571 bytes
.../framework/documentation/filterui/filterui.jar | Bin 0 -> 33924 bytes
.../framework/documentation/filterui/mainwin.png | Bin 0 -> 59724 bytes
.../documentation/filterui/mainwin_tbn.png | Bin 0 -> 8508 bytes
.../documentation/others/job_executor.gif | Bin 0 -> 11973 bytes
assets/framework/proposals/apply/apply_alert.gif | Bin 0 -> 3722 bytes
assets/framework/proposals/apply/format_area.gif | Bin 0 -> 10508 bytes
.../framework/proposals/apply/format_bullets.gif | Bin 0 -> 9741 bytes
assets/framework/proposals/apply/format_cell.gif | Bin 0 -> 11351 bytes
.../proposals/apply/format_conditions.gif | Bin 0 -> 8782 bytes
.../proposals/apply/format_dimensions.gif | Bin 0 -> 9935 bytes
assets/framework/proposals/apply/format_page.gif | Bin 0 -> 12193 bytes
.../framework/proposals/apply/format_paragraph.gif | Bin 0 -> 10735 bytes
assets/framework/proposals/apply/format_styles.gif | Bin 0 -> 7544 bytes
assets/framework/proposals/apply/format_text.gif | Bin 0 -> 9698 bytes
assets/framework/proposals/apply/oarch.gif | Bin 0 -> 899 bytes
assets/framework/proposals/dialogs/b1.gif | Bin 0 -> 14727 bytes
assets/framework/proposals/dialogs/b2.gif | Bin 0 -> 7905 bytes
assets/framework/proposals/dialogs/b3.gif | Bin 0 -> 9950 bytes
assets/framework/proposals/dialogs/b4.gif | Bin 0 -> 17022 bytes
.../dialogs/staroffice_60_desk_env_int.sdc | Bin 0 -> 115200 bytes
.../proposals/filterfactory/filterfactory.gif | Bin 0 -> 37627 bytes
.../proposals/filterfactory/seq_create_filter.gif | Bin 0 -> 12177 bytes
assets/framework/proposals/helpagent/offering.gif | Bin 0 -> 26213 bytes
.../Proposal_Keyboard_shortcuts_html_6a183024.gif | Bin 0 -> 26380 bytes
.../security_enhancements_html_51f79ff8.gif | Bin 0 -> 8372 bytes
.../security_enhancements_html_70928bb3.gif | Bin 0 -> 8012 bytes
.../security_enhancements_html_m2dbadf08.gif | Bin 0 -> 8445 bytes
.../security_enhancements_html_m4000e9d0.gif | Bin 0 -> 8078 bytes
.../security_enhancements_html_m4acea22c.gif | Bin 0 -> 8055 bytes
.../security_enhancements_html_md0eecca.gif | Bin 0 -> 8018 bytes
assets/{support/tryout => framework}/robots.txt | 0
assets/framework/scripting/EnableSF.zip | Bin 0 -> 392 bytes
assets/framework/scripting/EnableSF2.zip | Bin 0 -> 407 bytes
.../scripting/ScriptingFrameworkChapter.pdf | Bin 0 -> 748337 bytes
.../scripting/UtilityScripts/Capitalise.zip | Bin 0 -> 4264 bytes
.../scripting/UtilityScripts/ExportToHTML.zip | Bin 0 -> 3764 bytes
.../framework/scripting/UtilityScripts/InsertC.zip | Bin 0 -> 3563 bytes
.../scripting/UtilityScripts/InsertHiddenText.zip | Bin 0 -> 3905 bytes
.../scripting/UtilityScripts/InsertTM.zip | Bin 0 -> 3726 bytes
.../scripting/UtilityScripts/Newsgroup.zip | Bin 0 -> 542785 bytes
.../UtilityScripts/SFBugsQueryIssuezilla.zip | Bin 0 -> 4473 bytes
.../UtilityScripts/SFBugsQueryIssuezillaCalc.zip | Bin 0 -> 4469 bytes
.../scripting/UtilityScripts/WordCount.zip | Bin 0 -> 3957 bytes
assets/framework/scripting/UtilityScripts/all.zip | Bin 0 -> 572700 bytes
.../scripting/release-0.1/SFrameworkInstall.jar | Bin 0 -> 1959427 bytes
.../scripting/release-0.2/SFrameworkInstall.jar | Bin 0 -> 2538077 bytes
.../scripting/release-0.2/assign-event.gif | Bin 0 -> 9444 bytes
.../scripting/release-0.2/assign-menu.gif | Bin 0 -> 8930 bytes
.../framework/scripting/release-0.2/jsruntime.zip | Bin 0 -> 571284 bytes
.../scripting/release-0.3/SFrameworkInstall.jar | Bin 0 -> 3263774 bytes
.../scripting/release-0.3/assign-event.gif | Bin 0 -> 10007 bytes
.../scripting/release-0.3/assign-menu.gif | Bin 0 -> 9245 bytes
.../framework/scripting/release-0.3/beanshell.gif | Bin 0 -> 8925 bytes
.../framework/scripting/release-0.3/edit-debug.gif | Bin 0 -> 5432 bytes
assets/framework/scripting/release-0.3/rhino.gif | Bin 0 -> 22002 bytes
.../framework/scripting/scriptingf1/beanshell.gif | Bin 0 -> 8433 bytes
assets/framework/scripting/scriptingf1/fig1.png | Bin 0 -> 6259 bytes
assets/framework/scripting/scriptingf1/fig2.png | Bin 0 -> 5754 bytes
assets/framework/scripting/scriptingf1/fig3.png | Bin 0 -> 6902 bytes
assets/framework/scripting/scriptingf1/fig4.png | Bin 0 -> 28149 bytes
assets/framework/scripting/scriptingf1/fig5.png | Bin 0 -> 28089 bytes
assets/framework/scripting/scriptingf1/fig6.png | Bin 0 -> 5882 bytes
assets/framework/scripting/scriptingf1/office.jar | Bin 0 -> 165693 bytes
assets/framework/scripting/scriptingf1/rhino.gif | Bin 0 -> 14632 bytes
content/framework/binfilter.html | 82 +
.../framework/documentation/filters/example.html | 526 +++++
content/framework/documentation/filters/index.html | 486 +++++
.../framework/documentation/filters/reference.html | 109 +
.../framework/documentation/filters/services.html | 299 +++
.../framework/documentation/filterui/index.html | 211 ++
.../documentation/mimetypes/mimetypes.html | 644 ++++++
content/framework/documentation/others/index.html | 14 +
.../documentation/others/job_executor.html | 284 +++
content/framework/drafts/contribution.html | 202 ++
content/framework/drafts/documents.html | 207 ++
content/framework/drafts/modules.html | 193 ++
content/framework/drafts/proposals.html | 231 +++
content/framework/index.html | 564 ++++++
.../proposals/apply/apply_button_spec.htm | 266 +++
.../apply/apply_button_spec_appendix.html | 105 +
.../proposals/apply/new_preview_concept.html | 223 +++
content/framework/proposals/dialogs/index.html | 63 +
.../filterfactory/proposal_filterfactory.html | 119 ++
.../framework/proposals/filters/exportfilters.html | 115 ++
.../proposals/helpagent/HelpAgentProposal_01.htm | 272 +++
.../proposals/helpagent/helpagentproposal01.htm | 272 +++
.../Proposal_Keyboard_shortcuts.html | 345 ++++
.../framework/proposals/macro/macrorecording.html | 207 ++
.../macro_security/security_enhancements.html | 233 +++
.../proposals/printing/Standard_Printer.htm | 154 ++
.../setup_feature/setup_features60_proposal.html | 660 +++++++
.../EDR-IDLDocs/drafts/com/module-ix.html | 78 +
.../EDR-IDLDocs/drafts/com/sun/module-ix.html | 78 +
.../EDR-IDLDocs/drafts/com/sun/star/module-ix.html | 84 +
.../sun/star/script/browse/BrowseNodeTypes.html | 145 ++
.../sun/star/script/browse/XBrowseNode-xref.html | 82 +
.../com/sun/star/script/browse/XBrowseNode.html | 283 +++
.../com/sun/star/script/browse/module-ix.html | 90 +
.../com/sun/star/script/framework/module-ix.html | 81 +
.../framework/security/XScriptSecurity-xref.html | 82 +
.../script/framework/security/XScriptSecurity.html | 158 ++
.../star/script/framework/security/module-ix.html | 82 +
.../framework/storage/ScriptStorage-xref.html | 64 +
.../script/framework/storage/ScriptStorage.html | 106 +
.../storage/ScriptStorageManager-xref.html | 74 +
.../framework/storage/ScriptStorageManager.html | 100 +
.../script/framework/storage/XScriptInfo-xref.html | 72 +
.../star/script/framework/storage/XScriptInfo.html | 384 ++++
.../framework/storage/XScriptInfoAccess-xref.html | 82 +
.../framework/storage/XScriptInfoAccess.html | 230 +++
.../storage/XScriptStorageExport-xref.html | 82 +
.../framework/storage/XScriptStorageExport.html | 126 ++
.../storage/XScriptStorageManager-xref.html | 82 +
.../framework/storage/XScriptStorageManager.html | 344 ++++
.../storage/XScriptStorageRefresh-xref.html | 82 +
.../framework/storage/XScriptStorageRefresh.html | 126 ++
.../star/script/framework/storage/module-ix.html | 179 ++
.../framework/storage/theScriptStorageManager.html | 73 +
.../drafts/com/sun/star/script/module-ix.html | 84 +
.../provider/LanguageScriptProvider-xref.html | 77 +
.../script/provider/LanguageScriptProvider.html | 86 +
.../script/provider/MasterScriptProvider-xref.html | 64 +
.../star/script/provider/MasterScriptProvider.html | 86 +
.../star/script/provider/ScriptProvider-xref.html | 79 +
.../sun/star/script/provider/ScriptProvider.html | 92 +
.../provider/ScriptProviderForBasic-xref.html | 64 +
.../script/provider/ScriptProviderForBasic.html | 86 +
.../provider/ScriptProviderForBeanShell-xref.html | 64 +
.../provider/ScriptProviderForBeanShell.html | 86 +
.../provider/ScriptProviderForJava-xref.html | 64 +
.../script/provider/ScriptProviderForJava.html | 86 +
.../provider/ScriptProviderForJavaScript-xref.html | 64 +
.../provider/ScriptProviderForJavaScript.html | 86 +
.../com/sun/star/script/provider/XScript-xref.html | 82 +
.../com/sun/star/script/provider/XScript.html | 179 ++
.../star/script/provider/XScriptContext-xref.html | 72 +
.../sun/star/script/provider/XScriptContext.html | 208 ++
.../star/script/provider/XScriptProvider-xref.html | 92 +
.../sun/star/script/provider/XScriptProvider.html | 142 ++
.../provider/XScriptProviderSupplier-xref.html | 72 +
.../script/provider/XScriptProviderSupplier.html | 127 ++
.../com/sun/star/script/provider/module-ix.html | 157 ++
.../scripting/EDR-IDLDocs/drafts/module-ix.html | 78 +
.../scripting/EDR-IDLDocs/index-files/index-1.html | 60 +
.../EDR-IDLDocs/index-files/index-10.html | 56 +
.../EDR-IDLDocs/index-files/index-11.html | 56 +
.../EDR-IDLDocs/index-files/index-12.html | 61 +
.../EDR-IDLDocs/index-files/index-13.html | 58 +
.../EDR-IDLDocs/index-files/index-14.html | 56 +
.../EDR-IDLDocs/index-files/index-15.html | 56 +
.../EDR-IDLDocs/index-files/index-16.html | 59 +
.../EDR-IDLDocs/index-files/index-17.html | 56 +
.../EDR-IDLDocs/index-files/index-18.html | 63 +
.../EDR-IDLDocs/index-files/index-19.html | 75 +
.../scripting/EDR-IDLDocs/index-files/index-2.html | 61 +
.../EDR-IDLDocs/index-files/index-20.html | 59 +
.../EDR-IDLDocs/index-files/index-21.html | 56 +
.../EDR-IDLDocs/index-files/index-22.html | 58 +
.../EDR-IDLDocs/index-files/index-23.html | 56 +
.../EDR-IDLDocs/index-files/index-24.html | 74 +
.../EDR-IDLDocs/index-files/index-25.html | 56 +
.../EDR-IDLDocs/index-files/index-26.html | 56 +
.../EDR-IDLDocs/index-files/index-27.html | 56 +
.../scripting/EDR-IDLDocs/index-files/index-3.html | 66 +
.../scripting/EDR-IDLDocs/index-files/index-4.html | 58 +
.../scripting/EDR-IDLDocs/index-files/index-5.html | 61 +
.../scripting/EDR-IDLDocs/index-files/index-6.html | 59 +
.../scripting/EDR-IDLDocs/index-files/index-7.html | 85 +
.../scripting/EDR-IDLDocs/index-files/index-8.html | 58 +
.../scripting/EDR-IDLDocs/index-files/index-9.html | 59 +
.../framework/scripting/EDR-IDLDocs/module-ix.html | 111 ++
content/framework/scripting/build-guide.html | 285 +++
content/framework/scripting/index.html | 287 +++
.../framework/scripting/netbeans-debugging.html | 37 +
.../framework/scripting/release-0.1/SmokeTest.html | 1115 +++++++++++
.../scripting/release-0.1/developer-guide.html | 267 +++
.../release-0.1/developer-release-features.html | 75 +
content/framework/scripting/release-0.1/faq.html | 162 ++
content/framework/scripting/release-0.1/index.html | 200 ++
.../scripting/release-0.1/install-guide.html | 211 ++
.../scripting/release-0.1/issues-list.html | 103 +
.../scripting/release-0.1/jedit-devguide.html | 369 ++++
.../scripting/release-0.1/netbeans-devguide.html | 214 ++
.../scripting/release-0.1/user-guide.html | 136 ++
.../scripting/release-0.1/whats-next.html | 161 ++
.../framework/scripting/release-0.2/SmokeTest.html | 928 +++++++++
.../scripting/release-0.2/build-guide.html | 472 +++++
.../release-0.2/commandline-devguide.html | 212 ++
.../scripting/release-0.2/developer-guide.html | 294 +++
.../release-0.2/developer-release-features.html | 109 +
content/framework/scripting/release-0.2/faq.html | 91 +
content/framework/scripting/release-0.2/index.html | 323 +++
.../scripting/release-0.2/install-guide.html | 160 ++
.../scripting/release-0.2/javascript-devguide.html | 152 ++
.../scripting/release-0.2/netbeans-devguide.html | 244 +++
.../scripting/release-0.2/release-notes.html | 140 ++
.../scripting/release-0.2/runtime-howto.html | 1981 +++++++++++++++++++
.../scripting/release-0.2/uninstall-guide.html | 123 ++
.../scripting/release-0.2/user-guide.html | 497 +++++
.../scripting/release-0.2/whats-next.html | 44 +
.../framework/scripting/release-0.3/SmokeTest.html | 928 +++++++++
.../scripting/release-0.3/build-guide.html | 573 ++++++
.../release-0.3/commandline-devguide.html | 178 ++
.../scripting/release-0.3/developer-guide.html | 202 ++
.../release-0.3/developer-release-features.html | 123 ++
content/framework/scripting/release-0.3/faq.html | 91 +
content/framework/scripting/release-0.3/index.html | 238 +++
.../scripting/release-0.3/install-guide.html | 207 ++
.../scripting/release-0.3/netbeans-devguide.html | 244 +++
.../scripting/release-0.3/release-notes.html | 155 ++
.../scripting/release-0.3/runtime-howto.html | 2072 ++++++++++++++++++++
.../scripting/release-0.3/uninstall-guide.html | 126 ++
.../scripting/release-0.3/user-guide.html | 609 ++++++
.../scripting/release-0.3/whats-next.html | 44 +
.../framework/scripting/scriptingf1/SFArch.html | 1509 ++++++++++++++
.../scriptingf1/commandline-devguide.html | 185 ++
.../scripting/scriptingf1/developer-guide.html | 302 +++
content/framework/scripting/scriptingf1/faq.html | 97 +
content/framework/scripting/scriptingf1/index.html | 193 ++
.../scripting/scriptingf1/netbeans-devguide.html | 242 +++
.../scripting/scriptingf1/user-guide.html | 478 +++++
.../scripting/scriptingf1/whats-next.html | 58 +
content/framework/scripting/testindex.html | 193 ++
.../framework/scripting/utilities-download.html | 236 +++
226 files changed, 33332 insertions(+)
create mode 100644 assets/framework/documentation/devmanual/draft.sxw
create mode 100644 assets/framework/documentation/filters/configstructure.gif
create mode 100644 assets/framework/documentation/filterui/filterui.jar
create mode 100644 assets/framework/documentation/filterui/mainwin.png
create mode 100644 assets/framework/documentation/filterui/mainwin_tbn.png
create mode 100644 assets/framework/documentation/others/job_executor.gif
create mode 100644 assets/framework/proposals/apply/apply_alert.gif
create mode 100644 assets/framework/proposals/apply/format_area.gif
create mode 100644 assets/framework/proposals/apply/format_bullets.gif
create mode 100644 assets/framework/proposals/apply/format_cell.gif
create mode 100644 assets/framework/proposals/apply/format_conditions.gif
create mode 100644 assets/framework/proposals/apply/format_dimensions.gif
create mode 100644 assets/framework/proposals/apply/format_page.gif
create mode 100644 assets/framework/proposals/apply/format_paragraph.gif
create mode 100644 assets/framework/proposals/apply/format_styles.gif
create mode 100644 assets/framework/proposals/apply/format_text.gif
create mode 100644 assets/framework/proposals/apply/oarch.gif
create mode 100644 assets/framework/proposals/dialogs/b1.gif
create mode 100644 assets/framework/proposals/dialogs/b2.gif
create mode 100644 assets/framework/proposals/dialogs/b3.gif
create mode 100644 assets/framework/proposals/dialogs/b4.gif
create mode 100644 assets/framework/proposals/dialogs/staroffice_60_desk_env_int.sdc
create mode 100644 assets/framework/proposals/filterfactory/filterfactory.gif
create mode 100644 assets/framework/proposals/filterfactory/seq_create_filter.gif
create mode 100644 assets/framework/proposals/helpagent/offering.gif
create mode 100644 assets/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts_html_6a183024.gif
create mode 100644 assets/framework/proposals/macro_security/security_enhancements_html_51f79ff8.gif
create mode 100644 assets/framework/proposals/macro_security/security_enhancements_html_70928bb3.gif
create mode 100644 assets/framework/proposals/macro_security/security_enhancements_html_m2dbadf08.gif
create mode 100644 assets/framework/proposals/macro_security/security_enhancements_html_m4000e9d0.gif
create mode 100644 assets/framework/proposals/macro_security/security_enhancements_html_m4acea22c.gif
create mode 100644 assets/framework/proposals/macro_security/security_enhancements_html_md0eecca.gif
copy assets/{support/tryout => framework}/robots.txt (100%)
create mode 100644 assets/framework/scripting/EnableSF.zip
create mode 100644 assets/framework/scripting/EnableSF2.zip
create mode 100644 assets/framework/scripting/ScriptingFrameworkChapter.pdf
create mode 100644 assets/framework/scripting/UtilityScripts/Capitalise.zip
create mode 100644 assets/framework/scripting/UtilityScripts/ExportToHTML.zip
create mode 100644 assets/framework/scripting/UtilityScripts/InsertC.zip
create mode 100644 assets/framework/scripting/UtilityScripts/InsertHiddenText.zip
create mode 100644 assets/framework/scripting/UtilityScripts/InsertTM.zip
create mode 100644 assets/framework/scripting/UtilityScripts/Newsgroup.zip
create mode 100644 assets/framework/scripting/UtilityScripts/SFBugsQueryIssuezilla.zip
create mode 100644 assets/framework/scripting/UtilityScripts/SFBugsQueryIssuezillaCalc.zip
create mode 100644 assets/framework/scripting/UtilityScripts/WordCount.zip
create mode 100644 assets/framework/scripting/UtilityScripts/all.zip
create mode 100644 assets/framework/scripting/release-0.1/SFrameworkInstall.jar
create mode 100644 assets/framework/scripting/release-0.2/SFrameworkInstall.jar
create mode 100644 assets/framework/scripting/release-0.2/assign-event.gif
create mode 100644 assets/framework/scripting/release-0.2/assign-menu.gif
create mode 100644 assets/framework/scripting/release-0.2/jsruntime.zip
create mode 100644 assets/framework/scripting/release-0.3/SFrameworkInstall.jar
create mode 100644 assets/framework/scripting/release-0.3/assign-event.gif
create mode 100644 assets/framework/scripting/release-0.3/assign-menu.gif
create mode 100644 assets/framework/scripting/release-0.3/beanshell.gif
create mode 100644 assets/framework/scripting/release-0.3/edit-debug.gif
create mode 100644 assets/framework/scripting/release-0.3/rhino.gif
create mode 100644 assets/framework/scripting/scriptingf1/beanshell.gif
create mode 100644 assets/framework/scripting/scriptingf1/fig1.png
create mode 100644 assets/framework/scripting/scriptingf1/fig2.png
create mode 100644 assets/framework/scripting/scriptingf1/fig3.png
create mode 100644 assets/framework/scripting/scriptingf1/fig4.png
create mode 100644 assets/framework/scripting/scriptingf1/fig5.png
create mode 100644 assets/framework/scripting/scriptingf1/fig6.png
create mode 100644 assets/framework/scripting/scriptingf1/office.jar
create mode 100644 assets/framework/scripting/scriptingf1/rhino.gif
create mode 100755 content/framework/binfilter.html
create mode 100644 content/framework/documentation/filters/example.html
create mode 100644 content/framework/documentation/filters/index.html
create mode 100644 content/framework/documentation/filters/reference.html
create mode 100644 content/framework/documentation/filters/services.html
create mode 100644 content/framework/documentation/filterui/index.html
create mode 100644 content/framework/documentation/mimetypes/mimetypes.html
create mode 100644 content/framework/documentation/others/index.html
create mode 100644 content/framework/documentation/others/job_executor.html
create mode 100644 content/framework/drafts/contribution.html
create mode 100644 content/framework/drafts/documents.html
create mode 100644 content/framework/drafts/modules.html
create mode 100644 content/framework/drafts/proposals.html
create mode 100644 content/framework/index.html
create mode 100644 content/framework/proposals/apply/apply_button_spec.htm
create mode 100644 content/framework/proposals/apply/apply_button_spec_appendix.html
create mode 100644 content/framework/proposals/apply/new_preview_concept.html
create mode 100644 content/framework/proposals/dialogs/index.html
create mode 100644 content/framework/proposals/filterfactory/proposal_filterfactory.html
create mode 100644 content/framework/proposals/filters/exportfilters.html
create mode 100644 content/framework/proposals/helpagent/HelpAgentProposal_01.htm
create mode 100644 content/framework/proposals/helpagent/helpagentproposal01.htm
create mode 100644 content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html
create mode 100644 content/framework/proposals/macro/macrorecording.html
create mode 100644 content/framework/proposals/macro_security/security_enhancements.html
create mode 100644 content/framework/proposals/printing/Standard_Printer.htm
create mode 100644 content/framework/proposals/setup_feature/setup_features60_proposal.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/BrowseNodeTypes.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/XBrowseNode-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/XBrowseNode.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/XScriptSecurity-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/XScriptSecurity.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorage-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorage.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorageManager-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorageManager.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfo-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfo.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfoAccess-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfoAccess.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageExport-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageExport.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageManager-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageManager.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageRefresh-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageRefresh.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/theScriptStorageManager.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/LanguageScriptProvider-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/LanguageScriptProvider.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/MasterScriptProvider-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/MasterScriptProvider.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProvider-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProvider.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProviderForBasic-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProviderForBasic.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProviderForBeanShell-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProviderForBeanShell.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProviderForJava-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProviderForJava.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProviderForJavaScript-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/ScriptProviderForJavaScript.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/XScript-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/XScript.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/XScriptContext-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/XScriptContext.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/XScriptProvider-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/XScriptProvider.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/XScriptProviderSupplier-xref.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/XScriptProviderSupplier.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/provider/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/drafts/module-ix.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-1.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-10.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-11.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-12.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-13.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-14.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-15.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-16.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-17.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-18.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-19.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-2.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-20.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-21.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-22.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-23.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-24.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-25.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-26.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-27.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-3.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-4.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-5.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-6.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-7.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-8.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/index-files/index-9.html
create mode 100644 content/framework/scripting/EDR-IDLDocs/module-ix.html
create mode 100644 content/framework/scripting/build-guide.html
create mode 100644 content/framework/scripting/index.html
create mode 100644 content/framework/scripting/netbeans-debugging.html
create mode 100644 content/framework/scripting/release-0.1/SmokeTest.html
create mode 100644 content/framework/scripting/release-0.1/developer-guide.html
create mode 100644 content/framework/scripting/release-0.1/developer-release-features.html
create mode 100644 content/framework/scripting/release-0.1/faq.html
create mode 100644 content/framework/scripting/release-0.1/index.html
create mode 100644 content/framework/scripting/release-0.1/install-guide.html
create mode 100644 content/framework/scripting/release-0.1/issues-list.html
create mode 100644 content/framework/scripting/release-0.1/jedit-devguide.html
create mode 100644 content/framework/scripting/release-0.1/netbeans-devguide.html
create mode 100644 content/framework/scripting/release-0.1/user-guide.html
create mode 100644 content/framework/scripting/release-0.1/whats-next.html
create mode 100644 content/framework/scripting/release-0.2/SmokeTest.html
create mode 100644 content/framework/scripting/release-0.2/build-guide.html
create mode 100644 content/framework/scripting/release-0.2/commandline-devguide.html
create mode 100644 content/framework/scripting/release-0.2/developer-guide.html
create mode 100644 content/framework/scripting/release-0.2/developer-release-features.html
create mode 100644 content/framework/scripting/release-0.2/faq.html
create mode 100644 content/framework/scripting/release-0.2/index.html
create mode 100644 content/framework/scripting/release-0.2/install-guide.html
create mode 100644 content/framework/scripting/release-0.2/javascript-devguide.html
create mode 100644 content/framework/scripting/release-0.2/netbeans-devguide.html
create mode 100644 content/framework/scripting/release-0.2/release-notes.html
create mode 100644 content/framework/scripting/release-0.2/runtime-howto.html
create mode 100644 content/framework/scripting/release-0.2/uninstall-guide.html
create mode 100644 content/framework/scripting/release-0.2/user-guide.html
create mode 100644 content/framework/scripting/release-0.2/whats-next.html
create mode 100644 content/framework/scripting/release-0.3/SmokeTest.html
create mode 100644 content/framework/scripting/release-0.3/build-guide.html
create mode 100644 content/framework/scripting/release-0.3/commandline-devguide.html
create mode 100644 content/framework/scripting/release-0.3/developer-guide.html
create mode 100644 content/framework/scripting/release-0.3/developer-release-features.html
create mode 100644 content/framework/scripting/release-0.3/faq.html
create mode 100644 content/framework/scripting/release-0.3/index.html
create mode 100644 content/framework/scripting/release-0.3/install-guide.html
create mode 100644 content/framework/scripting/release-0.3/netbeans-devguide.html
create mode 100644 content/framework/scripting/release-0.3/release-notes.html
create mode 100644 content/framework/scripting/release-0.3/runtime-howto.html
create mode 100644 content/framework/scripting/release-0.3/uninstall-guide.html
create mode 100644 content/framework/scripting/release-0.3/user-guide.html
create mode 100644 content/framework/scripting/release-0.3/whats-next.html
create mode 100644 content/framework/scripting/scriptingf1/SFArch.html
create mode 100644 content/framework/scripting/scriptingf1/commandline-devguide.html
create mode 100644 content/framework/scripting/scriptingf1/developer-guide.html
create mode 100644 content/framework/scripting/scriptingf1/faq.html
create mode 100644 content/framework/scripting/scriptingf1/index.html
create mode 100644 content/framework/scripting/scriptingf1/netbeans-devguide.html
create mode 100644 content/framework/scripting/scriptingf1/user-guide.html
create mode 100644 content/framework/scripting/scriptingf1/whats-next.html
create mode 100644 content/framework/scripting/testindex.html
create mode 100644 content/framework/scripting/utilities-download.html
[openoffice-org] 01/03: Migration of
framework/scripting/release-0.3/SFrameworkInstall.jar large asset
Posted by wa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
commit 71b94998c0ecc7905ecbdaa27c6bdc388c5c8aaa
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Sun Nov 1 12:54:10 2020 -0800
Migration of framework/scripting/release-0.3/SFrameworkInstall.jar large asset
---
.../scripting/release-0.3/SFrameworkInstall.jar | Bin 0 -> 3263774 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/assets/framework/scripting/release-0.3/SFrameworkInstall.jar b/assets/framework/scripting/release-0.3/SFrameworkInstall.jar
new file mode 100644
index 0000000..13ba1e1
Binary files /dev/null and b/assets/framework/scripting/release-0.3/SFrameworkInstall.jar differ
[openoffice-org] 02/03: Migration of framework assets
Posted by wa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
commit 1539f721ae30ee5746fe912a778aa7cc0ba71bd4
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Sun Nov 1 12:54:10 2020 -0800
Migration of framework assets
---
assets/framework/documentation/devmanual/draft.sxw | Bin 0 -> 42590 bytes
.../documentation/filters/configstructure.gif | Bin 0 -> 16571 bytes
assets/framework/documentation/filterui/filterui.jar | Bin 0 -> 33924 bytes
assets/framework/documentation/filterui/mainwin.png | Bin 0 -> 59724 bytes
.../framework/documentation/filterui/mainwin_tbn.png | Bin 0 -> 8508 bytes
.../framework/documentation/others/job_executor.gif | Bin 0 -> 11973 bytes
assets/framework/proposals/apply/apply_alert.gif | Bin 0 -> 3722 bytes
assets/framework/proposals/apply/format_area.gif | Bin 0 -> 10508 bytes
assets/framework/proposals/apply/format_bullets.gif | Bin 0 -> 9741 bytes
assets/framework/proposals/apply/format_cell.gif | Bin 0 -> 11351 bytes
.../framework/proposals/apply/format_conditions.gif | Bin 0 -> 8782 bytes
.../framework/proposals/apply/format_dimensions.gif | Bin 0 -> 9935 bytes
assets/framework/proposals/apply/format_page.gif | Bin 0 -> 12193 bytes
assets/framework/proposals/apply/format_paragraph.gif | Bin 0 -> 10735 bytes
assets/framework/proposals/apply/format_styles.gif | Bin 0 -> 7544 bytes
assets/framework/proposals/apply/format_text.gif | Bin 0 -> 9698 bytes
assets/framework/proposals/apply/oarch.gif | Bin 0 -> 899 bytes
assets/framework/proposals/dialogs/b1.gif | Bin 0 -> 14727 bytes
assets/framework/proposals/dialogs/b2.gif | Bin 0 -> 7905 bytes
assets/framework/proposals/dialogs/b3.gif | Bin 0 -> 9950 bytes
assets/framework/proposals/dialogs/b4.gif | Bin 0 -> 17022 bytes
.../proposals/dialogs/staroffice_60_desk_env_int.sdc | Bin 0 -> 115200 bytes
.../proposals/filterfactory/filterfactory.gif | Bin 0 -> 37627 bytes
.../proposals/filterfactory/seq_create_filter.gif | Bin 0 -> 12177 bytes
assets/framework/proposals/helpagent/offering.gif | Bin 0 -> 26213 bytes
.../Proposal_Keyboard_shortcuts_html_6a183024.gif | Bin 0 -> 26380 bytes
.../security_enhancements_html_51f79ff8.gif | Bin 0 -> 8372 bytes
.../security_enhancements_html_70928bb3.gif | Bin 0 -> 8012 bytes
.../security_enhancements_html_m2dbadf08.gif | Bin 0 -> 8445 bytes
.../security_enhancements_html_m4000e9d0.gif | Bin 0 -> 8078 bytes
.../security_enhancements_html_m4acea22c.gif | Bin 0 -> 8055 bytes
.../security_enhancements_html_md0eecca.gif | Bin 0 -> 8018 bytes
assets/framework/robots.txt | 7 +++++++
assets/framework/scripting/EnableSF.zip | Bin 0 -> 392 bytes
assets/framework/scripting/EnableSF2.zip | Bin 0 -> 407 bytes
.../framework/scripting/ScriptingFrameworkChapter.pdf | Bin 0 -> 748337 bytes
.../framework/scripting/UtilityScripts/Capitalise.zip | Bin 0 -> 4264 bytes
.../scripting/UtilityScripts/ExportToHTML.zip | Bin 0 -> 3764 bytes
assets/framework/scripting/UtilityScripts/InsertC.zip | Bin 0 -> 3563 bytes
.../scripting/UtilityScripts/InsertHiddenText.zip | Bin 0 -> 3905 bytes
.../framework/scripting/UtilityScripts/InsertTM.zip | Bin 0 -> 3726 bytes
.../framework/scripting/UtilityScripts/Newsgroup.zip | Bin 0 -> 542785 bytes
.../UtilityScripts/SFBugsQueryIssuezilla.zip | Bin 0 -> 4473 bytes
.../UtilityScripts/SFBugsQueryIssuezillaCalc.zip | Bin 0 -> 4469 bytes
.../framework/scripting/UtilityScripts/WordCount.zip | Bin 0 -> 3957 bytes
assets/framework/scripting/UtilityScripts/all.zip | Bin 0 -> 572700 bytes
.../scripting/release-0.1/SFrameworkInstall.jar | Bin 0 -> 1959427 bytes
.../scripting/release-0.2/SFrameworkInstall.jar | Bin 0 -> 2538077 bytes
.../framework/scripting/release-0.2/assign-event.gif | Bin 0 -> 9444 bytes
.../framework/scripting/release-0.2/assign-menu.gif | Bin 0 -> 8930 bytes
assets/framework/scripting/release-0.2/jsruntime.zip | Bin 0 -> 571284 bytes
.../framework/scripting/release-0.3/assign-event.gif | Bin 0 -> 10007 bytes
.../framework/scripting/release-0.3/assign-menu.gif | Bin 0 -> 9245 bytes
assets/framework/scripting/release-0.3/beanshell.gif | Bin 0 -> 8925 bytes
assets/framework/scripting/release-0.3/edit-debug.gif | Bin 0 -> 5432 bytes
assets/framework/scripting/release-0.3/rhino.gif | Bin 0 -> 22002 bytes
assets/framework/scripting/scriptingf1/beanshell.gif | Bin 0 -> 8433 bytes
assets/framework/scripting/scriptingf1/fig1.png | Bin 0 -> 6259 bytes
assets/framework/scripting/scriptingf1/fig2.png | Bin 0 -> 5754 bytes
assets/framework/scripting/scriptingf1/fig3.png | Bin 0 -> 6902 bytes
assets/framework/scripting/scriptingf1/fig4.png | Bin 0 -> 28149 bytes
assets/framework/scripting/scriptingf1/fig5.png | Bin 0 -> 28089 bytes
assets/framework/scripting/scriptingf1/fig6.png | Bin 0 -> 5882 bytes
assets/framework/scripting/scriptingf1/office.jar | Bin 0 -> 165693 bytes
assets/framework/scripting/scriptingf1/rhino.gif | Bin 0 -> 14632 bytes
65 files changed, 7 insertions(+)
diff --git a/assets/framework/documentation/devmanual/draft.sxw b/assets/framework/documentation/devmanual/draft.sxw
new file mode 100644
index 0000000..83ae567
Binary files /dev/null and b/assets/framework/documentation/devmanual/draft.sxw differ
diff --git a/assets/framework/documentation/filters/configstructure.gif b/assets/framework/documentation/filters/configstructure.gif
new file mode 100644
index 0000000..362be39
Binary files /dev/null and b/assets/framework/documentation/filters/configstructure.gif differ
diff --git a/assets/framework/documentation/filterui/filterui.jar b/assets/framework/documentation/filterui/filterui.jar
new file mode 100644
index 0000000..5519e6d
Binary files /dev/null and b/assets/framework/documentation/filterui/filterui.jar differ
diff --git a/assets/framework/documentation/filterui/mainwin.png b/assets/framework/documentation/filterui/mainwin.png
new file mode 100644
index 0000000..c72896e
Binary files /dev/null and b/assets/framework/documentation/filterui/mainwin.png differ
diff --git a/assets/framework/documentation/filterui/mainwin_tbn.png b/assets/framework/documentation/filterui/mainwin_tbn.png
new file mode 100644
index 0000000..375ee5d
Binary files /dev/null and b/assets/framework/documentation/filterui/mainwin_tbn.png differ
diff --git a/assets/framework/documentation/others/job_executor.gif b/assets/framework/documentation/others/job_executor.gif
new file mode 100644
index 0000000..2044ffb
Binary files /dev/null and b/assets/framework/documentation/others/job_executor.gif differ
diff --git a/assets/framework/proposals/apply/apply_alert.gif b/assets/framework/proposals/apply/apply_alert.gif
new file mode 100644
index 0000000..2cfd676
Binary files /dev/null and b/assets/framework/proposals/apply/apply_alert.gif differ
diff --git a/assets/framework/proposals/apply/format_area.gif b/assets/framework/proposals/apply/format_area.gif
new file mode 100644
index 0000000..4f8428f
Binary files /dev/null and b/assets/framework/proposals/apply/format_area.gif differ
diff --git a/assets/framework/proposals/apply/format_bullets.gif b/assets/framework/proposals/apply/format_bullets.gif
new file mode 100644
index 0000000..39dffa0
Binary files /dev/null and b/assets/framework/proposals/apply/format_bullets.gif differ
diff --git a/assets/framework/proposals/apply/format_cell.gif b/assets/framework/proposals/apply/format_cell.gif
new file mode 100644
index 0000000..ea10d98
Binary files /dev/null and b/assets/framework/proposals/apply/format_cell.gif differ
diff --git a/assets/framework/proposals/apply/format_conditions.gif b/assets/framework/proposals/apply/format_conditions.gif
new file mode 100644
index 0000000..7cb5f5d
Binary files /dev/null and b/assets/framework/proposals/apply/format_conditions.gif differ
diff --git a/assets/framework/proposals/apply/format_dimensions.gif b/assets/framework/proposals/apply/format_dimensions.gif
new file mode 100644
index 0000000..34d0f33
Binary files /dev/null and b/assets/framework/proposals/apply/format_dimensions.gif differ
diff --git a/assets/framework/proposals/apply/format_page.gif b/assets/framework/proposals/apply/format_page.gif
new file mode 100644
index 0000000..4641629
Binary files /dev/null and b/assets/framework/proposals/apply/format_page.gif differ
diff --git a/assets/framework/proposals/apply/format_paragraph.gif b/assets/framework/proposals/apply/format_paragraph.gif
new file mode 100644
index 0000000..6ed6f2e
Binary files /dev/null and b/assets/framework/proposals/apply/format_paragraph.gif differ
diff --git a/assets/framework/proposals/apply/format_styles.gif b/assets/framework/proposals/apply/format_styles.gif
new file mode 100644
index 0000000..9dbb470
Binary files /dev/null and b/assets/framework/proposals/apply/format_styles.gif differ
diff --git a/assets/framework/proposals/apply/format_text.gif b/assets/framework/proposals/apply/format_text.gif
new file mode 100644
index 0000000..ca1b555
Binary files /dev/null and b/assets/framework/proposals/apply/format_text.gif differ
diff --git a/assets/framework/proposals/apply/oarch.gif b/assets/framework/proposals/apply/oarch.gif
new file mode 100644
index 0000000..3a355c3
Binary files /dev/null and b/assets/framework/proposals/apply/oarch.gif differ
diff --git a/assets/framework/proposals/dialogs/b1.gif b/assets/framework/proposals/dialogs/b1.gif
new file mode 100644
index 0000000..b8c05e4
Binary files /dev/null and b/assets/framework/proposals/dialogs/b1.gif differ
diff --git a/assets/framework/proposals/dialogs/b2.gif b/assets/framework/proposals/dialogs/b2.gif
new file mode 100644
index 0000000..bb88b2c
Binary files /dev/null and b/assets/framework/proposals/dialogs/b2.gif differ
diff --git a/assets/framework/proposals/dialogs/b3.gif b/assets/framework/proposals/dialogs/b3.gif
new file mode 100644
index 0000000..319294e
Binary files /dev/null and b/assets/framework/proposals/dialogs/b3.gif differ
diff --git a/assets/framework/proposals/dialogs/b4.gif b/assets/framework/proposals/dialogs/b4.gif
new file mode 100644
index 0000000..f6c2c8f
Binary files /dev/null and b/assets/framework/proposals/dialogs/b4.gif differ
diff --git a/assets/framework/proposals/dialogs/staroffice_60_desk_env_int.sdc b/assets/framework/proposals/dialogs/staroffice_60_desk_env_int.sdc
new file mode 100644
index 0000000..822f5ee
Binary files /dev/null and b/assets/framework/proposals/dialogs/staroffice_60_desk_env_int.sdc differ
diff --git a/assets/framework/proposals/filterfactory/filterfactory.gif b/assets/framework/proposals/filterfactory/filterfactory.gif
new file mode 100644
index 0000000..e08143c
Binary files /dev/null and b/assets/framework/proposals/filterfactory/filterfactory.gif differ
diff --git a/assets/framework/proposals/filterfactory/seq_create_filter.gif b/assets/framework/proposals/filterfactory/seq_create_filter.gif
new file mode 100644
index 0000000..5cd76c5
Binary files /dev/null and b/assets/framework/proposals/filterfactory/seq_create_filter.gif differ
diff --git a/assets/framework/proposals/helpagent/offering.gif b/assets/framework/proposals/helpagent/offering.gif
new file mode 100644
index 0000000..cd8676e
Binary files /dev/null and b/assets/framework/proposals/helpagent/offering.gif differ
diff --git a/assets/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts_html_6a183024.gif b/assets/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts_html_6a183024.gif
new file mode 100644
index 0000000..1b6eb56
Binary files /dev/null and b/assets/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts_html_6a183024.gif differ
diff --git a/assets/framework/proposals/macro_security/security_enhancements_html_51f79ff8.gif b/assets/framework/proposals/macro_security/security_enhancements_html_51f79ff8.gif
new file mode 100644
index 0000000..3856018
Binary files /dev/null and b/assets/framework/proposals/macro_security/security_enhancements_html_51f79ff8.gif differ
diff --git a/assets/framework/proposals/macro_security/security_enhancements_html_70928bb3.gif b/assets/framework/proposals/macro_security/security_enhancements_html_70928bb3.gif
new file mode 100644
index 0000000..a08b163
Binary files /dev/null and b/assets/framework/proposals/macro_security/security_enhancements_html_70928bb3.gif differ
diff --git a/assets/framework/proposals/macro_security/security_enhancements_html_m2dbadf08.gif b/assets/framework/proposals/macro_security/security_enhancements_html_m2dbadf08.gif
new file mode 100644
index 0000000..770fddd
Binary files /dev/null and b/assets/framework/proposals/macro_security/security_enhancements_html_m2dbadf08.gif differ
diff --git a/assets/framework/proposals/macro_security/security_enhancements_html_m4000e9d0.gif b/assets/framework/proposals/macro_security/security_enhancements_html_m4000e9d0.gif
new file mode 100644
index 0000000..34d1859
Binary files /dev/null and b/assets/framework/proposals/macro_security/security_enhancements_html_m4000e9d0.gif differ
diff --git a/assets/framework/proposals/macro_security/security_enhancements_html_m4acea22c.gif b/assets/framework/proposals/macro_security/security_enhancements_html_m4acea22c.gif
new file mode 100644
index 0000000..fcc4184
Binary files /dev/null and b/assets/framework/proposals/macro_security/security_enhancements_html_m4acea22c.gif differ
diff --git a/assets/framework/proposals/macro_security/security_enhancements_html_md0eecca.gif b/assets/framework/proposals/macro_security/security_enhancements_html_md0eecca.gif
new file mode 100644
index 0000000..0641478
Binary files /dev/null and b/assets/framework/proposals/macro_security/security_enhancements_html_md0eecca.gif differ
diff --git a/assets/framework/robots.txt b/assets/framework/robots.txt
new file mode 100644
index 0000000..7e0b2af
--- /dev/null
+++ b/assets/framework/robots.txt
@@ -0,0 +1,7 @@
+User-Agent: *
+Disallow: /source/
+Disallow: /issues/
+Disallow: /search/
+Disallow: /servlets/
+Disallow: /project/
+Disallow: /nonav/
diff --git a/assets/framework/scripting/EnableSF.zip b/assets/framework/scripting/EnableSF.zip
new file mode 100644
index 0000000..491d520
Binary files /dev/null and b/assets/framework/scripting/EnableSF.zip differ
diff --git a/assets/framework/scripting/EnableSF2.zip b/assets/framework/scripting/EnableSF2.zip
new file mode 100644
index 0000000..7308ba8
Binary files /dev/null and b/assets/framework/scripting/EnableSF2.zip differ
diff --git a/assets/framework/scripting/ScriptingFrameworkChapter.pdf b/assets/framework/scripting/ScriptingFrameworkChapter.pdf
new file mode 100644
index 0000000..c3cfb58
Binary files /dev/null and b/assets/framework/scripting/ScriptingFrameworkChapter.pdf differ
diff --git a/assets/framework/scripting/UtilityScripts/Capitalise.zip b/assets/framework/scripting/UtilityScripts/Capitalise.zip
new file mode 100644
index 0000000..0d2eeda
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/Capitalise.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/ExportToHTML.zip b/assets/framework/scripting/UtilityScripts/ExportToHTML.zip
new file mode 100644
index 0000000..2852034
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/ExportToHTML.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/InsertC.zip b/assets/framework/scripting/UtilityScripts/InsertC.zip
new file mode 100644
index 0000000..eabec72
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/InsertC.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/InsertHiddenText.zip b/assets/framework/scripting/UtilityScripts/InsertHiddenText.zip
new file mode 100644
index 0000000..491998d
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/InsertHiddenText.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/InsertTM.zip b/assets/framework/scripting/UtilityScripts/InsertTM.zip
new file mode 100644
index 0000000..3af2b14
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/InsertTM.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/Newsgroup.zip b/assets/framework/scripting/UtilityScripts/Newsgroup.zip
new file mode 100644
index 0000000..e046a67
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/Newsgroup.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/SFBugsQueryIssuezilla.zip b/assets/framework/scripting/UtilityScripts/SFBugsQueryIssuezilla.zip
new file mode 100644
index 0000000..3195599
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/SFBugsQueryIssuezilla.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/SFBugsQueryIssuezillaCalc.zip b/assets/framework/scripting/UtilityScripts/SFBugsQueryIssuezillaCalc.zip
new file mode 100644
index 0000000..7279bd8
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/SFBugsQueryIssuezillaCalc.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/WordCount.zip b/assets/framework/scripting/UtilityScripts/WordCount.zip
new file mode 100644
index 0000000..e4b1e12
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/WordCount.zip differ
diff --git a/assets/framework/scripting/UtilityScripts/all.zip b/assets/framework/scripting/UtilityScripts/all.zip
new file mode 100644
index 0000000..5a14a6d
Binary files /dev/null and b/assets/framework/scripting/UtilityScripts/all.zip differ
diff --git a/assets/framework/scripting/release-0.1/SFrameworkInstall.jar b/assets/framework/scripting/release-0.1/SFrameworkInstall.jar
new file mode 100644
index 0000000..63e935c
Binary files /dev/null and b/assets/framework/scripting/release-0.1/SFrameworkInstall.jar differ
diff --git a/assets/framework/scripting/release-0.2/SFrameworkInstall.jar b/assets/framework/scripting/release-0.2/SFrameworkInstall.jar
new file mode 100644
index 0000000..a230cf2
Binary files /dev/null and b/assets/framework/scripting/release-0.2/SFrameworkInstall.jar differ
diff --git a/assets/framework/scripting/release-0.2/assign-event.gif b/assets/framework/scripting/release-0.2/assign-event.gif
new file mode 100644
index 0000000..223ec7e
Binary files /dev/null and b/assets/framework/scripting/release-0.2/assign-event.gif differ
diff --git a/assets/framework/scripting/release-0.2/assign-menu.gif b/assets/framework/scripting/release-0.2/assign-menu.gif
new file mode 100644
index 0000000..6eef91c
Binary files /dev/null and b/assets/framework/scripting/release-0.2/assign-menu.gif differ
diff --git a/assets/framework/scripting/release-0.2/jsruntime.zip b/assets/framework/scripting/release-0.2/jsruntime.zip
new file mode 100644
index 0000000..494b55a
Binary files /dev/null and b/assets/framework/scripting/release-0.2/jsruntime.zip differ
diff --git a/assets/framework/scripting/release-0.3/assign-event.gif b/assets/framework/scripting/release-0.3/assign-event.gif
new file mode 100644
index 0000000..bd9aa64
Binary files /dev/null and b/assets/framework/scripting/release-0.3/assign-event.gif differ
diff --git a/assets/framework/scripting/release-0.3/assign-menu.gif b/assets/framework/scripting/release-0.3/assign-menu.gif
new file mode 100644
index 0000000..30e4f25
Binary files /dev/null and b/assets/framework/scripting/release-0.3/assign-menu.gif differ
diff --git a/assets/framework/scripting/release-0.3/beanshell.gif b/assets/framework/scripting/release-0.3/beanshell.gif
new file mode 100644
index 0000000..22c4617
Binary files /dev/null and b/assets/framework/scripting/release-0.3/beanshell.gif differ
diff --git a/assets/framework/scripting/release-0.3/edit-debug.gif b/assets/framework/scripting/release-0.3/edit-debug.gif
new file mode 100644
index 0000000..b812c3f
Binary files /dev/null and b/assets/framework/scripting/release-0.3/edit-debug.gif differ
diff --git a/assets/framework/scripting/release-0.3/rhino.gif b/assets/framework/scripting/release-0.3/rhino.gif
new file mode 100644
index 0000000..bee8442
Binary files /dev/null and b/assets/framework/scripting/release-0.3/rhino.gif differ
diff --git a/assets/framework/scripting/scriptingf1/beanshell.gif b/assets/framework/scripting/scriptingf1/beanshell.gif
new file mode 100644
index 0000000..11cb1cd
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/beanshell.gif differ
diff --git a/assets/framework/scripting/scriptingf1/fig1.png b/assets/framework/scripting/scriptingf1/fig1.png
new file mode 100644
index 0000000..a4a6fcd
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/fig1.png differ
diff --git a/assets/framework/scripting/scriptingf1/fig2.png b/assets/framework/scripting/scriptingf1/fig2.png
new file mode 100644
index 0000000..1322114
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/fig2.png differ
diff --git a/assets/framework/scripting/scriptingf1/fig3.png b/assets/framework/scripting/scriptingf1/fig3.png
new file mode 100644
index 0000000..a2a020c
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/fig3.png differ
diff --git a/assets/framework/scripting/scriptingf1/fig4.png b/assets/framework/scripting/scriptingf1/fig4.png
new file mode 100644
index 0000000..ef8cecc
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/fig4.png differ
diff --git a/assets/framework/scripting/scriptingf1/fig5.png b/assets/framework/scripting/scriptingf1/fig5.png
new file mode 100644
index 0000000..7647e0b
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/fig5.png differ
diff --git a/assets/framework/scripting/scriptingf1/fig6.png b/assets/framework/scripting/scriptingf1/fig6.png
new file mode 100644
index 0000000..38c0269
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/fig6.png differ
diff --git a/assets/framework/scripting/scriptingf1/office.jar b/assets/framework/scripting/scriptingf1/office.jar
new file mode 100644
index 0000000..0518ea7
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/office.jar differ
diff --git a/assets/framework/scripting/scriptingf1/rhino.gif b/assets/framework/scripting/scriptingf1/rhino.gif
new file mode 100644
index 0000000..d31d1b6
Binary files /dev/null and b/assets/framework/scripting/scriptingf1/rhino.gif differ
[openoffice-org] 03/03: Migration of framework html content
Posted by wa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
commit a95beeb2dc9c16c9dd967c86ce6ac9dbffe5018d
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Sun Nov 1 12:54:11 2020 -0800
Migration of framework html content
---
content/framework/binfilter.html | 82 +
.../framework/documentation/filters/example.html | 526 +++++
content/framework/documentation/filters/index.html | 486 +++++
.../framework/documentation/filters/reference.html | 109 +
.../framework/documentation/filters/services.html | 299 +++
.../framework/documentation/filterui/index.html | 211 ++
.../documentation/mimetypes/mimetypes.html | 644 ++++++
content/framework/documentation/others/index.html | 14 +
.../documentation/others/job_executor.html | 284 +++
content/framework/drafts/contribution.html | 202 ++
content/framework/drafts/documents.html | 207 ++
content/framework/drafts/modules.html | 193 ++
content/framework/drafts/proposals.html | 231 +++
content/framework/index.html | 564 ++++++
.../proposals/apply/apply_button_spec.htm | 266 +++
.../apply/apply_button_spec_appendix.html | 105 +
.../proposals/apply/new_preview_concept.html | 223 +++
content/framework/proposals/dialogs/index.html | 63 +
.../filterfactory/proposal_filterfactory.html | 119 ++
.../framework/proposals/filters/exportfilters.html | 115 ++
.../proposals/helpagent/HelpAgentProposal_01.htm | 272 +++
.../proposals/helpagent/helpagentproposal01.htm | 272 +++
.../Proposal_Keyboard_shortcuts.html | 345 ++++
.../framework/proposals/macro/macrorecording.html | 207 ++
.../macro_security/security_enhancements.html | 233 +++
.../proposals/printing/Standard_Printer.htm | 154 ++
.../setup_feature/setup_features60_proposal.html | 660 +++++++
.../EDR-IDLDocs/drafts/com/module-ix.html | 78 +
.../EDR-IDLDocs/drafts/com/sun/module-ix.html | 78 +
.../EDR-IDLDocs/drafts/com/sun/star/module-ix.html | 84 +
.../sun/star/script/browse/BrowseNodeTypes.html | 145 ++
.../sun/star/script/browse/XBrowseNode-xref.html | 82 +
.../com/sun/star/script/browse/XBrowseNode.html | 283 +++
.../com/sun/star/script/browse/module-ix.html | 90 +
.../com/sun/star/script/framework/module-ix.html | 81 +
.../framework/security/XScriptSecurity-xref.html | 82 +
.../script/framework/security/XScriptSecurity.html | 158 ++
.../star/script/framework/security/module-ix.html | 82 +
.../framework/storage/ScriptStorage-xref.html | 64 +
.../script/framework/storage/ScriptStorage.html | 106 +
.../storage/ScriptStorageManager-xref.html | 74 +
.../framework/storage/ScriptStorageManager.html | 100 +
.../script/framework/storage/XScriptInfo-xref.html | 72 +
.../star/script/framework/storage/XScriptInfo.html | 384 ++++
.../framework/storage/XScriptInfoAccess-xref.html | 82 +
.../framework/storage/XScriptInfoAccess.html | 230 +++
.../storage/XScriptStorageExport-xref.html | 82 +
.../framework/storage/XScriptStorageExport.html | 126 ++
.../storage/XScriptStorageManager-xref.html | 82 +
.../framework/storage/XScriptStorageManager.html | 344 ++++
.../storage/XScriptStorageRefresh-xref.html | 82 +
.../framework/storage/XScriptStorageRefresh.html | 126 ++
.../star/script/framework/storage/module-ix.html | 179 ++
.../framework/storage/theScriptStorageManager.html | 73 +
.../drafts/com/sun/star/script/module-ix.html | 84 +
.../provider/LanguageScriptProvider-xref.html | 77 +
.../script/provider/LanguageScriptProvider.html | 86 +
.../script/provider/MasterScriptProvider-xref.html | 64 +
.../star/script/provider/MasterScriptProvider.html | 86 +
.../star/script/provider/ScriptProvider-xref.html | 79 +
.../sun/star/script/provider/ScriptProvider.html | 92 +
.../provider/ScriptProviderForBasic-xref.html | 64 +
.../script/provider/ScriptProviderForBasic.html | 86 +
.../provider/ScriptProviderForBeanShell-xref.html | 64 +
.../provider/ScriptProviderForBeanShell.html | 86 +
.../provider/ScriptProviderForJava-xref.html | 64 +
.../script/provider/ScriptProviderForJava.html | 86 +
.../provider/ScriptProviderForJavaScript-xref.html | 64 +
.../provider/ScriptProviderForJavaScript.html | 86 +
.../com/sun/star/script/provider/XScript-xref.html | 82 +
.../com/sun/star/script/provider/XScript.html | 179 ++
.../star/script/provider/XScriptContext-xref.html | 72 +
.../sun/star/script/provider/XScriptContext.html | 208 ++
.../star/script/provider/XScriptProvider-xref.html | 92 +
.../sun/star/script/provider/XScriptProvider.html | 142 ++
.../provider/XScriptProviderSupplier-xref.html | 72 +
.../script/provider/XScriptProviderSupplier.html | 127 ++
.../com/sun/star/script/provider/module-ix.html | 157 ++
.../scripting/EDR-IDLDocs/drafts/module-ix.html | 78 +
.../scripting/EDR-IDLDocs/index-files/index-1.html | 60 +
.../EDR-IDLDocs/index-files/index-10.html | 56 +
.../EDR-IDLDocs/index-files/index-11.html | 56 +
.../EDR-IDLDocs/index-files/index-12.html | 61 +
.../EDR-IDLDocs/index-files/index-13.html | 58 +
.../EDR-IDLDocs/index-files/index-14.html | 56 +
.../EDR-IDLDocs/index-files/index-15.html | 56 +
.../EDR-IDLDocs/index-files/index-16.html | 59 +
.../EDR-IDLDocs/index-files/index-17.html | 56 +
.../EDR-IDLDocs/index-files/index-18.html | 63 +
.../EDR-IDLDocs/index-files/index-19.html | 75 +
.../scripting/EDR-IDLDocs/index-files/index-2.html | 61 +
.../EDR-IDLDocs/index-files/index-20.html | 59 +
.../EDR-IDLDocs/index-files/index-21.html | 56 +
.../EDR-IDLDocs/index-files/index-22.html | 58 +
.../EDR-IDLDocs/index-files/index-23.html | 56 +
.../EDR-IDLDocs/index-files/index-24.html | 74 +
.../EDR-IDLDocs/index-files/index-25.html | 56 +
.../EDR-IDLDocs/index-files/index-26.html | 56 +
.../EDR-IDLDocs/index-files/index-27.html | 56 +
.../scripting/EDR-IDLDocs/index-files/index-3.html | 66 +
.../scripting/EDR-IDLDocs/index-files/index-4.html | 58 +
.../scripting/EDR-IDLDocs/index-files/index-5.html | 61 +
.../scripting/EDR-IDLDocs/index-files/index-6.html | 59 +
.../scripting/EDR-IDLDocs/index-files/index-7.html | 85 +
.../scripting/EDR-IDLDocs/index-files/index-8.html | 58 +
.../scripting/EDR-IDLDocs/index-files/index-9.html | 59 +
.../framework/scripting/EDR-IDLDocs/module-ix.html | 111 ++
content/framework/scripting/build-guide.html | 285 +++
content/framework/scripting/index.html | 287 +++
.../framework/scripting/netbeans-debugging.html | 37 +
.../framework/scripting/release-0.1/SmokeTest.html | 1115 +++++++++++
.../scripting/release-0.1/developer-guide.html | 267 +++
.../release-0.1/developer-release-features.html | 75 +
content/framework/scripting/release-0.1/faq.html | 162 ++
content/framework/scripting/release-0.1/index.html | 200 ++
.../scripting/release-0.1/install-guide.html | 211 ++
.../scripting/release-0.1/issues-list.html | 103 +
.../scripting/release-0.1/jedit-devguide.html | 369 ++++
.../scripting/release-0.1/netbeans-devguide.html | 214 ++
.../scripting/release-0.1/user-guide.html | 136 ++
.../scripting/release-0.1/whats-next.html | 161 ++
.../framework/scripting/release-0.2/SmokeTest.html | 928 +++++++++
.../scripting/release-0.2/build-guide.html | 472 +++++
.../release-0.2/commandline-devguide.html | 212 ++
.../scripting/release-0.2/developer-guide.html | 294 +++
.../release-0.2/developer-release-features.html | 109 +
content/framework/scripting/release-0.2/faq.html | 91 +
content/framework/scripting/release-0.2/index.html | 323 +++
.../scripting/release-0.2/install-guide.html | 160 ++
.../scripting/release-0.2/javascript-devguide.html | 152 ++
.../scripting/release-0.2/netbeans-devguide.html | 244 +++
.../scripting/release-0.2/release-notes.html | 140 ++
.../scripting/release-0.2/runtime-howto.html | 1981 +++++++++++++++++++
.../scripting/release-0.2/uninstall-guide.html | 123 ++
.../scripting/release-0.2/user-guide.html | 497 +++++
.../scripting/release-0.2/whats-next.html | 44 +
.../framework/scripting/release-0.3/SmokeTest.html | 928 +++++++++
.../scripting/release-0.3/build-guide.html | 573 ++++++
.../release-0.3/commandline-devguide.html | 178 ++
.../scripting/release-0.3/developer-guide.html | 202 ++
.../release-0.3/developer-release-features.html | 123 ++
content/framework/scripting/release-0.3/faq.html | 91 +
content/framework/scripting/release-0.3/index.html | 238 +++
.../scripting/release-0.3/install-guide.html | 207 ++
.../scripting/release-0.3/netbeans-devguide.html | 244 +++
.../scripting/release-0.3/release-notes.html | 155 ++
.../scripting/release-0.3/runtime-howto.html | 2072 ++++++++++++++++++++
.../scripting/release-0.3/uninstall-guide.html | 126 ++
.../scripting/release-0.3/user-guide.html | 609 ++++++
.../scripting/release-0.3/whats-next.html | 44 +
.../framework/scripting/scriptingf1/SFArch.html | 1509 ++++++++++++++
.../scriptingf1/commandline-devguide.html | 185 ++
.../scripting/scriptingf1/developer-guide.html | 302 +++
content/framework/scripting/scriptingf1/faq.html | 97 +
content/framework/scripting/scriptingf1/index.html | 193 ++
.../scripting/scriptingf1/netbeans-devguide.html | 242 +++
.../scripting/scriptingf1/user-guide.html | 478 +++++
.../scripting/scriptingf1/whats-next.html | 58 +
content/framework/scripting/testindex.html | 193 ++
.../framework/scripting/utilities-download.html | 236 +++
160 files changed, 33332 insertions(+)
diff --git a/content/framework/binfilter.html b/content/framework/binfilter.html
new file mode 100755
index 0000000..1ef4a79
--- /dev/null
+++ b/content/framework/binfilter.html
@@ -0,0 +1,82 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <meta http-equiv="content-type"
+ content="text/html; charset=ISO-8859-1">
+ <title>binfilter</title>
+</head>
+<body>
+<h1>binfilter project<br>
+</h1>
+(short form of binary filters)<br>
+<h2>Summary:</h2>
+Before implementing the OpenOffice XML formats the main file
+format was the binary format for all applications. In OOo 1.0 and OOo
+1.1 we have both file formats included and did change the default
+format to XML. The binary formats exist as long as the applications
+exist. They were developed straightforward and run through various bug
+fixing/extension cycles. When starting implementing that filters it was
+straightforward to directly stream in and out the object model data.
+This was done mostly in implementing streaming operators at/for that
+classes defining the object model.<br>
+<p>
+Today, after that fixing/extension cycles, that format has several
+problems:<br>
+Due to extensions/changes (which is possible in small amounts in the
+binary files but always needs to stay readable for older versions,
+including previously made errors) the format is no longer
+straightforward. In many parts huge transitions to older object model
+data are done at saving and transition to newer data structures at
+loading.<br>
+The biggest problem is the streaming approach itself. This prevents us
+from doing necessary bigger changes at the application cores. It is
+possible to add new data to the binary format in a compatible manner,
+but at least at writing the corresponding older document model data
+needs to be created and written compatible for older versions. This
+also leads to having much data twice in the files. It is not possible
+to change the structure between the data chunks (which are the core
+classes normally) at all.<br>
+To get rid of that not well structured approach, the XML formats were
+developed and introduced as a first step. Now, in a second step, we
+want to break that document model core blockage by removing the old
+binary formats from the cores. Thus, a OOo 1.1 should be the last
+version containing XML and the binary filters. This will allow us to do
+a lot of more than necessary changes in the application cores for
+future versions.<br>
+This opens the problem that for later versions we still want to offer
+the user the possibility to read/write our 'old' binary file formats.
+There are different possibilities to do that which will now be shown.</p>
+<p>Thus, the targets of this project are:</p>
+<ul>
+ <li>Remove the binary filters from the document model cores</li>
+</ul>
+<ul>
+ <li>
+ <p> Find and supply a possibility for the users of OOo after 1.1
+to work with the 'old' binary file formats. This is called Filter
+Migration</p>
+ </li>
+</ul>
+The first point is obvoiusly not a big problem, but the 2nd one is.
+This new project thus deals with solvong the second point.<br>
+After the evaluation of different possibilities of Filter Migration it
+seems to be the safest and simplest to take a copy of the modules
+containing the binary filters and 'strip' everything that is not
+needed. Thus, the remaining modules will still contain the old data
+model cores, parts of the API implementations and the XML
+implementations. It is simplest to use XML as exchange format since we
+have a way to read/write XML with the current application cores and XML
+is well defined and will stay compatible to later OOo versions.<br>
+<br>
+<h2>Project Description:</h2>
+This OOo project covers the Filter Stripping approach to enable us
+to remove the outdated binary filters contained in OOo. Main reason is
+that the old filters are blocking future development. Since in later
+OOo versions there needs to be a possibiulity offered to still work
+with file formats from OOo 1.0 and OOo 1.1, this project will develop a
+solution for that. The solution will provide 'stripped' (reduced)
+versions of the core modules which keep the binary filter functionality
+and will be able to import/export from there to XML. Thus we will
+derive isolated, reduced filter modules for the old binary file formats.<br>
+</body>
+</html>
diff --git a/content/framework/documentation/filters/example.html b/content/framework/documentation/filters/example.html
new file mode 100644
index 0000000..d8af4c8
--- /dev/null
+++ b/content/framework/documentation/filters/example.html
@@ -0,0 +1,526 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE>Type Detection - Examples</TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="CREATED" CONTENT="20010222;14370867">
+ <META NAME="CHANGEDBY" CONTENT="Mathias Bauer">
+ <META NAME="CHANGED" CONTENT="20010411;13383007">
+</head>
+<body>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0 STYLE="page-break-before: always">
+ <TR>
+ <TD>
+ <P ALIGN=LEFT><A HREF="services.html"><<</A></P>
+ </TD>
+ <TD>
+ <P ALIGN=CENTER><BR>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=RIGHT><A HREF="reference.html">>></A></P>
+ </TD>
+ </TR>
+</TABLE>
+<HR SIZE=3 COLOR="#000000">
+<CENTER>
+ <TABLE WIDTH=1289 BORDER=0 CELLPADDING=2 CELLSPACING=0>
+ <COL WIDTH=1285>
+ <TR>
+ <TD WIDTH=1285>
+ <P><FONT SIZE=5>Examples</FONT>
+ </P>
+ <P>The following examples are to illustrate the use of the
+ services involved.</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">Creation of the necessary
+ objects
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#flat_detection">Flat</A>
+ or <A HREF="#deep_detection">deep</A> detection of a type on the
+ basis of different parameters
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#search_loader">Search
+ and use of a FrameLoader object</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#search_filter">Search
+ and use of a Filter object to import a document</A> (Export
+ similar!)
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#read_filtercfg">Reading
+ of the entire filters configuration</A> (Loader/Types similar!
+ ... however at different services!)
+ </P>
+ <LI><P><A HREF="#register_filter">Register a new filter</A>
+ (Loader/Types similar!)
+ </P>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=1285>
+ <P><A NAME="includes"></A><BR><FONT SIZE=4>Includes, Declarations
+ ...</FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#ffffcc">
+ <TD WIDTH=1285>
+ <PRE>//*****************************************************************************************************************
+//includes interfaces
+//*****************************************************************************************************************
+#ifndef _COM_SUN_STAR_LANG_XMULTISERVICEFACTORY_HPP_
+#include < com/sun/star/lang/XMultiServiceFactory.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_DOCUMENT_XTYPEDETECTION_HPP_
+#include < com/sun/star/document/XTypeDetection.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_FRAME_XFRAMELOADER_HPP_
+#include < com/sun/star/frame/XFrameLoader.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_FRAME_XSYNCHRONOUSFRAMELOADER_HPP_
+#include < com/sun/star/frame/XSynchronousFrameLoader.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_DOCUMENT_XFILTER_HPP_
+#include < com/sun/star/document/XFilter.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_DOCUMENT_XIMPORTER_HPP_
+#include < com/sun/star/document/XImporter.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_LANG_XCOMPONENT_HPP_
+#include < com/sun/star/lang/XComponent.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_BEANS_XPROPERTYSET_HPP_
+#include < com/sun/star/beans/XPropertySet.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_CONTAINER_XNAMEACCESS_HPP_
+#include < com/sun/star/container/XNameAccess.hpp>
+#endif
+
+#ifndef _COM_SUN_STAR_CONTAINER_XNAMECONTAINER_HPP_
+#include < com/sun/star/container/XNameContainer.hpp>
+#endif
+
+//*****************************************************************************************************************
+// uno interfaces
+//*****************************************************************************************************************
+#ifndef _COM_SUN_STAR_UNO_REFERENCE_H_
+#include < com/sun/star/uno/Reference.h>
+#endif
+
+#ifndef _COM_SUN_STAR_UNO_SEQUENCE_H_
+#include < com/sun/star/uno/Sequence.h>
+#endif
+
+#ifndef _COM_SUN_STAR_UNO_ANY_H_
+#include < com/sun/star/uno/Any.h>
+#endif
+
+//*****************************************************************************************************************
+// others
+//*****************************************************************************************************************
+#ifndef _COMPHELPER_PROCESSFACTORY_HXX_
+#include < comphelper/processfactory.hxx> // for getProcessServiceFactory()
+#endif
+
+//*****************************************************************************************************************
+// namespaces
+//*****************************************************************************************************************
+using namespace ::com::sun::star::uno ;
+using namespace ::com::sun::star::lang ;
+using namespace ::com::sun::star::container ;
+using namespace ::rtl ;
+using namespace ::comphelper ;
+
+//*****************************************************************************************************************
+// macros
+//*****************************************************************************************************************
+#define ASCII( SSTRING ) OUString(RTL_CONSTASCII_USTRINGPARAM( SSTRING )) // convert an ascii-value to unicode</PRE>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=1285>
+ <P><A NAME="flat_detection"></A><BR><FONT SIZE=4>Flat Detection</FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#ffffcc">
+ <TD WIDTH=1285>
+ <PRE>void example_flatDetection()
+{
+ // Create UNO-service for type detection.
+ // Use global servicemanager as factory and cast return value to right interface.
+ Reference< XTypeDetection > xTypeDetection( getProcessServiceFactory()->createInstance( ASCII("com.sun.star.document.TypeDetection") ), UNO_QUERY );
+
+ // a) Make flat detection by URL only.
+ OUString sInternalTypeName;
+ sInternalTypeName = xTypeDetection->queryTypeByURL( ASCII("file:///c|/temp/test.txt") );
+
+ // b) Make flat detection by URL and an additional search parameter.
+ Sequence< PropertyValue > lDescriptor( 2 );
+
+ lDescriptor[0].Name = ASCII("FileName" );
+ lDescriptor[0].Value <<= ASCII("file:///c|/temp/test.txt");
+
+ lDescriptor[1].Name = ASCII("ContentType" );
+ lDescriptor[1].Value <<= ASCII("text/plain" );
+
+ sal_Bool bDeep = sal_False;
+
+ // !!! These can add or change informations of given descriptor !!!
+ sInternalTypeName = xTypeDetection->queryTypeByDescriptor( lDescriptor, bDeep );
+}</PRE>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=1285>
+ <P><A NAME="deep_detection"></A><BR><FONT SIZE=4>Deep Detection</FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#ffffcc">
+ <TD WIDTH=1285>
+ <PRE>void example_deepDetection()
+{
+ // Create UNO-service for type detection.
+ // Use global servicemanager as factory and cast return value to right interface.
+ Reference< XTypeDetection > xTypeDetection( getProcessServiceFactory()->createInstance( ASCII("com.sun.star.document.TypeDetection") ), UNO_QUERY );
+
+ // Make deep detection by URL and an additional search parameter.
+ Sequence< PropertyValue > lDescriptor( 2 );
+
+ lDescriptor[0].Name = ASCII("FileName" );
+ lDescriptor[0].Value <<= ASCII("file:///c|/temp/test.txt");
+
+ lDescriptor[1].Name = ASCII("ContentType" );
+ lDescriptor[1].Value <<= ASCII("text/plain" );
+
+ sal_Bool bDeep = sal_True;
+
+ // !!! These can add or change informations of given descriptor !!!
+ sInternalTypeName = xTypeDetection->queryTypeByDescriptor( lDescriptor, bDeep );
+}</PRE>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=1285>
+ <P><A NAME="search_loader"></A><BR><FONT SIZE=4>Search for and
+ Use of a FrameLoader Object</FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#ffffcc">
+ <TD WIDTH=1285>
+ <PRE>void example_loadDocument()
+{
+ // Create UNO-services for type detection and loading document.
+ // Use global servicemanager as factory and cast return value to right interface.
+ Reference< XTypeDetection > xTypeDetection( getProcessServiceFactory()->createInstance( ASCII("com.sun.star.document.TypeDetection" ) ), UNO_QUERY );
+ Reference< XMultiServiceFactory > xLoaderFactory( getProcessServiceFactory()->createInstance( ASCII("com.sun.star.frame.FrameLoaderFactory") ), UNO_QUERY );
+
+ // Make deep detection by URL only.
+ Sequence< PropertyValue > lDescriptor( 1 );
+
+ lDescriptor[0].Name = ASCII("FileName" );
+ lDescriptor[0].Value <<= ASCII("file:///c|/temp/test.txt");
+
+ sal_Bool bDeep = sal_True;
+
+ sInternalTypeName = xTypeDetection->queryTypeByDescriptor( lDescriptor, bDeep );
+
+ // Search registered loader and create it.
+ Reference< XInterface > xLoaderInterface( xLoaderFactory->createInstance( sInternalTypeName ), UNO_QUERY );
+
+ // Check for supported load mechanism by this implementation? [async/sync]
+ Reference< XSynchronousFrameLoader > xSyncLoader ( xLoaderInterface, UNO_QUERY );
+ Reference< XFrameLoader > xAsyncLoader( xLoaderInterface, UNO_QUERY );
+
+ // Don't forget to create a new target frame to load document in it!
+ // Use findFrame() or queryDispatch() mechanism to do that.
+ Reference< XFrame > xTarget = ...;
+
+ if( xSyncLoader.is() == sal_True )
+ {
+ sal_Bool bState = xSyncLoader->load( lDescriptor, xTarget );
+ }
+ else
+ if( xAsyncLoader.is() == sal_True )
+ {
+ xAsyncLoader->load( xTarget ,
+ ASCII("file:///c|/temp/test.txt"),
+ lDescriptor ,
+ this ); // We must support XLoadEventListener interface to get information about succesful loading!
+ }
+}</PRE>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=1285>
+ <P><A NAME="search_filter"></A><BR><FONT SIZE=4>Search for and
+ Use of a Filter Object</FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#ffffcc">
+ <TD WIDTH=1285>
+ <PRE>void example_filterDocument()
+{
+ // Create UNO-services for type detection and loading document.
+ // Use global servicemanager as factory and cast return value to right interface.
+ Reference< XTypeDetection > xTypeDetection( getProcessServiceFactory()->createInstance( ASCII("com.sun.star.document.TypeDetection") ), UNO_QUERY );
+ Reference< XMultiServiceFactory > xFilterFactory( getProcessServiceFactory()->createInstance( ASCII("com.sun.star.document.FilterFactory") ), UNO_QUERY );
+
+ // Make deep detection by URL only.
+ Sequence< PropertyValue > lDescriptor( 1 );
+
+ lDescriptor[0].Name = ASCII("FileName" );
+ lDescriptor[0].Value <<= ASCII("file:///c|/temp/test.txt");
+
+ sal_Bool bDeep = sal_True;
+
+ sInternalTypeName = xTypeDetection->queryTypeByDescriptor( lDescriptor, bDeep );
+
+ // Search registered filter and create it.
+ // We will use it as an import filter here! cast it to right interface ...
+ Reference< XFilter > xFilter ( xFilterFactory->createInstance( sInternalTypeName ), UNO_QUERY );
+ Reference< XImporter > xImportFilter( xFilter , UNO_QUERY );
+
+ // We must create the document service which is used by these filter.
+ // These information is available as a property of created filter!
+ Reference< XPropertySet > xFilterProperties( xFilter, UNO_QUERY );
+ OUString sDocumentService;
+ xFilterProperties->getPropertyValue( ASCII("DocumentService") ) >>= sDocumentService;
+ Reference< XComponent > xDocument( getProcessServiceFactory()->createInstance( sDocumentService ), UNO_QUERY );
+
+ // Set target document service at import filter
+ // and start filter operation.
+ // (xImportFilter and xFilter are the same objects - but different interfaces!)
+ xImportFilter->setTargetDocument( xDocument );
+ sal_Bool bState = xFilter->filter( lDescriptor );
+}</PRE>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=1285>
+ <P><A NAME="read_filtercfg"></A><BR><FONT SIZE=4>Reading the
+ Filter Configuration</FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#ffffcc">
+ <TD WIDTH=1285>
+ <PRE>void example_readFilterCFG()
+{
+ // Create UNO-services FilterFactory - support name container interface too!
+ // Use global servicemanager as factory and cast return value to right interface.
+ Reference< XNameAccess > xFilterContainer( getProcessServiceFactory()->createInstance( ASCII("com.sun.star.document.FilterFactory") ), UNO_QUERY );
+
+ // Step over all registered filters.
+ Sequence< OUString > lFilterNames = xFilterContainer->getElementNames();
+ sal_Int32 nNameCount = lFilterNames.getLength() ;
+
+ for( sal_Int32 nName = 0; nName < nNameCount; ++nName )
+ {
+ // Get all properties of current filter as Sequence< PropertyValue >.
+ // Step over all these properties and copy values to local variables.
+ Sequence< PropertyValue > lProperties;
+ xFilterContainer->getByName( lFilterNames[ nName ] ) >>= lProperties;
+
+ OUString sType ;
+ OUString sUIName ;
+ OUString sDocumentService ;
+ OUString sFilterService ;
+ sal_Int32 nFlags ;
+ Sequence< OUString > lUserData ;
+ sal_Int32 nFileFormatVersion ;
+ OUString sTemplateName ;
+
+ sal_Int32 nPropertyCount = lProperties.getLength();
+ for( sal_Int32 nProperty = 0; nProperty < nPropertyCount; ++nProperty )
+ {
+ if( lProperties[ nProperty ].Name == ASCII("Type") )
+ lProperties[ nProperty ].Value >>= sType;
+ else
+ if( lProperties[ nProperty ].Name == ASCII("UIName") )
+ lProperties[ nProperty ].Value >>= sUIName;
+ else
+ if( lProperties[ nProperty ].Name == ASCII("DocumentService") )
+ lProperties[ nProperty ].Value >>= sDocumentService;
+ else
+ if( lProperties[ nProperty ].Name == ASCII("FilterService") )
+ lProperties[ nProperty ].Value >>= sFilterService;
+ else
+ if( lProperties[ nProperty ].Name == ASCII("Flags") )
+ lProperties[ nProperty ].Value >>= nFlags;
+ else
+ if( lProperties[ nProperty ].Name == ASCII("UserData") )
+ lProperties[ nProperty ].Value >>= lUserData;
+ else
+ if( lProperties[ nProperty ].Name == ASCII("FileFormatVersion") )
+ lProperties[ nProperty ].Value >>= nFileFormatVersion;
+ else
+ if( lProperties[ nProperty ].Name == ASCII("TemplateName") )
+ lProperties[ nProperty ].Value >>= sTemplateName;
+ }
+ }
+}</PRE>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=1285>
+ <P><A NAME="register_filter"></A><BR><FONT SIZE=4>Registering a
+ New Filter</FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#ffffcc">
+ <TD WIDTH=1285>
+ <PRE>void example_registerFilter()
+{
+ // Create UNO-services FilterFactory - support name container interface too!
+ // Use global servicemanager as factory and cast return value to right interface.
+ Reference< XNameContainer > xFilterContainer( getProcessServiceFactory()->createInstance( ASCII("com.sun.star.document.FilterFactory") ), UNO_QUERY );
+
+ // Define all properties and values of new filter.
+ OUString sType = ASCII("type_to_register_for" );
+ OUString sUIName = ASCII("Own Filter" );
+ OUString sDocumentService = ASCII("com.my.company.DocumentService");
+ OUString sFilterService = ASCII("com.my.company.FilterService" );
+ sal_Int32 nFlags = 0 ;
+ sal_Int32 nFileFormatVersion = 0 ;
+ OUString sTemplateName = OUString() ;
+ Sequence< OUString > lUserData = Sequence< OUString >() ;
+
+ // Pack it into a Sequence< PropertyValue > to support format of interface method.
+ // Order of elements in sequence isnt important ... We differ it by names only!
+ // You don't must give us all properties - we use default values for missing ones.
+ Sequence< PropertyValue > lProperties[8];
+
+ //--------------------------------------------------------------------------
+ lProperties[0].Name = ASCII("Type") ;
+ lProperties[0].Value <<= sType ;
+
+ /*ATTENTION
+ Register a human readable filtername for current the locale by using the
+ property „UIName“ or use the property "UINames" to set it for different
+ locales.
+ In the current build using „UINames“ does not work due to problems
+ in the configuration service, so currently always use „UIName“ !
+ */
+
+ //--------------------------------------------------------------------------
+ // set UIName for current locale
+ lProperties[1].Name = ASCII("UIName") ;
+ lProperties[1].Value <<= sUIName ;
+
+ //--------------------------------------------------------------------------
+ // set UINames for different locales – but not in current build, see above
+ // - name of property is an identifier for the locale
+ // - value is the value for these locale
+ // Sequence< PropertyValue > lUINames[2];
+ // lUINames[0].Name = ASCII("de-DE" );
+ // lUINames[0].Value <<= ASCII("Mein UIName");
+ // lUINames[1].Name = ASCII("en-US" );
+ // lUINames[1].Value <<= ASCII("my UIName" );
+ // lProperties[1].Name = ASCII("UINames");
+ // lProperties[1].Value <<= lUINames;
+
+ //--------------------------------------------------------------------------
+ lProperties[2].Name = ASCII("DocumentService") ;
+ lProperties[2].Value <<= sDocumentService ;
+
+ //--------------------------------------------------------------------------
+ lProperties[3].Name = ASCII("FilterService") ;
+ lProperties[3].Value <<= sFilterService ;
+
+ //--------------------------------------------------------------------------
+ lProperties[4].Name = ASCII("Flags") ;
+ lProperties[4].Value <<= nFlags ;
+
+ //--------------------------------------------------------------------------
+ lProperties[5].Name = ASCII("UserData") ;
+ lProperties[5].Value <<= lUserData ;
+
+ //--------------------------------------------------------------------------
+ lProperties[6].Name = ASCII("FileFormatVersion");
+ lProperties[6].Value <<= nFileFormatVersion ;
+
+ //--------------------------------------------------------------------------
+ lProperties[7].Name = ASCII("TemplateName") ;
+ lProperties[7].Value <<= sTemplateName ;
+
+ //--------------------------------------------------------------------------
+ // Pack Sequence< PropertyValue > into an any and insert these new filter.
+ // Give us a filter name too ... but check for already existing ones before!
+ // Otherwise follow call throw an ElementExistException!
+ // (use XNameAccess to do that)
+ Any aPropertySet;
+ aPropertySet <<= lProperties;
+ xFilterContainer->insertByName( ASCII("my_own_Filter"), aPropertySet );
+}</PRE>
+ </TD>
+ </TR>
+ </TABLE>
+</CENTER>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P ALIGN=LEFT><A HREF="services.html"><<</A></P>
+ </TD>
+ <TD>
+ <P ALIGN=CENTER><BR>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=RIGHT><A HREF="reference.html">>></A></P>
+ </TD>
+ </TR>
+</TABLE>
+<HR SIZE=3 COLOR="#000000">
+<TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">author</FONT></FONT> </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P><FONT SIZE=2><FONT FACE="Arial"> Andreas
+ Schlüns</FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">email</FONT></FONT> </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P> <A HREF="mailto:andreas.schluens@germany.sun.com"><FONT SIZE=2><FONT FACE="Arial">andreas.schluens@germany.sun.com</FONT></FONT></A>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">last modification</FONT></FONT>
+ </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P><FONT SIZE=2><FONT FACE="Arial"> 19.11.2001</FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+</TABLE>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/documentation/filters/index.html b/content/framework/documentation/filters/index.html
new file mode 100644
index 0000000..d63387a
--- /dev/null
+++ b/content/framework/documentation/filters/index.html
@@ -0,0 +1,486 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE>Home Page</TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="CREATED" CONTENT="20010222;14495345">
+ <META NAME="CHANGEDBY" CONTENT="Mathias Bauer">
+ <META NAME="CHANGED" CONTENT="20010411;13361546">
+ <STYLE>
+ <!--
+ TD P { color: #000000 }
+ H1 { color: #000000 }
+ P { color: #000000 }
+ -->
+ </STYLE>
+</head>
+<body TEXT="#000000" BGCOLOR="#ffffff">
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0 STYLE="page-break-before: always">
+ <TR>
+ <TD>
+ <P ALIGN=LEFT><BR>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=CENTER><BR>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=RIGHT><A HREF="services.html">>></A></P>
+ </TD>
+ </TR>
+</TABLE>
+<HR SIZE=3 COLOR="#000000">
+<CENTER>
+ <TABLE WIDTH=684 BORDER=0 CELLPADDING=2 CELLSPACING=0>
+ <COL WIDTH=13>
+ <COL WIDTH=355>
+ <COL WIDTH=286>
+ <COL WIDTH=14>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <H1>Type Detection</H1>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <P><FONT SIZE=5>General</FONT> <BR><BR>In version src619, the old
+ filter and type detection has been moved from "install.ini"
+ to the new configuration management. To do this, the information
+ was translated into XML format while the principle structure was
+ modified. Now you can use the complete process of the loading,
+ displaying or storing documents as a modular system. It functions
+ generically in many components and can easily be adapted to your
+ needs through the addition of your own modules or the removal of
+ others.</P>
+ <P><FONT COLOR="#ff0000">Note: <BR>The processes described in the
+ following sections are still in the development phase and may be
+ subject to change. We will update this site in the event of
+ changes. </FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <P><BR><FONT SIZE=5>Configuration</FONT> <BR><BR>The new
+ structure of the configuration is illustrated by the following
+ figure:
+ </P>
+ <P><IMG SRC="configstructure.gif" NAME="Graphic1" ALT="configuration structure" ALIGN=LEFT WIDTH=680 HEIGHT=605 BORDER=0><BR>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <P>As shown on the left, the file consists of four lists (called
+ Sets) and two DEFAULT entries. The list items are described by
+ the structures shown on the right to which the arrows point.</P>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <HR SIZE=1 COLOR="#cccccc">
+ <UL>
+ <LI><P><A NAME="description_Type"></A>The most important
+ component of the configuration is the <STRONG>Type</STRONG>.<BR>It
+ describes the type of contents which can be represented in the
+ Office. This is usually a document type. However, the results of
+ active contents (e.g. macros) or DB contents can also be
+ described here.</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">The <STRONG>internal name</STRONG>
+ of a type must be unique and is also used as list entry. It
+ cannot contain any special characters. For example, a valid
+ name is "<EM>my_own_type_for_example_files</EM>".</P>
+ <LI><P STYLE="margin-bottom: 0cm">The <STRONG>UIName</STRONG>
+ is used to display UI names and is localized. That means you
+ can choose an assignment between value and language for it.
+ Thus, support of CJK versions is possible. All UniCode
+ characters are permitted here.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><STRONG>MediaType</STRONG>
+ describes the MIME type of the contents. The regulations of the
+ XML format are the reason for the separation into MediaType and
+ "internal type name". Since the latter is used as an
+ entry in the type list – and thus corresponds to one XML
+ tag - not all special characters can be used. As a by-product
+ of this, the internal names can be altered at any time without
+ effecting the process as such.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">The <STRONG>ClipboardFormat</STRONG>
+ is a unique description of this type for use in clipboards.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">Important components of a
+ type are the <STRONG>URLPatterns</STRONG>. They enable the
+ support of your own URL pattern.<BR>e.g. in the Office:
+ "private:factory/swriter" for opening an empty writer
+ document
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">Most important, however, are
+ the <STRONG>Extensions</STRONG>. They make the assignment of a
+ type to a URL possible. In 90% of the cases, the flat detection
+ depends on them alone.</P>
+ <LI><P STYLE="margin-bottom: 0cm">Since file endings cannot
+ always be assigned to a particular type, the <STRONG>Preferred</STRONG>
+ flag was introduced. It indicates the preferred type for a
+ group of types with the same extensions. Otherwise, the first
+ match is the one that will be used.</P>
+ <LI><P>Finally, one type can also be assigned an icon. To do
+ this, the <STRONG>DocumentIconID</STRONG> is used as reference
+ to a resource.
+ </P>
+ </UL>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <P><BR><BR>
+ </P>
+ <P>Especially interesting is the possibility of <STRONG><SPAN STYLE="font-weight: medium">registering
+ modules, <STRONG><SPAN STYLE="font-weight: medium">suitable for a
+ type</SPAN></STRONG>, which are capable of taking over various
+ tasks. The </SPAN></STRONG>"<STRONG>Filters<STRONG>/",
+ "<STRONG>DetectServices</STRONG>" and "<STRONG>FrameLoaders</STRONG>"
+ <SPAN STYLE="font-weight: medium">lists were created for this
+ purpose.</SPAN></STRONG></STRONG></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <HR SIZE=1 COLOR="#cccccc">
+ <UL>
+ <LI><P><A NAME="description_DetectService"></A>What are
+ <STRONG>DetectServices</STRONG>?
+ </P>
+ <P>Due to the registered types, flat detection is already
+ possible, i.e. the assignment of types (e.g. to a URL) only on
+ the basis of configuration data. If, however, you imagine
+ special cases (e.g. modifying the file extension of a Writer
+ file from .sdw to .doc), it quickly becomes clear that you
+ cannot always get a correct result with flat detection. To be
+ certain to get correct results, you need deep detection, i.e.
+ the file itself has to be examined. And that is exactly the
+ function of DetectServices. They get all the information
+ collected so far on a document and then decide which type to
+ assign it to. In the new modular model, such a detector is meant
+ as UNO service which registers itself in the Office and is
+ requested by the generic type detection if necessary. Therefore
+ you need two pieces of information:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">The <STRONG>ServiceName -</STRONG>
+ This must be a valid UNO service name. It is also an entry in
+ the corresponding configuration list. <BR>Example:
+ "<EM>com.company.devision.DetectService</EM>"
+ </P>
+ <LI><P>A list of <STRONG>Types</STRONG> able to be recognized
+ by this service - You can also implement and register detectors
+ for groups of types.
+ </P>
+ </UL>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <HR SIZE=1 COLOR="#cccccc">
+ <UL>
+ <LI><P>What are <STRONG>FrameLoaders</STRONG>?
+ </P>
+ <P>FrameLoaders are also UNO services, but ones that are
+ supposed to "load" a detected type. A visual component
+ is expected as the result. The component can be
+ com.sun.star.awt.XWindow or, optionally, a view component
+ com.sun.star.frame.XController.
+ </P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">The <STRONG>UIName</STRONG>
+ permits a localized display in selection dialogs.
+ </P>
+ <LI><P>In this case as well, the list of <STRONG>Types</STRONG>
+ corresponds to the registration as possible loader for groups
+ of types.
+ </P>
+ </UL>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <HR SIZE=1 COLOR="#cccccc">
+ <UL>
+ <LI><P>What are <STRONG>Filters</STRONG>?
+ </P>
+ <P>These objects also represent a service. Their function is to
+ import or export the contents of a type into a component.
+ Accordingly, import filters are differentiated from export
+ filters. The component must implement the
+ com.sun.star.lan.XComponent interface. Further interfaces are
+ determined by the respective document service. The use of a
+ filter usually comes from a loader.
+ </P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">The <STRONG>Installed</STRONG>
+ flag indicates the installation status of a filter. A filter is
+ generally registered equally for all users. But even in a
+ network installation you should be able to deactivate this for
+ certain groups or single users.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">Even a filter should be able
+ to show a localized <STRONG>UIName</STRONG> in selection
+ dialogs.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">A filter must register itself
+ for a <STRONG>Type <SPAN STYLE="font-weight: medium">that i</SPAN></STRONG>t
+ can edit. Multiple assignments are not possible.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">The <STRONG>DocumentService</STRONG>
+ describes the component on which the filter operates. Depending
+ upon the use, this is seen either as output or goal of the
+ filter process. A UNO service name is expected.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">The <STRONG>FilterService</STRONG>
+ is the real UNO service name of the filter implementation.
+ </P>
+ <LI><P>The <STRONG>Flags</STRONG> describe the sort of filter.
+ This is where, among other things, the organization into import
+ and export filters takes place. <BR><FONT COLOR="#aa0000">Note:
+ External filters must set the ThirdParty flag in order to be
+ detected <FONT COLOR="#aa0000">as such</FONT>!</FONT>
+ <BR>Supported flags are:
+ </P>
+ </UL>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD ROWSPAN=19 WIDTH=13 VALIGN=TOP></TD>
+ <TD WIDTH=355>
+ <P>Import</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000001 <SUB>h</SUB></P>
+ </TD>
+ <TD ROWSPAN=19 WIDTH=14 VALIGN=TOP></TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Export</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000002 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Template</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000004 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Internal</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000008 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>TemplatePath</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000010 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Own</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000020 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Alien</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000040 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>UsesOptions</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000080 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Default</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00000100 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>NotInFileDialog</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00001000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>NotInChooser</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00002000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Asynchron</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00004000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Readonly</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00010000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>NotInstalled</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00020000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>ConsultService</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00040000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>ThirdParty</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00080000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Packed</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00100000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>SilentExport</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x00200000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=355>
+ <P>Preferred</P>
+ </TD>
+ <TD WIDTH=286>
+ <P> 0x10000000 <SUB>h</SUB></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD COLSPAN=4 WIDTH=680>
+ <UL>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">Some filters need to be able
+ to store more configuration data than usual. This can be
+ realized with the <STRONG>UserData</STRONG> entry. The format
+ of the string list is not restricted in any way.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><STRONG>FileFormatVersion</STRONG>
+ indicates a certain version number of a document which can be
+ edited by this filter.
+ </P>
+ <LI><P>A <STRONG>TemplateName</STRONG> ...
+ </P>
+ </UL>
+ </UL>
+ </TD>
+ </TR>
+ </TABLE>
+</CENTER>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P ALIGN=LEFT><BR>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=CENTER><BR>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=RIGHT><A HREF="services.html">>></A>
+ </P>
+ </TD>
+ </TR>
+</TABLE>
+<HR SIZE=3 COLOR="#000000">
+<TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">author</FONT></FONT> </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P><FONT SIZE=2><FONT FACE="Arial"> Andreas
+ Schlüns</FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">email</FONT></FONT> </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P> <A HREF="mailto:andreas.schluens@germany.sun.com"><FONT SIZE=2><FONT FACE="Arial">andreas.schluens@germany.sun.com</FONT></FONT></A>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">last modification</FONT></FONT>
+ </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P><FONT SIZE=2><FONT FACE="Arial"> 11.04.2001</FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+</TABLE>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/documentation/filters/reference.html b/content/framework/documentation/filters/reference.html
new file mode 100644
index 0000000..19e99d1
--- /dev/null
+++ b/content/framework/documentation/filters/reference.html
@@ -0,0 +1,109 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE>Home Page</TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="CREATED" CONTENT="20010411;12335951">
+ <META NAME="CHANGEDBY" CONTENT="Mathias Bauer">
+ <META NAME="CHANGED" CONTENT="20010411;13390702">
+ <STYLE>
+ <!--
+ TD P { color: #000000 }
+ P { color: #000000 }
+ -->
+ </STYLE>
+</head>
+<body TEXT="#000000" BGCOLOR="#ffffff">
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0 STYLE="page-break-before: always">
+ <TR>
+ <TD>
+ <P ALIGN=LEFT><A HREF="example.html"><<</A></P>
+ </TD>
+ <TD>
+ <P ALIGN=CENTER><BR>
+ </P>
+ </TD>
+ </TR>
+</TABLE>
+<HR SIZE=3 COLOR="#000000">
+<CENTER>
+ <TABLE WIDTH=70% BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P><FONT SIZE=5>Referenzen</FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">UNO base concepts<BR>
+ <A HREF="http://udk.openoffice.org/common/man/uno.html">"The
+ base concepts of Universal Network Objects"</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">UNO components<BR>
+ <A HREF="http://udk.openoffice.org/cpp/man/component_tutorial.html">"Writing
+ a simple UNO component in C++"</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">Filter realization<BR>
+ <A HREF="http://xml.openoffice.org/filter/">"Filters using
+ the XML based file format"</A>
+ </P>
+ <LI><P>Configuration<BR> <A HREF="http://dba.openoffice.org/">Homepage</A>
+ </P>
+ </UL>
+ </TD>
+ </TR>
+ </TABLE>
+</CENTER>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P ALIGN=LEFT><A HREF="example.html"><<</A></P>
+ </TD>
+ <TD>
+ <P ALIGN=CENTER><BR>
+ </P>
+ </TD>
+ </TR>
+</TABLE>
+<HR SIZE=3 COLOR="#000000">
+<TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">author</FONT></FONT> </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P><FONT SIZE=2><FONT FACE="Arial"> Andreas
+ Schlüns</FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">email</FONT></FONT> </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P> <A HREF="mailto:andreas.schluens@germany.sun.com"><FONT SIZE=2><FONT FACE="Arial">andreas.schluens@germany.sun.com</FONT></FONT></A>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">last modification</FONT></FONT>
+ </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P><FONT SIZE=2><FONT FACE="Arial"> 11.04.2001</FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+</TABLE>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/documentation/filters/services.html b/content/framework/documentation/filters/services.html
new file mode 100644
index 0000000..6c12370
--- /dev/null
+++ b/content/framework/documentation/filters/services.html
@@ -0,0 +1,299 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE>TypeDetection-Services</TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="CREATED" CONTENT="20010222;17102408">
+ <META NAME="CHANGEDBY" CONTENT="Mathias Bauer">
+ <META NAME="CHANGED" CONTENT="20010411;13373543">
+ <STYLE>
+ <!--
+ TD P { color: #000000 }
+ P { color: #000000 }
+ A:visited { color: #800080 }
+ A:link { color: #0000ff }
+ -->
+ </STYLE>
+</head>
+<body TEXT="#000000" LINK="#0000ff" VLINK="#800080">
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0 STYLE="page-break-before: always">
+ <TR>
+ <TD>
+ <P ALIGN=LEFT><A HREF="index.html"><<</A></P>
+ </TD>
+ <TD>
+ <P ALIGN=CENTER><BR>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=RIGHT><A HREF="example.html">>></A></P>
+ </TD>
+ </TR>
+</TABLE>
+<HR SIZE=3 COLOR="#000000">
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<CENTER>
+ <TABLE WIDTH=70% BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P><FONT SIZE=5>Realization</FONT> <BR><BR>The generic approach,
+ as was already shown in the configuration, continues in
+ realization and implementation. Modularity and exchangeability
+ are generally achieved by consistent use of the UNO service
+ concept.
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><BR><FONT SIZE=5>Service Description</FONT> <BR><BR>The
+ following services were specified:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#service_MediaDescriptor">com.sun.star.document.MediaDescriptor</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#service_TypeDetection">com.sun.star.document.TypeDetection</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#service_FrameLoaderFactory">com.sun.star.frame.FrameLoaderFactory</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#service_Loader">com.sun.star.frame.FrameLoader</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#service_Loader">com.sun.star.frame.SynchronousFrameLoader</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#service_FilterFactory">com.sun.star.document.FilterFactory</A>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm"><A HREF="#service_Filter">com.sun.star.document.ImportFilter</A>
+ </P>
+ <LI><P><A HREF="#service_Filter">com.sun.star.document.ExportFilter</A>
+ </P>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <HR SIZE=1 COLOR="#cccccc">
+ <P><A NAME="service_MediaDescriptor"></A><STRONG>com.sun.star.document.MediaDescriptor
+ </STRONG><BR><BR>This is not really a service. Rather, it is a
+ structure that tries to unite all the document information. This
+ is where e.g. URL, MediaType, FilterName, Referrer, Version and
+ an InputStream are available. The point is to <SPAN STYLE="background: transparent">take</SPAN>
+ the MediaDescriptor through all the processes of type detection
+ (detect flat/deep, filter, load...). Resulting information should
+ be added or corrected so that it is available for the next step
+ in the process. <BR>Some things to be aware of:
+ </P>
+ <OL>
+ <LI><P STYLE="margin-bottom: 0cm">The UNO feature that
+ corresponds to this service is a sequence of elements of the
+ com.sun.star.beans.PropertyValue type. It is thus not a real
+ service in the sense of an object. <BR>e.g. in C++
+ "<FONT COLOR="#666666">::com::sun::star::uno::Sequence<
+ ::com::sun::star::beans::PropertyValue > lProperties</FONT>"
+ </P>
+ <LI><P>The elements may only be referenced or kept as a copy for
+ the time necessary for direct processing.
+ </P>
+ </OL>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <HR SIZE=1 COLOR="#cccccc">
+ <P><A NAME="service_TypeDetection"></A><STRONG>com.sun.star.document.TypeDetection
+ </STRONG>
+ </P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm"><FONT COLOR="#d74601">interface
+ com.sun.star.document.XTypeDetection</FONT> <BR>Makes flat or
+ deep detection of the type of contents, described by the URL or
+ a MediaDescriptor. The result you receive is the internal name
+ of the detected type. This can be used to get registered loaders
+ or filters. The FrameLoaderFactory and FilterFactory services
+ help you do this.
+ </P>
+ <LI><P><FONT COLOR="#d74601">interface
+ com.sun.star.container.XNameAccess</FONT> <BR>Allows <SPAN STYLE="background: transparent">read-access</SPAN>
+ to the configuration data of all types.
+ </P>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <HR SIZE=1 COLOR="#cccccc">
+ <P><A NAME="service_FrameLoaderFactory"></A><STRONG>com.sun.star.frame.FrameLoaderFactory
+ </STRONG>
+ </P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm"><FONT COLOR="#d74601">interface
+ com.sun.star.lang.XMultiServiceFactory</FONT> <BR>Creates a
+ loader service registered to one type. You enter the internal
+ type name you received from a TypeDetection and get a reference
+ to the object produced. The loader factory already initializes
+ the object produced with its configuration data. <BR>See also
+ <A HREF="#service_Loader">FrameLoader/SynchronousFrameLoader</A>
+ for further information.
+ </P>
+ <LI><P><FONT COLOR="#d74601">interface
+ com.sun.star.container.XNameAccess</FONT> Allows <SPAN STYLE="background: transparent">read-access</SPAN>
+ to the configuration of all FrameLoaders.
+ </P>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <HR SIZE=1 COLOR="#cccccc">
+ <P><A NAME="service_Loader"></A><STRONG>com.sun.star.frame.FrameLoader<BR>com.sun.star.frame.SynchronousFrameLoader
+ </STRONG>
+ </P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm"><FONT COLOR="#d74601">interface
+ com.sun.star.frame.XFrameLoader</FONT> |
+ <FONT COLOR="#d74601">com.sun.star.frame.XSynchronousFrameLoader</FONT>
+ <BR>With the help of the methods load() and cancel(), you can
+ start processing a document or also abort it. The various
+ services differ only in the way results are returned. The
+ FrameLoader returns immediately and allows the client to listen
+ for the loading completion, whereas the SynchronousFrameLoader
+ returns when finished loading with the result of the process. <SPAN STYLE="background: transparent">If
+ an object implements both interfaces, the synchronous version is
+ preferred. </SPAN>
+ </P>
+ <LI><P><FONT COLOR="#d74601">interface
+ com.sun.star.lang.XInitialization<BR>interface
+ com.sun.star.beans.XPropertySet<BR>[property, readonly]
+ sequence< string > Name<BR>[property, readonly] sequence<
+ string > Types<BR>[property, readonly] string UIName<BR></FONT>These
+ interfaces must be supported by a loader implementation, t<SPAN STYLE="background: transparent">hus
+ making configuration data available by asking the object instead
+ of retrieving it from</SPAN> the FrameLoaderFactory. The
+ properties are re defined as read-only because it does not make
+ sense to make changes at run-time. The XInitialization interface
+ is used by the FrameLoaderFactory to provide the Loader with its
+ configuration data, clients can get them via XPropertySet.</P>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <HR SIZE=1 COLOR="#cccccc">
+ <P><A NAME="service_FilterFactory"></A><STRONG><SPAN STYLE="background: transparent">com.sun.star.document.FilterFactory</SPAN></STRONG></P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm"><FONT COLOR="#d74601">interface
+ com.sun.star.lang.XMultiServiceFactory</FONT> <BR>Use this to
+ create a registered filter suitable for a determined type. You
+ transfer the internal type names and receive a reference to the
+ filter object. The factory then initializes the object with its
+ configuration data. <BR>See also <A HREF="#service_Filter">import/export
+ filters</A>
+ </P>
+ <LI><P><FONT COLOR="#d74601">interface
+ com.sun.star.container.XNameAccess</FONT> <BR>Allows <SPAN STYLE="background: transparent">read-access</SPAN>
+ to the configuration of all filters.
+ </P>
+ </UL>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <HR SIZE=1 COLOR="#cccccc">
+ <P><A NAME="service_Filter"></A><STRONG>com.sun.star.document.ImportFilter<BR>com.sun.star.document.ExportFilter
+ </STRONG>
+ </P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm"><FONT COLOR="#d74601">interface
+ com.sun.star.document.XFilter</FONT> <BR>This interface is
+ supported by both services. Use it to start or interrupt the
+ actual filter process. The result is indicated synchronously.
+ The interface only supports a synchronous loading.</P>
+ <LI><P STYLE="margin-bottom: 0cm"><FONT COLOR="#d74601">interface
+ com.sun.star.document.XImporter<BR>interface
+ com.sun.star.document.XExporter</FONT> <BR>A filter is
+ identified as an import and/or export filter by appropriate
+ flags in its configuration data (see also filter configuration).
+ It can implement one or both interfaces. The purpose of these
+ interfaces is to transfer an interface to the output or target
+ document to the filter.<BR>The following algorithm is used:
+ <BR> a) get suitable interface for
+ respective process (XImporter/XExporter) <BR> b)
+ set the document on it (setTargetDocument()/setSourceDocument())
+ <BR> c) get XFilter interface for
+ the same object and start the process with filter() <BR>Problems
+ might be caused by simultaneous implementation of both
+ interfaces. Then the implementation must detect the method
+ called for setting the document, and, based on that, infer the
+ type of filter process.</P>
+ <LI><P><FONT COLOR="#d74601">interface
+ com.sun.star.lang.XInitialization<BR>interface
+ com.sun.star.beans.XPropertySet<BR>[property, readonly] string
+ Name;<BR>[property, readonly] string Type;<BR>[property,
+ readonly] string UIName;<BR>[property, readonly] string
+ DocumentService;<BR>[property, readonly] string
+ FilterService;<BR>[property, readonly] string Flags;<BR>[property,
+ readonly] string UserData;<BR>[property, readonly] string
+ FileFormatVersion;<BR>[property, readonly] string
+ TemplateName;<BR></FONT><FONT COLOR="#000000">A filter must also
+ make its own configuration accessible to others by implementing
+ these interfaces. <BR>See also the description</FONT>
+ <A HREF="#service_Loader">FrameLoader/SynchronousFrameLoader</A>!</P>
+ </UL>
+ </TD>
+ </TR>
+ </TABLE>
+</CENTER>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P ALIGN=LEFT><A HREF="index.html"><<</A>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=CENTER><BR>
+ </P>
+ </TD>
+ <TD>
+ <P ALIGN=RIGHT><A HREF="example.html">>></A></P>
+ </TD>
+ </TR>
+</TABLE>
+<HR SIZE=3 COLOR="#000000">
+<TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">author</FONT></FONT> </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P><FONT SIZE=2><FONT FACE="Arial"> Andreas
+ Schlüns</FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">email</FONT></FONT> </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P> <A HREF="mailto:andreas.schluens@germany.sun.com"><FONT SIZE=2><FONT FACE="Arial">andreas.schluens@germany.sun.com</FONT></FONT></A>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD>
+ <P><STRONG><FONT SIZE=2><FONT FACE="Arial">last modification</FONT></FONT>
+ </STRONG>
+ </P>
+ </TD>
+ <TD>
+ <P><FONT SIZE=2><FONT FACE="Arial"> 11.04.2001</FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+</TABLE>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/documentation/filterui/index.html b/content/framework/documentation/filterui/index.html
new file mode 100644
index 0000000..7a0ac27
--- /dev/null
+++ b/content/framework/documentation/filterui/index.html
@@ -0,0 +1,211 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <STYLE>
+ <!--
+ @page { margin: 2cm }
+ P { margin-bottom: 0.21cm; text-align: justify }
+ P.western { font-family: "Arial", sans-serif; font-size: 10pt }
+ TD P { margin-bottom: 0.21cm; text-align: justify }
+ TD P.western { font-family: "Arial", sans-serif; font-size: 10pt }
+ H1 { margin-bottom: 0.21cm }
+ H1.western { font-family: "Arial", sans-serif; font-size: 11pt }
+ H1.cjk { font-size: 16pt }
+ H1.ctl { font-size: 16pt }
+ P.textk�rper-einzug-western { text-indent: 0.5cm; font-family: "Arial", sans-serif; font-size: 10pt }
+ P.textk�rper-einzug-cjk { text-indent: 0.5cm }
+ P.textk�rper-einzug-ctl { text-indent: 0.5cm }
+ -->
+ </STYLE>
+</head>
+<body LANG="de-DE">
+<HR>
+<P ALIGN=LEFT STYLE="margin-top: 0.42cm; page-break-after: avoid">
+<H1>
+Java Application „FilterUI“
+</H1>
+</P>
+<H2 CLASS="western">Content</H2>
+<UL>
+ <LI><A HREF="#general">General</A></LI>
+ <LI><A HREF="#intention">Intention</LI>
+ <LI><A HREF="#licence">Licence</LI>
+ <LI><A HREF="#features">Features</LI>
+ <LI><A HREF="#requirements">Requirements</LI>
+ <LI><A HREF="#installation">Installation</LI>
+ <LI><A HREF="#startit">Start It</LI>
+ <LI><A HREF="#documentation">Documentation</LI>
+ <LI><A HREF="#snapshots">Snapshots</LI>
+ <LI><A HREF="#download">Download / Source</LI>
+</UL>
+<H2 CLASS="western"><A NAME="general">General</A></H2>
+<P CLASS="western"><FONT FACE="Arial, sans-serif">
+I've started development of a new java based application to access filter
+configuration data of any StarOffice or OpenOffice installation.
+The first version of it will be a very simple tool and supports
+read only access only. It's planned to extend it's functionality,
+step by step, to get a full-featured administration tool. But
+this task can't be done by one person only. So I offer the code
+on OpenOffice. Please feel free to contact me if you are
+interested in this code.
+</FONT></P>
+<H2 CLASS="western"><A NAME="intention">Intention</A></H2>
+<P CLASS="western"><FONT FACE="Arial, sans-serif">
+The filter configuration of an office is a very complex mechanism.
+Configuration data is organized similar to a database, e.g.,
+filters are registered for different types. This data is
+available, inside an office installation, in a file named
+TypeDetection.xml. The structure of the file is simple, but the
+number of entries can be very high, e.g., on a full installation
+set. Reading and editing large sets isn't easy. That is the
+reason for this application: to provide a simple access to the
+data source and also illustrate the use of the office filter
+api.
+</FONT></P>
+<H2 CLASS="western"><A NAME="licence">Licence</A></H2>
+<P CLASS="western"><FONT FACE="Arial, sans-serif">
+It's completely free. Use of the binaries and source will not be regulated in any
+way. That doesn't include any external requirements, e.g., jdk /
+office, which may use their own license models.
+</FONT></P>
+<H2 CLASS="western"><A NAME="features">Features</A></H2>
+<UL>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">Version 1.0</FONT></P>
+ <UL>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">
+ remote connection to an already(!) running office<BR>
+ (doesn't include proxy support)
+ </FONT></P>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">
+ read only view of all installed filters/types and their properties of remote office
+ </FONT></P>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">
+ query mode to specify which filter should be shown
+ </FONT></P>
+ <LI><P CLASS="western">
+ locale of application is changeable during runtime<BR>
+ (prepared but not fully used)
+ </P>
+ </UL>
+</UL>
+<H2 CLASS="western"><A NAME="requirements">Requirements</A></H2>
+<UL>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">
+ an OS which supports java and uses a windowing environment<BR>
+ (e.g. Linux with Gnome/KDE)
+ </FONT></P>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">
+ JDK 1.2
+ </FONT></P>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">
+ Office installation<BR>
+ (StarOffice 6.0 [beta] or OpenOffice [641c])<BR>
+ For access of all known filters, it is necessary to make a full
+ installation of office; otherwise, only a subset will be
+ available. Furthermore, it is necessary to enable java support.
+ The following JAR files will be used:
+ </FONT></P>
+</UL>
+<P CLASS="western" STYLE="margin-left: 2.2cm">
+ <FONT FACE="Arial, sans-serif">
+ unoil.jar<BR>
+ ridl.jar<BR>
+ jurt.jar<BR>
+ juh.jar<BR>
+ sandbox.jar
+ </FONT></P>
+<H2 CLASS="western"><A NAME="installation">Installation</A></H2>
+<P CLASS="western"><FONT FACE="Arial, sans-serif">
+ There exist three possiblities:</FONT></P>
+<OL>
+ <LI><P CLASS="textkörper-einzug-western"><A NAME="install_1"/>
+ Get the <A HREF="http://framework.openoffice.org/documentation/filterui/filterui.jar">JAR</A> file, for direct use.<BR>
+ Copy it into your office installation (this means your directory „<office_install>/program/classes“) or to any
+ other directory which includes the required JAR files.<BR>
+ (see Requirements)
+ </P>
+ <LI><P CLASS="western" ALIGN=LEFT><FONT FACE="Arial, sans-serif"><A NAME="install_2"/>
+ Use sources from OpenOffice project <A HREF="http://framework.openoffice.org/source/browse/framework/framework">framework/framework</A>.
+ Change to sub directory <A HREF="http://framework.openoffice.org/source/browse/framework/framework/java/filterui/">“java/filterui“</A>.
+ There you will find all necessary sources to build the application as a
+ packed JAR file, as well as to generate the class and property
+ files. See <A HREF="http://framework.openoffice.org/source/browse/framework/framework/java/filterui/readme.txt">“java/filterui/readme.txt“</A> for further information.
+ After compilation, you will have a JAR file. Use it
+ in the same manner as described in <A HREF="#install_1">1</A>.
+ </FONT></P>
+ <LI><P CLASS="western" ALIGN=LEFT><FONT FACE="Arial, sans-serif">
+ Get the java sources and build it by yourself.<BR>
+ Of course, this is possible also – but I will not document
+ it here. See <A HREF="#install_1">1</A> and <A HREF="#install_2">2</A>
+ for more information on how to build from source, and use it for your own interests.
+ </FONT></P>
+</OL>
+<H2 CLASS="western"><A NAME="startit">Start It</A></H2>
+<OL>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">
+ Start office with the following command line parameter to initiate remote mode:<BR>
+ „<I>soffice -accept=socket,host=<HOST>,port=<PORT>;urp;</I>“<BR>
+ Variable <HOST> describe the host on which office runs, e.g., „localhost“.<BR>
+ Variable <PORT> describe the port on which office listens for incoming requests.<BR>
+ These values must correspond to values set in the configuration
+ file of the „FilterUI“ application named „filterui.ini“.
+ </FONT>
+ </P>
+ <LI><P CLASS="western"><FONT FACE="Arial, sans-serif">
+ Start application with the following command: „<I>java -jar filterui.jar</I>“
+ </FONT></P>
+</OL>
+<H2 CLASS="western"><A NAME="documentation">Documentation</A></H2>
+<P CLASS="western"><FONT FACE="Arial, sans-serif">
+ It will come as soon as possible ...
+ </FONT>
+<H2 CLASS="western"><A NAME="snapshots">Snapshots</A></H2>
+<TABLE BORDER=0 CELLPADDING=0 CELLSPACING=5 STYLE="page-break-inside: avoid">
+ <TR VALIGN=MIDDLE>
+ <TD><A HREF="mainwin.png">Main Window</A></TD>
+ <TD><IMG SRC="mainwin_tbn.png"></TD>
+ </TR>
+</TABLE>
+<H2 CLASS="western"><A NAME="download">Download/Source</A></H2>
+<UL>
+ <LI><A HREF="filterui.jar">JAR</A></LI>
+ <LI><A HREF="http://framework.openoffice.org/source/browse/framework/framework/java/filterui/">Link to CVS directory of openoffice</A></LI>
+</UL>
+</P>
+<HR>
+<TABLE WIDTH=367 BORDER=0 CELLPADDING=0 CELLSPACING=0 STYLE="page-break-inside: avoid">
+ <COL WIDTH=113>
+ <COL WIDTH=254>
+ <TR VALIGN=TOP>
+ <TD WIDTH=113>
+ <P CLASS="western" ALIGN=LEFT><FONT FACE="Arial, sans-serif"><FONT SIZE=2><B>Author</B></FONT></FONT></P>
+ </TD>
+ <TD WIDTH=254>
+ <P CLASS="western" ALIGN=LEFT><FONT FACE="Arial, sans-serif"><FONT SIZE=2>Andreas
+ Schlüns</FONT></FONT></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=113>
+ <P CLASS="western" ALIGN=LEFT><B><FONT SIZE=2><FONT FACE="Arial, sans-serif">email</FONT></FONT></B></P>
+ </TD>
+ <TD WIDTH=254>
+ <P CLASS="western" ALIGN=LEFT><FONT FACE="Arial, sans-serif"><FONT SIZE=2><A HREF="mailto:andreas.schluens@germany.sun.com">andreas.schluens@germany.sun.com</A></FONT></FONT></P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=113 VALIGN=TOP>
+ <P CLASS="western" ALIGN=LEFT><FONT FACE="Arial, sans-serif"><FONT SIZE=2><B>last
+ modified</B></FONT></FONT></P>
+ </TD>
+ <TD WIDTH=254 VALIGN=BOTTOM SDVAL="37280" SDNUM="1031;0;TT.MM.JJ">
+ <P CLASS="western" ALIGN=LEFT><FONT FACE="Arial, sans-serif"><FONT SIZE=2>25.01.2002</FONT></FONT></P>
+ </TD>
+ </TR>
+</TABLE>
+<P ALIGN=LEFT STYLE="margin-bottom: 0cm"><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/documentation/mimetypes/mimetypes.html b/content/framework/documentation/mimetypes/mimetypes.html
new file mode 100644
index 0000000..9e497b5
--- /dev/null
+++ b/content/framework/documentation/mimetypes/mimetypes.html
@@ -0,0 +1,644 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+ <meta content="text/html; charset=iso-8859-1"
+ http-equiv="CONTENT-TYPE">
+ <title>Type Detection - Examples</title>
+ <meta content="StarOffice/5.2 (Win32)" name="GENERATOR">
+ <meta content="20010222;14370867" name="CREATED">
+ <meta content="Mathias Bauer" name="CHANGEDBY">
+ <meta content="20010411;13383007" name="CHANGED">
+</head>
+<body>
+<table style="page-break-before: always;" cellspacing="0"
+ cellpadding="0" border="0" width="100%">
+ <tbody>
+ <tr>
+ <td>
+ <p align="left"><a href="../../index.html"><<</a> </p>
+ </td>
+ <td>
+ <p align="center"><br>
+ </p>
+ </td>
+ <td><br>
+ <p align="right"></p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<hr color="#000000" size="3">
+<center>
+<table cellspacing="0" cellpadding="2" border="0" width="100%">
+ <col width="1285"><tbody>
+ <tr>
+ <td width="1285">
+ <h1><font size="5">Mime Content Types used in OpenOffice.org1.0 /
+StarOffice 4.x and later<br>
+ </font></h1>
+ <p>For general information regarding mime content types please
+have a look at <a href="http://www.iana.org">IANA</a> . Please note
+that only the OpenOffice.org 2.0 mime content types are currently registered at <a
+ href="http://www.iana.org">IANA</a> . <a
+ href="http://specs.openoffice.org/appwide/fileIO/FileFormatNames.sxw"></a><br>
+ </p>
+ <p> </p>
+ </td>
+ </tr>
+ <tr>
+ <td width="1285">
+ <h2>Mime Content Types used in OpenOffice.org2.0 / StarOffice 8
+and later</h2>
+ <br>
+See also the specification <a
+ href="http://specs.openoffice.org/appwide/fileIO/FileFormatNames.sxw">File
+format names and Mime types for OpenOffice.org XML format.</a><br>
+ <table width="100%" border="1" cellspacing="2" cellpadding="2">
+ <tbody>
+ <tr>
+ <th width="300" valign="top">Mime Content Type<br>
+ </th>
+ <th width="300" valign="top">Default Document Extension<br>
+ </th>
+ <th valign="top">Description<br>
+ </th>
+ </tr>
+ <tr>
+ <td width="300" valign="top">
+ <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=utf-8">
+ <title></title>
+ <meta name="GENERATOR"
+ content="StarOffice 7 (Solaris Sparc)">
+ <meta name="CREATED" content="20040621;13501400">
+ <meta name="CHANGEDBY" content="Frank Loehmann">
+ <meta name="CHANGED" content="20041207;16143800">
+ <style><big>
+ <!--
+ @page { size: 8.27in 11.69in; margin: 0.79in }
+ P { margin-bottom: 0.08in; text-align: justify; page-break-before: auto }
+ P.western { font-family: "Albany", sans-serif; font-size: 10pt }
+ -->
+ </big></style><big>
+ </big>application/vnd.oasis.opendocument.text<big>
+ </big><br>
+ </td>
+ <td width="300" valign="top">odt <br>
+ </td>
+ <td valign="top">OpenDocument Text<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;"><big> </big>application/vnd.oasis.opendocument.text-template</td>
+ <td style="vertical-align: top;">ott</td>
+ <td style="vertical-align: top;">OpenDocument Text Template</td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.text-web<br>
+ </td>
+ <td width="300" valign="top">oth<br>
+ </td>
+ <td valign="top">HTML Document Template<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.text-master</td>
+ <td width="300" valign="top">odm<br>
+ </td>
+ <td valign="top">OpenDocument Master Document<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.graphics</td>
+ <td width="300" valign="top">odg<br>
+ </td>
+ <td valign="top">OpenDocument Drawing<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">application/vnd.oasis.opendocument.graphics-template</td>
+ <td style="vertical-align: top;">otg</td>
+ <td style="vertical-align: top;">OpenDocument Drawing
+Template</td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.presentation<br>
+ </td>
+ <td width="300" valign="top">odp<br>
+ </td>
+ <td valign="top">OpenDocument Presentation <br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">application/vnd.oasis.opendocument.presentation-template</td>
+ <td style="vertical-align: top;">otp<br>
+ </td>
+ <td style="vertical-align: top;">OpenDocument Presentation
+Template</td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.spreadsheet</td>
+ <td width="300" valign="top">ods<br>
+ </td>
+ <td valign="top">OpenDocument Spreadsheet<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">application/vnd.oasis.opendocument.spreadsheet-template</td>
+ <td style="vertical-align: top;">ots<br>
+ </td>
+ <td style="vertical-align: top;"> OpenDocument Spreadsheet
+Template</td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.chart</td>
+ <td width="300" valign="top">odc<br>
+ </td>
+ <td valign="top">OpenDocument Chart<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.formula</td>
+ <td width="300" valign="top">odf<br>
+ </td>
+ <td valign="top">OpenDocument Formula<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.database</td>
+ <td width="300" valign="top">odb<br>
+ </td>
+ <td valign="top">OpenDocument Database<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.oasis.opendocument.image</td>
+ <td width="300" valign="top">odi<br>
+ </td>
+ <td valign="top">OpenDocument Image <br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.openofficeorg.extension</td>
+ <td width="300" valign="top">oxt<br>
+ </td>
+ <td valign="top">OpenOffice.org extension (since OOo 2.1) <br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <br>
+ <br>
+ <h2>Mime Content Types used in OpenOffice.org1.0 / StarOffice6.0
+and later<br>
+ </h2>
+ <table width="100%" border="1" cellspacing="2" cellpadding="2">
+ <tbody>
+ <tr>
+ <th width="300" valign="top">Mime Content Type<br>
+ </th>
+ <th width="300" valign="top">Default Document Extension<br>
+ </th>
+ <th valign="top">Description<br>
+ </th>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.writer<br>
+ </td>
+ <td width="300" valign="top">sxw<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Writer 6.0 documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.writer.template<br>
+ </td>
+ <td width="300" valign="top">stw<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Writer 6.0 templates.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.calc<br>
+ </td>
+ <td width="300" valign="top">sxc<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Calc 6.0 spreadsheets.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.calc.template<br>
+ </td>
+ <td width="300" valign="top">stc<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Calc 6.0 templates.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.draw<br>
+ </td>
+ <td width="300" valign="top">sxd<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Draw 6.0 documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.draw.template<br>
+ </td>
+ <td width="300" valign="top">std<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Draw 6.0 templates.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.impress<br>
+ </td>
+ <td width="300" valign="top">sxi<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Impress 6.0 presentations.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.impress.template<br>
+ </td>
+ <td width="300" valign="top">sti<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Impress 6.0 templates.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.writer.global<br>
+ </td>
+ <td width="300" valign="top">sxg<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Writer 6.0 global documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.sun.xml.math<br>
+ </td>
+ <td width="300" valign="top">sxm<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+Math 6.0 documents.<br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <br>
+ <h2>Mime Content Types used in StarOffice 5.x</h2>
+ <table width="100%" border="1" cellspacing="2" cellpadding="2">
+ <tbody>
+ <tr>
+ <th valign="top">Mime Content Type<br>
+ </th>
+ <th valign="top">Default Document Extension <br>
+ </th>
+ <th valign="top">Description<br>
+ </th>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/vnd.stardivision.writer<br>
+ </td>
+ <td width="300" valign="top">sdw<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarWriter 5.x documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/vnd.stardivision.writer-global<br>
+ </td>
+ <td valign="top">sgl<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarWriter 5.x global documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">-<br>
+ </td>
+ <td valign="top">vor<br>
+ </td>
+ <td valign="top">There is no mime content type for ".vor"
+files because this extension will used for templates in general.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/vnd.stardivision.calc<br>
+ </td>
+ <td valign="top">sdc<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarCalc 5.x spreadsheets.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/vnd.stardivision.draw<br>
+ </td>
+ <td valign="top">sda<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarDraw 5.x documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/vnd.stardivision.impress<br>
+ </td>
+ <td valign="top">sdd<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarImpress 5.x presentations.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/vnd.stardivision.impress-packed<br>
+ </td>
+ <td valign="top">sdp<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarImpress Packed 5.x files.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/vnd.stardivision.math<br>
+ </td>
+ <td valign="top">smf<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarMath 5.x documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/vnd.stardivision.chart<br>
+ </td>
+ <td valign="top">sds<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StaChart 5.x documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/vnd.stardivision.mail<br>
+ </td>
+ <td valign="top">sdm<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarMail 5.x mail files.<br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <br>
+ <h2>Mime Content Types used in StarOffice 4.x</h2>
+ <table width="100%" border="1" cellspacing="2" cellpadding="2">
+ <tbody>
+ <tr>
+ <th valign="top">Mime Content Type<br>
+ </th>
+ <th valign="top">Default Document Extension<br>
+ </th>
+ <th valign="top">Description<br>
+ </th>
+ </tr>
+ <tr>
+ <td width="300" valign="top">application/x-starwriter<br>
+ </td>
+ <td width="300" valign="top">sdw<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarWriter 4.x documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/x-starcalc<br>
+ </td>
+ <td valign="top">sdc<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarCalc 4.x spreadsheets.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/x-stardraw<br>
+ </td>
+ <td valign="top">sda<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarDraw 4.x documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/x-starimpress<br>
+ </td>
+ <td valign="top">sdd<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarImpress 4.x presentations.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/x-starmath<br>
+ </td>
+ <td valign="top">smf<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarMath 4.x documents.<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">application/x-starchart<br>
+ </td>
+ <td valign="top">sds<br>
+ </td>
+ <td valign="top">This mime content type will be used for
+StarChart 4.x documents.<br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <br>
+ <h2>Sample Configuration for Apache Web Server</h2>
+ <table bgcolor="#ffffcc" width="100%" border="0" cellspacing="2"
+ cellpadding="2">
+ <tbody>
+ <tr>
+ <td valign="top">[httpd.conf] <br>
+... <br>
+AddType application/vnd.stardivision.chart .sds <br>
+AddType application/vnd.stardivision.calc .sdc <br>
+AddType application/vnd.stardivision.writer .sdw <br>
+AddType application/vnd.stardivision.writer-global .sgl <br>
+AddType application/vnd.stardivision.draw .sda <br>
+AddType application/vnd.stardivision.impress .sdd <br>
+AddType application/vnd.stardivision.math .sdf <br>
+AddType application/vnd.sun.xml.writer .sxw <br>
+AddType application/vnd.sun.xml.writer.template .stw<br>
+AddType application/vnd.sun.xml.writer.global .sxg <br>
+AddType application/vnd.sun.xml.calc .sxc <br>
+AddType application/vnd.sun.xml.calc.template .stc <br>
+AddType application/vnd.sun.xml.impress .sxi <br>
+AddType application/vnd.sun.xml.impress.template .sti<br>
+AddType application/vnd.sun.xml.draw .sxd <br>
+AddType application/vnd.sun.xml.draw.template .std<br>
+AddType application/vnd.sun.xml.math .sxm<br>
+AddType application/vnd.oasis.opendocument.text .odt<br>
+AddType application/vnd.oasis.opendocument.text-template .ott<br>
+AddType application/vnd.oasis.opendocument.text-web .oth<br>
+AddType application/vnd.oasis.opendocument.text-master .odm<br>
+AddType application/vnd.oasis.opendocument.graphics .odg<br>
+AddType application/vnd.oasis.opendocument.graphics-template .otg<br>
+AddType application/vnd.oasis.opendocument.presentation .odp<br>
+AddType application/vnd.oasis.opendocument.presentation-template .otp<br>
+AddType application/vnd.oasis.opendocument.spreadsheet .ods<br>
+AddType application/vnd.oasis.opendocument.spreadsheet-template .ots<br>
+AddType application/vnd.oasis.opendocument.chart .odc<br>
+AddType application/vnd.oasis.opendocument.formula .odf<br>
+AddType application/vnd.oasis.opendocument.database .odb<br>
+AddType application/vnd.oasis.opendocument.image .odi<br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <h2>Sample Configuration for iPlanet</h2>
+ <table bgcolor="#ffffcc" width="100%" border="0" cellspacing="2"
+ cellpadding="2">
+ <tbody>
+ <tr>
+ <td valign="top">type=application/vnd.stardivision.calc
+exts=sdc <br>
+type=application/vnd.stardivision.chart exts=sds <br>
+type=application/vnd.stardivision.writer exts=sdw <br>
+type=application/vnd.stardivision.writer-global exts=sgl <br>
+type=application/vnd.stardivision.draw exts=sda <br>
+type=application/vnd.stardivision.impress exts=sdd <br>
+type=application/vnd.stardivision.math exts=sdf <br>
+type=application/vnd.sun.xml.writer exts=sxw<br>
+type=application/vnd.sun.xml.writer.template exts=stw <br>
+type=application/vnd.sun.xml.writer.global exts=sxg <br>
+type=application/vnd.sun.xml.calc exts=sxc <br>
+type=application/vnd.sun.xml.calc.template exts=stc <br>
+type=application/vnd.sun.xml.impress exts=sxi <br>
+type=application/vnd.sun.xml.impress.template exts=sti <br>
+type=application/vnd.sun.xml.draw exts=sxd <br>
+type=application/vnd.sun.xml.draw.template exts=std<br>
+type=application/vnd.sun.xml.math exts=sxm<br>
+type=application/vnd.oasis.opendocument.text exts=odt<br>
+type=application/vnd.oasis.opendocument.text-template exts=ott<br>
+type=application/vnd.oasis.opendocument.text-web exts=oth<br>
+type=application/vnd.oasis.opendocument.text-master exts=odm<br>
+type=application/vnd.oasis.opendocument.graphics exts=odg<br>
+type=application/vnd.oasis.opendocument.graphics-template exts=otg<br>
+type=application/vnd.oasis.opendocument.presentation exts=odp<br>
+type=application/vnd.oasis.opendocument.presentation-template exts=otp<br>
+type=application/vnd.oasis.opendocument.spreadsheet exts=ods<br>
+type=application/vnd.oasis.opendocument.spreadsheet-template exts=ots<br>
+type=application/vnd.oasis.opendocument.chart exts=odc<br>
+type=application/vnd.oasis.opendocument.formula exts=odf<br>
+type=application/vnd.oasis.opendocument.database exts=odb<br>
+type=application/vnd.oasis.opendocument.image exts=odi<br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">
+ <h2>Sample mime.types entries</h2>
+ <table width="100%" border="0" cellspacing="2" cellpadding="2">
+ <tbody>
+ <tr>
+ <td bgcolor="#ffffcc" valign="top">
+ <p>application/vnd.sun.xml.writer sxw<br>
+application/vnd.sun.xml.writer.template stw<br>
+application/vnd.sun.xml.writer.global sxg<br>
+application/vnd.stardivision.writer sdw vor<br>
+application/vnd.stardivision.writer-global sgl<br>
+application/vnd.sun.xml.calc sxc<br>
+application/vnd.sun.xml.calc.template stc<br>
+application/vnd.stardivision.calc sdc<br>
+application/vnd.sun.xml.impress sxi<br>
+application/vnd.sun.xml.impress.template sti<br>
+application/vnd.stardivision.impress sdd sdp<br>
+application/vnd.sun.xml.draw sxd<br>
+application/vnd.sun.xml.draw.template std<br>
+application/vnd.stardivision.draw sda<br>
+application/vnd.sun.xml.math sxm<br>
+application/vnd.stardivision.math smf<br>
+application/vnd.oasis.opendocument.text odt<br>
+application/vnd.oasis.opendocument.text-template ott<br>
+application/vnd.oasis.opendocument.text-web oth<br>
+application/vnd.oasis.opendocument.text-master odm<br>
+application/vnd.oasis.opendocument.graphics odg<br>
+application/vnd.oasis.opendocument.graphics-template otg<br>
+application/vnd.oasis.opendocument.presentation odp<br>
+application/vnd.oasis.opendocument.presentation-template otp<br>
+application/vnd.oasis.opendocument.spreadsheet ods<br>
+application/vnd.oasis.opendocument.spreadsheet-template ots<br>
+application/vnd.oasis.opendocument.chart odc<br>
+application/vnd.oasis.opendocument.formula odf<br>
+application/vnd.oasis.opendocument.database odb<br>
+application/vnd.oasis.opendocument.image odi<br>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ </tbody>
+</table>
+</center>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+ <tbody>
+ <tr>
+ <td>
+ <p align="left"><a href="../../index.html"><<</a> </p>
+ </td>
+ <td>
+ <p align="center"><br>
+ </p>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<hr color="#000000" size="3">
+<table bgcolor="#ffffff" width="100%" cellspacing="0" cellpadding="0"
+ border="0">
+ <tbody>
+ <tr>
+ <td width="150"><strong><font size="2"><font face="Arial">Author:</font></font></strong></td>
+ <td><font size="2"><font face="Arial"> Tino Rachui </font></font></td>
+ </tr>
+ <tr>
+ <td><strong><font size="2"><font face="Arial">Email:</font></font></strong></td>
+ <td><a href="mailto:tino.rachui@sun.com"> tino.rachui</a> <a
+ href="mailto:tino.rachui@sun.com"><font size="2"><font face="Arial">
+@sun.com</font></font></a> </td>
+ </tr>
+ <tr>
+ <td><strong><font size="2"><font face="Arial">Last modification:</font></font></strong></td>
+ <td><font size="2"><font face="Arial"> 13.12.2004</font></font></td>
+ </tr>
+ </tbody>
+</table>
+<p><br>
+<br>
+</p>
+<br>
+<br>
+</body>
+</html>
diff --git a/content/framework/documentation/others/index.html b/content/framework/documentation/others/index.html
new file mode 100644
index 0000000..5e5e4a5
--- /dev/null
+++ b/content/framework/documentation/others/index.html
@@ -0,0 +1,14 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <TITLE>Other documentation</TITLE>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+ <H1>Themes</H1>
+ <UL>
+ <LI><A HREF="job_executor.html">Job Execution Service</A></LI>
+ </UL>
+</body>
+</HTML>
diff --git a/content/framework/documentation/others/job_executor.html b/content/framework/documentation/others/job_executor.html
new file mode 100644
index 0000000..b30ee19
--- /dev/null
+++ b/content/framework/documentation/others/job_executor.html
@@ -0,0 +1,284 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 6.0 (Win32)">
+ <META NAME="CREATED" CONTENT="20020530;14220812">
+ <META NAME="CHANGED" CONTENT="20020530;15563490">
+ <STYLE>
+ <!--
+ @page { margin: 2cm }
+ P { margin-bottom: 0.21cm; text-align: justify; page-break-before: auto }
+ P.western { font-family: "Times New Roman", serif; font-size: 11pt }
+ TD P { margin-bottom: 0.21cm; text-align: justify; page-break-before: auto }
+ TD P.western { font-family: "Times New Roman", serif; font-size: 11pt }
+ TH P { margin-bottom: 0.21cm; page-break-before: auto }
+ TH P.western { font-family: "Times New Roman", serif; font-size: 11pt; font-style: italic }
+ TH P.cjk { font-style: italic }
+ TH P.ctl { font-style: italic }
+ H1 { margin-bottom: 0.21cm }
+ H1.western { font-family: "Times New Roman", serif; font-size: 14pt }
+ H1.cjk { font-size: 16pt }
+ H1.ctl { font-size: 16pt }
+ H2 { margin-bottom: 0.21cm }
+ H2.western { font-family: "Times New Roman", serif; font-size: 12pt; font-style: normal }
+ H2.cjk { font-size: 14pt; font-style: italic }
+ H2.ctl { font-size: 14pt; font-style: italic }
+ H3 { margin-bottom: 0.21cm }
+ H3.western { font-family: "Times New Roman", serif; font-size: 12pt; font-weight: medium }
+ -->
+ </STYLE>
+</head>
+<body>
+<P ALIGN=LEFT STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Job
+Execution Service</B></FONT></P>
+<P CLASS="western"><BR>Inside the office exist a special service
+com.sun.star.task.JobExecutor. He can be used to trigger special
+events for which some uno components can be registered. Such
+components must provide the interfaces com.sun.star.task.XJob –
+for synchronous job execution – or com.sun.star.task.XAsyncJob
+– for asnychronous job execution. The global executor knows all
+these registered jobs and her possible trigger events by using a
+configuration package org.openoffice.Office.Jobs. He starts jobs if
+requested – control their life time and maintain her
+configuration.</P>
+<P CLASS="western">Note this</P>
+<UL>
+ <LI><P CLASS="western">Because it's currently not implemented –
+ asynchronous jobs are not supported yet.</P>
+ <LI><P CLASS="western">Every trigger event must be coded inside the
+ office. It requires creation of the global job executor and call his
+ method trigger() with a string value which describe the detected
+ event. The executor services reacts then only.</P>
+</UL>
+<P CLASS="western"><BR><BR>
+</P>
+<P CLASS="western">Following events are available:</P>
+<UL>
+ <LI><P CLASS="western"><I>onFirstVisibleTask</I><BR>This occures one
+ times only at runtime of an office. It will be triggered if any
+ first visible document frame will be shown. Next occurence will
+ happen after next startup.<BR>Note: An already running quickstart
+ module (under windows) hinder the office on a real shutdown.</P>
+ <LI><P CLASS="western"><I>onFirstRunInitialization</I><BR>This
+ occures on first startup of an office directly after installation.
+ After that a special flag inside configuration will be set –
+ to disable it. It willn't be called again.</P>
+</UL>
+<P CLASS="western"><BR><BR>
+</P>
+<H1 CLASS="western">Configuration</H1>
+<P CLASS="western">To add job functionality to the office it's
+neccessary to write a service (will be described later) and of course
+to register it inside configuration. The name of corresponding
+package is org.openoffice.Office.Jobs. There exist two sets (lists):</P>
+<OL>
+ <LI><P CLASS="western">Job</P>
+ <LI><P CLASS="western">Event</P>
+</OL>
+<H2 CLASS="western"><BR>The Job List</H2>
+<P CLASS="western">Every job must be registered here with some
+informations which describe it. Following entries are neccessary:</P>
+<P CLASS="western"><BR><BR>
+</P>
+<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
+ <COL WIDTH=44*>
+ <COL WIDTH=34*>
+ <COL WIDTH=179*>
+ <THEAD>
+ <TR VALIGN=TOP>
+ <TH WIDTH=17%>
+ <P CLASS="western">property name</P>
+ </TH>
+ <TH WIDTH=13%>
+ <P CLASS="western">value type</P>
+ </TH>
+ <TH WIDTH=70%>
+ <P CLASS="western">description</P>
+ </TH>
+ </TR>
+ </THEAD>
+ <TBODY>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17%>
+ <P CLASS="western">AdminTime</P>
+ </TD>
+ <TD WIDTH=13%>
+ <P CLASS="western">[string]</P>
+ </TD>
+ <TD WIDTH=70%>
+ <P CLASS="western">Time stamp of an administrator (neccessary for
+ network installations). A service will be started only if this
+ stamp is new then the following one UserTime. By using these two
+ stamps it's possible to reactivate as finished declared jobs
+ again.</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17%>
+ <P CLASS="western">UserTime</P>
+ </TD>
+ <TD WIDTH=13%>
+ <P CLASS="western">[string]</P>
+ </TD>
+ <TD WIDTH=70%>
+ <P CLASS="western">Time stamp of the office user. If a job was
+ finished and wish to be deregistered – this stamp is set to
+ the current time. After that AdminTime should be older and the
+ job never will be started again. That's true till the
+ administrator change his stamp.</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17%>
+ <P CLASS="western">Service</P>
+ </TD>
+ <TD WIDTH=13%>
+ <P CLASS="western">[string]</P>
+ </TD>
+ <TD WIDTH=70%>
+ <P CLASS="western">This is the service name of the job component.
+ But it must be the real implementation name of this service.
+ Because the service name isn't unambigous and nobody can
+ guarantee which implementation will be used in case the generic
+ job service name is used.</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17%>
+ <P CLASS="western">Arguments</P>
+ </TD>
+ <TD WIDTH=13%>
+ <P CLASS="western">[any list]</P>
+ </TD>
+ <TD WIDTH=70%>
+ <P CLASS="western">Every job can use this set to add his own
+ configuration data. Such set provides the possibility to add
+ key-value pairs.</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17%>
+ <P CLASS="western">Async</P>
+ </TD>
+ <TD WIDTH=13%>
+ <P CLASS="western">[boolean]</P>
+ </TD>
+ <TD WIDTH=70%>
+ <P CLASS="western">Mark this job as an asynchronous one.<BR>Note:
+ is currently not supported and must be false!</P>
+ </TD>
+ </TR>
+ </TBODY>
+</TABLE>
+<P CLASS="western"><BR><BR>
+</P>
+<H3 CLASS="western">Notation of a time stamp</H3>
+<P CLASS="western">Used time stamps are realized as special formated
+strings. See following
+notation:<BR>„<day>.<month>.<year>/<hour>:<minute>:<seconds>“.<BR>E.g.:
+„01.01.2002/00:00:01“</P>
+<P CLASS="western"><BR><BR>
+</P>
+<H2 CLASS="western">The Event List</H2>
+<P CLASS="western">These list contains all possible trigger events
+and knows which job components are registered for. The event names
+are used as entries inside this list. Every string value is possible
+– but he must be used inside the office code too. Every entry
+contains a list of strings which describes all registered services
+for this event. These strings are the same like the entries of the
+job list – not the service names.</P>
+<P CLASS="western"><BR><BR>
+</P>
+<H1 CLASS="western">How it works</H1>
+<P CLASS="western">Some code inside the office detect a special event
+– e.g. first visible document frame was opened. He creates the
+global job executor service and call him with a string value which
+descibe the event. The executor searches for any registered job
+inside his configuration which is registered for this event and not
+disabled. To check that two time stamps AdminTime and UserTime are
+used. (see before). After creation he queries the job component for
+the required interface and start it. Possible configuration data are
+passed to the job before. The job does his work then and return. At
+this time he must decide if he whish to be active and whish to be
+deactivated for further occurences of this event. He can do that by
+using a special protocol packed inside the returned Any value. A list
+of com.sun.star.beans.NamedValue is required there. Following values
+are supported:</P>
+<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
+ <COL WIDTH=44*>
+ <COL WIDTH=58*>
+ <COL WIDTH=154*>
+ <THEAD>
+ <TR VALIGN=TOP>
+ <TH WIDTH=17%>
+ <P CLASS="western">property name</P>
+ </TH>
+ <TH WIDTH=23%>
+ <P CLASS="western">value type</P>
+ </TH>
+ <TH WIDTH=60%>
+ <P CLASS="western">description</P>
+ </TH>
+ </TR>
+ </THEAD>
+ <TBODY>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17%>
+ <P CLASS="western">Deactivate</P>
+ </TD>
+ <TD WIDTH=23%>
+ <P CLASS="western">[boolean]</P>
+ </TD>
+ <TD WIDTH=60%>
+ <P CLASS="western">Job wish to be deactivated. He should call
+ that after successfull execution,or if something was wrong and
+ couldnt be resolved ...<BR>If this property is set, all other
+ ones are ignored. Because the service can be deregistered by
+ setting the time stamp or be real deletion of hi entries. That
+ depends from the implementation of the exceutor service and can
+ be changed for further versions of it.</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17%>
+ <P CLASS="western">SaveArguments</P>
+ </TD>
+ <TD WIDTH=23%>
+ <P CLASS="western">[list of NamedValue]</P>
+ </TD>
+ <TD WIDTH=60%>
+ <P CLASS="western">Job can save his own special arguments back to
+ configuration and mustn't implement it by itself.</P>
+ </TD>
+ </TR>
+ </TBODY>
+</TABLE>
+<P CLASS="western"><BR><BR>
+</P>
+<P CLASS="western">Note this</P>
+<P CLASS="western">If a job will be a synchronous one – he
+shouldn't show any UI during his execution. Because nobody knows the
+time when this job will be triggered and executed. And any UI dialogs
+can produce many trouble if the come at wrong time.</P>
+<P CLASS="western"><BR><BR>
+</P>
+<P CLASS="western">Example</P>
+<P CLASS="western">Following sequence diagram shows an example job
+which is triggered for an „event1“. He gets his own
+configuration data which includes a „count“ value. The
+job increased and checked it. In case of „count==1“ he
+knows that it was the first execution and he invite the job executor
+to save some configuration data for it – which means especialy
+the count value. But the job shouldn't be deactivated. If next
+„event1“ is triggered the job is started again and gets
+his count information. He found out that it was the second execution
+and decide to be deactivated from now. He invite the job executor and
+this service deactivate it inside the configuration.</P>
+<P CLASS="western"><BR><BR>
+</P>
+<P CLASS="western"><IMG SRC="job_executor.gif" NAME="Objekt1" ALIGN=LEFT ><BR CLEAR=LEFT><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/drafts/contribution.html b/content/framework/drafts/contribution.html
new file mode 100644
index 0000000..f2b59d5
--- /dev/null
+++ b/content/framework/drafts/contribution.html
@@ -0,0 +1,202 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+ <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+ <title>Patch Contributors</title>
+
+
+</head>
+
+
+<body>
+
+<h2>Patch Contributors</h2>
+
+Patches of are most welcome by the framework project. Those who submit
+patches deserve a
+lot of credit for dealing with a build enviornment which to say the
+very least can be intimating. To acknowledge the efforts of these
+people and the work they have put in here is a little info on them. If
+I have forgotten anyone here or there was omissions or something just
+plain wrong send an <a href="mailto:cd@openoffice.org">email</a>.<br>
+
+<br>
+
+<table>
+
+ <thead> <tr style="color: rgb(255, 255, 255); font-weight: bold;">
+
+ <td style="background-color: rgb(0, 49, 90); text-align: center;" color="#ffffff" background-color="#00315a" text-align="center" vertical-align="middle" colspan="4">Contributors</td>
+
+ </tr>
+
+ <tr class="liteblue-back">
+
+ <th bgcolor="#99ccff">Name</th>
+
+ <th bgcolor="#99ccff">Email</th>
+
+ <th bgcolor="#99ccff">Comment</th>
+
+ <th bgcolor="#99ccff">Issues</th>
+
+ </tr>
+
+ </thead><tbody>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">kendy</td>
+
+ <td style="background-color: rgb(204, 204, 204);">kendy {at} openoffice.org</td>
+
+ <td style="background-color: rgb(204, 204, 204);">A big and nice patch which improves the handling of
+accelerator configuration files. </td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=64717">64717</a></td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">kendy</td>
+
+ <td style="background-color: rgb(204, 204, 204);">kendy {at} openoffice.org</td>
+
+ <td style="background-color: rgb(204, 204, 204);">Fixes a problem that the crash reporter starts although
+disabled by a configuration entry</td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=65325">65325</a></td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">cmc</td>
+
+ <td style="background-color: rgb(204, 204, 204);">cmc
+{at} openoffice.org</td>
+
+ <td style="background-color: rgb(204, 204, 204);">Fixes
+a possible crash browsing in the macro dialog</td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=67976">67976</a></td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">cmc</td>
+
+ <td style="background-color: rgb(204, 204, 204);">cmc
+{at} openoffice.org</td>
+
+ <td style="background-color: rgb(204, 204, 204);">Fixes
+a small user interface problem in the OpenOffice.org
+Java configuration dialog. </td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=68018">68018</a></td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">beppec56<br>
+
+ </td>
+
+ <td style="background-color: rgb(204, 204, 204);">beppec56
+{at} openoffice.org<br>
+
+ </td>
+
+ <td style="background-color: rgb(204, 204, 204);">A
+nice patch which solves problems with links to external files within
+documents that should be send via e-Mail as PDF documents.<br>
+
+ </td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=68777">68777<br>
+
+ </a> </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">rail<br>
+
+ </td>
+
+ <td style="background-color: rgb(204, 204, 204);">rail
+{at] openoffice.org<br>
+
+ </td>
+
+ <td style="background-color: rgb(204, 204, 204);">A
+patch which fixes problems with the russian father's name in the
+'Tools-Option-OpenOffice-UserData' tab page.<br>
+
+ </td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=69133">69133<br>
+
+ </a></td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">kendy<br>
+
+ </td>
+
+ <td style="background-color: rgb(204, 204, 204);">kendy
+{at] openoffice.org<br>
+
+ </td>
+
+ <td style="background-color: rgb(204, 204, 204);">A
+patch which solves the problem that csv files stored with xls
+extension are opened in Writer instead of Calc</td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=70809">70809</a></td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">cmc</td>
+
+ <td style="background-color: rgb(204, 204, 204);">cmc
+{at} openoffice.org</td>
+
+ <td style="background-color: rgb(204, 204, 204);">Fixes
+a problem where a deleted pointer was returned</td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=71284">71284</a></td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(204, 204, 204);">mmeeks</td>
+
+ <td style="background-color: rgb(204, 204, 204);">mmeeks
+{at} openoffice.org</td>
+
+ <td style="background-color: rgb(204, 204, 204);">Fixes
+problems with GTK based quickstarter</td>
+
+ <td style="background-color: rgb(204, 204, 204);"><a href="http://www.openoffice.org/issues/show_bug.cgi?id=71567">71567</a></td>
+
+ </tr>
+
+ </tbody>
+</table>
+
+<br>
+
+</body>
+</html>
diff --git a/content/framework/drafts/documents.html b/content/framework/drafts/documents.html
new file mode 100644
index 0000000..a6d3bd2
--- /dev/null
+++ b/content/framework/drafts/documents.html
@@ -0,0 +1,207 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+ <title>Documents</title>
+</head>
+<body>
+<center>
+<table bgcolor="#f0f0f0" border="0" cellpadding="10" cellspacing="0" width="100%">
+
+ <col width="88*"> <col width="107*"> <col width="61*"> <tbody>
+
+ <tr>
+
+ <td colspan="3" bgcolor="#00315a" width="100%">
+ <p align="center"><font color="#ffffff"><comment title=" 1. row: "Documentation" 100% with " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 1. row: "Documentation" 100% with --></comment><font face="Arial, Helvetica"><font size="2"><b>Documents<comment title=" 2. row: "Title" & "Description" & "Author" 40/40/20% for every column " xmlns="http://disruptive-innovations.co [...]
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td bgcolor="#99ccff" width="34%">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Title
+ </b></font></font></font> </p>
+
+ </td>
+
+ <td bgcolor="#99ccff" width="42%">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Description
+ </b></font></font></font> </p>
+
+ </td>
+
+ <td bgcolor="#99ccff" width="24%">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Author<comment title=" 3. row: first content line dialog proposal " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 3. row: first content line dialog proposal --></comment></b></font></font></font></p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0" width="34%">
+ <p align="left"><a href="../documentation/filters/index.html"><font size="2"><font face="Arial, Helvetica">Implementation and registrations of
+filtes</font></font></a> </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="42%">
+ <p align="left"><font face="Arial, Helvetica"><font size="2">How to implement import or export filters and
+document loaders for OpenOffice.org</font></font></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Andreas Schlüns <br>
+
+ <a href="mailto:andreas.schluens@sun.com">andreas.schluens@sun.com
+ </a></font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td width="34%">
+ <p><font size="2"><font face="Arial, Helvetica"><a href="../documentation/mimetypes/mimetypes.html">Mime Content
+Types used in OpenOffice</a> </font></font> </p>
+
+ </td>
+
+ <td width="42%">
+ <p><font face="Arial, Helvetica"><font size="2">Description of the Mime Content Types used in
+OpenOffice and in StarOffice 4.x/5.x</font></font></p>
+
+ </td>
+
+ <td width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Mikhail Voitenko<br>
+
+ <a href="mailto:mikhail.voitenko@sun.com">mikhail.voitenko@sun.com</a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td width="34%">
+ <p><font size="2"><font face="Arial, Helvetica"><a href="../documentation/filterui/index.html">Java application
+"FilterUI"</a> </font></font> </p>
+
+ </td>
+
+ <td width="42%">
+ <p><font face="Arial, Helvetica"><font size="2">Application to administrate filter configuration
+data of office and demonstrate using of filter api</font></font></p>
+
+ </td>
+
+ <td width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Andreas Schlüns<br>
+
+ <a href="mailto:andreas.schluens@sun.com">andreas.schluens@sun.com</a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td width="34%">
+ <p><a href="../documentation/devmanual/draft.sxw"><font size="2"><font face="Arial, Helvetica">Preliminary
+developer documention for the framework module</font></font></a></p>
+
+ </td>
+
+ <td width="42%">
+ <p><font size="2"><font face="Arial, Helvetica">Some chapters of the upcoming
+developers manual in draft state. Some chapters are still not finished
+and will be added later.<br>
+
+Currently no diagrams and no source code snippets are provided. Java
+example code that illustrates the outlined concepts can be found in the
+ <a href="http://api.openoffice.org/source/browse/api/devmanual/OfficeDev/samples/DesktopEnvironment/">api
+project.</a></font></font></p>
+
+ <p><font size="2"><font face="Arial, Helvetica">You must reckon on this
+documentation being changed a little bit until the final release.<br>
+
+The current office builds still behave a little bit different than
+outlined in the documentation. These differences and also some known
+bugs are documented in <a href="../documentation/devmanual/bugs.sxw">a
+separated file</a>.</font></font></p>
+
+ </td>
+
+ <td width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Mathias Bauer<br>
+
+ <a href="mailto:mathias.bauer@sun.com">mathias.bauer@sun.com</a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td width="34%">
+ <p><a href="../documentation/others/index.html"><font size="2"><font face="Arial, Helvetica">Documentation
+collection for the framework module</font></font></a></p>
+
+ </td>
+
+ <td width="42%">
+ <p><font face="Arial, Helvetica"><font size="2">Its the first draft of some documentations for the
+framework module which describes the supported features and some
+internal mechanism of it. </font></font> </p>
+
+ </td>
+
+ <td width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Andreas Schlüns<br>
+
+ <a href="mailto:andreas.schluens@sun.com">andreas.schluens@sun.com</a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td width="34%">
+ <p><a href="../scripting/index.html"> <font size="2"><font face="Arial, Helvetica">Scripting
+Framework </font></font> </a></p>
+
+ </td>
+
+ <td width="42%">
+ <p> <font face="Arial, Helvetica"><font size="2"> This is the home page of the Scripting Framework
+for OpenOffice.org. </font></font> </p>
+
+ </td>
+
+ <td width="24%">
+ <p align="right"> <font size="2"><font face="Arial, Helvetica">Andreas Bregas<br>
+
+ <a href="mailto:andreas.bregas@sun.com">andreas.bregas@sun.com</a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ </tbody>
+</table>
+
+</center>
+</body>
+</html>
diff --git a/content/framework/drafts/modules.html b/content/framework/drafts/modules.html
new file mode 100644
index 0000000..44d4511
--- /dev/null
+++ b/content/framework/drafts/modules.html
@@ -0,0 +1,193 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+ <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
+ <title>Modules</title>
+
+
+</head>
+
+
+<body>
+
+<table style="width: 100%;" border="0" cellpadding="4" cellspacing="0">
+
+ <tbody>
+
+ <tr>
+
+ <td style="width: 1%; vertical-align: top;" rowspan="9">
+ <p></p>
+
+ <p><br>
+
+ </p>
+
+ </td>
+
+ <td style="background-color: rgb(0, 49, 90);" colspan="2">
+ <p align="center"><font color="#ffffff"><font face="Arial, Helvetica"><font size="2"><b>Modules
+in Application Framework Project </b></font></font></font>
+ </p>
+
+ </td>
+
+ <td rowspan="9" style="width: 1%; vertical-align: top;">
+ <p><br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <th style="background-color: rgb(153, 204, 255); width: 15%;">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Module
+ </b></font></font></font> </p>
+
+ </th>
+
+ <th style="background-color: rgb(153, 204, 255); width: 85%;">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Function
+ </b></font></font></font> </p>
+
+ </th>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="background-color: rgb(240, 240, 240);">
+ <p><tt><tt>sfx2</tt></tt></p>
+
+ </td>
+
+ <td style="background-color: rgb(240, 240, 240);">
+ <p><tt>The SFX is the core of the framework. It is
+built on the "Template" pattern and so it is comparable to the
+Microsoft Foundation Classes (MFC) library. This means that it uses
+base classes for documents and views to build up the common behaviour (
+the "framework" ) of all components. This covers state and interaction
+of the components. The specialized behaviour of the individual
+components like Writer, Calc etc. is customized through classes derived
+from the base classes. <br>
+
+There are other helper classes also. For example, helper classes are
+used to execute commands, for example commands from a toolbar button.
+These helper classes also communicate state information. There are also
+other helper classes for building the user interface and the object
+persistance.</tt></p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0">
+ <p><tt><tt>res</tt></tt></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="61%">
+ <p><tt>Contains typical resource files such as
+bitmaps, icons, and cursor files. </tt> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0">
+ <p><tt><tt>idl</tt></tt></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="61%">
+ <p><tt>All SFX based components contain Interface
+definition Language (IDL) files. These files are compiled with the IDL
+compiler for the SFX framework. It does not generate code, but
+generates definition ( header ) files used in the components code.</tt></p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0">
+ <p><tt><tt>framework</tt></tt></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="61%">
+ <p><tt>Integrates the application components in
+different environments like a desktop or a browser plugin etc. It
+integrates SFX based components as well as other components not based
+on SFX. The integration base is the frame package of the OpenOffice
+API. <br>
+
+The framework module is also responsible for the content detection and
+content activation.</tt></p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0">
+ <p><tt><tt>desktop</tt></tt></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="61%">
+ <p><tt>The code for the office executable, based on
+the offmgr module.</tt></p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0">
+ <p><tt><tt>DocumentProperties</tt></tt></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="61%">
+ <p><tt>Makes properties of the documents available
+through OpenOffice API.<comment title=" Page End " xmlns="http://disruptive-innovations.com/zoo/nvu"><!-- Page End --></comment><comment title=" footer " xmlns="http://disruptive-innovations.com/zoo/nvu"><!-- footer --></comment></tt></p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0">
+ <p><tt><tt>scripting</tt></tt></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="61%">
+ <p><tt><tt>Scripting Framework which allows
+OpenOffice.org to be scripted in multiple languages. You can view the
+source code <a href="../source/browse/framework/scripting">here</a>,
+and the module home page <a href="../scripting/index.html">here</a>.
+ </tt></tt></p>
+
+ </td>
+
+ </tr>
+
+ </tbody>
+</table>
+
+</body>
+</html>
diff --git a/content/framework/drafts/proposals.html b/content/framework/drafts/proposals.html
new file mode 100644
index 0000000..ed9cb96
--- /dev/null
+++ b/content/framework/drafts/proposals.html
@@ -0,0 +1,231 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+ <title>Proposals</title>
+</head>
+<body>
+<h3>Proposals</h3>
+
+<center>
+<table style="background-color: rgb(255, 255, 255); width: 100%;" border="0" cellpadding="10" cellspacing="0">
+
+ <col width="97*"> <col width="98*"> <col width="61*"> <tbody>
+
+ <tr>
+
+ <td colspan="3" bgcolor="#00315a" width="100%">
+ <p align="center"><font color="#ffffff"><comment title=" 1. row: "Documentation" 100% with " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 1. row: "Documentation" 100% with --></comment><font face="Arial, Helvetica"><font size="2"><b>Proposals<comment title=" 2. row: "Title" & "Description" & "Author" 40/40/20% for every column " xmlns="http://disruptive-innovations.co [...]
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="background-color: rgb(153, 204, 255); width: 30%;">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Title
+ </b></font></font></font> </p>
+
+ </td>
+
+ <td style="background-color: rgb(153, 204, 255); width: 50%;">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Description
+ </b></font></font></font> </p>
+
+ </td>
+
+ <td style="background-color: rgb(153, 204, 255); width: 20%;">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Author<comment title=" 3. row: first content line dialog proposal " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 3. row: first content line dialog proposal --></comment></b></font></font></font></p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html"><font size="2"><font face="Arial, Helvetica">New keyboard shortcut configuration. </font></font></a>
+ </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><font face="Arial, Helvetica"><font size="2">The current keyboard shortcut configuration is
+based on a sfx implementation that doesn't support our new components
+that are not sfx based. We need for accessibility a new implementation
+to support a better keyboard shortcut configuration, too.l </font></font>
+ </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Carsten Driesner <br>
+
+ <a href="mailto:carsten.driesner@sun.com">carsten.driesner@sun.com<comment title=" 4. row: second content line system integration " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 4. row: second content line system integration --></comment></a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/dialogs/index.html"><font size="2"><font face="Arial, Helvetica">New dialog size and
+a modified tab page handling. </font></font></a> </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><font face="Arial, Helvetica"><font size="2">The current standard size of the tabbed dialogues
+is not large enough. Due to this fact we are running into trouble
+especially for the CJK–version of OpenOffice / StarOffice ...
+ </font></font> </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Christian Jansen <br>
+
+ <a href="mailto:christian.jansen@sun.com">christian.jansen@sun.com<comment title=" 4. row: second content line system integration " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 4. row: second content line system integration --></comment></a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><a href="file:///D:/prj/framework/framework/www/framework/www/proposals/printing/Standard_Printer.htm"><font size="2"><font face="Arial, Helvetica">Standard
+printer definition</font></font></a> </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><font face="Arial, Helvetica"><font size="2">New definition of which printer will be used if a
+document will be printed via the direct print button in the objectbar
+of OO</font> (<font size="2">Realized as a HTML
+document)</font></font></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Frank Loehmann <br>
+
+ <a href="mailto:frank.loehmann@sun.com">frank.loehmann@sun.com<comment title=" HelpAgent " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- HelpAgent --></comment></a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/apply/new_preview_concept.html"><font size="2"><font face="Arial, Helvetica">Preview feature in dialogs</font></font></a> </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><font face="Arial, Helvetica"><font size="2">This proposal is about a Preview feature to be used
+in dialogs. It presents an alternative to the formerly proposed Apply
+button concept.</font> ( <font size="2">Realized as
+a HTML document)</font></font></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="24%">
+ <p align="right"><font face="Arial, Helvetica"><font size="2">Frank Loehmann</font></font></p>
+ <p align="right"><font size="2"><font face="Arial, Helvetica"><a href="mailto:frank.loehmann@sun.com">frank.loehmann@sun.com</a></font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/filterfactory/proposal_filterfactory.html"><font size="2"><font face="Arial, Helvetica">Change mechanism for searching and creating filters </font></font></a>
+ </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><font face="Arial, Helvetica"><font size="2">Our current mechanism to search and create filters
+which are registered for types is not really understandable for api
+user. This proposal describes a better but incompatible way to make it
+easier ... </font></font> </p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Andreas Schlüns<br>
+
+ <a href="mailto:andreas.schluens@sun.com">andreas.schluens@sun.com</a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/macro/macrorecording.html"><font size="2"><font face="Arial, Helvetica">Problems with and proposals for
+macro recording</font></font></a></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><font face="Arial, Helvetica"><font size="2">OpenOffice.org does not contain a macro recorder.
+The problems are described and some possible solutions are discussed</font></font></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Mathias Bauer<br>
+
+ <a href="mailto:mathias.bauer@sun.com">mathias.bauer@sun.com</a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/filters/exportfilters.html"><font size="2"><font face="Arial, Helvetica">Unifying the filter API for storing
+and exporting documents</font></font></a></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="38%">
+ <p align="left"><font face="Arial, Helvetica"><font size="2">The OpenOffice.org filter API is used for loading
+and storing documents, but some special export functionality is not
+usable through this API (f.e. Impress export filters). This proposal
+tries to unify all filters and their API.</font></font></p>
+
+ </td>
+
+ <td bgcolor="#f0f0f0" width="24%">
+ <p align="right"><font size="2"><font face="Arial, Helvetica">Mathias Bauer<br>
+
+ <a href="mailto:mathias.bauer@sun.com">mathias.bauer@sun.com</a>
+ </font></font> </p>
+
+ </td>
+
+ </tr>
+
+ </tbody>
+</table>
+
+</center>
+
+<h3><br>
+</h3>
+</body>
+</html>
diff --git a/content/framework/index.html b/content/framework/index.html
new file mode 100644
index 0000000..ad7942b
--- /dev/null
+++ b/content/framework/index.html
@@ -0,0 +1,564 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+
+ <meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1">
+ <title>index</title>
+
+
+ <meta name="GENERATOR" content="StarOffice 6.1 BETA1 (Linux)">
+
+ <meta name="CREATED" content="20001011;13012900">
+
+ <meta name="CHANGEDBY" content="tom o connor">
+
+ <meta name="CHANGED" content="20021120;17214600">
+
+</head>
+
+
+<body lang="de-DE">
+
+<p style="margin-bottom: 0cm;"><br>
+
+</p>
+
+<br>
+
+<table style="width: 100%;" border="0" cellpadding="4" cellspacing="0">
+
+ <col width="3*"> <col width="93*"> <col width="157*"> <col width="3*"> <tbody>
+
+ <tr>
+
+ <td colspan="4" valign="top" width="100%">
+ <h1>Application Framework Project</h1>
+
+ <p><b>Project Owner:</b><a href="mailto:carsten.driesner@sun.com"> Carsten Driesner</a>
+ </p>
+
+ <p>This project contains modules, that define the general
+behaviour of the OpenOffice application components ( Writer, Calc etc.
+). This covers common operations, common objects or functionality on
+one hand and a module for the integration of the components into the
+external environment on the other hand. While the latter one is done by
+the framework module, the first is done by the sfx2 module.</p>
+
+ <big>The application framework project has a<a href="http://wiki.services.openoffice.org/wiki/framework">
+wiki page</a>. We want to move
+to the wiki in the near future! </big>
+ <p>The sfx2 module offers a complete set of features for an
+application component, the most important are: </p>
+
+ <ul>
+
+ <ul>
+
+ <ul>
+
+ <li>document persistance; loading and saving through
+UCB
+access</li>
+
+ <li>compound document support, inplace editing</li>
+
+ <li>multiple and different views for a document</li>
+
+ <li>context sensitive user interface</li>
+
+ <li>command dispatching infrastructure</li>
+
+ <li>template handling</li>
+
+ <li>docking windows</li>
+
+ </ul>
+
+ </ul>
+
+ </ul>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="width: 1%; vertical-align: top;" rowspan="9">
+ <p><br>
+
+ </p>
+
+ </td>
+
+ <td style="background-color: rgb(0, 49, 90);" colspan="2">
+ <p align="center"><font color="#ffffff"><font face="Arial, Helvetica"><font size="2"><b>Modules
+in Application Framework Project </b></font></font></font>
+ </p>
+
+ </td>
+
+ <td rowspan="9" valign="top" width="1%">
+ <p><br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <th style="background-color: rgb(153, 204, 255); width: 15%;">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Module
+ </b></font></font></font> </p>
+
+ </th>
+
+ <th style="background-color: rgb(153, 204, 255);" width="61%">
+ <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Function
+ </b></font></font></font> </p>
+
+ </th>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="background-color: rgb(240, 240, 240); font-family: monospace;">
+ <p>sfx2</p>
+
+ </td>
+
+ <td style="background-color: rgb(240, 240, 240); width: 85%; font-family: monospace;">
+ <p>The SFX is the core of the framework.</p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>res</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Contains typical resource files such as
+bitmaps, icons, and cursor files. </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>idl</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>IDL
+compiler for the SFX framework. It generates definition (header) files
+used in the components code.</p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>framework</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Integrates the application components in
+different environments like a desktop or a browser plugin etc. The
+framework module is also responsible for the content detection and
+content activation.</p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>desktop</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>The code for the office executable.</p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>DocumentProperties</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Makes properties of the documents available
+through OpenOffice API.</p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>scripting</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Scripting Framework which allows
+OpenOffice.org to be scripted in multiple languages. You can find the
+module home page <a href="scripting/index.html">here</a>.
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>tools</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Contains base classes, like string, date, time, streams,
+and so on. These classes do not need a UI system, so you can also use
+them in an character based user interface.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>svtools</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Tools layered on top of VCL.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>std2</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Contains the STLport 3.5.1-a derivative from the SGI/STL.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>io</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Contains basic UNO I/O services for streaming (Pipe,
+DataStreams, MarkableStreams) and interprocess connections (sockets and
+pipes).</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p>eventattacher</p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Component-based event handling.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p><code>unzip</code></p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>The freeware infozip compression library.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p><code>unotools</code></p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Helper classes that provide UNO-based APIs.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p><code>extensions</code></p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Independent UNO Components for various purposes like
+OLE, PGP and Speech.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p><code>external</code></p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Contains stubs or makefiles for external components.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p><code>configmgr</code></p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Registry client containing UNO Components for
+Configuration access.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p><code>officecfg</code></p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Contains the configuration schemas for applications and
+components.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p><code>sot</code></p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Microsoft Office compatible storage implementation.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+ <td style="font-family: monospace;" bgcolor="#f0f0f0">
+ <p><code>automation</code></p>
+
+ </td>
+
+ <td style="font-family: monospace;" bgcolor="#f0f0f0" width="61%">
+ <p>Stub for testing framework for automated testing.<br>
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td></td>
+
+ <td></td>
+
+ <td>A more comprehensive description of the application
+framework modules can be found <a href="drafts/modules.html">here</a>.</td>
+
+ <td></td>
+
+ </tr>
+
+ </tbody>
+</table>
+
+<h3>Documentation/Examples/Add-ons</h3>
+
+There are several documents available which describe
+features, provide valuable information about the framework
+internals.
+We also offer some example <a href="http://framework.openoffice.org/servlets/ProjectDocumentList?folderID=226&expandFolder=226&folderID=0">add-ons</a>
+which show interesting features of the
+framework UNO API. Most documents/add-ons are available <a href="http://framework.openoffice.org/servlets/ProjectDocumentList">via
+download as OpenOffice.org documents</a>. There is a second
+section which presents <a href="drafts/documents.html">online
+documents</a>.<br>
+
+<br>
+
+<h3>To Do List</h3>
+
+<p>You can find a list of tasks that we would like to implement
+but
+until now didn't find the time to do so. These tasks can be implemented
+by experienced C++ developers that want to help us. You would
+definitely get support or help of the regular framework developers. If
+you are interested to work on one of these tasks please contact us on
+our "dev" mailing list or via e-mail to the framework project lead.</p>
+
+<ul>
+
+ <li> Vista Shell Extensions
+ <ul>
+
+ <li> #<a href="https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i72556" class="external text" title="https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i72556" rel="nofollow">i72556</a># Use new FileOpenDialog. OOo
+should support the same Look & Feel then other Vista programs
+does.
+ </li>
+
+ <li> #<a href="https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i71112" class="external text" title="https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i71112" rel="nofollow">i71112</a># Desktop full text search in
+ODF Documents doesn't work.
+ </li>
+
+ <li> #<a href="https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i70944" class="external text" title="https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i70944" rel="nofollow">i70944</a># Meta information will not
+shown in explorer.
+ </li>
+
+ </ul>
+
+ </li>
+
+ <li>OpenOffice.org startup.
+Optimizing
+the startup process, find bottlenecks and refactor libraries so we
+don't load unnecessary code.</li>
+
+ <li>Toolbar and popup menu
+controllers which are more powerful and easier to use than the current
+ones.</li>
+
+ <li>Cleanup the svtools configuration items (make them
+write-through
+instead of write-back with their own cache) to support immediate
+updates on configuration changes.</li>
+
+ <li>Update the 'Tools - Options' dialogs to support the
+read-only OpenOffice.org configuration item state.</li>
+
+ <li>A search toolbar as an extensions (see Firefox search bar)
+ </li>
+
+ <li> Add support for user-defined properties in the document
+properties dialog
+ </li>
+
+ <li> Brush-up the "Styles and Formatting" floating window
+ </li>
+
+ <li> Brush-up the "Templates" dialog
+ </li>
+
+ <li> User interface to associate templates to existing
+documents
+ </li>
+
+</ul>
+
+<h3>Contributions</h3>
+
+We had several valuable contribution from the community. <a href="drafts/contribution.html">Here</a> is a
+list of contributors with some information on
+what they have done and who they are. Credit where credit is due as
+they say.<br>
+
+<br>
+
+<h3><a name="Proposals"></a><!-- Table for proposals -->Proposals</h3>
+
+We have a <a href="drafts/proposals.html">list of
+proposal documents</a> which describe how we can
+solve various problems, create a better user interface and other
+framework related tasks.
+<span style="font-weight: bold;"></span>
+</body>
+</html>
diff --git a/content/framework/proposals/apply/apply_button_spec.htm b/content/framework/proposals/apply/apply_button_spec.htm
new file mode 100644
index 0000000..085dc0a
--- /dev/null
+++ b/content/framework/proposals/apply/apply_button_spec.htm
@@ -0,0 +1,266 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="AUTHOR" CONTENT=" ">
+ <META NAME="CREATED" CONTENT="20010105;8322800">
+ <META NAME="CHANGEDBY" CONTENT=" ">
+ <META NAME="CHANGED" CONTENT="20010216;14322466">
+</HEAD>
+<BODY>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="SunSans-Heavy"><FONT SIZE=4 STYLE="font-size: 16pt">Proposal
+for the Use of an Apply Button in Dialogs</FONT></FONT></P>
+<P ALIGN=CENTER><FONT FACE="SunSans-Heavy"><FONT SIZE=4>Version 1</FONT></FONT></P>
+<P ALIGN=CENTER><FONT FACE="Times New Roman, serif">Date: February
+14<SUP>th</SUP>, 2001</FONT></P>
+<P ALIGN=CENTER>David Engen, Andrea Mankoski, Leyla Schroeder</P>
+<H1><B>Introduction</B></H1>
+<H2><B>User Problem Being Addressed</B></H2>
+<P STYLE="font-style: normal; text-decoration: none">These guidelines
+for the placement and functionality of a standard "apply button
+set" in dialog boxes have been developed to facilitate the
+process of finely adjusting objects within StarOffice /
+OpenOffice.org documents. The benefit is that users will be able to
+see their changes immediately reflected in the context of the
+document while the dialog box is still open. Users frequently want to
+make iterative changes to the selection, and if the dialog closes as
+each change is made, it is inefficient to re-open the dialog multiple
+times.</P>
+<P STYLE="font-style: normal; text-decoration: none">The "Apply
+button" functionality was deemed as a necessary tool for the
+medium-skill to advanced-skill user to avoid tedious command
+repetitions and for efficiency. Because this functionality will
+replace several other button sets, it is important that while it
+helps with efficiency to the advanced user, it does not hinder novice
+or cross-over users.</P>
+<H2><B>Project Definition</B></H2>
+<P>The proposed guidelines set standards for the placement of a
+"standard set of Apply buttons" as well as the behavior of
+each of the buttons in the set. Inclusion and exclusion principles
+have been established to more clearly state when and when not to use
+this functionality. It clearly states what buttons should be included
+in the "standard set of Apply buttons", what types of
+dialog boxes they should be used with, and their location and
+arrangement in those appropriate dialog boxes.</P>
+<P>In addition to guidelines for the use of the standard set of apply
+buttons, a non-exhaustive list of dialog boxes to which it might be
+useful to add the standard set of apply buttons has been included -
+these can be found in the Appendix. Dialog boxes in four modules of
+StarOffice / Openoffice.org (Writer, Calc, Impress, Draw) were
+examined to see whether they warranted the Apply functionality.
+Because of the variation in conditions under which these buttons can
+be used, some dialog boxes were verified individually. All of those
+mentioned in this specification were found under the Format menus on
+the main menu bar of StarOffice v5.2. There is some overlap from
+module to module, but there are also dialog boxes that are
+module-specific.</P>
+<P>In summary, this report provides inclusion and exclusion
+guidelines, button configuration and behavior guidelines, scenario
+descriptions, and screen-shots of some of the dialog boxes that may
+be affected by the implementation of this functionality.</P>
+<H2><B>Related and Competitive Products</B></H2>
+<P>StarOffice v5.2 used several variations of an Apply button without
+any apparent standardization measures, and this functionality is not
+new. Some examples of programs that have already implemented similar
+functionality are: for Windows Display and Desktop Themes (Start -
+Settings - Control Panel - Display/Desktop Themes); and for GNOME the
+Panel Properties dialog. This dialog shows a button set with <SPAN STYLE="background: transparent">"OK",
+"Apply", "Close", "Help", t</SPAN>hough
+in the desktop's Control Center <SPAN STYLE="background: transparent">(Main
+Menu Button - Programs - Settings - Desktop - Panel) </SPAN>you can
+find a set with <SPAN STYLE="background: transparent">"Try",
+"Revert", "OK", and "Cancel".</SPAN></P>
+<P STYLE="margin-bottom: 0cm"><B>Note:</B></P>
+<P STYLE="margin-bottom: 0cm">The Assign button that can be found in
+several dialog boxes in StarOffice / OpenOffice.org Draw (i.e. Format
+- 3D Graphics) is not dealt with in this HCI Specification. It is
+suggested that when the behavior of those Assign buttons is identical
+to that of the Apply button, the mouse-over tip for the assign button
+be changed from "Assign" to "Apply" to avoid
+confusion. Otherwise, the name of this command should be changed to
+something less ambiguous.</P>
+<H1><A NAME="Main"></A>Basic Functionality</H1>
+<P>It is recommended that dialog boxes employ the standard set of
+apply buttons: "OK", "Apply", "Reset",
+and "Close". Because it is also useful to be able to find
+contextual help from each of those dialog boxes, the standard button
+set will also include a "Help" button. The buttons order
+and layout can be seen in Figure 1.</P>
+<P ALIGN=CENTER><IMG SRC="oarch.gif" NAME="Graphic3" ALIGN=BOTTOM WIDTH=517 HEIGHT=25 BORDER=0>
+<BR><B>Figure 1:</B> This is what the button layout and order should
+be for dialog boxes that require the standard set of apply buttons.
+</P>
+<P>The buttons should be aligned along the bottom of the dialog boxes
+in question and should be referred to as "the standard set of
+apply buttons". Their behavior is as follows:</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">When a user clicks the OK button,
+ the settings should be saved and the commands specified in the
+ dialog box should be carried out. The dialog box should then be
+ closed.</P>
+ <LI><P STYLE="margin-bottom: 0cm">When a user clicks the Apply
+ button from the main dialog box, changes are applied to the selected
+ object within the document, but the dialog box is not closed.</P>
+ <LI><P STYLE="margin-bottom: 0cm">When a user clicks the Reset
+ button from the main dialog box, the settings in the dialog box are
+ returned to their values as per the last Apply command. If the user
+ has opened the dialog and has made changes but has not yet clicked
+ the Apply button, the settings are returned to the values
+ corresponding to when they first opened the dialog box. The Reset
+ button does not close the dialog box.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">When a user makes changes to the
+ values in the dialog box and clicks the Close button from the main
+ dialog box without first clicking Apply, an alertbox like the one
+ shown below should be displayed to allow them to continue without
+ losing any information.</P>
+ <LI><P>The Help button invokes the standard Help Tool window
+ contextualized to the dialog box in question.</P>
+</UL>
+<P ALIGN=CENTER><IMG SRC="apply_alert.gif" NAME="Graphic2" ALIGN=BOTTOM WIDTH=280 HEIGHT=105 BORDER=0></P>
+<P ALIGN=CENTER><FONT SIZE=2 STYLE="font-size: 9pt"><B>Figure 2:</B>
+This is the alert-box that is displayed if a user clicks the Close
+button and there are changed settings that have not yet been applied
+to the document. </FONT>
+</P>
+<P>The wording of the text within the alert-box is modeled after
+phrasing that is already used throughout StarOffice 5.2. It should
+read: "Settings have been modified. Do you want to apply your
+changes?" The alert-box is similar to that which appears when a
+user attempts to close a document without saving its contents first.
+The behavior of each button in this alert-box is as follows:</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">When a user clicks the Apply
+ button in the alert-box, the changes they made to the values within
+ the main dialog box will be applied to the selection in the
+ document, and the dialog box is closed.</P>
+ <LI><P STYLE="margin-bottom: 0cm">When a user clicks the Discard
+ button in the alert-box, the changes they made to the values within
+ the main dialog box should <I>not</I><SPAN STYLE="font-style: normal">
+ be applied, and the dialog box should be closed.</SPAN></P>
+ <LI><P>When a user clicks the Cancel button in the alert-box, the
+ alert-box should be closed but the changes should <I>not</I> be
+ applied and the user should be returned to the main dialog box.
+ </P>
+</UL>
+<H2><B>Mouseless navigation</B></H2>
+<P STYLE="margin-bottom: 0cm">Mouseless navigation and keyboard
+traversal should work as in other StarOffice / OpenOffice.org dialog
+boxes employing default buttons, mnemonics, and full keyboard access.</P>
+<H2>Mnemonics</H2>
+<P STYLE="margin-bottom: 0cm">For accessibility reasons, mnemonics
+have been added to the Apply and Reset buttons. The Close button does
+not require one because the Escape key defaults to Close in a dialog
+box. The letters "a" and "r" have been chosen as
+the mnemonics for Apply and Reset respectively. The letter "h"
+will remain as the default for Help as is standard.</P>
+<H2>"Undo" Command Protection</H2>
+<P STYLE="margin-bottom: 0cm">To ensure that users have a safety net,
+they should always be allowed to undo commands that were invoked
+through an Apply button in a dialog box. The current behavior in one
+of the few modeless dialog box that currently (v5.2) contains an
+Apply button (Insert - Hyperlink) is to undo each of the apply
+commands individually, even if the selection has been changed. It is
+suggested that modal dialog boxes follow this behavior as closely as
+possible for the sake of consistency. This means that for both modal
+and modeless dialog boxes the Undo command should only go as far back
+as one Apply command, and not as far as all the Apply commands
+invoked in the last instance of the dialog box.</P>
+<H1>Guidelines</H1>
+<H2>Inclusion Guidelines</H2>
+<P>The "standard set of apply buttons" should be used ... :
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">When it might be helpful to users
+ to make iterative changes to a selection within a document without
+ closing and re-opening the dialog box.</P>
+ <LI><P STYLE="margin-bottom: 0cm">Even in instances where the dialog
+ box presents the user with a preview of the changes in question.
+ This allows the user to view the object's properties in the context
+ of the document.</P>
+</UL>
+<H2>Exclusion Guidelines</H2>
+<P>The "standard set of apply buttons" should <I>not</I><SPAN STYLE="font-style: normal">
+be used ... :</SPAN></P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">If the changes applied to the
+ user's selection are not visibly noticeable. Dialog boxes that
+ contain visibly confirmable changes <I>and</I> non-visibly
+ confirmable changes may still use the apply button set, and should
+ apply both sets of changes.</P>
+ <LI><P STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">If
+ the changed settings will not immediately be reflected in the user's
+ document.</SPAN></P>
+ <LI><P STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">If
+ the Apply command is in reference to an action that will occur
+ within that specific dialog box. It should only be used when setting
+ are transferred from a dialog box directly to a document.</SPAN></P>
+ <LI><P STYLE="margin-bottom: 0cm">In any dialog box that is accessed
+ from within another dialog box (i.e. secondary, terciary, ... ).</P>
+ <LI><P STYLE="margin-bottom: 0cm">When the changes made in the
+ dialog box are immediately reflected in the document, as in an
+ inspector window.</P>
+</UL>
+<H2>Behavior Guidelines</H2>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">The Apply and Reset buttons should
+ be inactive(graye<SPAN STYLE="background: transparent">d out) when
+ the user first opens a dialog box that contains the standard set of
+ apply buttons. They should become active as soon as any of the
+ values are changed in that dialog box. As soon as the Apply or Reset
+ buttons are clicked, they should again revert to their greyed out
+ condition.</SPAN></P>
+ <LI><P STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">When
+ a user clicks the Apply button in a dialog box containing multiple
+ tabs, the settings in all tabs within that dialog box should be
+ applied, not only those in the active window. To be consistent, when
+ the Reset command is clicked, the settings in all tabs within that
+ dialog box should be reset.</SPAN></P>
+ <LI><P STYLE="margin-bottom: 0cm">The Reset button (that returns
+ settings to previously applied values) should not be confused for a
+ defaults button (that returns settings to program defaults). Dialog
+ boxes that need a Defaults button should present it separately from
+ the standard set of apply buttons.</P>
+</UL>
+<H1>Open Issues</H1>
+<H2>Button set</H2>
+<P>The account of buttons should be reduced to a minimum as too much
+buttons could be confusing for a user. Because of this two questions
+came up:</P>
+<UL>
+ <LI><P>It is not clear if the Reset button should be an optional
+ part of the button set. As there might be situations where an Apply
+ button would be useful, but a Reset button would not make so much
+ sense. An example are dialogs, where just some simple values are
+ entered, e.g. for adjusting the row height of a table (see Format –
+ Row – Height). The more complex the possible dialog settings
+ are, the more useful a Reset button would be. Should the Apply
+ button set always contain a Reset button?</P>
+ <LI><P>Can we find another solution for the Help button, for example
+ by replacing it with an icon? (As this also affects other dialogs,
+ that won't have an Apply button, this will probably be an open issue
+ for the future.)</P>
+</UL>
+<H2>Reset Button Behavior</H2>
+<P>The Reset button's current behavior allows users to revert the
+settings in the dialog box to their values as of the last Apply
+command. As we see it, there are several options here:</P>
+<OL>
+ <LI><P>Change the behavior of the Reset button to more of an Undo so
+ that it reverts the settings back to the values at the invocation of
+ the dialog box</P>
+ <LI><P>Eliminate the Reset button altogether to eliminate clutter,
+ still allowing the user to "cancel" their Apply commands
+ using the Undo function</P>
+ <LI><P>Leave the Reset button like it is.</P>
+</OL>
+<P>Again, there are other options that are listed here, but what is
+the best solution?</P>
+<HR>
+<P STYLE="margin-top: 0.42cm; page-break-after: avoid"><A HREF="apply_button_spec_appendix.html"><FONT SIZE=4><FONT FACE="Times New Roman, serif">Appendix
+ 1: Proposed Additions</FONT></FONT></A></P>
+<HR>
+</BODY>
+</HTML>
\ No newline at end of file
diff --git a/content/framework/proposals/apply/apply_button_spec_appendix.html b/content/framework/proposals/apply/apply_button_spec_appendix.html
new file mode 100644
index 0000000..28da0ca
--- /dev/null
+++ b/content/framework/proposals/apply/apply_button_spec_appendix.html
@@ -0,0 +1,105 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="CREATED" CONTENT="20010124;11183400">
+ <META NAME="CHANGEDBY" CONTENT=" ">
+ <META NAME="CHANGED" CONTENT="20010216;14401605">
+</head>
+<body>
+<H3>Apply Button Specification: Appendix #1 - Proposed Additions</H3>
+<P STYLE="margin-bottom: 0cm">When a module (e.g., StarOffice /
+OpenOffice.org Writer) is not specified, it is because the function
+appears in more than one, or perhaps in all four (Writer, Calc, Draw,
+Impress). This list of proposed additions is not exhaustive. A
+proposal that contains a list of dialogs is currently in work. The
+following are screen-shots of the revised dialog boxes.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><B>Format - Numbering / Bullets: </B>The
+"Remove" button should be exchanged for a "No Bullets"
+option. Change the "OK" button to "Apply", and
+the "Cancel" button to "Close". The buttons take
+on the configuration below. <BR>
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><IMG SRC="format_bullets.gif" NAME="Graphic15" ALIGN=BOTTOM BORDER=0></P>
+<P><BR><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><B>Format - Page: </B><SPAN STYLE="font-weight: medium">Change
+the "OK" button to "Apply", and the "Cancel"
+button to </SPAN>"Close". The buttons take on the
+configuration below.</P>
+<P STYLE="margin-bottom: 0cm"><B>Problem: </B>Under Page layout you
+can select for which layout the settings should be valid. Thus it can
+happen, that the settings made are not immediately visible in the
+document.<BR>
+</P>
+<P ALIGN=CENTER><IMG SRC="format_page.gif" NAME="Graphic16" ALIGN=BOTTOM 9 BORDER=0></P>
+<P STYLE="margin-bottom: 0cm"><B>Format - Paragraph: </B><SPAN STYLE="font-weight: medium">Change
+the "OK" button to "Apply", and the "Cancel"
+button to </SPAN>"Close". The buttons take on the
+configuration below.
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P ALIGN=CENTER><IMG SRC="format_paragraph.gif" NAME="Graphic17" ALIGN=BOTTOM BORDER=0></P>
+<P STYLE="margin-bottom: 0cm"><B>Format - Styles - Catalog:</B>
+Change the "OK" button to "Apply", the "Cancel"
+button to "Close" and add a "Reset" button. These
+buttons, along with the "Help" button, should appear at the
+bottom of the dialog box to distinguish them from contextual buttons
+such as "New", "Modify", "Delete", and
+"Organizer". The buttons take on the configuration below.
+<BR>
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><IMG SRC="format_styles.gif" NAME="Graphic18" ALIGN=BOTTOM BORDER=0></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P><BR><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><B>Draw - Format - Area: </B><SPAN STYLE="font-weight: medium">Change
+the "OK" button to "Apply", and the
+"Cancel"</SPAN>button to "Close". The buttons
+take on the configuration below. <BR>
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><IMG SRC="format_area.gif" NAME="Graphic21" ALIGN=BOTTOM BORDER=0></P>
+<P><BR><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><B>Draw - Format - Dimensions:</B>
+Change the "OK" button to "Apply", the "Cancel"
+button to "Close", and add a "Reset" button.
+Align these buttons in the standard order at the bottom of the dialog
+box. The buttons take on the configuration below. <BR>
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><IMG SRC="format_dimensions.gif" NAME="Graphic3" ALIGN=BOTTOM BORDER=0></P>
+<P><BR><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><B>Draw - Format - Text: </B><SPAN STYLE="font-weight: medium">Change
+the "OK" button to "Apply", and the
+"Cancel"</SPAN>button to "Close". The buttons
+take on the configuration below. <BR>
+</P>
+<P ALIGN=CENTER><IMG SRC="format_text.gif" NAME="Graphic24" ALIGN=BOTTOM WIDTH=529 HEIGHT=308 BORDER=0></P>
+<P STYLE="margin-bottom: 0cm"><B>Calc - Format - Cell: </B>Change the
+"OK" button to "Apply", and the "Cancel"
+button to "Close". The buttons take on the configuration
+below. <BR>
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><IMG SRC="format_cell.gif" NAME="Graphic25" ALIGN=BOTTOM BORDER=0></P>
+<P><BR><BR>
+</P>
+<P><B>Calc - Format - Conditions:</B> Change the "OK"
+button to "Apply", and the "Cancel" button to
+"Close". Align these buttons in the standard order, and add
+a "Reset" button to the right of those three buttons. The
+buttons take on the configuration below.
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><IMG SRC="format_conditions.gif" NAME="Graphic4" ALIGN=BOTTOM BORDER=0></P>
+<P STYLE="margin-bottom: 0cm"><BR> <BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/proposals/apply/new_preview_concept.html b/content/framework/proposals/apply/new_preview_concept.html
new file mode 100644
index 0000000..e5e760c
--- /dev/null
+++ b/content/framework/proposals/apply/new_preview_concept.html
@@ -0,0 +1,223 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="AUTHOR" CONTENT=" ">
+ <META NAME="CREATED" CONTENT="20010228;15350717">
+ <META NAME="CHANGEDBY" CONTENT=" ">
+ <META NAME="CHANGED" CONTENT="20010309;11552907">
+ <STYLE>
+ <!--
+ @page { size: 21cm 29.7cm; margin: 2cm }
+ H1 { margin-bottom: 0.21cm; font-size: 16pt }
+ TD P { margin-bottom: 0.21cm }
+ H2 { margin-bottom: 0.21cm; font-size: 14pt; font-style: italic }
+ P { margin-bottom: 0.21cm }
+ -->
+ </STYLE>
+</head>
+<body>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; margin-bottom: 0.5cm; page-break-after: avoid">
+<FONT FACE="SunSans-Demi, sans-serif"><FONT SIZE=4 STYLE="font-size: 16pt">Proposal
+for a Preview Feature in Dialogs</FONT></FONT></P>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; margin-bottom: 0.5cm; page-break-after: avoid">
+<FONT FACE="Times New Roman, serif"><FONT SIZE=3>Version 1</FONT></FONT></P>
+<P ALIGN=CENTER>Date: March 8, 2001</P>
+<H1>Table of Contents</H1>
+<P><A HREF="#2.Introduction|outline">Introduction</A></P>
+<P STYLE="margin-left: 2cm"><A HREF="#2.1.Modeless and Modal Dialogs|outline">Modeless
+and Modal Dialogs</A></P>
+<P><A HREF="#3.Live Mode Concept|outline">Live Mode Concept</A></P>
+<P STYLE="margin-left: 2cm"><A HREF="#3.1.Basic Functionality|outline">Basic
+Functionality</A></P>
+<P STYLE="margin-left: 2cm"><A HREF="#3.2.Buttons|outline">Buttons</A></P>
+<P STYLE="margin-left: 2cm"><A HREF="#3.3.Undo|outline">Undo</A></P>
+<P STYLE="margin-left: 2cm"><A HREF="#3.4.Live Mode Behavior|outline">Live
+Mode Behavior</A></P>
+<P><A HREF="#4.Alternative: Preview Icon|outline">Alternative:
+Preview Icon</A></P>
+<P><A HREF="#5.Benefits to former Apply Proposal|outline">Benefits to
+former Apply Proposal</A></P>
+<P><A HREF="#6.Open Issues|outline">Open Issues</A></P>
+<H1><A NAME="2.Introduction|outline"></A>Introduction</H1>
+<P><FONT FACE="Times New Roman, serif">This document is based on the
+</FONT><A HREF="apply_button_spec.htm"><FONT FACE="Times New Roman, serif">first
+proposal</FONT></A><FONT FACE="Times New Roman, serif"> for a new
+Apply button concept in StarOffice / OpenOffice.org. Based on the
+feedback of the community, we decided to think this concept over. As
+a result a new idea came up, which is described in this document.</FONT></P>
+<P>The initial idea of having an Apply button in dialogs was to
+improve the usability of the program, namely the dialog handling,
+with the goal to reduce the number of steps a user would have to
+complete a task. Therefore an Apply button seemed to be a good
+solution as it allows applying and changing settings without having
+to re-open a dialog several times.</P>
+<P>The community's feedback to the proposal for the use of an Apply
+button in dialogs has shown some problems that would occur when
+introducing it in the application as suggested.
+</P>
+<P>The disadvantage of the proposed button set was that</P>
+<UL>
+ <LI><P>it contained too much buttons what could be dazzling for a
+ user</P>
+ <LI><P>the combination of OK, Cancel/Close, Apply could be confusing
+ for a user</P>
+ <LI><P>the meaning of an Apply button might not be intuitively
+ understandable</P>
+ <LI><P>it might not be understood easily which data will be effected
+ by the Reset button: single tab, whole dialog or applied data.</P>
+</UL>
+<P>The community's feedback also made clear, that not an Apply
+(=Assign) button is desired but a Preview (=Try) feature. Whereas an
+Apply always assigns settings made in a dialog, a Preview is only for
+testing the settings without applying them ultimately.</P>
+<H2><A NAME="2.1.Modeless and Modal Dialogs|outline"></A>Modeless and
+Modal Dialogs</H2>
+<P>The proposed Apply concept did not distinguish between modal and
+modeless dialog boxes, as the possibility of "testing" some
+settings with having the dialog opened should not depend on the
+dialog type. Therefore the Apply button - that is usually used in
+modeless dialog boxes - seemed to be a good solution for modal
+dialogs, too. But this does not correspond to the desired Preview
+feature:</P>
+<P>In <B>modeless</B> dialog boxes an Apply button is necessary, that
+assigns settings to the actual selection. Changing the selection is
+possible here. Thus it must be possible to assign settings ultimately
+before changing the selection. Here Apply has the same functionality
+as an OK button, the only difference is, that the dialog box is not
+closed when pressing Apply. The sense of an Apply button is not for
+testing but for a better and faster workflow as the dialog remains
+open when switching the selection.</P>
+<P>When introducing this Apply button to <B>modal</B> dialog boxes,
+the behavior of the Apply button must, of course, be the same. Thus
+the settings made in a dialog must be assigned to the document/object
+selection ultimately. But this is something, the user might not
+expect or what he does not want. Instead something like a Preview or
+Try button, that is only for testing the settings without applying
+them ultimately, should be offered. The final assignment should be
+done by clicking on an OK button. (Otherwise, if the settings are
+assigned ultimately via Apply, an Undo of the settings made could be
+too complicated for the user.)</P>
+<H1><A NAME="3.Live Mode Concept|outline"></A>Live Mode Concept</H1>
+<P>Trying to find a solution for all those issues that came up in the
+community's discussion, a new idea came up, which is described in the
+following.</P>
+<H2><A NAME="3.1.Basic Functionality|outline"></A>Basic Functionality</H2>
+<P>Two different button sets should be used for modal/modeless
+dialogs, that only offer the basic functionality that is necessary</P>
+<UL>
+ <LI><P>modal: OK, Cancel, Help</P>
+ <LI><P>modeless: Apply, Close, Help</P>
+</UL>
+<P>Beneath these buttons a Live mode icon is offered for both dialog
+types. If Live mode is active, all settings made in the dialog get
+directly visible in the document. But they are not applied ultimately
+unless the user clicks on OK (for modal) or Apply (for modeless
+dialogs). Switching back to Normal mode is possible by clicking on
+the Live mode icon again (=deactivation).</P>
+<P>If the user changes something in the Normal/Live mode and then
+switches to Live/Normal mode, the information within the dialog
+should not be lost:</P>
+<P>When switching from Normal mode to Live mode, the changes made
+before get directly visible in the document.</P>
+<P>When switching from Live mode to Normal mode, the screen display
+of the document switches back to its former state, with those
+settings that were valid, before the dialog was opened. (But the
+settings made in the Live mode are not re-set in the dialog.)</P>
+<H2><A NAME="3.2.Buttons|outline"></A>Buttons</H2>
+<P>The button set is reduced to a minimum, whereby modal and modeless
+dialogs must have different sets due to their nature.</P>
+<P>The buttons behave as follows:</P>
+<UL>
+ <LI><P>OK: Finally applies the settings made. The dialog is closed.</P>
+ <LI><P>Cancel: Cancels the settings made to return to the original
+ state before the dialog was opened (=undo for all steps). The dialog
+ is closed.</P>
+ <LI><P><SPAN STYLE="background: transparent">Apply: Changes are
+ applied to the selected object within the document but the dialog
+ box is not closed.</SPAN></P>
+ <LI><P><SPAN STYLE="background: transparent">Close: Closes the
+ dialog. (Settings are not applied to the document, unless the user
+ has used the Apply button before.)</SPAN></P>
+ <LI><P>Help: Opens context sensitive help for the dialog.</P>
+</UL>
+<H2><A NAME="3.3.Undo|outline"></A>Undo</H2>
+<P><SPAN STYLE="background: transparent">Undo is possible via menu
+(Edit – Undo). Thus for modal dialogs the user can use this
+command after the dialog has been closed via OK. Here Undo would
+return to the original state before the dialog was opened. For
+modeless dialogs he can even use Undo while the dialog is still open.
+Here an Undo step is valid for the settings applied via Apply button.</SPAN></P>
+<H2><A NAME="3.4.Live Mode Behavior|outline"></A>Live Mode Behavior</H2>
+<P>In the Live mode the user can change the settings of the dialog as
+usual. The only difference to the Normal mode is, that the changes
+get directly visible in the document.</P>
+<P>Whenever the focus is removed from a control, the settings should
+get visible in the document as soon as possible. If the focus is not
+changed from one control to another and the user changes something
+within that single control, then the changes should get visible after
+a defined time. This delay time is necessary to avoid fast screen
+display changes due to hectic user actions. Whenever a change has
+been made and no user's action takes place in this time, then the
+settings get automatically visible in the document.</P>
+<P>The delay time has to be verified, perhaps it should be about 2-3
+seconds. The time might also be adjustable in a Tools/Options dialog.</P>
+<H1><A NAME="4.Alternative: Preview Icon|outline"></A><SPAN STYLE="background: transparent">Alternative:
+Preview Icon</SPAN></H1>
+<P>Instead of a Live mode that shows dialog changes automatically, it
+is also possible to offer a Preview icon: When pressing it, all the
+changes made in the dialog get directly visible in the document (but
+they are not applied ultimately). The difference to the Live mode is,
+that the user must be active to see the changes.
+</P>
+<P>With this alternative technical problems that might occur with the
+Live mode, such as time consuming data processing, are avoided.</P>
+<H1><A NAME="5.Benefits to former Apply Proposal|outline"></A><FONT FACE="Times New Roman, serif">Benefits
+to former Apply Proposal</FONT></H1>
+<UL>
+ <LI><P>The button set has been reduced to a minimum to offer only
+ the basic features that are necessary. Thus the problem of having
+ too much buttons in a dialog, that might not be understandable,
+ should not appear.</P>
+ <LI><P>A Live or a Preview mode does not apply any settings to the
+ object selection in the document. Therefore a user must not worry
+ about how to undo changes. He just has to decide, if he wants to
+ apply the current settings and then click on Apply (modeless) or OK
+ (modal).</P>
+</UL>
+<H1><A NAME="6.Open Issues|outline"></A><FONT FACE="Times New Roman, serif"><B>Open
+Issues</B></FONT></H1>
+<UL>
+ <LI><P>Should a modal dialog contain an Apply button? This only
+ makes sense to apply settings of an intermediary state, while
+ "playing" with the dialog and trying out some settings. If
+ yes, it should be tested, if the combination of OK/Apply is
+ understood by a user.</P>
+ <LI><P>Should a modeless dialog contain an OK button? This could
+ make sense for offering the possibility to apply settings and close
+ the dialog with just one mouse-click instead of two (=Apply +
+ Close). If yes, it should be tested, if the combination of OK/Apply
+ is easily understood by a user.</P>
+ <LI><P>Is a Live mode, that shows changes automatically, better than
+ a Preview button, that just displays the changes on the screen, when
+ it is pressed by the user? (Technical problems that might appear
+ with a Live mode must be cleared.)</P>
+ <LI><P>Live mode: The names Live mode and Normal mode have to be
+ verified (=> Preview mode active/not active?)</P>
+</UL>
+<P><FONT SIZE=4 STYLE="font-size: 16pt"><B>Further Issues</B></FONT></P>
+<P STYLE="font-weight: medium">Independent of this proposal of a Live
+mode or a Preview button, some issues are still open and are
+summarized for the future:</P>
+<UL>
+ <LI><P>We need to establish functional button sets for use
+ throughout our dialogs to avoid that users might be confused as to
+ the behavior of the buttons (e.g. Reset, Back, Standard).</P>
+ <LI><P>We need to establish window behavior, such as making sure all
+ dialogs that can AND should be modeless, are modeless. This is to
+ guarantee a faster workflow.</P>
+</UL>
+</body>
+</HTML>
diff --git a/content/framework/proposals/dialogs/index.html b/content/framework/proposals/dialogs/index.html
new file mode 100644
index 0000000..14cd159
--- /dev/null
+++ b/content/framework/proposals/dialogs/index.html
@@ -0,0 +1,63 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Christian Jansen">
+ <META NAME="CREATED" CONTENT="20010124;9262370">
+ <META NAME="CHANGEDBY" CONTENT="Christian Jansen">
+ <META NAME="CHANGED" CONTENT="20010124;14113550">
+</head>
+<body>
+<A HREF="../../index.html#Proposals">back</A>
+<P ALIGN=RIGHT><FONT FACE="Arial, sans-serif"><FONT SIZE=2><B>Christian
+Jansen</B></FONT></FONT></P>
+<P><FONT FACE="Arial, sans-serif"><FONT SIZE=4><B>Proposal of a new
+dialogue size and a modified tab page handling.</B></FONT></FONT></P>
+<P><FONT FACE="Arial, sans-serif"><B>Problem 1:</B></FONT></P>
+<P><FONT FACE="Arial, sans-serif">The current standard size of the
+tabbed dialogues is not large enough. Due to this fact we are running
+into trouble especially for the CJK – version of OpenOffice /
+StarOffice.</FONT></P>
+<P><FONT FACE="Arial, sans-serif"><B>Solution:</B></FONT></P>
+<P><FONT FACE="Arial, sans-serif">The solution could be to provide
+the user a new dialogue which is nearly double in height than the old
+one. </FONT><A HREF="#Rahmen1|frame"><FONT FACE="Arial, sans-serif">Figure
+1</FONT></A><FONT FACE="Arial, sans-serif"> shows the proposed
+dialogue in a rough sketch. The dotted line visualizes the change in
+the total height, if more then one tab row is needed. In my opinion
+it is not recommended to extend the dialogue in width too, because
+most of the space is <FONT FACE="Arial, sans-serif">needed </FONT>in
+the vertical. And it give the whole look and feel a nicer touch,
+because of the format which adopts the 4:3 ratio of the monitor. If
+the dialogue is extended with a tree view for example it will have a
+size of about 620 pixel in width (on a Windows system with a Tahoma
+UI-Font 8pt, at a resolution 1280x1024 with 96 dpi).</FONT></P>
+<P><IMG SRC="./b1.gif" NAME="Rahmen5" ALT="Rahmen5" ALIGN=BOTTOM></P>
+<P><FONT FACE="Arial, sans-serif">In a real world the dialogue could
+look like the scribble in <A HREF="#Rahmen2|frame">figure 2</A>. </FONT>
+</P>
+<P><IMG SRC="./b2.gif" NAME="Rahmen6" ALT="Rahmen6" ALIGN=BOTTOM></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Arial, sans-serif"><B>Problem 2:</B></FONT></P>
+<P><FONT FACE="Arial, sans-serif">Another problem that should be
+solved is the circumstance, that to many tabs are confusing and hard
+to handle for the user. Especially if more than two rows are used in
+the design. </FONT>
+</P>
+<P><FONT FACE="Arial, sans-serif"><B>Solution:</B></FONT></P>
+<P><FONT FACE="Arial, sans-serif"><A HREF="#Rahmen4|frame">Figure 3</A>
+shows the original design of <FONT FACE="Arial, sans-serif">the
+property dialogue of the CJK version</FONT>. (Also this is still the
+old tab page size)</FONT></P>
+<P><FONT FACE="Arial, sans-serif"><IMG SRC="./b3.gif" NAME="Rahmen7" ALT="Rahmen7" ALIGN=BOTTOM></FONT></P>
+<P><FONT FACE="Arial, sans-serif"><A HREF="#Rahmen3|frame">Figure 4</A>
+shows how it could look with the new design. It provides a lot of
+more clarity, than a dialogue with 14 tabs.</FONT></P>
+<P><IMG SRC="./b4.gif" NAME="Rahmen8" ALT="Rahmen8" ALIGN=BOTTOM></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/proposals/filterfactory/proposal_filterfactory.html b/content/framework/proposals/filterfactory/proposal_filterfactory.html
new file mode 100644
index 0000000..dc2e53b
--- /dev/null
+++ b/content/framework/proposals/filterfactory/proposal_filterfactory.html
@@ -0,0 +1,119 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 6.0 (Win32)">
+ <META NAME="CREATED" CONTENT="20020116;12484000">
+ <META NAME="CHANGED" CONTENT="20020215;8401975">
+ <STYLE>
+ <!--
+ @page { margin: 2cm }
+ P { margin-bottom: 0.21cm }
+ H1 { margin-bottom: 0.21cm }
+ H1.western { font-family: "Albany", sans-serif; font-size: 16pt }
+ H1.cjk { font-size: 16pt }
+ H1.ctl { font-size: 16pt }
+ H2 { margin-bottom: 0.21cm }
+ H2.western { font-family: "Albany", sans-serif; font-size: 14pt; font-style: italic }
+ H2.cjk { font-size: 14pt; font-style: italic }
+ H2.ctl { font-size: 14pt; font-style: italic }
+ -->
+ </STYLE>
+</head>
+<body LANG="de-DE">
+<H1 CLASS="western">Proposal: Searching and creating filters (3)</H1>
+<H2 CLASS="western" ALIGN=JUSTIFY>Problem</H2>
+<P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><SPAN STYLE="background: transparent">Our
+current mechanism to <SPAN STYLE="font-weight: medium">search</SPAN>
+and create filters which are registered for types is not really
+understandable for api user. This proposal describes a better (but
+incompatible) way to make it easier.</SPAN></FONT></P>
+<H2 CLASS="western">Changes</H2>
+<P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><SPAN STYLE="background: transparent">Please
+see the follow list corresponding with the graphic below to get all
+information.</SPAN></FONT></P>
+<P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><BR>
+</P>
+<OL>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><B>com.sun.star.container.XNameAccess</B><A HREF="http://com.sun.star.container.XNameAccess/"><SPAN STYLE="background: transparent"><U><FONT COLOR="#000000"><BR></FONT></U></SPAN></A><B><FONT COLOR="#008000">(unchanged)</FONT></B><A HREF="file:///X:/as/proposal/com.sun.star.container.XNameAccess"><SPAN STYLE="background: transparent"><U><FONT COLOR="#000000"><BR></FONT></U></SPAN></A><SPAN STYLE="background: transparent"><FONT COLOR="#000000">Use
+ it for a low level read/write access to pure filter configuration in
+ the same manner as now. The interface works with internal filter
+ names only and supports set/get filter properties.</FONT></SPAN></P>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><B>draft.com.sun.star.container.XContainerQuery</B><A HREF="http://draft.com.sun.star.util.XSimpleQuery/"><SPAN STYLE="background: transparent"><FONT COLOR="#000000"><BR></FONT></SPAN></A><B><FONT COLOR="#b3b300">(draft)</FONT></B><A HREF="http://draft.com.sun.star.util.XSimpleQuery/"><SPAN STYLE="background: transparent"><BR></SPAN></A>Use
+ it to search/group filters by special parameters. Returned
+ enumeration contains filters wich match your search parameters. They
+ are represented by flat data structures as Sequence<PropertyValue>
+ including all properties of them. So it's not neccessary to use
+ XNameAccess again to get the properties. Internal name of filters
+ will be a part of returned data structures too and can be used on
+ interface XMultiServiceFactory to create the filter objects.</P>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><B>com.sun.star.lang.XMultiServiceFactory</B><A HREF="http://com.sun.star.lang.XMultiServiceFactory/"><SPAN STYLE="background: transparent"><FONT COLOR="#000000"><BR></FONT></SPAN></A><B><FONT COLOR="#800000">(changed)</FONT></B></P>
+</OL>
+<UL>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><SPAN STYLE="background: transparent"><I>old</I><BR>The
+ method „createInstance()“ called with an internal filter
+ name wasn't supported. Same method called with an internal type name
+ searched for any suitable (registered default) filter in the
+ configuration and returned a created filter object.<BR>The method
+ „createInstanceWithArguments()“ does the same as
+ „createInstance()“. The optional argument „FilterName“
+ suppresses the search and create the specified filter object by name
+ directly.</SPAN></FONT></P>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent"><FONT COLOR="#000000"><I>new</I><BR>Both
+ methods of this interface create filter objects by internal name
+ only. There exist no optional search mechanism any longer. The
+ return value is the created filter object, initialized with his own
+ configuration data by calling
+ „XInitialization::initialize()“.<BR>Format of
+ initialization data:<BR>Sequence<Any>[0] = filter config
+ data as Sequence<PropertyValue><BR>Sequence<Any>[1..n] =
+ optional arguments of „createInstanceWithArguments()“<BR>
+ directly</FONT></SPAN></P>
+</UL>
+<P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P ALIGN=JUSTIFY><IMG SRC="filterfactory.gif" NAME="Objekt1" ALIGN=LEFT><BR CLEAR=LEFT><BR><BR>
+</P>
+<H2 CLASS="western" ALIGN=JUSTIFY>Consequences</H2>
+<OL>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><SPAN STYLE="background: transparent"><I>XMultiServiceFactory</I>
+ methods doesn't support the creation of filters using internal type
+ names any longer.</SPAN></FONT></P>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><SPAN STYLE="background: transparent">This
+ should be a part of new interface <I>XContainerQuery</I>. Please
+ have a look on
+ <A HREF="http://api.openoffice.org/source/browse/api/udkapi/com/sun/star/container/XContainerQuery.idl">http://api.openoffice.org/source/browse/api/udkapi/com/sun/star/container/XContainerQuery.idl</A>
+ too, to get more information about the generic functionality of this
+ interface.</SPAN></FONT></P>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><SPAN STYLE="background: transparent">Filter
+ implementations must support <I>XInitialization</I> to get her own
+ configuration data and optional arguments of
+ <I>XMultiServiceFactory::createInstanceWithArguments()</I>.</SPAN></FONT></P>
+ <LI><P ALIGN=JUSTIFY STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><SPAN STYLE="background: transparent">They
+ can implement <I>XNamed()</I> to identify herself. User of a filter
+ object can use returned internal name on service FilterFactory to
+ get more information about it.<BR>„getName()“ must
+ return the internal name of the filter<BR>„setName()“
+ can be ignored or should be used to rename the filter inside the
+ configuration by using mechanism of service FilterFactory.<BR>=>
+ Discussion: Should it be allowed to rename a filter during
+ runtime?<BR>=> I would say: „NO“! Nobody can support
+ a right error handling for name clashes if a filter with same name
+ already exist. This functionality should be a part of the setup or
+ an administration process.</SPAN></FONT></P>
+</OL>
+<H2 CLASS="western" ALIGN=JUSTIFY>Example</H2>
+<P ALIGN=JUSTIFY>Follow sequence diagram should show creation of a
+suitable (default) filter for a detected type. First the user try to
+get the internal filter name by using <I>XContainerQuery</I>
+interface with the internal type name and some optional search
+parameters. The returned filter name can be used on another interface
+<I>XMultiServiceFactory</I> to create the filter object directly.
+Filter will be created and initialized (by calling
+<I>XInitialization::initialize())</I> with his own configuration data
+by used FilterFactory.</P>
+<P ALIGN=JUSTIFY><IMG SRC="seq_create_filter.gif" NAME="Objekt2" ALIGN=LEFT><BR CLEAR=LEFT><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/proposals/filters/exportfilters.html b/content/framework/proposals/filters/exportfilters.html
new file mode 100644
index 0000000..1f08154
--- /dev/null
+++ b/content/framework/proposals/filters/exportfilters.html
@@ -0,0 +1,115 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 6.0 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Mathias Bauer">
+ <META NAME="CREATED" CONTENT="20020320;11105752">
+ <META NAME="CHANGEDBY" CONTENT="Mathias Bauer">
+ <META NAME="CHANGED" CONTENT="20020320;17323202">
+</head>
+<body LANG="de-DE">
+<H2>Proposal for a unified API for exporting and saving documents</H2>
+<P>Impress has two different kinds of export filters. Some of them
+can be used for „SaveAs“ (like PowerPoint and StarOffice
+binary filters), some of them are only accessible throuh the „Export“
+function. While the first kind of filters can be used via API (
+com::sun::star::XStorable::store(To/AsURL) ), the second kind of
+filters can't. We want to change this, and the most natural way is to
+use the same API for both. The „Export“ functionality in
+the user interface will use this API in the same way the „SaveAs“
+functionality does it, with some slight differences:</P>
+<OL>
+ <LI><P>„Export“ uses storeToURL, SaveAs uses storeAsURL.
+ The difference is, that the latter method also changes the URL of
+ the document in memory.</P>
+ <LI><P>This implies that it's not possible to use a pure export
+ filter in the storeAsURL method, because the generated file would
+ not be importable. Pure export filters can only be used in the
+ storeToURL method. Using a wrong filter will cause throwing of an
+ exception.</P>
+ <LI><P>To ease the implementation to find out which filters shall be
+ used in which funtion, „Export“ uses only pure export
+ filters, while „SaveAs“ only uses filters that can both
+ import and export. If an Import/Export filter should also be used
+ for „Exporting“, another filter must be created in the
+ filter configuration for the same file type, but without the
+ „Import“ flag set. If new filters are created in the
+ configuration, they can get the same UI names as the old
+ import/export filter (because they won't be seen in the same file
+ dialog), but must get a new internal filter name. Filter names of
+ import filters must not be changed, because they may have been used
+ before. If an import filter shall not be used in the „SaveAs“
+ dialog, they must not have the „Export“ flag set, use a
+ different filter ony for export.<BR>We will have three kind of
+ filters then: pure import filter (document can't be stored over the
+ old file after loading), pure export filters (saved document is not
+ loadable again, so this filter will be used only in the „Export“
+ function) and combined import/export filters.</P>
+ <LI><P>Export filters support an additional property
+ „ExportSelection“ in the media descriptor, that tells
+ the filter to export only the current selection and not the whole
+ document. This will be reflected by a checkbox in the file dialog.</P>
+</OL>
+<P>All parameters to configure the export operation will be passed in
+the „FilterData“ property of the media descriptor that is
+passed to the filter (implemented as sequence<PropertyValue>).
+If there is no configuration data given, the filter must use some
+suitable defaults.
+</P>
+<P>In the user interface it's also possible to provide a UI component
+that retrieves the needed information and adds it to the media
+descriptor. If the filter wants, it can also store the input in a
+configuration file and use it as default in the next operation
+without given parameters. Here also the „UserData“
+parameter of the Typedetection.xml can be used for storing the
+configuration. This is only possible for data representable as a
+string, but the advantage is that the default for the filter can be
+specified in the Typedetection.xml, not in the source code. In this
+case the filter implementation first must look for „FilterData“,
+then for „UserData“.</P>
+<P>The UI component is identified by an implementation name in the
+filter configuration (Typedetection.xml). The UI code for the
+„Export“ function will look into the configuration and
+instantiate the UI component. The exact interface for this component
+will be specified in a different proposal, it should use a media
+descriptor as input/output paremeter and return a boolean value, that
+will be set to „false“ if the user cancels the operation.</P>
+<P>The UI component is not restricted for usage inside the „Export“
+functionality. We will also have this new feature for the filters
+used for loading and storing documents.</P>
+<P>At the end we will have one single API for storing or exporting
+documents, one single set of filters with a common API, only the two
+UI functions will use it in two different ways. This API also enables
+other developers to provide export filters for OO.o documents using
+our filter API, with the additional capabilities of exporting only
+parts of the document.</P>
+<P>Of course this mechanism can be used in other office components
+also.</P>
+<P>ToDo's:</P>
+<OL>
+ <LI><P>Extend Typedetection.xml for new implementation name for UI
+ component and change filtercache implementation. Make sure that the
+ compatibilty to 6.0 is preserved.</P>
+ <LI><P>Provide properties „ExportSelection“ and
+ „FilterData“ in media descriptor and SfxItemSet at
+ SfxMedium.</P>
+ <LI><P>Divide filters into import, export and import/export filters.</P>
+ <LI><P>Create interface for the UI component.</P>
+ <LI><P>Implement a UI component for all current export filters and
+ register it for all of them in the configuration.</P>
+ <LI><P>Move the old „core“ code from the FuExport to the
+ ConvertTo method in Impress.</P>
+ <LI><P>Offer SID_EXPORT in SFX that will look for the UI component
+ and feed the API call.</P>
+ <LI><P>Check for pure export filters in storeToURL and for pure
+ import filters in store calls.</P>
+ <LI><P>Enable the current code for loading and storing documents to
+ use the filters UI components.</P>
+ <LI><P>Document all parameters of our current export filters.</P>
+</OL>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/proposals/helpagent/HelpAgentProposal_01.htm b/content/framework/proposals/helpagent/HelpAgentProposal_01.htm
new file mode 100644
index 0000000..b5f2493
--- /dev/null
+++ b/content/framework/proposals/helpagent/HelpAgentProposal_01.htm
@@ -0,0 +1,272 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE>Proposal for a new Help Agent</TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Lutz Hoeger">
+ <META NAME="CREATED" CONTENT="20010209;15581100">
+ <META NAME="CHANGEDBY" CONTENT="Lutz Hoeger">
+ <META NAME="CHANGED" CONTENT="20010209;15581700">
+ <META NAME="CLASSIFICATION" CONTENT="Help Agent in StarOffice / OpenOffice.org">
+ <META NAME="KEYWORDS" CONTENT="User assistance, documentation, help system, Help Agent">
+ <STYLE>
+ <!--
+ @page { size: 21cm 29.7cm; margin: 2cm }
+ P { margin-bottom: 0.21cm; font-family: "sunserif regular", "SunSerif-Regular", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 10pt; page-break-before: auto }
+ H1 { margin-top: 0.63cm; margin-bottom: 0.21cm; font-family: "sunsans demi", "SunSans-Demi", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 14pt; font-weight: demi-bold; page-break-before: auto }
+ H2 { margin-bottom: 0.21cm; font-family: "sunsans demi", "SunSans-Demi", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 12pt; font-weight: demi-bold; page-break-before: auto }
+ -->
+ </STYLE>
+</HEAD>
+<BODY>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Sunsans Heavy"><FONT SIZE=4 STYLE="font-size: 16pt">Proposal
+for a new Help Agent</FONT></FONT></P>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; font-style: normal; font-weight: demi-bold; page-break-after: avoid">
+<FONT FACE="sunsans heavy, SunSans-Heavy, Geneva, Arial, Helvetica, Lucida Sans, Sans-Serif"><FONT SIZE=4>Version
+1, Lutz Höger, 02/09/2001</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<DIV ID="Table of Contents1">
+ <DIV ID="Table of Contents1_Head">
+ <P STYLE="margin-top: 0.42cm; font-weight: medium; page-break-after: avoid">
+ <FONT FACE="Sunsans Demi"><FONT SIZE=4>Table of Contents</FONT></FONT></P>
+ </DIV>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#1.Preface|outline">Preface</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#2.Problem|outline">Problem</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#3.Solution|outline">Solution</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.Details|outline">Details</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.1.WhenshouldtheHelpAgentbetriggered?|outline">When
+ should the Help Agent be triggered?</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.2.Let'sgetvisual|outline">Let's
+ get visual</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.3.UsingtheHelpAgent|outline">Using
+ the Help Agent</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.4.Advancedfeatures|outline">Advanced
+ features</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.5.ConfiguringtheHelpAgent|outline">Configuring
+ the Help Agent</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#5.ImplementationSteps|outline">Implementation
+ Steps</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#6.OpenIssues|outline">Open
+ Issues</A></FONT></P>
+</DIV>
+<H1><A NAME="1.Preface|outline"></A>Preface</H1>
+<P>This short proposal doesn't claim to completely cover all aspects
+of the subject, even though I'm trying to propose the feature as
+complete as possible.</P>
+<H1><A NAME="2.Problem|outline"></A>Problem</H1>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">When
+working with StarOffice / OpenOffice.org (SO / OO.o) there are
+various situations where the program 'decides' to act in a certain
+way that might not have been expected by the user. Some examples for
+this are: </FONT>
+</P>
+<UL STYLE="margin-left: 0.5cm">
+ <LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+ 'AutoCorrect' feature automatically completes a word the user has
+ just started to type</FONT></P>
+ <LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+ same feature automatically creates a bullet list from plain text
+ while typing (type '- test', press Enter)</FONT></P>
+ <LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+ 'Print' dialog box is shown even though the user has clicked on the
+ 'Print File Directly' symbol in the 'Function Bar' (because there
+ was a mismatch between the default system printer and the printer
+ stored in the document)</FONT></P>
+</UL>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">To
+simplify it: from a user's point of view in some situations a program
+behaves unpredictably. No matter how hard we try to avoid these
+cases, in certain situation the expectations of users simply are too
+different.</FONT></P>
+<H1><A NAME="3.Solution|outline"></A>Solution</H1>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">The
+first and very simple idea is to tell users what's happening, e.g.
+use some plain text explaining the current behavior. We tried that in
+SO 5.x, using the so called Help Agent. In the current SO / OO.o
+release (614) there is no such information any more. </FONT>
+</P>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">Due to
+the lack of this feature, we can now see the real benefit of this
+mechanism. It helps users in getting out of 'screen mysteries', it
+offers support when users actually need it. So this proposal is about
+the re-implementation of the Help Agent feature to be more elegant,
+more intelligent but also less annoying than formerly.</FONT></P>
+<H1><A NAME="4.Details|outline"></A>Details</H1>
+<H2><A NAME="4.1.WhenshouldtheHelpAgentbetriggered?|outline"></A>When
+should the Help Agent be triggered?</H2>
+<P>The most important feature of the Help Agent is to 'proactively'
+(I don't know any better word) offer support in certain situations.
+This distinguishes it from common help systems which offer help only
+if a user asks for it, e.g. by hitting the 'help' button. The Help
+Agent needs to detect if the user performs an action that may lead to
+confusion or that's generally difficult to understand in order to
+present helpful information to the user.</P>
+<P>The detection of these situations is a quite critical part of the
+Help Agent. The range of implementations for this goes from a static,
+pre-defined list (like in SO 5.x) to some artificial intelligence
+driven agent analyzing the user's behavior and thus detecting usage
+problems. The compromise between release driven reality and feature
+theory lies somewhere in-between.
+</P>
+<P>I think it's best to start with the simple list implementation and
+advance to something more sophisticated later. A list of situations
+that require user assistance already exists in SO 5.x and can be
+maintained based upon the feedback from our users, e.g. by evaluating
+the FAQ lists that are regularly generated by Sun's Support.
+</P>
+<H2><A NAME="4.2.Let'sgetvisual|outline"></A>Let's get visual</H2>
+<P>When designing the UI of the new Help Agent, we tried to follow
+the paradigm 'K.I.S.S.' (keep it short & simple). SO 5.x users
+sometimes did complain about the old Help Agent. Very often the first
+thing that was done with it was to disable this feature completely,
+because it was rather irritating than helpful. That was caused by two
+aspects: The window showed up automatically but had to be closed
+again manually, and the content wasn't appropriate for the majority
+of our users - beginners.</P>
+<P>To change the content of the help system is one thing. It's safe
+to say that it will take some time to be accomplished and the whole
+process will probably span a couple of SO / OO.o releases. Fixing the
+usability issue should be possible soon, so let's have a look at a
+first UI design idea.
+</P>
+<P>Here's a mock-up screen shot of a typical Help Agent situation:
+The user adjusts some settings that have 'invisible side effects' -
+in this case the spell check for the selected languages only
+functions if the appropriate language has been installed, something
+users very often aren't aware of, if they are just 'playing around'
+with some character formatting settings.</P>
+<P ALIGN=CENTER><IMG SRC="offering.gif" NAME="Graphic1" ALIGN=BOTTOM WIDTH=384 HEIGHT=303 BORDER=0></P>
+<P>Due to the 'SO 5.x help content issue', we decided to initially
+display as few text as possible. This leads to the idea of just
+showing up an image button indicating that help is available. The
+Help Agent gets triggered and shows up in the lower right corner of
+the current document window. The design of the image above is just a
+placeholder for some artwork that would still have to be created.</P>
+<P>The Help Agent window or indicator should appear on top of the
+current document window but underneath a potentially open dialog box
+that has got the focus. It shouldn't be possible to raise the
+document window's z-order above the Help Agent's one. The current
+focus should remain unchanged so that the user can continue his work
+without being interrupted. (This is exactly the behavior of the Help
+Agent window in SO 5.x.)</P>
+<P>Behind the scenes, the help ID of the control that triggered the
+Help Agent gets forwarded to the Help Agent in order to be available
+for later processing.</P>
+<H2><A NAME="4.3.UsingtheHelpAgent|outline"></A>Using the Help Agent</H2>
+<P>To address the complains about the old Help Agent's stickiness,
+the new Help Agent should disappear after a time-out of 30 seconds.
+If the user doesn't do anything but continue his normal work and
+ignores the Help Agent, the pop-up window simply disappears after
+this time-out. If another item triggers the Help Agent within this
+time-out, the countdown timer should be reset and the new help ID
+should be stored instead of the old one.</P>
+<P>If the user clicks on the Help Agent indicator within the time-out
+timeframe, the help system will be opened and the help related to the
+temporarily stored help ID will be displayed. Starting with SO 6.0 /
+OO.0, the help system is an own operating system task. In case this
+task is already running at the time the Help Agent is used (clicked),
+it simply gets the focus and displays the respective help topic. That
+way, only one help task can be open at the same time.</P>
+<H2><A NAME="4.4.Advancedfeatures|outline"></A>Advanced features</H2>
+<P>Turning the static list of Help Agent relevant help IDs into a
+'semi-static' list could be achieved by dropping items dynamically.
+Whenever the Help Agent detects that his help offer didn't succeed,
+i.e. the user didn't make use of it a couple of times (3? 5? 10?)
+within a certain time (e.g. 90 days), an item can be dropped from the
+list. That way the occurrences of the Help Agent can be minimized
+down to what an individual user actually needs.
+</P>
+<P>I'm not sure whether or not it is necessary to manually reset a
+list that has been modified this way to the factory default. But my
+guts tell me that there might be a number of people who want to have
+this feature.
+</P>
+<P>So far this is not 'rocket science'. A far more advanced feature
+would be to add new items to the list based on an analysis of the
+program's usage. This could come pretty close to an interactive
+tutor, detecting certain 'inefficiencies' in usage patterns and
+offering the respective shortcuts to the user. This feature itself
+would need a much more extensive description than this proposal is
+supposed to deliver. Maybe someone else wants to pick this up and
+follow upon it?</P>
+<P>Regardless whether or not the typical geek likes it: animations
+are one of those neat features that particularly beginners do like.
+As there is a quite contradictory discussion about this detail, I'll
+leave it open and name it just for the purpose of completeness.</P>
+<P>Something maybe more important to think about is the position of
+the Help Agent indicator. On one hand it brings a certain calmness to
+the user interface, if this window always shows up at the same
+position, on the other hand if this position should ever be occupied
+by something else (like a toolbar or a docked float), it could be
+desirable to open the window somewhere else. SO 5.x had a mechanism
+that tried to position the Help Agent's floating window intelligently
+so that it doesn't cover the currently used dialog box. Of course
+such a feature would be helpful for the new Help Agent's window, too.
+But as the new window should be much smaller than the old one, it
+might be something that can be done later.</P>
+<H2><A NAME="4.5.ConfiguringtheHelpAgent|outline"></A>Configuring the
+Help Agent</H2>
+<P>Even though the new Help Agent tries to be both - as visible as
+necessary and as invisible as possible - there's probably the
+requirement to configure at least some basic settings.
+</P>
+<UL STYLE="margin-left: 0.5cm">
+ <LI><P>Advanced users might want to switch the feature completely
+ off; so this option should be offered. This implies that the default
+ should be 'on' ;-)</P>
+ <LI><P>The suggested default time-out of 30 seconds might be
+ something that users want to adjust, too. We should offer a scale
+ from 0 to 60 seconds in 5 second steps, so this can be combined with
+ the above configuration setting ('0 seconds' means 'feature is
+ deactivated'). Or should the two settings be independent from each
+ other?</P>
+ <LI><P>As soon as the Help Agent is able to 'forget' or 'learn'
+ about situations it should show up, there's probably some
+ requirement to reset a modified list to the factory default.
+ </P>
+ <LI><P>As mentioned above, the position of the Help Agent window
+ should later be configurable if it's not possible to make it evade
+ intelligently .</P>
+</UL>
+<H1><A NAME="5.ImplementationSteps|outline"></A>Implementation Steps</H1>
+<P>Driven by product release reality, I suggest the following three
+steps of implementation. However, if someone thinks this isn't
+appropriate, I would be happy to see an alternative.</P>
+<OL STYLE="margin-left: 0.5cm">
+ <LI><P>The first implementation basically should include anything
+ described in the chapters "When should...", "Let's
+ get..." and "Using", plus the basic configuration
+ option of enabling/disabling the feature and justifying the
+ time-out.</P>
+ <LI><P>The addition of the feature "dropping items from the
+ list" and the possibility to reset the list should be the main
+ parts of step 2. In addition to this, the window positioning issue
+ (if at all there is such an issue) should be finalized.</P>
+ <LI><P>The third step could be a mid-term to long-term project,
+ defining and implementing the feature "add new items to the
+ list", as this would probably affect other projects as well.</P>
+</OL>
+<H1><A NAME="6.OpenIssues|outline"></A>Open Issues</H1>
+<P>These are just a few open issues that would need to be resolved in
+order to achieve step 1 and step 2 of the implementation. Probably
+there are many more if one starts digging into the details, but I
+think these are the most obvious ones.</P>
+<UL STYLE="margin-left: 0.5cm">
+ <LI><P>Artwork for the Help Agent indicator<BR>This should clearly
+ indicate 'click me' and 'there's something you might want to know'</P>
+ <LI><P>Further configuration details<BR>Are the configurable
+ settings sufficient or already too detailed? What are reasonable
+ default values to minimize the necessity of configuring this
+ feature?</P>
+ <LI><P>Window behavior<BR>What about stickiness, movability, focus
+ behavior?
+ </P>
+</UL>
+<DIV TYPE=FOOTER>
+ <P STYLE="margin-top: 0.1cm; margin-bottom: 0.2cm"><FONT SIZE=1 STYLE="font-size: 8pt"><SDFIELD TYPE=DOCINFO SUBTYPE=CHANGE FORMAT=DATE SDNUM="1033;1033;MM/DD/YYYY">02/09/2001</SDFIELD> <SDFIELD TYPE=DOCINFO SUBTYPE=TITLE>Proposal for a new Help Agent</SDFIELD> Page
+ <SDFIELD TYPE=PAGE SUBTYPE=RANDOM FORMAT=PAGE>4</SDFIELD> of <SDFIELD TYPE=DOCSTAT SUBTYPE=PAGE FORMAT=PAGE>4</SDFIELD></FONT></P>
+</DIV>
+</BODY>
+</HTML>
diff --git a/content/framework/proposals/helpagent/helpagentproposal01.htm b/content/framework/proposals/helpagent/helpagentproposal01.htm
new file mode 100644
index 0000000..b5f2493
--- /dev/null
+++ b/content/framework/proposals/helpagent/helpagentproposal01.htm
@@ -0,0 +1,272 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE>Proposal for a new Help Agent</TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Lutz Hoeger">
+ <META NAME="CREATED" CONTENT="20010209;15581100">
+ <META NAME="CHANGEDBY" CONTENT="Lutz Hoeger">
+ <META NAME="CHANGED" CONTENT="20010209;15581700">
+ <META NAME="CLASSIFICATION" CONTENT="Help Agent in StarOffice / OpenOffice.org">
+ <META NAME="KEYWORDS" CONTENT="User assistance, documentation, help system, Help Agent">
+ <STYLE>
+ <!--
+ @page { size: 21cm 29.7cm; margin: 2cm }
+ P { margin-bottom: 0.21cm; font-family: "sunserif regular", "SunSerif-Regular", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 10pt; page-break-before: auto }
+ H1 { margin-top: 0.63cm; margin-bottom: 0.21cm; font-family: "sunsans demi", "SunSans-Demi", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 14pt; font-weight: demi-bold; page-break-before: auto }
+ H2 { margin-bottom: 0.21cm; font-family: "sunsans demi", "SunSans-Demi", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 12pt; font-weight: demi-bold; page-break-before: auto }
+ -->
+ </STYLE>
+</HEAD>
+<BODY>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Sunsans Heavy"><FONT SIZE=4 STYLE="font-size: 16pt">Proposal
+for a new Help Agent</FONT></FONT></P>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; font-style: normal; font-weight: demi-bold; page-break-after: avoid">
+<FONT FACE="sunsans heavy, SunSans-Heavy, Geneva, Arial, Helvetica, Lucida Sans, Sans-Serif"><FONT SIZE=4>Version
+1, Lutz Höger, 02/09/2001</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<DIV ID="Table of Contents1">
+ <DIV ID="Table of Contents1_Head">
+ <P STYLE="margin-top: 0.42cm; font-weight: medium; page-break-after: avoid">
+ <FONT FACE="Sunsans Demi"><FONT SIZE=4>Table of Contents</FONT></FONT></P>
+ </DIV>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#1.Preface|outline">Preface</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#2.Problem|outline">Problem</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#3.Solution|outline">Solution</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.Details|outline">Details</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.1.WhenshouldtheHelpAgentbetriggered?|outline">When
+ should the Help Agent be triggered?</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.2.Let'sgetvisual|outline">Let's
+ get visual</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.3.UsingtheHelpAgent|outline">Using
+ the Help Agent</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.4.Advancedfeatures|outline">Advanced
+ features</A></FONT></P>
+ <P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.5.ConfiguringtheHelpAgent|outline">Configuring
+ the Help Agent</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#5.ImplementationSteps|outline">Implementation
+ Steps</A></FONT></P>
+ <P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#6.OpenIssues|outline">Open
+ Issues</A></FONT></P>
+</DIV>
+<H1><A NAME="1.Preface|outline"></A>Preface</H1>
+<P>This short proposal doesn't claim to completely cover all aspects
+of the subject, even though I'm trying to propose the feature as
+complete as possible.</P>
+<H1><A NAME="2.Problem|outline"></A>Problem</H1>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">When
+working with StarOffice / OpenOffice.org (SO / OO.o) there are
+various situations where the program 'decides' to act in a certain
+way that might not have been expected by the user. Some examples for
+this are: </FONT>
+</P>
+<UL STYLE="margin-left: 0.5cm">
+ <LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+ 'AutoCorrect' feature automatically completes a word the user has
+ just started to type</FONT></P>
+ <LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+ same feature automatically creates a bullet list from plain text
+ while typing (type '- test', press Enter)</FONT></P>
+ <LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+ 'Print' dialog box is shown even though the user has clicked on the
+ 'Print File Directly' symbol in the 'Function Bar' (because there
+ was a mismatch between the default system printer and the printer
+ stored in the document)</FONT></P>
+</UL>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">To
+simplify it: from a user's point of view in some situations a program
+behaves unpredictably. No matter how hard we try to avoid these
+cases, in certain situation the expectations of users simply are too
+different.</FONT></P>
+<H1><A NAME="3.Solution|outline"></A>Solution</H1>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">The
+first and very simple idea is to tell users what's happening, e.g.
+use some plain text explaining the current behavior. We tried that in
+SO 5.x, using the so called Help Agent. In the current SO / OO.o
+release (614) there is no such information any more. </FONT>
+</P>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">Due to
+the lack of this feature, we can now see the real benefit of this
+mechanism. It helps users in getting out of 'screen mysteries', it
+offers support when users actually need it. So this proposal is about
+the re-implementation of the Help Agent feature to be more elegant,
+more intelligent but also less annoying than formerly.</FONT></P>
+<H1><A NAME="4.Details|outline"></A>Details</H1>
+<H2><A NAME="4.1.WhenshouldtheHelpAgentbetriggered?|outline"></A>When
+should the Help Agent be triggered?</H2>
+<P>The most important feature of the Help Agent is to 'proactively'
+(I don't know any better word) offer support in certain situations.
+This distinguishes it from common help systems which offer help only
+if a user asks for it, e.g. by hitting the 'help' button. The Help
+Agent needs to detect if the user performs an action that may lead to
+confusion or that's generally difficult to understand in order to
+present helpful information to the user.</P>
+<P>The detection of these situations is a quite critical part of the
+Help Agent. The range of implementations for this goes from a static,
+pre-defined list (like in SO 5.x) to some artificial intelligence
+driven agent analyzing the user's behavior and thus detecting usage
+problems. The compromise between release driven reality and feature
+theory lies somewhere in-between.
+</P>
+<P>I think it's best to start with the simple list implementation and
+advance to something more sophisticated later. A list of situations
+that require user assistance already exists in SO 5.x and can be
+maintained based upon the feedback from our users, e.g. by evaluating
+the FAQ lists that are regularly generated by Sun's Support.
+</P>
+<H2><A NAME="4.2.Let'sgetvisual|outline"></A>Let's get visual</H2>
+<P>When designing the UI of the new Help Agent, we tried to follow
+the paradigm 'K.I.S.S.' (keep it short & simple). SO 5.x users
+sometimes did complain about the old Help Agent. Very often the first
+thing that was done with it was to disable this feature completely,
+because it was rather irritating than helpful. That was caused by two
+aspects: The window showed up automatically but had to be closed
+again manually, and the content wasn't appropriate for the majority
+of our users - beginners.</P>
+<P>To change the content of the help system is one thing. It's safe
+to say that it will take some time to be accomplished and the whole
+process will probably span a couple of SO / OO.o releases. Fixing the
+usability issue should be possible soon, so let's have a look at a
+first UI design idea.
+</P>
+<P>Here's a mock-up screen shot of a typical Help Agent situation:
+The user adjusts some settings that have 'invisible side effects' -
+in this case the spell check for the selected languages only
+functions if the appropriate language has been installed, something
+users very often aren't aware of, if they are just 'playing around'
+with some character formatting settings.</P>
+<P ALIGN=CENTER><IMG SRC="offering.gif" NAME="Graphic1" ALIGN=BOTTOM WIDTH=384 HEIGHT=303 BORDER=0></P>
+<P>Due to the 'SO 5.x help content issue', we decided to initially
+display as few text as possible. This leads to the idea of just
+showing up an image button indicating that help is available. The
+Help Agent gets triggered and shows up in the lower right corner of
+the current document window. The design of the image above is just a
+placeholder for some artwork that would still have to be created.</P>
+<P>The Help Agent window or indicator should appear on top of the
+current document window but underneath a potentially open dialog box
+that has got the focus. It shouldn't be possible to raise the
+document window's z-order above the Help Agent's one. The current
+focus should remain unchanged so that the user can continue his work
+without being interrupted. (This is exactly the behavior of the Help
+Agent window in SO 5.x.)</P>
+<P>Behind the scenes, the help ID of the control that triggered the
+Help Agent gets forwarded to the Help Agent in order to be available
+for later processing.</P>
+<H2><A NAME="4.3.UsingtheHelpAgent|outline"></A>Using the Help Agent</H2>
+<P>To address the complains about the old Help Agent's stickiness,
+the new Help Agent should disappear after a time-out of 30 seconds.
+If the user doesn't do anything but continue his normal work and
+ignores the Help Agent, the pop-up window simply disappears after
+this time-out. If another item triggers the Help Agent within this
+time-out, the countdown timer should be reset and the new help ID
+should be stored instead of the old one.</P>
+<P>If the user clicks on the Help Agent indicator within the time-out
+timeframe, the help system will be opened and the help related to the
+temporarily stored help ID will be displayed. Starting with SO 6.0 /
+OO.0, the help system is an own operating system task. In case this
+task is already running at the time the Help Agent is used (clicked),
+it simply gets the focus and displays the respective help topic. That
+way, only one help task can be open at the same time.</P>
+<H2><A NAME="4.4.Advancedfeatures|outline"></A>Advanced features</H2>
+<P>Turning the static list of Help Agent relevant help IDs into a
+'semi-static' list could be achieved by dropping items dynamically.
+Whenever the Help Agent detects that his help offer didn't succeed,
+i.e. the user didn't make use of it a couple of times (3? 5? 10?)
+within a certain time (e.g. 90 days), an item can be dropped from the
+list. That way the occurrences of the Help Agent can be minimized
+down to what an individual user actually needs.
+</P>
+<P>I'm not sure whether or not it is necessary to manually reset a
+list that has been modified this way to the factory default. But my
+guts tell me that there might be a number of people who want to have
+this feature.
+</P>
+<P>So far this is not 'rocket science'. A far more advanced feature
+would be to add new items to the list based on an analysis of the
+program's usage. This could come pretty close to an interactive
+tutor, detecting certain 'inefficiencies' in usage patterns and
+offering the respective shortcuts to the user. This feature itself
+would need a much more extensive description than this proposal is
+supposed to deliver. Maybe someone else wants to pick this up and
+follow upon it?</P>
+<P>Regardless whether or not the typical geek likes it: animations
+are one of those neat features that particularly beginners do like.
+As there is a quite contradictory discussion about this detail, I'll
+leave it open and name it just for the purpose of completeness.</P>
+<P>Something maybe more important to think about is the position of
+the Help Agent indicator. On one hand it brings a certain calmness to
+the user interface, if this window always shows up at the same
+position, on the other hand if this position should ever be occupied
+by something else (like a toolbar or a docked float), it could be
+desirable to open the window somewhere else. SO 5.x had a mechanism
+that tried to position the Help Agent's floating window intelligently
+so that it doesn't cover the currently used dialog box. Of course
+such a feature would be helpful for the new Help Agent's window, too.
+But as the new window should be much smaller than the old one, it
+might be something that can be done later.</P>
+<H2><A NAME="4.5.ConfiguringtheHelpAgent|outline"></A>Configuring the
+Help Agent</H2>
+<P>Even though the new Help Agent tries to be both - as visible as
+necessary and as invisible as possible - there's probably the
+requirement to configure at least some basic settings.
+</P>
+<UL STYLE="margin-left: 0.5cm">
+ <LI><P>Advanced users might want to switch the feature completely
+ off; so this option should be offered. This implies that the default
+ should be 'on' ;-)</P>
+ <LI><P>The suggested default time-out of 30 seconds might be
+ something that users want to adjust, too. We should offer a scale
+ from 0 to 60 seconds in 5 second steps, so this can be combined with
+ the above configuration setting ('0 seconds' means 'feature is
+ deactivated'). Or should the two settings be independent from each
+ other?</P>
+ <LI><P>As soon as the Help Agent is able to 'forget' or 'learn'
+ about situations it should show up, there's probably some
+ requirement to reset a modified list to the factory default.
+ </P>
+ <LI><P>As mentioned above, the position of the Help Agent window
+ should later be configurable if it's not possible to make it evade
+ intelligently .</P>
+</UL>
+<H1><A NAME="5.ImplementationSteps|outline"></A>Implementation Steps</H1>
+<P>Driven by product release reality, I suggest the following three
+steps of implementation. However, if someone thinks this isn't
+appropriate, I would be happy to see an alternative.</P>
+<OL STYLE="margin-left: 0.5cm">
+ <LI><P>The first implementation basically should include anything
+ described in the chapters "When should...", "Let's
+ get..." and "Using", plus the basic configuration
+ option of enabling/disabling the feature and justifying the
+ time-out.</P>
+ <LI><P>The addition of the feature "dropping items from the
+ list" and the possibility to reset the list should be the main
+ parts of step 2. In addition to this, the window positioning issue
+ (if at all there is such an issue) should be finalized.</P>
+ <LI><P>The third step could be a mid-term to long-term project,
+ defining and implementing the feature "add new items to the
+ list", as this would probably affect other projects as well.</P>
+</OL>
+<H1><A NAME="6.OpenIssues|outline"></A>Open Issues</H1>
+<P>These are just a few open issues that would need to be resolved in
+order to achieve step 1 and step 2 of the implementation. Probably
+there are many more if one starts digging into the details, but I
+think these are the most obvious ones.</P>
+<UL STYLE="margin-left: 0.5cm">
+ <LI><P>Artwork for the Help Agent indicator<BR>This should clearly
+ indicate 'click me' and 'there's something you might want to know'</P>
+ <LI><P>Further configuration details<BR>Are the configurable
+ settings sufficient or already too detailed? What are reasonable
+ default values to minimize the necessity of configuring this
+ feature?</P>
+ <LI><P>Window behavior<BR>What about stickiness, movability, focus
+ behavior?
+ </P>
+</UL>
+<DIV TYPE=FOOTER>
+ <P STYLE="margin-top: 0.1cm; margin-bottom: 0.2cm"><FONT SIZE=1 STYLE="font-size: 8pt"><SDFIELD TYPE=DOCINFO SUBTYPE=CHANGE FORMAT=DATE SDNUM="1033;1033;MM/DD/YYYY">02/09/2001</SDFIELD> <SDFIELD TYPE=DOCINFO SUBTYPE=TITLE>Proposal for a new Help Agent</SDFIELD> Page
+ <SDFIELD TYPE=PAGE SUBTYPE=RANDOM FORMAT=PAGE>4</SDFIELD> of <SDFIELD TYPE=DOCSTAT SUBTYPE=PAGE FORMAT=PAGE>4</SDFIELD></FONT></P>
+</DIV>
+</BODY>
+</HTML>
diff --git a/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html b/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html
new file mode 100644
index 0000000..cedade7
--- /dev/null
+++ b/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html
@@ -0,0 +1,345 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 6.0 (Win32)">
+ <META NAME="CREATED" CONTENT="20020128;9504400">
+ <META NAME="CHANGED" CONTENT="20020205;7150155">
+ <STYLE>
+ <!--
+ @page { margin: 2cm }
+ -->
+ </STYLE>
+</head>
+<body LANG="en-US">
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><FONT SIZE=5><B>Proposal
+v0.2</B></FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><FONT SIZE=5><B>A new
+keyboard shortcut implementation</B></FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Due to our efforts making the office
+accessible we have to solve some problems regarding keyboard
+shortcuts. This is a chance to enhance our current implementation for
+a better user convenience.
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The following list shows problems
+regarding our current keyboard shortcut implementation:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">The database and bibliography
+ components are not sfx based. So these components are not able to
+ use a component specific keyboard shortcut configuration. They are
+ only bound to the global keyboard shortcut configuration implemented
+ in the sfx project.<BR><BR>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">Currently we support keyboard
+ shortcut configuration files, but we have to present a better
+ integration for the user to easily adopt his office to other
+ systems/office (See proposal from FLO “<B>Keyboard
+ Accessibility Concept</B>” about MS Office compatible keyboard
+ shortcut configuration).<BR><BR>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">We have two different keyboard
+ shortcut configuration file formats. One is based on our old
+ resource file format and supports different languages. If the user
+ changes the keyboard shortcut configuration through our UI dialogs
+ it is stored in our new XML format. Our xml based keyboard shortcut
+ configuration doesn't support more than one language. So we have to
+ find a way to create language specific XML files. We can write a
+ converter that creates XML files out of our old resource file format
+ automatically.<BR><BR>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">Our current implementation is not
+ fine grained enough. We have a global keyboard shortcut
+ configuration and a component based configuration (writer, calc,
+ ...). We should introduce a new keyboard shortcut configuration that
+ can be temporary used . For example complex dialogs can use this
+ kind of keyboard shortcut configuration to improve their
+ accessibility.<BR><BR>
+ </P>
+</UL>
+<P STYLE="margin-bottom: 0cm">A new implementation should use our new
+XML configuration files. It should support sfx and non-sfx based
+components to enable a better integration of newly written
+components, like <SPAN LANG="en-US">OpenOffice</SPAN>-based ones. So
+the new implementation must be based on UNO-interfaces and should
+support querying, changing, extending and applying configuration data
+through this API. This proposal describes an architecture that can be
+used for all our UI configuration data.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The new implementation has three
+configuration levels:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">Office configuration level<BR>The
+ office configuration level stores data that is visible to all
+ components. This level assures that common functions are mapped to a
+ defined keyboard shortcut.</P>
+ <LI><P STYLE="margin-bottom: 0cm">Component configuration level<BR>The
+ component configuration level store data that is visible to one type
+ of a component (like writer, calc). This level assures that common
+ component functions are always the same for one component.</P>
+ <LI><P STYLE="margin-bottom: 0cm">Document configuration level<BR>This
+ configuration level stores data that is only visible to a document.
+ It is possible to map document specific functions to a keyboard
+ shortcut. For example a calc document can provide a private function
+ to make a time consuming calculation that be easily access by a
+ shortcut.</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><IMG SRC="Proposal_Keyboard_shortcuts_html_6a183024.gif" ALIGN=LEFT><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The implementation should work with two
+different kinds of configurations:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">A one instance service that holds
+ the office configurations and can create settings objects for all
+ components (like writer, <SPAN LANG="en-US">calc</SPAN>, ... ) that
+ are available at runtime. So it works as a factory for component
+ settings objects. The implementation can support new components if
+ the “configuration storage service” is able to provide
+ streams to the configuration of the component.</P>
+ <LI><P STYLE="margin-bottom: 0cm">Model based configuration that has
+ all configuration data that was stored for a single document.
+ </P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The one instance implementation gives
+access to the office configuration and can create all supported
+component based settings objects through a <SPAN LANG="en-US">XMultiServiceFactory</SPAN>
+interface. The controller has references to two different kinds of
+configurations:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">Component shortcut configuration
+ that is shared by all controller instances of a component.</P>
+ <LI><P STYLE="margin-bottom: 0cm">Document shortcut configuration
+ that is shared by all controllers of a model. They data is stored in
+ the model. The access between controller and model is a private
+ implementation detail.</P>
+ <P STYLE="margin-bottom: 0cm"></P>
+</UL>
+<P STYLE="margin-bottom: 0cm">The controller implements an interface
+to give access to the component and document settings objects. These
+setting objects support loading/saving a XML based configuration
+(through XInput- <SPAN LANG="en-US">XoutputStream</SPAN>) and to get,
+add, remove and replace keyboard shortcuts. These settings objects
+can be applied to the controller or the global configuration. So it
+is possible to have generic access to this data for example for an UI
+dialog that supports changing the configuration. As the access is
+granted through UNO interfaces an external developer is able to use
+this implementation, too.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Saving and loading a configuration
+would work in the following way. The controller knows its “component”
+and the current configuration type (for example keyboard ). It asks
+the “global configuration storage service” for a stream
+that stores data for a “writer keyboard” configuration.
+So the knowledge output the real storage is only known by this
+service, all other implementation uses XInputStream and XOutputStream
+to fulfill their work. This stream is given to the concrete settings
+object that knows how to store its data as an XML stream and Save(
+stream ) is called.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The controller supports a function
+<I>MapKeyToFunction</I><SPAN STYLE="font-style: normal"> to get a
+mapping between a com.sun.star.awt.KeyEvent and a function. It should
+first make a lookup into the office configuration to find a valid
+mapping if this is not successful the controller has to ask the
+component settings object and last the document settings object. So
+the call hierachy would be:</SPAN></P>
+<P STYLE="margin-bottom: 0cm; font-style: normal">“office cfg”
+->
+</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal">“component
+cfg” ->
+</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal">“document
+cfg”.</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal">The
+<I>MapKeyToFunction</I> function returns a string that is one of the
+following types:</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal"><BR>
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm; font-style: normal">A slot command
+ URL that can be dispatched.</P>
+ <LI><P STYLE="margin-bottom: 0cm; font-style: normal">A command
+ string that must be executed in the component context, like
+ “.uno:copy”, “.uno:cut”, “.uno:paste”.
+ The command string must comply to the command URL specification
+ “protocol:command”. The command part can be any kind of
+ string. It would be even possible to have an encoded byte stream
+ that could be executed by a special implementation.</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Thorndale, serif"><FONT SIZE=3>The
+current sfx2 keyboard shortcut configuration implementation uses only
+a kind of merged “component shortcut configuration”. A
+closer look reveals that we can split this configuration into three
+different parts:</FONT></FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">Office configuration that is the
+ real base for all components.</P>
+ <LI><P STYLE="margin-bottom: 0cm">Generic sfx based component
+ configuration.
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">Component based configuration (
+ writer, calc, draw, ...).</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The last two configurations should be
+loaded and merged into the “component” shortcut
+configuration” to fit into our new architecture if we are
+running on a system with old configuration layout.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">This proposal just presents a new
+design for the keyboard shortcut configuration but it isn't
+restricted to this special type. There should be no problem to use
+the design to support also:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0cm">Menus</P>
+ <LI><P STYLE="margin-bottom: 0cm">Toolbars</P>
+ <LI><P STYLE="margin-bottom: 0cm">Statusbars</P>
+ <LI><P STYLE="margin-bottom: 0cm">Events</P>
+ <LI><P STYLE="margin-bottom: 0cm">Images</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/proposals/macro/macrorecording.html b/content/framework/proposals/macro/macrorecording.html
new file mode 100644
index 0000000..c96762c
--- /dev/null
+++ b/content/framework/proposals/macro/macrorecording.html
@@ -0,0 +1,207 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 6.0 (Win32)">
+ <META NAME="CREATED" CONTENT="20020218;17044700">
+ <META NAME="CHANGED" CONTENT="20020219;16054255">
+ <STYLE>
+ <!--
+ @page { margin: 2cm }
+ H1 { margin-bottom: 0.21cm }
+ H1.western { font-family: "Albany", sans-serif; font-size: 16pt }
+ H1.cjk { font-size: 16pt }
+ H1.ctl { font-size: 16pt }
+ -->
+ </STYLE>
+</head>
+<body LANG="de-DE">
+<H1 CLASS="western">Some thoughts about Macro Recording</H1>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">All StarOffice versions prior to the
+release of OpenOffice.org had a macro recorder. This tool was able to
+record actions of the user and translate them into StarBasic code. It
+was removed before the OO.o source code was released. To understand
+why it was removed and why it is so hard to create a replacement for
+it, it's necessary to learn something about the way it worked and
+about the internal command processing in OO.o applications.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The OO.o applications are based on the
+SFX application framework. This framework is not an UNO based one,
+it's pure C++. It's main operational area is the management of the
+user interface and the processing of commands created by user
+actions. Every functionality (functions, properties) provided by an
+SFX based application component is described by a structure called
+„slot“. It contains a number identifying the slot (the
+„slot id“), some additional information for internal
+processing inside SFX (some mostly boolean parameters describing the
+slot), a name (its „API name“) and the information wether
+this slot represents a function or a property. For functions it also
+contains a list of all parameters and their names and types and the
+type of the return value, for properties it contains the property
+type.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">All the slots and their properties are
+known at compile time to the application module they belong to.
+Inside the application modules the slots are grouped together into
+data structures called „(slot) interface“. Every module
+knows several interfaces, each of them representing a „context“
+of the user interface. Examples are the contexts „text
+document“, „impress slide view“, „table
+selection“, each of them is represented by a corresponding slot
+interface (or a group of them). The sum of all currently available
+contextes (slot interfaces) defines the available feature set of an
+SFX based application component.</P>
+<P STYLE="margin-bottom: 0cm">
+</P>
+<P STYLE="margin-bottom: 0cm">The SFX application framework learns
+about the slots by being dynamically bound to the modules and slot
+interfaces at runtime. So it is able to browse through the whole
+available feature set of the application component. All currently
+bound slot interfaces are pushed on a stack provided by the SFX
+framework, thus defining an ordering mechanism for them. Pushing
+interfaces on the stack or removing interfaces from there is the way
+context switches in the user interface are reflected in the SFX.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">All user interface elements written for
+the SFX (f.e. toolboxes, menus, keyboard shortcuts) don't call
+directly into the application code, they just call a very generic SFX
+based API to execute a slot. The slot is identified by its slot id
+and the SFX framework is able to find the right code that is able to
+process the slot by browsing through the bound slot interfaces in a
+well defined manner, using the stack of slot interfaces mentioned
+above. Many calls are executed without additional parameters, but
+many others also pass parameters while executing the slot. An example
+for the first case is a simple click on a menu entry. An example for
+the second case is when the user changes some values in a dialog and
+leaves the dialog by clicking its „OK“ button. Here all
+changed values in the dialog are sent as parameters of the slot
+command.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The generic API assures that every
+command goes through the same code in the SFX framework, and so this
+framework is able to translate every slot execution into a single
+StarBasic statement or a group of them, just by finding the slot
+structure belonging to the slot being executed, the slot interface it
+is belonging to, getting the slots' API name and identifying the
+parameters. (In the user interface usually no return values are
+processed.) Here a slot interface or a group of slot interfaces
+represents an object, every slot is a method or a property of such
+object. Both together form a StarBasic statement like „Object.Method(
+)“.</P>
+<P STYLE="margin-bottom: 0cm">The Basic code generated this way used
+the so called „old“ SO-Basic API, that is not supported
+anymore in OO.o and SO6, and it is not in any way related to the
+„real“ API of the OO.o/SO applications.
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The slot based API is still used for
+large parts of the internal command execution in OO.o (the
+communication between the application component and its user
+interface), but it is not possible to translate it into any UNO based
+API. To be honest, only a few slot calls will ever end up in calling
+a UNO based API of the underlying application component.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">It is possible to transform every slot
+command into a call for the generic UNO based „dispatch API“,
+where every functionality is described by a command string (we call
+them „command URLs“, because they use the form
+„scheme:scheme dependent part“).</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">This API uses a chain of objects
+implementing the DispatchProvider service. If the first object in the
+chain is asked for a Dispatch object for an arbitrary command, it
+will check the command if it wants to handle it. If the check turns
+out to be positive, a Dispatch object is returned that is able to
+execute the command, otherwise the query is passed to the next chain
+object etc. If a Dispatch object was found anywhere in the chain,
+the command is executed by calling the dispatch method of the
+Dispatch object, where all parameters are passed as PropertyValue
+structs.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The result of a transformation from SFX
+slot execution to dispatch call is a call dispatching the command
+„<A HREF="slot:xxxx">slot:xxxx</A>“ (xxxx=slot id),
+passing all necessary parameters as PropertyValues. Newer UI
+components are using this API instead of the slot based SFX API, just
+to have a UNO based interface to the application componnent and not a
+C++ based one. The SFX framework provides some wrapper code to
+translate between the slot based API and the dispatch framework for
+all these newer UI components if they are used for a SFX based
+application component.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">But the dispatch API, though being UNO
+based, is only of limited practical use, because these calls are just
+textual representations of the binary slot data. If you want to write
+a program that uses OO.o API to work on OO.o documents, the dispatch
+API is definitely not the one you want to use (except in some special
+cases, where the functionality is not accessible by other APIs). The
+dispatch API is just thought as the generic programming interface for
+a mostly generic UI code.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">It is possible to record macros just
+for automation purposes using the SFX or the dispatch API calls:
+take the internal binary representation of the slot commands (or the
+command URL and the parameters of the dispatch call), store it
+anywhere and execute it afterwards by using a „slot machine“
+(only evil thinking persons will misunderstood this name in this
+context here ;-) ) or a „dispatch machine“. But usually a
+macro macro recorder is wanted to offer more than only automation:
+most people want to have created source code they can browse and
+modify. And this is exactly what you can't get from the SFX. Many
+(most?) user interactions in the OO.o applications are processed
+without any single UNO call, so there is nothing you can „record“.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">So what do we need to have the „macro
+recording“ feature back?</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">First, every slot execution (or
+dispatch call) must be mapped to one or several API calls of the
+objects they are working on. This is hard work enough, don't expect
+this to happen in the near future.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">But even if you have got this made, you
+will need something that translates the API calls made into source
+code of any (scripting) language supporting UNO. This can't be a
+built-in UNO feature, because you want only the „top level“
+UNO calls to be recorded, not the subsequent calls, because you will
+get them called anyway when executing the macro. Perhaps the „top
+level“ calls could marked as recordable by the (AFAIK currently
+not accessible UNO context), but this looks „hacky“ and
+ugly to me.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">I'd prefer an explicit solution, where
+every dispatch provider object that returns a dispatch object will be
+asked to record this call into one or several API statements, but I
+don't have any clever ideas for that.
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">So I'd appreciate any ideas from
+anybody who wants to contribute to that. May be it turns out that the
+„UNO built in“ solution is not that hacky as it seems,
+may be that there is something completely different that puts a new
+light on the problem.
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/framework/proposals/macro_security/security_enhancements.html b/content/framework/proposals/macro_security/security_enhancements.html
new file mode 100644
index 0000000..3a4c8ee
--- /dev/null
+++ b/content/framework/proposals/macro_security/security_enhancements.html
@@ -0,0 +1,233 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 6.0 (Win32)">
+ <META NAME="CREATED" CONTENT="20011123;18135200">
+ <META NAME="CHANGED" CONTENT="20011128;10004660">
+
+</head>
+<body LANG="de-DE">
+<H1 CLASS="western"><SPAN LANG="en-US">Security Enhancements in
+StarOffice 6.0 / OpenOffice.org according to IssueZilla Bug
+#1120
+</span></H1>
+<SPAN LANG="en-US">
+<H1 CLASS="western"> Problem to Solve</H1>
+<OL>
+ <P LANG="en-US" STYLE="margin-bottom: 0cm">Macros in all documents, executed
+ via file:// url; will be executed without warning.</P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<OL>
+ <H2 CLASS="western">Solution</H2>
+</OL>
+<OL>
+ <P STYLE="margin-bottom: 0cm"><SPAN LANG="en-US">A solution to solve this problem
+ is to give users the possibility to set all macro related security settings
+ in <I>Tools-Option-Security </I><SPAN STYLE="font-style: normal">tab.</SPAN></SPAN></P>
+</OL>
+<OL>
+ <P LANG="en-US" STYLE="margin-bottom: 0cm; font-style: normal">The following
+ steps should solve the problem.</P>
+</OL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm; font-style: normal"><BR>
+</P>
+<OL>
+ <H3 CLASS="western"><B>Path Settings</B></H3>
+ <P CLASS="western">The path list (<I>Tools-Options-Security</I>) contains all
+ trusted path given by users. The default<BR>
+ 'file://' entry in the path list should be replace by more precise paths listed
+ below:</P>
+</OL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm; font-style: normal"><BR>
+</P>
+<UL>
+ <LI>
+ <P LANG="en-US" STYLE="margin-bottom: 0cm">$instURL</P>
+ <LI>
+ <P STYLE="margin-bottom: 0cm">$userURL</P>
+ <LI>
+ <P LANG="en-US" STYLE="margin-bottom: 0cm">$workDIR</P>
+</UL>
+<P LANG="en-US" STYLE="margin-left: 0.53cm; margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-left: 0.53cm; margin-bottom: 0cm"><SPAN LANG="en-US">All path
+ has to point to standard folders. Changing the old file URL to the three new
+ once provides more security due to the fact that users do not have the possibility
+ to run macros from directories like <I>Temp for </I><SPAN STYLE="font-style: normal">example.</SPAN></SPAN></P>
+<P STYLE="margin-left: 0.53cm; margin-bottom: 0cm"><BR>
+</P>
+<OL START=2>
+ <H3 CLASS="western"><B>Run Macro Settings</B></H3>
+ <P STYLE="margin-bottom: 0cm">The three radio buttons (From list, Never execute,
+ Always execute) located on the Tools-Options-Security page will be replace
+ by a dropdown list box (labeled <I>Run macros</I>) which contains the three
+ options</P>
+ <P LANG="en-US" STYLE="margin-bottom: 0cm; font-style: normal">
+ <SPAN ID="Frame1" STYLE="float: left; width: 15.88cm; height: 0.53cm; padding: 0cm; background: #ffffff">
+ <TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
+ <COL WIDTH=128*> <COL WIDTH=128*> <THEAD>
+ <TR VALIGN=TOP>
+ <TH WIDTH=50%>
+ <P CLASS="western">Old Term</P>
+ </TH>
+ <TH WIDTH=50%>
+ <P CLASS="western">New Term</P>
+ </TH>
+ </TR>
+ </THEAD> <TBODY>
+ <TR VALIGN=TOP>
+ <TD WIDTH=50%>
+ <P CLASS="western">From list</P>
+ </TD>
+ <TD WIDTH=50%>
+ <P CLASS="western">According to path list</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=50%>
+ <P LANG="en-US" CLASS="western">Never execute</P>
+ </TD>
+ <TD WIDTH=50%>
+ <P CLASS="western">Never</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=50%>
+ <P LANG="en-US" CLASS="western">Always execute</P>
+ </TD>
+ <TD WIDTH=50%>
+ <P CLASS="western">Always</P>
+ </TD>
+ </TR>
+ </TBODY>
+ </TABLE>
+ <P CLASS="frame-contents-western"><BR>
+ <BR>
+ </P>
+ </SPAN><BR CLEAR=LEFT>
+ The options will be renamed as listed below:<BR>
+ In addition beneath to the <I>Run</I> <I>macros</I> dropdown list box are located
+ two check boxes. The first one is labeled <I>Confirm in the case of other document
+ sources</I> the other is labeled <I>Show warning before running macros. </I>The<I>
+ Show warning before running </I>feature is the renamed and removed feature of
+ Tools-Configure-Events / Security settings (Figure <A HREF="#Graphic1|graphic">1</A>
+ & <A HREF="#Graphic2|graphic">2</A>)<BR>
+ <BR>
+ The<I> Confirm in the case of other document sources</I> option will be enabled
+ if users chose the <I>According to path list</I> option in the dropdown list,
+ otherwise the Confirm ..... item remains disabled (grayed out).<BR>
+ <BR>
+ <p></P>
+ <P STYLE="margin-bottom: 0cm"><SPAN LANG="en-US"><SPAN STYLE="font-style: normal">The
+ </SPAN><I>Show warning before running macros </I><SPAN STYLE="font-style: normal">option
+ will be disabled if the option </SPAN><I>Never</I><SPAN STYLE="font-style: normal">
+ was chosen in the </SPAN><I>Run Macros</I><SPAN STYLE="font-style: normal">
+ dropdown list box. The states are illustrated in Figure <A HREF="#Graphic3|graphic">3</A>,<A HREF="#Graphic4|graphic">4</A>,<A HREF="#Graphic4|graphic">5</A>
+ & </SPAN></SPAN><A HREF="#Graphic6|graphic">6</A>.<BR>
+ <BR>
+ </P>
+ <H3 CLASS="western" STYLE="font-style: normal"><B>Warning Message</B></H3>
+ <P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="font-style: normal">The
+ warning message which appears, if a macro will be run from a </SPAN>location
+ which is not trusted, should be expanded by a more detailed information. The
+ renewed warning dialogue needs much space for text than the old one.</P>
+ <P STYLE="margin-bottom: 0cm"><SPAN LANG="en-US"><BR>
+ <B>Current Text</B><BR>
+ <I>An event to which a macro is configured has been started. Do you want to
+ execute the macro?</I><BR>
+ <BR>
+ <SPAN STYLE="font-style: normal">CheckBox</SPAN><I> Do not warn again for
+ this document</I>.<BR>
+ OKButton <I>Run</I><BR>
+ CancelButton <I>Don't</I> <I>run</I></SPAN></P>
+ <P STYLE="margin-bottom: 0cm"><SPAN LANG="en-US"><BR>
+ <B>New Text (macro title is an example):</B><BR>
+ <I>An event to which a macro, called "soffice.Gimmicks..GetTexts. GetCalcGraphicNames",
+ is configured has been started. Do you want to run the macro?<BR>
+ <BR>
+ </I><SPAN STYLE="font-style: normal">CheckBox</SPAN><I> Do not warn again
+ for this document</I></SPAN>.<BR>
+ OKButton <I>Run</I><BR>
+ CancelButton <I>Don't</I> <I>run</I></P>
+ <H3 CLASS="western"><BR>
+ Illustrations</H3>
+</OL>
+<P CLASS="western">
+<SPAN ID="Frame2" STYLE="background: #ffffff"
+ >
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic1|graphic"></A></P>
+</SPAN><span lang="en-US"><span id="Frame2" style="background: #ffffff"
+ ><img src="security_enhancements_html_m2dbadf08.gif" name="Graphic1" align=LEFT width=572 border=0 height="422"></span></span><SPAN ID="Frame2" STYLE="background: #ffffff"
+ >
+<P STYLE="margin-top: 0.21cm"><BR CLEAR=LEFT>
+ <FONT SIZE=2><I>Illustration 1 current Configuration/Events tab</I></FONT></P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western"><BR>
+ <BR>
+</P>
+<P CLASS="western"><BR>
+ <BR>
+</P>
+<P CLASS="western"><BR>
+ <BR>
+</P>
+<P CLASS="western">
+<SPAN ID="Frame3" STYLE="background: #ffffff"
+ >
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic2|graphic"></A><IMG SRC="security_enhancements_html_51f79ff8.gif" NAME="Graphic2" ALIGN=LEFT WIDTH=572 BORDER=0 height="422"><BR CLEAR=LEFT>
+ <FONT SIZE=2><I> Illustration 2 Configuration/Events dialogue after removing
+ the "Show warning" option.</I></FONT></P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western">
+<SPAN ID="Frame4" STYLE="background: #ffffff"
+ >
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic3|graphic"></A><IMG SRC="security_enhancements_html_70928bb3.gif" NAME="Graphic3" ALIGN=LEFT WIDTH=536 BORDER=0 height="371"><BR CLEAR=LEFT>
+ <FONT SIZE=2><I>Illustration 3 Renewed Tool Options Security dialogue </I></FONT>
+</P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western">
+<SPAN ID="Frame5" STYLE="background: #ffffff"
+ >
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic4|graphic"></A><IMG SRC="security_enhancements_html_m4000e9d0.gif" NAME="Graphic4" ALIGN=LEFT WIDTH=536 BORDER=0><BR CLEAR=LEFT>
+ <FONT SIZE=2><I>Illustration 4 The security dialogue with "Run macro Never"
+ option</I></FONT></P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western"><BR>
+ <BR>
+</P>
+<P CLASS="western">
+<SPAN ID="Frame6" STYLE="background: #ffffff"
+ >
+<P STYLE="margin-top: 0.21cm"><IMG SRC="security_enhancements_html_m4acea22c.gif" NAME="Graphic5" ALIGN=LEFT WIDTH=536 BORDER=0><BR CLEAR=LEFT>
+ <FONT SIZE=2><I>Illustration 5 The security dialogue with "Run macro Alway"
+ option</I></FONT></P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western">
+<SPAN ID="Frame7" STYLE="background: #ffffff">
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic6|graphic"></A><IMG SRC="security_enhancements_html_md0eecca.gif" NAME="Graphic6" ALIGN=LEFT WIDTH=536 BORDER=0><BR CLEAR=LEFT>
+ <FONT SIZE=2><I>Illustration 6 German Version of the new features</I></FONT></P>
+</SPAN><BR>
+<BR>
+<p></P>
+</span>
+</body>
+</HTML>
diff --git a/content/framework/proposals/printing/Standard_Printer.htm b/content/framework/proposals/printing/Standard_Printer.htm
new file mode 100644
index 0000000..ab6b887
--- /dev/null
+++ b/content/framework/proposals/printing/Standard_Printer.htm
@@ -0,0 +1,154 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Frank Loehmann">
+ <META NAME="CREATED" CONTENT="20001107;9561921">
+ <META NAME="CHANGEDBY" CONTENT="Frank Loehmann">
+ <META NAME="CHANGED" CONTENT="20010219;17473391">
+ <STYLE>
+ <!--
+ P { font-family: "Arial", sans-serif }
+ H2 { font-family: "Arial", sans-serif }
+ TD P { font-family: "Arial", sans-serif }
+ TH P { font-family: "Arial", sans-serif }
+ -->
+ </STYLE>
+</HEAD>
+<BODY>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Arial, sans-serif">Autor:
+Frank Loehmann; </FONT><A HREF="mailto:frank.loehmann@germany.sun.com"><FONT FACE="Arial, sans-serif">frank.loehmann@germany.sun.c</FONT></A></P>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Arial, sans-serif">Date: 16
+January 2001; final</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Arial, sans-serif">Use
+Standard Printer as Default Document Printer</FONT></P>
+<H2><FONT FACE="Arial, sans-serif">Problem</FONT></H2>
+<P><FONT FACE="Arial, sans-serif">OpenOffice stores the printer, used
+for the formatting and printing of the current document, in the
+document file itself.</FONT></P>
+<P STYLE="page-break-before: always"><FONT FACE="Arial, sans-serif">The
+restoring of this document printer after loading a document can be a
+problem, if OpenOffice will be used in a global network environment
+(e.g. a WAN or especially in Sun's flexible Office concept using
+SunRay's) or on a system (e.g. a notebook) where different
+environments (printer queue's) are present at the same time. (e.g. a
+notebook used at home and in the company). In such an environment
+documents will often be printed on the false printer when the print
+direct function (offered in the standard object bar) will be used.</FONT></P>
+<P><FONT FACE="Arial, sans-serif">Maybe this problem occurs as well
+if OpenOffice will be used in the new Sun Webtop environment. (not
+evaluated at this point)</FONT></P>
+<H2><FONT FACE="Arial, sans-serif">Solution</FONT></H2>
+<P><FONT FACE="Arial, sans-serif">We have analysed different
+possibilities to solve this problem. Due to our main concern, not to
+confuse the user with a new UI, we decided to look for an easy way to
+solve the problem without big UI changes and without loosing
+features. Always keep in mind that printing is a very key critical
+feature and will be used by nearly every user!</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">The
+direct printing button in the objectbar of OpenOffice does not call
+the print dialog in the current version. For our solution we want to
+show the print dialog in some cases which will cause the problem
+described above.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">We want
+to call the print dialog on condition that the document printer
+differs from the system standard printer and the printer is available
+on the system too. Just not to loose the information which printer
+was set on the document (important for document templates used in
+companies), we should preselect this printer in the print dialog.
+Additionally we should implement a new option in the tools-options
+section to suppress this print dialog at any time and to force the
+printout on the system or document printer.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">If a
+document printer is not available on the current system, the printout
+will be done on the system default printer without any print dialog.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Furthermore
+a bubble help on the direct printout button should show the printer
+which will be used for the printout. Also a new section to the help
+should be added. The help should contain a tip how to set a system
+default printer “hard” to the document without the standard
+printer flag. (maybe important for template design) (-> In this
+case the current standard printer should be changed to a temporary
+one)</FONT></P>
+<P><FONT FACE="Arial, sans-serif"><B>Dialog</B></FONT></P>
+<TABLE WIDTH=753 BORDER=1 CELLPADDING=4 CELLSPACING=0>
+ <COL WIDTH=367>
+ <COL WIDTH=368>
+ <THEAD>
+ <TR VALIGN=TOP>
+ <TH WIDTH=367>
+ <P ALIGN=CENTER><FONT FACE="Arial, sans-serif"><FONT SIZE=3><I>Local
+ System Configuration</I></FONT></FONT></P>
+ </TH>
+ <TH WIDTH=368>
+ <P ALIGN=CENTER><FONT SIZE=3><I><FONT FACE="Arial, sans-serif">
+ Action</FONT></I></FONT></P>
+ </TH>
+ </TR>
+ </THEAD>
+ <TBODY>
+ <TR VALIGN=TOP>
+ <TD WIDTH=367>
+ <P><SPAN STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Document
+ printer is equal to default system printer</FONT></SPAN></P>
+ </TD>
+ <TD WIDTH=368>
+ <P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Printout
+ on default system printer without dialog</FONT></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=367>
+ <P><SPAN STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Printer
+ available but not set as system default</FONT></SPAN></P>
+ </TD>
+ <TD WIDTH=368>
+ <P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Show
+ print dialog with document printer preselected</FONT></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=367>
+ <P><SPAN STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Document
+ printer is not available</FONT></SPAN></P>
+ </TD>
+ <TD WIDTH=368>
+ <P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Printout
+ on default system printer without dialog</FONT></P>
+ </TD>
+ </TR>
+ </TBODY>
+</TABLE>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Arial, sans-serif"><B>Option in the tools-option
+section for print direct</B></FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">We
+should add the following option on tools-options-common-printing:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Print
+direct (group box)</FONT></P>
+<TABLE WIDTH=361 BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
+ <COL WIDTH=351>
+ <THEAD>
+ <TR>
+ <TD WIDTH=351 VALIGN=TOP>
+ <P><FONT FACE="Arial, sans-serif"><B>[ ] Suppress print
+ dialog if document printer does not match system default printer</B></FONT></P>
+ <P><FONT FACE="Arial, sans-serif">(X) always print on system
+ default printer (defaulted)</FONT></P>
+ <P><FONT FACE="Arial, sans-serif">( ) always print on
+ document printer (if available)</FONT></P>
+ </TD>
+ </TR>
+ </THEAD>
+</TABLE>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">The two
+options are disabled as long as the main option (suppressing the
+dialog) is not checked (and this is the default). The option “always
+use system default print” will be defaulted too.</FONT></P>
+</BODY>
+</HTML>
\ No newline at end of file
diff --git a/content/framework/proposals/setup_feature/setup_features60_proposal.html b/content/framework/proposals/setup_feature/setup_features60_proposal.html
new file mode 100644
index 0000000..5feb636
--- /dev/null
+++ b/content/framework/proposals/setup_feature/setup_features60_proposal.html
@@ -0,0 +1,660 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="AUTHOR" CONTENT=" ">
+ <META NAME="CREATED" CONTENT="20001213;10454075">
+ <META NAME="CHANGEDBY" CONTENT=" ">
+ <META NAME="CHANGED" CONTENT="20010216;12114919">
+ <META NAME="SDFOOTNOTE" CONTENT=";;;;;C">
+ <STYLE>
+ <!--
+ @page { size: 21cm 29.7cm; margin: 2cm }
+ H1 { margin-bottom: 0.21cm; font-family: "Arial", sans-serif; font-size: 16pt }
+ TD P { margin-bottom: 0.21cm }
+ P { margin-bottom: 0.21cm }
+ -->
+ </STYLE>
+</head>
+<body>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=4>
+Proposal for a StarOffice / OpenOffice.org 6.0 Setup Feature List</FONT></FONT></P>
+<P ALIGN=CENTER>Version 1, 02/16/2001,
+<A HREF="mailto:Leyla.Schroeder@germany.sun.com">Leyla.Schroeder@germany.sun.com</A></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">Priorities:</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">1 – Must</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">2 – Should</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">3 - Can / Nice to
+have</FONT></P>
+<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000080" CELLPADDING=4 CELLSPACING=0>
+ <COL WIDTH=51*>
+ <COL WIDTH=161*>
+ <COL WIDTH=44*>
+ <THEAD>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Installation in General</H1>
+ </TD>
+ </TR>
+ </THEAD>
+ <TBODY>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>CD / AutoRun</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>AutoRun should be supported under Windows</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>CD / Introscreen</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>An introduction screen should offer installation of the
+ programs that are available on the CD:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">StarOffice / OpenOffice.org
+ 6.0</P>
+ <LI><P STYLE="margin-bottom: 0cm">Acrobat Reader</P>
+ <LI><P>Java Runtime Environment</P>
+ </UL>
+ <P>Furthermore, links to additional information should be
+ offered:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">Documentation</P>
+ <LI><P>Patches (for Solaris)</P>
+ </UL>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Download / Customization</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Download packages should be generated during online-connection
+ to include only those components, the user selects in his
+ session. Therefore we need a tool to create a binary installable
+ file which includes only the required modules.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation package</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The different installation packages should only show those
+ files to the user, that are important to him:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">setup.exe</P>
+ <LI><P STYLE="margin-bottom: 0cm">readme.txt</P>
+ <LI><P STYLE="margin-bottom: 0cm">lincense.txt</P>
+ <LI><P STYLE="margin-bottom: 0cm">jre-(...).exe</P>
+ <LI><P>setup.inf</P>
+ </UL>
+ <P>The installation files (f_00xx) should be moved to a
+ sub-folder.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Setup / Wizard</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The setup should run in window mode, not full screen. The new
+ wizard only consists of sequenced dialog windows.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Setup / Design</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The design of the setup dialogs must be worked over (=>
+ white background with Sun colors).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Setup / Help</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">Pressing the Help button
+ should open the Help in a second, resizable window. For the
+ display our own Textengine (MultiLineEdit) should be used.</SPAN></P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">2</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Setup / Readme</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">For displaying the
+ Readme in a more readable form, an additional button should be
+ offered in the dialog that opens the Readme in a HTML view.</SPAN></P>
+ <P><SPAN STYLE="background: transparent">If no browser exists on
+ the system, the button is disabled. Here only the view in the
+ text field of the dialog is available. (The txt format of the
+ Readme must still exist in the installation package.)</SPAN></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">3</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Migration</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>A migration 5.2 => 6.0 should include:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined AutoCorrect
+ settings</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined AutoText modules</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's Basic macros</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined gallery themes</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined templates</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined dictionaries</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's AddIns</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's Workfolder</P>
+ <LI><P STYLE="margin-bottom: 0cm">Database migration
+ including:<BR>- Addressbook data<BR>- Bibliography data</P>
+ <LI><P><SPAN STYLE="background: transparent">User's
+ configuration data (from user/config), including:<BR>-
+ Palettes<BR>- User-defined Math symbols<BR>- User data<BR>(Further
+ configuration data has to be defined in detail.)</SPAN></P>
+ </UL>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / Program</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>An installation package for multiple languages is needed for
+ the OEM version.</P>
+ <P><FONT FACE="Times New Roman, serif"><SPAN STYLE="background: transparent">Thereby
+ choosing a language is valid for the program language (for menus,
+ dialogs) and the document language (samples, templates).</SPAN></FONT></P>
+ <P>Changing the language after installation should be possible
+ via setup (modify installation).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / linguistic (CJK)</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The Standard installation installs a default set of languages
+ for the linguistic. This set depends on the Office language to be
+ installed. Here the language modules for the CJK version must be
+ re-defined.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / linguistic</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>AutoText and AutoCorrect data must be written language
+ dependent into the installation.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Languages / linguistic</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">The languages for the
+ linguistic that are installed should include not only spell
+ checking, thesaurus and hyphenation but also language-dependent
+ AutoText modules and replacement and exception settings of
+ AutoCorrect.</SPAN></P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">1</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation path</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The default installation path should
+ be:<BR>$:\Programs\(%Productname)60 under
+ Windows<BR>\home\(UserID)\(%productname)60 under Linux/Unix</P>
+ <P>The variable stands for StarOffice60, OpenOffice60,
+ StarSuite60.</P>
+ <P>If using the variable is not possible, the installation path
+ has to use "Office60" instead of the product name.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation space</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user should get more information about the available space
+ when selecting the installation path. (=> list box with
+ devices and available/estimated required space)</P>
+ <P>As we cannot show how many space is really needed for a
+ customized installation as long as the user has not selected the
+ modules to be installed, here the installation path has to be
+ determined by the user after selecting the modules.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Dialog buttons</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Button for starting installation/deinstallation must be
+ renamed from "Complete" to "Install"/"Uninstall"</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Java setup</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user should be better informed for what installing the JRE
+ is good for (Applets, Java services). For this the setup dialog
+ should give a hint and/or the help must be improved.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="3" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Progress bar</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>During the installation process a progress bar appears with
+ text display for actual process description.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Install on demand</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Features, that are not installed yet, will be installed on
+ demand. Thereby the needed files are left on the source (CD or
+ network share) and can be copied down automatically the first
+ time they are used.</P>
+ <P>The user's workflow will not be aborted by this process.</P>
+ <P><A NAME="DDE_LINK1"></A>(It is not clear, if this feature can
+ be realized.)</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">File type info</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>If more than one installation exists on the system, the file
+ type info should be assigned to the latest installation.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>Done</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Adabas</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Adabas must be re-integrated in the setup.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Custom Installation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Module selection</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user may not be allowed to deselect something, that is
+ necessary for a feature/component to be installed.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Subtree icons</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Icons in the subtree should be replaced by more meaningful
+ ones.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><FONT FACE="Times New Roman, serif">Module descriptions</FONT></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Module descriptions must be improved</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / dictionaries</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The dictionaries of the add-on folder must be included in the
+ setup to offer more than 5 languages.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Filterlist</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The filterlist must be reviewed and updated.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Fonts</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>It must be clear to the user which fonts will be installed and
+ for what they are needed. For this a font list must be offered
+ that shows all fonts to be installed (same as Writer / Textfilter
+ Im/Export). Selecting a font entry would display a description.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Product name</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The module selection list box should use the variable for the
+ product name like:
+ </P>
+ <P>- %Productname components</P>
+ <P>+Writer<BR>+Calc</P>
+ <P>Whenever the product name itself is clear, we can use just the
+ short names (Writer, Calc etc. instead of %Productname Writer,
+ %Productname Calc). Thus the variable is necessary only the first
+ time.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Summary</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Before starting the installation the user should get a summary
+ of the settings made.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Change / Repair / Deinstallation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Control Panel</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Win95/98/NT:<BR>When starting deinstallation from the Control
+ Panel's Add/Remove Programs of Windows the option Deinstallation
+ must be selected as default. (Windows only)</P>
+ <P>Win2000:<BR>Here we should offer one Change and one Remove
+ button (instead of Change/Remove). When Change is selected, the
+ default option is "Change installation", when Remove is
+ selected, a message box should appear to ask, if StarOffice /
+ OpenOffice.org really should be deleted.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="3" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Restricted User</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Under W2000/NT installation, deinstallation and changes of the
+ installation are not allowed for restricted users and may not be
+ possible.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>File Deletion</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>All program files and folders of the StarOffice /
+ OpenOffice.org installation must be deleted when deinstalling,
+ only those created or modified by the user remain on the disc
+ (unless, before starting the deinstallation, the user explicitly
+ states that these files have to be deleted, too).</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1 (Windows)</P>
+ <P ALIGN=CENTER>2 (others)</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Repair / Description</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Option is often not understood, must be made more transparent
+ (change text).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Repair / Source</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Repairing from CD should be possible.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Network installation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>/net</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>For calling a network installation we should offer a new
+ possibility (in addition to using DOS box + /net). For this
+ clicking on setupnet.lnk starts network installation:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">setup.exe (calls single-user
+ installation)</P>
+ <LI><P>setupnet.lnk (executes the command "setup -net")</P>
+ </UL>
+ <P>Changing an installation should be possible via
+ double-clicking on the setupnet.lnk, which must remain on the CD)</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Multilingual version</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Installing StarOffice / OpenOffice.org in more than one
+ language should be possible for the network installation. The
+ administrator can choose the language to be installed from all
+ available languages that we offer. The user can choose his
+ language from this sub-set. Only one language can be selected by
+ the user. Thus he should be able to change it later by the setup.</P>
+ <P>=> The workstation installation needs a page for choosing
+ the language.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Naming</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The workstation installation offers the two options "Standard
+ Workstation Installation" and Standard Installation local".
+ </P>
+ <P>These options should be renamed to</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">Workstation Installation</P>
+ <LI><P>Local Installation</P>
+ </UL>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ </TBODY>
+</TABLE>
+<H1><BR><BR>
+</H1>
+<DIV TYPE=FOOTER>
+ <P ALIGN=RIGHT STYLE="margin-top: 0.5cm; margin-bottom: 0cm"><SDFIELD TYPE=PAGE SUBTYPE=RANDOM FORMAT=PAGE>1</SDFIELD></P>
+</DIV>
+</body>
+</HTML>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/module-ix.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/module-ix.html
new file mode 100644
index 0000000..b515025
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/module-ix.html
@@ -0,0 +1,78 @@
+<html>
+<head>
+<title>Module com</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimainself">Module</td>
+<td class="navimainnone">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#NestedModules" class="navisub">Nested Modules</a></td>
+<td class="navisub">Services</td>
+<td class="navisub">Singletons</td>
+<td class="navisub">Interfaces</td>
+<td class="navisub">Structs</td>
+<td class="navisub">Exceptions</td>
+<td class="navisub">Enums</td>
+<td class="navisub">Typedefs</td>
+<td class="navisub">Constant Groups</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../module-ix.html" class="namechain">::</a> <a href="../module-ix.html" class="namechain">drafts</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title">module com</td>
+</tr>
+<tr>
+<td/></tr>
+</table>
+<hr>
+<a name="NestedModules"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Nested Modules</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="sun/module-ix.html">sun</a></td>
+<td class="imsum_right"/></tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/module-ix.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/module-ix.html
new file mode 100644
index 0000000..064a469
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/module-ix.html
@@ -0,0 +1,78 @@
+<html>
+<head>
+<title>Module sun</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimainself">Module</td>
+<td class="navimainnone">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#NestedModules" class="navisub">Nested Modules</a></td>
+<td class="navisub">Services</td>
+<td class="navisub">Singletons</td>
+<td class="navisub">Interfaces</td>
+<td class="navisub">Structs</td>
+<td class="navisub">Exceptions</td>
+<td class="navisub">Enums</td>
+<td class="navisub">Typedefs</td>
+<td class="navisub">Constant Groups</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../module-ix.html" class="namechain">::</a> <a href="../../module-ix.html" class="namechain">drafts</a> :: <a href="../module-ix.html" class="namechain">com</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title">module sun</td>
+</tr>
+<tr>
+<td/></tr>
+</table>
+<hr>
+<a name="NestedModules"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Nested Modules</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="star/module-ix.html">star</a></td>
+<td class="imsum_right"/></tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/module-ix.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/module-ix.html
new file mode 100644
index 0000000..dc3dc67
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/module-ix.html
@@ -0,0 +1,84 @@
+<html>
+<head>
+<title>Module star</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimainself">Module</td>
+<td class="navimainnone">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#NestedModules" class="navisub">Nested Modules</a></td>
+<td class="navisub">Services</td>
+<td class="navisub">Singletons</td>
+<td class="navisub">Interfaces</td>
+<td class="navisub">Structs</td>
+<td class="navisub">Exceptions</td>
+<td class="navisub">Enums</td>
+<td class="navisub">Typedefs</td>
+<td class="navisub">Constant Groups</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../module-ix.html" class="namechain">::</a> <a href="../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../module-ix.html" class="namechain">com</a> :: <a href="../module-ix.html" class="namechain">sun</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title">module star</td>
+</tr>
+<tr>
+<td/></tr>
+</table>
+<hr>
+<a name="NestedModules"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Nested Modules</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="form/module-ix.html">form</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="script/module-ix.html">script</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="table/module-ix.html">table</a></td>
+<td class="imsum_right"/></tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/BrowseNodeTypes.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/BrowseNodeTypes.html
new file mode 100644
index 0000000..b2f28ba
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/BrowseNodeTypes.html
@@ -0,0 +1,145 @@
+<html>
+<head>
+<title>Constants' Group BrowseNodeTypes</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainnone">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#Constants" class="navisub">Constants</a></td>
+<td class="navisub"><a href="#ConstantDetails" class="navisub">Constants' Details</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../module-ix.html" class="namechain">sun</a> :: <a href="../../module-ix.html" class="namechain">star</a> :: <a href="../module-ix.html" class="namechain">script</a> :: <a href="module-ix.html" class="namechain">browse</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title">constants group BrowseNodeTypes</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+<hr>
+<a name="Constants"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Constants</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#SCRIPT">SCRIPT</a></td>
+<td class="imsum_right">
+ Indicates node is a script
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#CONTAINER">CONTAINER</a></td>
+<td class="imsum_right">
+ Indicates node is a container
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#ROOT">ROOT</a></td>
+<td class="imsum_right">
+ Indicates node is root of the tree.
+</td>
+</tr>
+</table>
+<a name="ConstantDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Constants' Details</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="SCRIPT" class="membertitle">SCRIPT</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td>const short <b>SCRIPT</b> = 0;<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Indicates node is a script
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="CONTAINER" class="membertitle">CONTAINER</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td>const short <b>CONTAINER</b> = 1;<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Indicates node is a container
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="ROOT" class="membertitle">ROOT</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td>const short <b>ROOT</b> = 2;<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Indicates node is root of the tree.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/XBrowseNode-xref.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/XBrowseNode-xref.html
new file mode 100644
index 0000000..5c82f98
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/XBrowseNode-xref.html
@@ -0,0 +1,82 @@
+<html>
+<head>
+<title>Uses of Interface XBrowseNode-xref</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XBrowseNode</td>
+</tr>
+<tr>
+<td><p><a href="XBrowseNode.html"><b>back to interface XBrowseNode</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+<a href="#SupportingServices">Services which Support this Interface<br>
+
+</a>Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a name="SupportingServices"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Services which Support this Interface</td>
+</tr>
+<tr>
+<td>::drafts::com::sun::star::script::<a href="../provider/module-ix.html">provider</a>::<a href="../provider/ScriptProvider.html">ScriptProvider</a><br>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/XBrowseNode.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/XBrowseNode.html
new file mode 100644
index 0000000..0cb560c
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/XBrowseNode.html
@@ -0,0 +1,283 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <title>Interface XBrowseNode</title>
+ <style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+ </style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+ <tbody>
+ <tr>
+ <td class="navimain"><a
+ href="../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+ <td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+ <td class="navimain"><a href="XBrowseNode-xref.html"
+ class="navimain">Use</a></td>
+ <td class="navimainnone">Devguide</td>
+ <td class="navimain"><a
+ href="../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+ </tr>
+ </tbody>
+</table>
+<table border="0" cellpadding="0">
+ <tbody>
+ <tr>
+ <td class="navisub"><a href="#MethodsSummary" class="navisub">Methods'
+Summary</a></td>
+ <td class="navisub"><a href="#MethodsDetails" class="navisub">Methods'
+Details</a></td>
+ <td class="navisub">Attributes' Summary</td>
+ <td class="navisub">Attributes' Details</td>
+ </tr>
+ </tbody>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3"
+ style="margin-bottom: 6pt;">
+ <tbody>
+ <tr>
+ <td>
+ <p class="namechain"><a href="../../../../../../module-ix.html"
+ class="namechain">::</a> <a href="../../../../../module-ix.html"
+ class="namechain">drafts</a> :: <a href="../../../../module-ix.html"
+ class="namechain">com</a> :: <a href="../../../module-ix.html"
+ class="namechain">sun</a> :: <a href="../../module-ix.html"
+ class="namechain">star</a> :: <a href="../module-ix.html"
+ class="namechain">script</a> :: <a href="module-ix.html"
+ class="namechain">browse</a> :: </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="title">interface XBrowseNode</td>
+ </tr>
+ <tr>
+ <td>
+ <dl>
+ <dt><b>Base Hierarchy</b></dt>
+ <dd>
+ <pre style="font-family: monospace;">::com::sun::star::uno::XInterface<br> |<br> +-<b>XBrowseNode</b></pre>
+ </dd>
+ </dl>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <dl>
+ <dt><b>Description</b></dt>
+ <dd><br>
+ </dd>
+ </dl>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<hr>
+<a name="MethodsSummary"></a>
+<table border="1" width="100%" cellpadding="5" cellspacing="0"
+ class="subtitle">
+ <tbody>
+ <tr>
+ <td class="subtitle" colspan="2">Methods' Summary</td>
+ </tr>
+ <tr>
+ <td class="imsum_left"><a href="#getName">getName</a></td>
+ <td class="imsum_right"> Get the name of the node
+ </td>
+ </tr>
+ <tr>
+ <td class="imsum_left"><a href="#getChildNodes">getChildNodes</a></td>
+ <td class="imsum_right"> Get the children of this node
+ </td>
+ </tr>
+ <tr>
+ <td class="imsum_left"><a href="#hasChildNodes">hasChildNodes</a></td>
+ <td class="imsum_right"> Indicates if this node contains any
+children
+ </td>
+ </tr>
+ <tr>
+ <td class="imsum_left"><a href="#getType">getType</a></td>
+ <td class="imsum_right"> the type of the node.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<a name="MethodsDetails"></a>
+<table border="1" width="100%" cellpadding="5" cellspacing="0"
+ class="subtitle">
+ <tbody>
+ <tr>
+ <td class="subtitle">Methods' Details</td>
+ </tr>
+ <tr>
+ <td class="imdetail"><a name="getName" class="membertitle">getName</a>
+ <table border="0" width="96%" cellpadding="5" cellspacing="0"
+ bgcolor="#ffffff" align="center">
+ <tbody>
+ <tr>
+ <td>
+ <table border="0">
+ <tbody>
+ <tr>
+ <td valign="top">string<br>
+ <b>getName</b>();</td>
+ <td valign="top"> <br>
+ </td>
+ <td valign="top"> <br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <hr>
+ <dl>
+ <dt><b>Description</b></dt>
+ <dd> Get the name of the node
+ </dd>
+ <dt><b>Returns</b></dt>
+ <dd> The<code> string</code> name of this node
+ </dd>
+ </dl>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ <tr>
+ <td class="imdetail"><a name="getChildNodes" class="membertitle">getChildNodes</a>
+ <table border="0" width="96%" cellpadding="5" cellspacing="0"
+ bgcolor="#ffffff" align="center">
+ <tbody>
+ <tr>
+ <td>
+ <table border="0">
+ <tbody>
+ <tr>
+ <td valign="top">sequence< <a
+ href="XBrowseNode.html">XBrowseNode</a> ><br>
+ <b>getChildNodes</b>();</td>
+ <td valign="top"> <br>
+ </td>
+ <td valign="top"> <br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <hr>
+ <dl>
+ <dt><b>Description</b></dt>
+ <dd> Get the children of this node
+ </dd>
+ <dt><b>Returns</b></dt>
+ <dd><a href="XBrowseNode.html">XBrowseNode</a> sequence
+of child nodes
+ </dd>
+ </dl>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ <tr>
+ <td class="imdetail"><a name="hasChildNodes" class="membertitle">hasChildNodes</a>
+ <table border="0" width="96%" cellpadding="5" cellspacing="0"
+ bgcolor="#ffffff" align="center">
+ <tbody>
+ <tr>
+ <td>
+ <table border="0">
+ <tbody>
+ <tr>
+ <td valign="top">boolean<br>
+ <b>hasChildNodes</b>();</td>
+ <td valign="top"> <br>
+ </td>
+ <td valign="top"> <br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <hr>
+ <dl>
+ <dt><b>Description</b></dt>
+ <dd> Indicates if this node contains any children
+ </dd>
+ <dt><b>Returns</b></dt>
+ <dd><code> boolean</code> true if there are child nodes.
+ </dd>
+ </dl>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ <tr>
+ <td class="imdetail"><a name="getType" class="membertitle">getType</a>
+ <table border="0" width="96%" cellpadding="5" cellspacing="0"
+ bgcolor="#ffffff" align="center">
+ <tbody>
+ <tr>
+ <td>
+ <table border="0">
+ <tbody>
+ <tr>
+ <td valign="top">short<br>
+ <b>getType</b>();</td>
+ <td valign="top"> <br>
+ </td>
+ <td valign="top"> <br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <hr>
+ <dl>
+ <dt><b>Description</b></dt>
+ <dd> the type of the node.
+ </dd>
+ <dt><b>Returns</b></dt>
+ <dd> A<code> short</code> reresenting the type of this
+node.
+ </dd>
+ </dl>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<a href="#_top_">Top of Page</a>
+<hr size="3">
+<p class="copyright" align="center">Copyright © 2003 Sun
+Microsystems, Inc.</p>
+</body>
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/module-ix.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/module-ix.html
new file mode 100644
index 0000000..3c7b693
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/browse/module-ix.html
@@ -0,0 +1,90 @@
+<html>
+<head>
+<title>Module browse</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimainself">Module</td>
+<td class="navimainnone">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub">Nested Modules</td>
+<td class="navisub">Services</td>
+<td class="navisub">Singletons</td>
+<td class="navisub"><a href="#Interfaces" class="navisub">Interfaces</a></td>
+<td class="navisub">Structs</td>
+<td class="navisub">Exceptions</td>
+<td class="navisub">Enums</td>
+<td class="navisub">Typedefs</td>
+<td class="navisub"><a href="#ConstantGroups" class="navisub">Constant Groups</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../module-ix.html" class="namechain">sun</a> :: <a href="../../module-ix.html" class="namechain">star</a> :: <a href="../module-ix.html" class="namechain">script</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title">module browse</td>
+</tr>
+<tr>
+<td/></tr>
+</table>
+<hr>
+<a name="Interfaces"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Interfaces</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XBrowseNode.html">XBrowseNode</a></td>
+<td class="imsum_right">
+</td>
+</tr>
+</table>
+<a name="ConstantGroups"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Constant Groups</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="BrowseNodeTypes.html">BrowseNodeTypes</a></td>
+<td class="imsum_right">
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/module-ix.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/module-ix.html
new file mode 100644
index 0000000..27ea8f6
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/module-ix.html
@@ -0,0 +1,81 @@
+<html>
+<head>
+<title>Module framework</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimainself">Module</td>
+<td class="navimainnone">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#NestedModules" class="navisub">Nested Modules</a></td>
+<td class="navisub">Services</td>
+<td class="navisub">Singletons</td>
+<td class="navisub">Interfaces</td>
+<td class="navisub">Structs</td>
+<td class="navisub">Exceptions</td>
+<td class="navisub">Enums</td>
+<td class="navisub">Typedefs</td>
+<td class="navisub">Constant Groups</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../module-ix.html" class="namechain">sun</a> :: <a href="../../module-ix.html" class="namechain">star</a> :: <a href="../module-ix.html" class="namechain">script</a> :: </p>
+</td>
+</tr>
+<tr>
+<td class="title">module framework</td>
+</tr>
+<tr>
+<td/></tr>
+</table>
+<hr>
+<a name="NestedModules"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Nested Modules</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="security/module-ix.html">security</a></td>
+<td class="imsum_right"/></tr>
+<tr>
+<td class="imsum_left"><a href="storage/module-ix.html">storage</a></td>
+<td class="imsum_right"/></tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/XScriptSecurity-xref.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/XScriptSecurity-xref.html
new file mode 100644
index 0000000..1922d4a
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/XScriptSecurity-xref.html
@@ -0,0 +1,82 @@
+<html>
+<head>
+<title>Uses of Interface XScriptSecurity-xref</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XScriptSecurity</td>
+</tr>
+<tr>
+<td><p><a href="XScriptSecurity.html"><b>back to interface XScriptSecurity</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+<a href="#SupportingServices">Services which Support this Interface<br>
+
+</a>Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a name="SupportingServices"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Services which Support this Interface</td>
+</tr>
+<tr>
+<td>::drafts::com::sun::star::script::framework::<a href="../storage/module-ix.html">storage</a>::<a href="../storage/ScriptStorageManager.html">ScriptStorageManager</a><br>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/XScriptSecurity.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/XScriptSecurity.html
new file mode 100644
index 0000000..4f3731d
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/XScriptSecurity.html
@@ -0,0 +1,158 @@
+<html>
+<head>
+<title>Interface XScriptSecurity</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimain"><a href="XScriptSecurity-xref.html" class="navimain">Use</a></td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#MethodsSummary" class="navisub">Methods' Summary</a></td>
+<td class="navisub"><a href="#MethodsDetails" class="navisub">Methods' Details</a></td>
+<td class="navisub">Attributes' Summary</td>
+<td class="navisub">Attributes' Details</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../../module-ix.html" class="namechain">sun</a> :: <a href="../../../module-ix.html" class="namechain">star</a> :: <a href="../../module-ix.html" class="namechain">script</a> :: <a href="../module-ix.html" class="namechain">framework</a> [...]
+</td>
+</tr>
+<tr>
+<td class="title">interface XScriptSecurity</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Hierarchy</b></dt>
+<dd><pre style="font-family:monospace;">::com::sun::star::uno::XInterface
+ |
+ +-<b>XScriptSecurity</b></pre></dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>
+ This interface provides a means of determining whether a requested type
+ of access (eg. read, execute) to a given script is allowed or denied.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+<hr>
+<a name="MethodsSummary"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Methods' Summary</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#checkPermission">checkPermission</a></td>
+<td class="imsum_right">
+ Determines whether permission is allowed for a given action on a
+ given script. Returns silently if permission is granted, throws an
+ ::com::sun::star::security::AccessControlException
+ if permission is denied.
+
+</td>
+</tr>
+</table>
+<a name="MethodsDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Methods' Details</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="checkPermission" class="membertitle">checkPermission</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">void<br>
+<b>checkPermission</b>(</td>
+<td valign="top"> <br>
+[in] string<br>
+[in] string <br><p class="raise">raises( </p>
+</td>
+<td valign="top"> <br>
+docURI,<br>
+permissionRequested ) <br>
+::com::sun::star::lang::IllegalArgumentException,<br>
+::com::sun::star::security::AccessControlException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Determines whether permission is allowed for a given action on a
+ given script. Returns silently if permission is granted, throws an
+ ::com::sun::star::security::AccessControlException
+ if permission is denied.
+
+</dd>
+<dt><b>Parameter docURI</b></dt>
+<dd>
+ a URI for the script storage
+
+</dd>
+<dt><b>Parameter permissionRequested</b></dt>
+<dd>
+ a string describing the type of permission being requested,
+ eg. "execute", "read".
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd> ::com::sun::star::lang::IllegalArgumentException
+ if there is no matching script name, if the permissionRequested
+ is not recognised
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd> ::com::sun::star::security::AccessControlException
+ if the permission requested is not granted
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/module-ix.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/module-ix.html
new file mode 100644
index 0000000..48684b0
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/security/module-ix.html
@@ -0,0 +1,82 @@
+<html>
+<head>
+<title>Module security</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimainself">Module</td>
+<td class="navimainnone">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub">Nested Modules</td>
+<td class="navisub">Services</td>
+<td class="navisub">Singletons</td>
+<td class="navisub"><a href="#Interfaces" class="navisub">Interfaces</a></td>
+<td class="navisub">Structs</td>
+<td class="navisub">Exceptions</td>
+<td class="navisub">Enums</td>
+<td class="navisub">Typedefs</td>
+<td class="navisub">Constant Groups</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../../module-ix.html" class="namechain">sun</a> :: <a href="../../../module-ix.html" class="namechain">star</a> :: <a href="../../module-ix.html" class="namechain">script</a> :: <a href="../module-ix.html" class="namechain">framework</a> [...]
+</td>
+</tr>
+<tr>
+<td class="title">module security</td>
+</tr>
+<tr>
+<td/></tr>
+</table>
+<hr>
+<a name="Interfaces"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Interfaces</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XScriptSecurity.html">XScriptSecurity</a></td>
+<td class="imsum_right">
+ This interface provides a means of determining whether a requested type
+ of access (eg. read, execute) to a given script is allowed or denied.
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorage-xref.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorage-xref.html
new file mode 100644
index 0000000..9a3b219
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorage-xref.html
@@ -0,0 +1,64 @@
+<html>
+<head>
+<title>Uses of Service ScriptStorage-xref</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of service ScriptStorage</td>
+</tr>
+<tr>
+<td><p><a href="ScriptStorage.html"><b>back to service ScriptStorage</b></a><br>
+<br>
+
+Services which Include this Service<br>
+
+Singletons which Instantiate this Service<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorage.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorage.html
new file mode 100644
index 0000000..b383ba2
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorage.html
@@ -0,0 +1,106 @@
+<html>
+<head>
+<title>Service ScriptStorage</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimain"><a href="ScriptStorage-xref.html" class="navimain">Use</a></td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub">Included Services</td>
+<td class="navisub"><a href="#ExportedInterfaces" class="navisub">Exported Interfaces</a></td>
+<td class="navisub">Properties' Summary</td>
+<td class="navisub">Properties' Details</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../../module-ix.html" class="namechain">sun</a> :: <a href="../../../module-ix.html" class="namechain">star</a> :: <a href="../../module-ix.html" class="namechain">script</a> :: <a href="../module-ix.html" class="namechain">framework</a> [...]
+</td>
+</tr>
+<tr>
+<td class="title">service ScriptStorage</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>
+ This service provides an interface for accessing the scripts contained in a
+ script storage area (user, share or individual documents). It also provides a
+ means of saving this information (not currently supported), and refreshing its
+ data.
+
+ Also see the<a href="http://framework.openoffice.org/scripting/developer-guide.html"> General Developer Guide</a> for details of the parcel-descriptor.xml file from which the script metadata is read.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+<hr>
+<a name="ExportedInterfaces"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Exported Interfaces</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XScriptInfoAccess.html">XScriptInfoAccess</a></td>
+<td class="imsum_right"><dl></dl>
+
+ This interface provides information on the scripts available from a
+ ScriptStorage.
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XScriptStorageExport.html">XScriptStorageExport</a></td>
+<td class="imsum_right"><dl></dl>
+
+ This interface provides a means of saving the information contained in the
+ ScriptStorage component.<b> (Not currently supported)</b>
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XScriptStorageRefresh.html">XScriptStorageRefresh</a></td>
+<td class="imsum_right"><dl></dl>
+
+ This interface provides a means of refreshing the information contained in the
+ ScriptStorage component.
+</td>
+</tr>
+</table>
+<br> <a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorageManager-xref.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorageManager-xref.html
new file mode 100644
index 0000000..4769d65
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorageManager-xref.html
@@ -0,0 +1,74 @@
+<html>
+<head>
+<title>Uses of Service ScriptStorageManager-xref</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of service ScriptStorageManager</td>
+</tr>
+<tr>
+<td><p><a href="ScriptStorageManager.html"><b>back to service ScriptStorageManager</b></a><br>
+<br>
+
+Services which Include this Service<br>
+
+<a href="#Singletons">Singletons which Instantiate this Service<br>
+
+</a>References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a name="Singletons"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Singletons which Instantiate this Service</td>
+</tr>
+<tr>
+<td><a href="theScriptStorageManager.html">theScriptStorageManager</a><br>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorageManager.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorageManager.html
new file mode 100644
index 0000000..931c627
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/ScriptStorageManager.html
@@ -0,0 +1,100 @@
+<html>
+<head>
+<title>Service ScriptStorageManager</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimain"><a href="ScriptStorageManager-xref.html" class="navimain">Use</a></td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub">Included Services</td>
+<td class="navisub"><a href="#ExportedInterfaces" class="navisub">Exported Interfaces</a></td>
+<td class="navisub">Properties' Summary</td>
+<td class="navisub">Properties' Details</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../../module-ix.html" class="namechain">sun</a> :: <a href="../../../module-ix.html" class="namechain">star</a> :: <a href="../../module-ix.html" class="namechain">script</a> :: <a href="../module-ix.html" class="namechain">framework</a> [...]
+</td>
+</tr>
+<tr>
+<td class="title">service ScriptStorageManager</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>
+ This service provides a means for creation and access of ScriptStorage
+ instances. It also acts as an XEventListener in order to free up a
+ document's script related storage (ScriptStorage instance) when that
+ document closes.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+<hr>
+<a name="ExportedInterfaces"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Exported Interfaces</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="XScriptStorageManager.html">XScriptStorageManager</a></td>
+<td class="imsum_right"><dl></dl>
+
+ This interface provides access to data associated with a script
+</td>
+</tr>
+<tr>
+<td class="imsum_left">::drafts::com::sun::star::script::framework::<a href="../security/module-ix.html">security</a>::<a href="../security/XScriptSecurity.html">XScriptSecurity</a></td>
+<td class="imsum_right"><dl></dl>
+
+ This interface provides a means of determining whether a requested type
+ of access (eg. read, execute) to a given script is allowed or denied.
+</td>
+</tr>
+<tr>
+<td class="imsum_left">::com::sun::star::lang::XEventListener</td>
+<td class="imsum_right"><dl></dl>
+</td>
+</tr>
+</table>
+<br> <a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfo-xref.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfo-xref.html
new file mode 100644
index 0000000..66cde75
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfo-xref.html
@@ -0,0 +1,72 @@
+<html>
+<head>
+<title>Uses of Interface XScriptInfo-xref</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XScriptInfo</td>
+</tr>
+<tr>
+<td><p><a href="XScriptInfo.html"><b>back to interface XScriptInfo</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+Services which Support this Interface<br>
+
+Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfo.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfo.html
new file mode 100644
index 0000000..efae2c1
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfo.html
@@ -0,0 +1,384 @@
+<html>
+<head>
+<title>Interface XScriptInfo</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimain"><a href="XScriptInfo-xref.html" class="navimain">Use</a></td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#MethodsSummary" class="navisub">Methods' Summary</a></td>
+<td class="navisub"><a href="#MethodsDetails" class="navisub">Methods' Details</a></td>
+<td class="navisub">Attributes' Summary</td>
+<td class="navisub">Attributes' Details</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../../module-ix.html" class="namechain">sun</a> :: <a href="../../../module-ix.html" class="namechain">star</a> :: <a href="../../module-ix.html" class="namechain">script</a> :: <a href="../module-ix.html" class="namechain">framework</a> [...]
+</td>
+</tr>
+<tr>
+<td class="title">interface XScriptInfo</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Hierarchy</b></dt>
+<dd><pre style="font-family:monospace;">::com::sun::star::uno::XInterface
+ |
+ +-<b>XScriptInfo</b></pre></dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd> This interface allows access to information of one script
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+<hr>
+<a name="MethodsSummary"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Methods' Summary</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getLogicalName">getLogicalName</a></td>
+<td class="imsum_right">
+ Get the logical name for the script
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getDescription">getDescription</a></td>
+<td class="imsum_right">
+ Get a textual description of the script's function.
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getParcelURI">getParcelURI</a></td>
+<td class="imsum_right">
+ Get the parcel URI
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getLanguageProperties">getLanguageProperties</a></td>
+<td class="imsum_right">
+ Get the language dependant properties of a script
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getLanguage">getLanguage</a></td>
+<td class="imsum_right"> Returns the language the script is written in
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getFunctionName">getFunctionName</a></td>
+<td class="imsum_right"> Access to the language specific name of a script.
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getFileSetNames">getFileSetNames</a></td>
+<td class="imsum_right">
+ Access to the list of filesets defined for this script
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getFilesInFileSet">getFilesInFileSet</a></td>
+<td class="imsum_right">
+ Access to the list of files defined for a given FileSet in this script
+
+</td>
+</tr>
+</table>
+<a name="MethodsDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Methods' Details</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getLogicalName" class="membertitle">getLogicalName</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">string<br>
+<b>getLogicalName</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Get the logical name for the script
+
+</dd>
+<dt><b>Returns</b></dt>
+<dd>
+ The<code> string</code> representing the logical name of the
+ script
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getDescription" class="membertitle">getDescription</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">string<br>
+<b>getDescription</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Get a textual description of the script's function.
+
+</dd>
+<dt><b>Returns</b></dt>
+<dd>
+ A<code> string</code> containing the description.
+ If there is no description, return an empty string
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getParcelURI" class="membertitle">getParcelURI</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">string<br>
+<b>getParcelURI</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Get the parcel URI
+</dd>
+<dt><b>Returns</b></dt>
+<dd>
+ The<code> string</code> URI for the root of the parcel
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getLanguageProperties" class="membertitle">getLanguageProperties</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">::com::sun::star::beans::XPropertySet<br>
+<b>getLanguageProperties</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Get the language dependant properties of a script
+
+</dd>
+<dt><b>Returns</b></dt>
+<dd>
+ com::sun::star::beans::XPropertySet of the language dependant properties
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getLanguage" class="membertitle">getLanguage</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">string<br>
+<b>getLanguage</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd> Returns the language the script is written in
+</dd>
+<dt><b>Returns</b></dt>
+<dd> A<code> string</code> reresenting the language of the script.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getFunctionName" class="membertitle">getFunctionName</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">string<br>
+<b>getFunctionName</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd> Access to the language specific name of a script.
+</dd>
+<dt><b>Returns</b></dt>
+<dd> A<code> string</code> that contains the language specific name.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getFileSetNames" class="membertitle">getFileSetNames</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">sequence< string ><br>
+<b>getFileSetNames</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Access to the list of filesets defined for this script
+</dd>
+<dt><b>Returns</b></dt>
+<dd> A sequence of FileSet names
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getFilesInFileSet" class="membertitle">getFilesInFileSet</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">sequence< string ><br>
+<b>getFilesInFileSet</b>(</td>
+<td valign="top"> <br>
+[in] string</td>
+<td valign="top"> <br>
+fileSetName );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd>
+ Access to the list of files defined for a given FileSet in this script
+
+</dd>
+<dt><b>Parameter fileSetName</b></dt>
+<dd> the name of the FileSet
+
+</dd>
+<dt><b>Returns</b></dt>
+<dd> a sequence of file names
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfoAccess-xref.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfoAccess-xref.html
new file mode 100644
index 0000000..d11eba6
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfoAccess-xref.html
@@ -0,0 +1,82 @@
+<html>
+<head>
+<title>Uses of Interface XScriptInfoAccess-xref</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XScriptInfoAccess</td>
+</tr>
+<tr>
+<td><p><a href="XScriptInfoAccess.html"><b>back to interface XScriptInfoAccess</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+<a href="#SupportingServices">Services which Support this Interface<br>
+
+</a>Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a name="SupportingServices"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Services which Support this Interface</td>
+</tr>
+<tr>
+<td><a href="ScriptStorage.html">ScriptStorage</a><br>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfoAccess.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfoAccess.html
new file mode 100644
index 0000000..7a2f994
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptInfoAccess.html
@@ -0,0 +1,230 @@
+<html>
+<head>
+<title>Interface XScriptInfoAccess</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimain"><a href="XScriptInfoAccess-xref.html" class="navimain">Use</a></td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<table border="0" cellpadding="0">
+<tr>
+<td class="navisub"><a href="#MethodsSummary" class="navisub">Methods' Summary</a></td>
+<td class="navisub"><a href="#MethodsDetails" class="navisub">Methods' Details</a></td>
+<td class="navisub">Attributes' Summary</td>
+<td class="navisub">Attributes' Details</td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td><p class="namechain"><a href="../../../../../../../module-ix.html" class="namechain">::</a> <a href="../../../../../../module-ix.html" class="namechain">drafts</a> :: <a href="../../../../../module-ix.html" class="namechain">com</a> :: <a href="../../../../module-ix.html" class="namechain">sun</a> :: <a href="../../../module-ix.html" class="namechain">star</a> :: <a href="../../module-ix.html" class="namechain">script</a> :: <a href="../module-ix.html" class="namechain">framework</a> [...]
+</td>
+</tr>
+<tr>
+<td class="title">interface XScriptInfoAccess</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Base Hierarchy</b></dt>
+<dd><pre style="font-family:monospace;">::com::sun::star::uno::XInterface
+ |
+ +-<b>XScriptInfoAccess</b></pre></dd>
+</dl>
+</td>
+</tr>
+<tr>
+<td><dl>
+<dt><b>Description</b></dt>
+<dd>
+ This interface provides information on the scripts available from a
+ ScriptStorage.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+<hr>
+<a name="MethodsSummary"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle" colspan="2">Methods' Summary</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getScriptLogicalNames">getScriptLogicalNames</a></td>
+<td class="imsum_right"> Provides a means of obtaining a list of all of the available logical
+ names in the ScriptStorage
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getImplementations">getImplementations</a></td>
+<td class="imsum_right"> Provides a list of scripts implementing a given logical name
+
+</td>
+</tr>
+<tr>
+<td class="imsum_left"><a href="#getAllImplementations">getAllImplementations</a></td>
+<td class="imsum_right"> Provides a list of all scripts in a storage area
+
+</td>
+</tr>
+</table>
+<a name="MethodsDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Methods' Details</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getScriptLogicalNames" class="membertitle">getScriptLogicalNames</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">sequence< string ><br>
+<b>getScriptLogicalNames</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd> Provides a means of obtaining a list of all of the available logical
+ names in the ScriptStorage
+
+</dd>
+<dt><b>Returns</b></dt>
+<dd>
+ A sequence of strings the logical names stored.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getImplementations" class="membertitle">getImplementations</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">sequence< <a href="XScriptInfo.html">XScriptInfo</a> ><br>
+<b>getImplementations</b>(</td>
+<td valign="top"> <br>
+[in] string <br><p class="raise">raises( </p>
+</td>
+<td valign="top"> <br>
+queryURI ) <br>
+::com::sun::star::lang::IllegalArgumentException );</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd> Provides a list of scripts implementing a given logical name
+
+</dd>
+<dt><b>Parameter queryURI</b></dt>
+<dd>
+ a<code> string</code> script URI. Only the logical name is used in the query.
+
+</dd>
+<dt><b>Returns</b></dt>
+<dd>
+ A sequence of
+ <a href="XScriptInfo.html">XScriptInfo</a>
+ for implementations which match queryURI
+
+</dd>
+<dt><b>Throws</b></dt>
+<dd> ::com::sun::star::lang::IllegalArgumentException
+ never
+
+</dd>
+<dt><b>See also</b></dt>
+<dd>::drafts::com::sun::star::script::framework::runtime::ScriptNameResolver<br>
+
+ for more details of Script URIs.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr>
+<td class="imdetail"><a name="getAllImplementations" class="membertitle">getAllImplementations</a>
+<table border="0" width="96%" cellpadding="5" cellspacing="0" bgcolor="#ffffff" align="center">
+<tr>
+<td><table border="0">
+<tr>
+<td valign="top">sequence< <a href="XScriptInfo.html">XScriptInfo</a> ><br>
+<b>getAllImplementations</b>();</td>
+<td valign="top"> <br>
+</td>
+<td valign="top"> <br>
+</td>
+</tr>
+</table>
+<hr>
+<dl>
+<dt><b>Description</b></dt>
+<dd> Provides a list of all scripts in a storage area
+
+</dd>
+<dt><b>Returns</b></dt>
+<dd>
+ A sequence of
+ <a href="XScriptInfo.html">XScriptInfo</a>
+ for script implementations.
+
+</dd>
+<dt><b>See also</b></dt>
+<dd>::drafts::com::sun::star::script::framework::runtime::ScriptNameResolver<br>
+
+ for more details of Script URIs.
+</dd>
+</dl>
+</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageExport-xref.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageExport-xref.html
new file mode 100644
index 0000000..9d3e15d
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageExport-xref.html
@@ -0,0 +1,82 @@
+<html>
+<head>
+<title>Uses of Interface XScriptStorageExport-xref</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
+td.navimain, td.navisub { padding-left:7pt; padding-right:7pt; }
+p.raise { font-size:11pt; margin-top:0pt; text-align:right; padding-right:5pt; }
+a.navimain, a.navisub { color:#000000; }
+.dt { font-weight:bold; }
+.namechain { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:6pt; }
+.tpl { font-size:13pt; margin-top:3pt; margin-bottom:6pt; }
+</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body bgcolor="#ffffff">
+<a name="_top_"> </a>
+<table border="0" cellpadding="3" class="lightbg">
+<tr>
+<td class="navimain"><a href="../../../../../../../com/sun/star/module-ix.html" class="navimain">Overview</a></td>
+<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
+<td class="navimainself">Use</td>
+<td class="navimainnone">Devguide</td>
+<td class="navimain"><a href="../../../../../../../index-files/index-1.html" class="navimain">Index</a></td>
+</tr>
+</table>
+<hr>
+<table border="0" width="100%" cellpadding="5" cellspacing="3" style="margin-bottom:6pt;">
+<tr>
+<td class="title">uses of interface XScriptStorageExport</td>
+</tr>
+<tr>
+<td><p><a href="XScriptStorageExport.html"><b>back to interface XScriptStorageExport</b></a><br>
+<br>
+
+Derived Interfaces<br>
+
+Synonym Typedefs<br>
+
+<a href="#SupportingServices">Services which Support this Interface<br>
+
+</a>Uses as Return Type<br>
+
+Uses as Parameter<br>
+
+Uses as Data Type<br>
+
+References in Developers Guide<br>
+
+</p>
+</td>
+</tr>
+</table>
+<hr>
+<a name="SupportingServices"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
+<tr>
+<td class="subtitle">Services which Support this Interface</td>
+</tr>
+<tr>
+<td><a href="ScriptStorage.html">ScriptStorage</a><br>
+</td>
+</tr>
+</table>
+<hr>
+<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2003 Sun Microsystems, Inc.</p>
+</body>
+
+</html>
diff --git a/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageExport.html b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageExport.html
new file mode 100644
index 0000000..99ed6e8
--- /dev/null
+++ b/content/framework/scripting/EDR-IDLDocs/drafts/com/sun/star/script/framework/storage/XScriptStorageExport.html
@@ -0,0 +1,126 @@
+<html>
+<head>
+<title>Interface XScriptStorageExport</title>
+<style>h3 { font-size:13pt; font-weight:bold; margin-top:3pt; margin-bottom:1pt; }
+p, dt, dd, pre { font-size:11pt; margin-top:3pt; margin-bottom:1pt; }
+table.lightbg { background-color:#eeeeff; }
+table.subtitle { margin-top:6pt; margin-bottom:6pt; }
+td { font-size:11pt; }
+td.title { font-family: Arial; font-size:19pt; font-weight:bold; text-align:center; background-color:#ccccff; line-height:30pt; }
+td.subtitle { font-family: Arial; font-size:13pt; background-color:#ccccff; line-height:20pt; }
+td.imdetail { width:100%; background-color:#eeeeff; }
+a.membertitle { font-size:12pt; font-weight:bold; line-height:18pt; }
+td.imsum_left { width:30%; }
+td.imsum_right { width:70%; }
+td.navimain, a.navimain { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; }
+td.navimainself { text-align:center; font-family: Arial; font-size:12pt; font-weight:bold; color:#ffffff; background-color:#2222ad; }
+td.navimainnone { text-align:center; font-family: Arial; font-size:12pt; }
+td.attrtitle { font-weight:bold; background-color:#eeeeff; }
+td.navisub, a.navisub, td.attrtitle, td.attrvalue { text-align:center; font-family: Arial; font-size:9pt; font-variant:small-caps; }
... 24462 lines suppressed ...