mir/libreoffice
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
dca5cf3fdaaed8be10e8ca32fa8d7b4e0647e17b
libreoffice/extensions/source/propctrlr/formcontroller.cxx

303 lines
12 KiB
C++
Raw Normal View History

initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
/*************************************************************************
*
INTEGRATION: CWS changefileheader (1.90.276); FILE MERGED 2008/04/01 15:15:16 thb 1.90.276.3: #i85898# Stripping all external header guards 2008/04/01 12:29:49 thb 1.90.276.2: #i85898# Stripping all external header guards 2008/03/31 12:31:42 rt 1.90.276.1: #i87441# Change license header to LPGL v3.
2008-04-11 09:53:21 +00:00
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
*
INTEGRATION: CWS changefileheader (1.90.276); FILE MERGED 2008/04/01 15:15:16 thb 1.90.276.3: #i85898# Stripping all external header guards 2008/04/01 12:29:49 thb 1.90.276.2: #i85898# Stripping all external header guards 2008/03/31 12:31:42 rt 1.90.276.1: #i87441# Change license header to LPGL v3.
2008-04-11 09:53:21 +00:00
* Copyright 2008 by Sun Microsystems, Inc.
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
*
INTEGRATION: CWS changefileheader (1.90.276); FILE MERGED 2008/04/01 15:15:16 thb 1.90.276.3: #i85898# Stripping all external header guards 2008/04/01 12:29:49 thb 1.90.276.2: #i85898# Stripping all external header guards 2008/03/31 12:31:42 rt 1.90.276.1: #i87441# Change license header to LPGL v3.
2008-04-11 09:53:21 +00:00
* OpenOffice.org - a multi-platform office productivity suite
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
*
INTEGRATION: CWS changefileheader (1.90.276); FILE MERGED 2008/04/01 15:15:16 thb 1.90.276.3: #i85898# Stripping all external header guards 2008/04/01 12:29:49 thb 1.90.276.2: #i85898# Stripping all external header guards 2008/03/31 12:31:42 rt 1.90.276.1: #i87441# Change license header to LPGL v3.
2008-04-11 09:53:21 +00:00
* $RCSfile: formcontroller.cxx,v $
* $Revision: 1.91 $
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
*
INTEGRATION: CWS changefileheader (1.90.276); FILE MERGED 2008/04/01 15:15:16 thb 1.90.276.3: #i85898# Stripping all external header guards 2008/04/01 12:29:49 thb 1.90.276.2: #i85898# Stripping all external header guards 2008/03/31 12:31:42 rt 1.90.276.1: #i87441# Change license header to LPGL v3.
2008-04-11 09:53:21 +00:00
* This file is part of OpenOffice.org.
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
*
INTEGRATION: CWS changefileheader (1.90.276); FILE MERGED 2008/04/01 15:15:16 thb 1.90.276.3: #i85898# Stripping all external header guards 2008/04/01 12:29:49 thb 1.90.276.2: #i85898# Stripping all external header guards 2008/03/31 12:31:42 rt 1.90.276.1: #i87441# Change license header to LPGL v3.
2008-04-11 09:53:21 +00:00
* OpenOffice.org is free software: you can redistribute it and/or modify
* it under the terms of the GNU Lesser General Public License version 3
* only, as published by the Free Software Foundation.
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
*
INTEGRATION: CWS changefileheader (1.90.276); FILE MERGED 2008/04/01 15:15:16 thb 1.90.276.3: #i85898# Stripping all external header guards 2008/04/01 12:29:49 thb 1.90.276.2: #i85898# Stripping all external header guards 2008/03/31 12:31:42 rt 1.90.276.1: #i87441# Change license header to LPGL v3.
2008-04-11 09:53:21 +00:00
* OpenOffice.org is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU Lesser General Public License version 3 for more details
* (a copy is included in the LICENSE file that accompanied this code).
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
*
INTEGRATION: CWS changefileheader (1.90.276); FILE MERGED 2008/04/01 15:15:16 thb 1.90.276.3: #i85898# Stripping all external header guards 2008/04/01 12:29:49 thb 1.90.276.2: #i85898# Stripping all external header guards 2008/03/31 12:31:42 rt 1.90.276.1: #i87441# Change license header to LPGL v3.
2008-04-11 09:53:21 +00:00
* You should have received a copy of the GNU Lesser General Public License
* version 3 along with OpenOffice.org. If not, see
* <http://www.openoffice.org/license.html>
* for a copy of the LGPLv3 License.
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
*
************************************************************************/
INTEGRATION: CWS pchfix02 (1.89.94); FILE MERGED 2006/09/01 17:26:41 kaib 1.89.94.1: #i68856# Added header markers and pch files
2006-09-16 12:17:41 +00:00
// MARKER(update_precomp.py): autogen include statement, do not remove
#include "precompiled_extensions.hxx"
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
#include "formcontroller.hxx"
#include "pcrcommon.hxx"
#include "formstrings.hxx"
#include "defaultforminspection.hxx"
#ifndef _EXTENSIONS_FORMCTRLR_FORMHELPID_HRC_
#include "formhelpid.hrc"
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
#endif
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
/** === begin UNO includes === **/
#include <com/sun/star/beans/PropertyAttribute.hpp>
#include <com/sun/star/form/XGridColumnFactory.hpp>
#include <com/sun/star/form/XForm.hpp>
#include <com/sun/star/container/XChild.hpp>
/** === end UNO includes === **/
#include <cppuhelper/typeprovider.hxx>
#include <toolkit/helper/vclunohelper.hxx>
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//------------------------------------------------------------------------
extern "C" void SAL_CALL createRegistryInfo_FormController()
{
::pcr::OAutoRegistration< ::pcr::FormController > aFormControllerRegistration;
::pcr::OAutoRegistration< ::pcr::DialogController > aDialogControllerRegistration;
}
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//........................................................................
namespace pcr
{
//........................................................................
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
/** === begin UNO using === **/
using ::com::sun::star::uno::Reference;
using ::com::sun::star::uno::TypeClass_INTERFACE;
using ::com::sun::star::uno::TypeClass_STRING;
using ::com::sun::star::uno::XComponentContext;
using ::com::sun::star::inspection::XObjectInspectorModel;
using ::com::sun::star::uno::RuntimeException;
using ::com::sun::star::uno::UNO_QUERY_THROW;
using ::com::sun::star::uno::Sequence;
using ::com::sun::star::uno::XInterface;
using ::com::sun::star::beans::XPropertySetInfo;
using ::com::sun::star::beans::XPropertySet;
using ::com::sun::star::beans::Property;
using ::com::sun::star::uno::Any;
using ::com::sun::star::lang::IllegalArgumentException;
using ::com::sun::star::uno::Exception;
using ::com::sun::star::uno::Type;
using ::com::sun::star::util::VetoException;
using ::com::sun::star::beans::PropertyVetoException;
using ::com::sun::star::uno::UNO_QUERY;
using ::com::sun::star::form::XGridColumnFactory;
using ::com::sun::star::form::XForm;
using ::com::sun::star::container::XChild;
using ::com::sun::star::frame::XFrame;
using ::com::sun::star::awt::XWindow;
/** === end UNO using === **/
INTEGRATION: CWS frmcontrols04 (1.59.8); FILE MERGED 2004/06/16 04:06:53 fs 1.59.8.5: RESYNC: (1.59-1.66); FILE MERGED 2004/05/03 16:00:28 fs 1.59.8.4: #28672# ImagePosition replacing ImageAlign 2004/04/29 10:55:57 fs 1.59.8.3: #i24694# support for BorderColor 2004/04/29 07:37:34 fs 1.59.8.2: #i24681# WordBreak property for push buttons, option buttons, and check boxes 2004/04/29 06:28:49 fs 1.59.8.1: #i24683# #i24684# #i24685# #i24686# new properties: flat/3D for radios/check boxes, HideSelection for edits, Toggle/TakeFocusOnClick for buttons
2004-07-05 15:23:01 +00:00
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
namespace PropertyAttribute = ::com::sun::star::beans::PropertyAttribute;
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//====================================================================
//= FormController
//====================================================================
//--------------------------------------------------------------------
FormController::FormController( const Reference< XComponentContext >& _rxContext, ServiceDescriptor _aServiceDescriptor,
bool _bUseFormFormComponentHandlers )
:OPropertyBrowserController( _rxContext )
,FormController_PropertyBase1( m_aBHelper )
,m_aServiceDescriptor( _aServiceDescriptor )
{
osl_incrementInterlockedCount( &m_refCount );
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Reference< XObjectInspectorModel > xModel(
*(new DefaultFormComponentInspectorModel( _rxContext, _bUseFormFormComponentHandlers )),
UNO_QUERY_THROW
);
setInspectorModel( xModel );
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
osl_decrementInterlockedCount( &m_refCount );
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
FormController::~FormController()
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//------------------------------------------------------------------------
IMPLEMENT_FORWARD_XINTERFACE2( FormController, OPropertyBrowserController, FormController_PropertyBase1 )
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Sequence< Type > SAL_CALL FormController::getTypes( ) throw(RuntimeException)
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
::cppu::OTypeCollection aTypes(
::getCppuType( static_cast< Reference< XPropertySet >* >(NULL) ),
::getCppuType( static_cast< Reference< XMultiPropertySet >* >(NULL) ),
::getCppuType( static_cast< Reference< XFastPropertySet >* >(NULL) ),
OPropertyBrowserController::getTypes());
return aTypes.getTypes();
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
IMPLEMENT_GET_IMPLEMENTATION_ID( FormController )
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
::rtl::OUString SAL_CALL FormController::getImplementationName( ) throw(RuntimeException)
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
return m_aServiceDescriptor.GetImplementationName();
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Sequence< ::rtl::OUString > SAL_CALL FormController::getSupportedServiceNames( ) throw(RuntimeException)
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Sequence< ::rtl::OUString > aSupported( m_aServiceDescriptor.GetSupportedServiceNames() );
aSupported.realloc( aSupported.getLength() + 1 );
aSupported[ aSupported.getLength() - 1 ] = ::rtl::OUString( RTL_CONSTASCII_USTRINGPARAM( "com.sun.star.inspection.ObjectInspector" ) );
return aSupported;
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
::rtl::OUString FormController::getImplementationName_static( ) throw(RuntimeException)
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
return ::rtl::OUString::createFromAscii("org.openoffice.comp.extensions.FormController");
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Sequence< ::rtl::OUString > FormController::getSupportedServiceNames_static( ) throw(RuntimeException)
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Sequence< ::rtl::OUString > aSupported(1);
aSupported[0] = ::rtl::OUString::createFromAscii( "com.sun.star.form.PropertyBrowserController" );
return aSupported;
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Reference< XInterface > SAL_CALL FormController::Create(const Reference< XComponentContext >& _rxContext )
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
ServiceDescriptor aService;
aService.GetImplementationName = &FormController::getImplementationName_static;
aService.GetSupportedServiceNames = &FormController::getSupportedServiceNames_static;
return *(new FormController( _rxContext, aService, true ) );
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Reference< XPropertySetInfo > SAL_CALL FormController::getPropertySetInfo( ) throw(RuntimeException)
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
return ::cppu::OPropertySetHelper::createPropertySetInfo(getInfoHelper());
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
::cppu::IPropertyArrayHelper& SAL_CALL FormController::getInfoHelper()
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
return *getArrayHelper();
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
::cppu::IPropertyArrayHelper* FormController::createArrayHelper( ) const
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Sequence< Property > aProps( 2 );
aProps[0] = Property(
PROPERTY_CURRENTPAGE,
OWN_PROPERTY_ID_CURRENTPAGE,
::getCppuType( static_cast< ::rtl::OUString* >( NULL ) ),
PropertyAttribute::TRANSIENT
);
aProps[1] = Property(
PROPERTY_INTROSPECTEDOBJECT,
OWN_PROPERTY_ID_INTROSPECTEDOBJECT,
XPropertySet::static_type(),
PropertyAttribute::TRANSIENT | PropertyAttribute::CONSTRAINED
);
return new ::cppu::OPropertyArrayHelper( aProps );
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
sal_Bool SAL_CALL FormController::convertFastPropertyValue( Any & rConvertedValue, Any & rOldValue, sal_Int32 nHandle, const Any& rValue ) throw (IllegalArgumentException)
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
switch ( nHandle )
{
case OWN_PROPERTY_ID_INTROSPECTEDOBJECT:
if ( rValue.getValueTypeClass() != TypeClass_INTERFACE )
throw IllegalArgumentException();
break;
case OWN_PROPERTY_ID_CURRENTPAGE:
if ( rValue.getValueTypeClass() != TypeClass_STRING )
throw IllegalArgumentException();
break;
}
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
getFastPropertyValue( rOldValue, nHandle );
rConvertedValue = rValue;
return sal_True;
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
//------------------------------------------------------------------------
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
void SAL_CALL FormController::setFastPropertyValue_NoBroadcast(sal_Int32 _nHandle, const Any& _rValue) throw (Exception)
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
switch ( _nHandle )
{
case OWN_PROPERTY_ID_INTROSPECTEDOBJECT:
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Reference< XObjectInspectorModel > xModel( getInspectorModel() );
if ( xModel.is() )
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
try
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
m_xCurrentInspectee.set( _rValue, UNO_QUERY );
Sequence< Reference< XInterface > > aObjects;
if ( m_xCurrentInspectee.is() )
{
aObjects.realloc( 1 );
aObjects[0] = m_xCurrentInspectee;
}
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Reference< XObjectInspector > xInspector( *this, UNO_QUERY_THROW );
xInspector->inspect( aObjects );
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
catch( const VetoException& e )
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
throw PropertyVetoException( e.Message, e.Context );
INTEGRATION: CWS formdesign01 (1.55.4); FILE MERGED 2004/03/10 09:45:19 fs 1.55.4.18: #i26280# corrected control type for TabIndex 2004/03/03 09:20:34 fs 1.55.4.17: corrected some small issues discovered during pre-QA 2004/01/09 13:42:04 fs 1.55.4.16: #i22878# measurement unit (ms) for Delay property 2004/01/09 08:24:42 fs 1.55.4.15: corrected spelling issue, as suggested by UFI 2003/12/19 14:25:00 fs 1.55.4.14: RESYNC: (1.55-1.57); FILE MERGED 2003/12/19 13:41:23 fs 1.55.4.13: #22878# properly active the query design window 2003/12/18 13:06:32 fs 1.55.4.12: #i22878# easier input of selection / default selection with dedicated dialog 2003/12/17 10:38:20 fs 1.55.4.11: #i22878# filter and sort order dialog from within the property browser 2003/12/15 13:42:16 fs 1.55.4.10: #i23418# 2003/12/15 07:55:21 fs 1.55.4.9: #i23418# linking master/detail form via a dedicated dialog 2003/12/05 14:26:19 fs 1.55.4.8: #i22878# availability of ScaleImage does depend on *two* other props 2003/12/05 09:03:35 fs 1.55.4.7: #i23190# disable more input fields while the query design is open 2003/12/04 14:11:38 fs 1.55.4.6: #i23190# graphically design SQL commands, using the usual query design UI 2003/12/03 10:06:41 fs 1.55.4.5: #i22878# measurement units for Width and RowHeight 2003/11/27 14:47:27 fs 1.55.4.4: #i22878# file URL display and date input 2003/11/27 10:21:05 fs 1.55.4.3: #i22878# added TabOrder dialog handling 2003/11/26 15:57:36 fs 1.55.4.2: #i22878# implementations for disabling property controls depending on other property's values 2003/11/26 11:39:59 fs 1.55.4.1: #i22878# implementations for disabling property controls depending on other property's values
2004-03-19 11:01:11 +00:00
}
}
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
break;
case OWN_PROPERTY_ID_CURRENTPAGE:
restoreViewData( _rValue );
break;
INTEGRATION: CWS formcelllinkage (1.54.94); FILE MERGED 2003/10/01 09:17:52 fs 1.54.94.1: #i18994# merging the changes from the CWS fs002
2003-10-21 08:04:59 +00:00
}
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//------------------------------------------------------------------------
void SAL_CALL FormController::getFastPropertyValue( ::com::sun::star::uno::Any& rValue, sal_Int32 nHandle ) const
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
switch ( nHandle )
{
case OWN_PROPERTY_ID_INTROSPECTEDOBJECT:
rValue <<= m_xCurrentInspectee;
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
break;
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
case OWN_PROPERTY_ID_CURRENTPAGE:
rValue = const_cast< FormController* >( this )->getViewData();
break;
}
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//====================================================================
//= DialogController
//====================================================================
//------------------------------------------------------------------------
::rtl::OUString DialogController::getImplementationName_static( ) throw(RuntimeException)
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
return ::rtl::OUString::createFromAscii("org.openoffice.comp.extensions.DialogController");
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//------------------------------------------------------------------------
Sequence< ::rtl::OUString > DialogController::getSupportedServiceNames_static( ) throw(RuntimeException)
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
Sequence< ::rtl::OUString > aSupported(1);
aSupported[0] = ::rtl::OUString::createFromAscii( "com.sun.star.awt.PropertyBrowserController" );
return aSupported;
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//------------------------------------------------------------------------
Reference< XInterface > SAL_CALL DialogController::Create(const Reference< XComponentContext >& _rxContext)
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
{
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
ServiceDescriptor aService;
aService.GetImplementationName = &DialogController::getImplementationName_static;
aService.GetSupportedServiceNames = &DialogController::getSupportedServiceNames_static;
return *(new FormController( _rxContext, aService, false ) );
INTEGRATION: CWS docking1 (1.66.4); FILE MERGED 2004/07/01 09:51:04 dfoster 1.66.4.1: #i30032#
2004-07-06 15:47:12 +00:00
}
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//........................................................................
initial checkin - outsourced the form property browser
2001-01-12 10:35:45 +00:00
} // namespace pcr
INTEGRATION: CWS pbrwuno (1.85.88); FILE MERGED 2006/02/10 08:30:34 fs 1.85.88.14: RESYNC: (1.87-1.88); FILE MERGED 2005/11/01 11:09:46 fs 1.85.88.13: RESYNC: (1.85-1.87); FILE MERGED 2005/10/26 14:49:35 fs 1.85.88.12: #i53095# 2005/10/25 07:13:11 fs 1.85.88.11: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:49 fs 1.85.88.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:22 fs 1.85.88.9: #i53095# some cleanup of remaining TODOs 2005/10/14 10:48:00 fs 1.85.88.8: #i53095# replace InspectorModel::InspectedObjects with Inspector::inspect 2005/10/13 13:00:29 fs 1.85.88.7: #i53095# (slightly) specialized version of the ObjectInspector which does the legacy implementation of css.form.PropertyBrowserController 2005/09/05 07:41:50 fs 1.85.88.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:29 fs 1.85.88.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:02 fs 1.85.88.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:11 fs 1.85.88.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:45 fs 1.85.88.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.85.88.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:28 +00:00
//........................................................................
Reference in New Issue Copy Permalink