Chrome Again

From OpenOffice.org Wiki

Jump to: navigation, search

Understand any current weaknesses, gather requirements and discuss suggestions where we want to head with OOos GUI technology ...

See also http://blogs.sun.com/GullFOSS/entry/chrome_again

Current Weaknesses

Title Source
inflexible - requires VCL (or VCL's behavior in a vast number of classes) Thorsten
increasingly alienating on modern systems (MacOS X being the prime example) Thorsten
needs (c++) developers to modify existing dialogs Thorsten

Requirements

The following requirements are not mandatory (yet :-), but just reflect what the different parties think what needs to be achieved and how important it is ...

Title Source
needs to be flexible - it should allow us to adapt to future developments in UI design much easier than today Thorsten
needs to blend in well with all supported platforms (and take into consideration future ports) Thorsten
needs to provide at least the same amount of accessibility support as OOo has today Thorsten
Vector Based UI CJ
Draw objects Anti-Aliased CJ
Draw objects, w. 50% opacity during drag & drop CJ
Allow to modify GUI-Elements based on CSS CJ
Smooth animations of GUI-Elements (e.g. for scrolling) CJ
Transition and blend-over effects for GUI Objects (OpenGL, DirectX, Quartz, Compiz, Java/FX?) CJ
Layout Manager CJ
Declarative Description MHU/KR
Cross Platform KR
Simple Code Changes Linked by KR
QA Test tool Linked by KR
Re-use of existing code Linked by KR
Simple new APIs Linked by KR
i18n Linked by KR
Automatic Layout Linked by KR
Reduced Inheritance Linked by KR
New resource file format Linked by KR
Easy to use Dialog Editor Linked by KR
Support for native controls PL
Support for displaying data using reflexion (Example: Windows.Forms ComponentModel PropertyGrid) b_michaelsen
Toolbars
Allow to add flexible space between items CJ
Allow to display context toolbars CJ

Material

Personal tools
Create a book