To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52724
                  Issue #:|52724
                  Summary:|migrate form control implementations to new drawing
                          |layer mechanisms
                Component:|Database access
                  Version:|680m121
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|none
              Assigned to:|fs
              Reported by:|fs





------- Additional comments from [EMAIL PROTECTED] Mon Aug  1 04:01:40 -0700 
2005 -------
Currently, certain form layer implementations related to UNO controls, and how
they are organized and maintained, use old, complex, hard-to-understand,
error-prone, hard-to-maintain mechanisms which kind of bypass the drawing layer
in certain situations.

We should migrate those implementations to the new mechanisms provided by the
drawing layer, namely the View/ObjectContact model.

Advantages of this change would include:
- decreased complexity, thus easier maintainability
- form layer 'tricks' in PaintViews currently break the derive mechanism and
  thus prevent clean designs
- form objects could be painted on virtual devices by default, enabling them to 
be
  be printed as they appear on screen
- painting on virtual devices would enable removing additional drawing layer 
code
  which does exceptional handling for form objects
- removing those exceptions is a necessary step to allow all applications to use
  a pre-rendered drawing layer output (no blinking)
- currently existing repaint failures in the form layer which are hard to fix 
within
  the old architecture could be addressed
- using the new architecture would create a base for placing form controls in
  Writer's headers and footers, which is a feature required for Microsoft
  Interoperability
- Changing the implementations is a necessary step for other projects, such as
  moving (part of) the form layer runtime into a separate library, and accessing
  it as UNO service only.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to