1 Commits

Author	SHA1	Message	Date
Vladimir Glazounov	c926f0b43c	INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED ... 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #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:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #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.5: #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) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work	2006-03-14 10:23:06 +00:00