INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2005/11/02 11:43:40 fs 1.1.2.15: #i10000# exception specifications 2005/10/31 11:13:06 fs 1.1.2.14: teach the ComposedPropertyUIUpdate to handle missing properties 2005/10/25 07:13:09 fs 1.1.2.13: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:45 fs 1.1.2.12: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:16 fs 1.1.2.11: #i53095# some cleanup of remaining TODOs 2005/10/17 13:18:59 fs 1.1.2.10: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 08:58:16 fs 1.1.2.9: some mutex locking 2005/10/14 12:43:45 fs 1.1.2.8: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 09:37:21 fs 1.1.2.7: #i53095# let the ObjectInspectorModel provide relative property ordering 2005/10/14 08:40:35 fs 1.1.2.6: typo in interface name 2005/10/13 13:01:02 fs 1.1.2.5: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:09 fs 1.1.2.4: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:15 fs 1.1.2.3: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:48 fs 1.1.2.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into   the control for property A, which causes property B to be committed,   which causes the UI for property A to be rebuilt, then this will   crash currently. Reason: rebuildPropertyUI now synchronously replaces   the VCL-Window of the rebuilt control, which is exactly the one   which is still in some MouseButtonDown-handler.   possible solutions:   - see if rebuiltPropertyUI can be obsoleted - handlers should be able     to just obtain the XPropertyControl from the PropertyUI, and     re-initialize the control. Shouldn't they?`   - make one of the steps in the chain (mouse-click, handler-call,     rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.1: #i53095#, phase 2
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2005/11/02 11:43:40 fs 1.1.2.15: #i10000# exception specifications
2005/10/31 11:13:06 fs 1.1.2.14: teach the ComposedPropertyUIUpdate to handle missing properties
2005/10/25 07:13:09 fs 1.1.2.13: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:45 fs 1.1.2.12: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:16 fs 1.1.2.11: #i53095# some cleanup of remaining TODOs
2005/10/17 13:18:59 fs 1.1.2.10: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 08:58:16 fs 1.1.2.9: some mutex locking
2005/10/14 12:43:45 fs 1.1.2.8: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 09:37:21 fs 1.1.2.7: #i53095# let the ObjectInspectorModel provide relative property ordering
2005/10/14 08:40:35 fs 1.1.2.6: typo in interface name
2005/10/13 13:01:02 fs 1.1.2.5: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:09 fs 1.1.2.4: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:15 fs 1.1.2.3: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:48 fs 1.1.2.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
  the control for property A, which causes property B to be committed,
  which causes the UI for property A to be rebuilt, then this will
  crash currently. Reason: rebuildPropertyUI now synchronously replaces
  the VCL-Window of the rebuilt control, which is exactly the one
  which is still in some MouseButtonDown-handler.
  possible solutions:
  - see if rebuiltPropertyUI can be obsoleted - handlers should be able
    to just obtain the XPropertyControl from the PropertyUI, and
    re-initialize the control. Shouldn't they?`
  - make one of the steps in the chain (mouse-click, handler-call,
    rebuildPropertyUI-callback) asynchronous.
2005/08/18 12:44:28 fs 1.1.2.1: #i53095#, phase 2

moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers

open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
  knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
  which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment

other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)

JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core