Difference between revisions of "Framework"

From Apache OpenOffice Wiki
Jump to: navigation, search
(ToDO)
Line 26: Line 26:
  
 
== ToDo ==
 
== ToDo ==
 +
 +
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.
 +
 
* [[Performance|OpenOffice.org startup. Optimizing the startup process, find bottlenecks and refactor libraries so we don't load unnecessary code.]]
 
* [[Performance|OpenOffice.org startup. Optimizing the startup process, find bottlenecks and refactor libraries so we don't load unnecessary code.]]
 
* Toolbar and popup menu controllers which are more powerful and easier to use than the current ones.
 
* Toolbar and popup menu controllers which are more powerful and easier to use than the current ones.
 
* Cleanup the svtools configuration items (make them write-through instead of write-back with their own cache) to support immediate updates on configuration changes.
 
* Cleanup the svtools configuration items (make them write-through instead of write-back with their own cache) to support immediate updates on configuration changes.
 
* Update the 'Tools - Options' dialogs to support the read-only OpenOffice.org configuration item state
 
* Update the 'Tools - Options' dialogs to support the read-only OpenOffice.org configuration item state
 
  
 
<DPL>
 
<DPL>

Revision as of 16:26, 21 December 2006

Framework Lead: Carsten Driesner Framework Co-Lead: Mathias Bauer

This is the Framework Project Wiki. It is planned to move most content from the http://framework.openoffice.org pages into the Wiki. Probably most interesting for many people is, what we are currently doing in the Framework project. You can find that in the work in progress area. One of the bigger things is to better support extension developers.

The Framework Wiki follows this organization.

Functional Overview

Work in progress

  • Extending the UNO AWT toolkit to better support extension developers.
    • Language support for UNO AWT dialogs
    • Easy to use message boxes
  • An UNO API for the application document titles
  • Docking windows in LayoutManager (preparation for usage in extensions)
  • Vista Readiness


ToDo

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.


Articles & Tutorials

Framework Terms

Personal tools