Files
libreoffice/extensions/source/propctrlr/formcontroller.cxx

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

275 lines
8.8 KiB
C++
Raw Normal View History

/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
re-base on ALv2 code. Includes (at least) relevant parts of: linecap: Reintegrating finished LineCap feature Patch contributed by Regina Henschel http://svn.apache.org/viewvc?view=revision&revision=1232507 Patches contributed by Sven Jacobi impress212: #i81610# fixed animation export http://svn.apache.org/viewvc?view=revision&revision=1167620 impress212: drawinglayer gbuild environment changes http://svn.apache.org/viewvc?view=revision&revision=1167627 http://svn.apache.org/viewvc?view=revision&revision=1167628 impress212: DffPropSet -> minor code improvements, removing table http://svn.apache.org/viewvc?view=revision&revision=1167634 impress212: #158494# fixed excel import (text rotation) http://svn.apache.org/viewvc?view=revision&revision=1167638 Patches contributed by Armin Le Grand Svg: Reintegrated Svg replacement from /branches/alg/svgreplavement http://svn.apache.org/viewvc?view=revision&revision=1220836 #118728# changed indentifying definitions for Svg file detection http://svn.apache.org/viewvc?view=revision&revision=1229961 #118838# LineGeometry creation for complicated cases optimized to create single Polygons http://svn.apache.org/viewvc?view=revision&revision=1236232 #119176# corrected file type detection for SVG for svg files without xml header http://svn.apache.org/viewvc?view=revision&revision=1309445 #118728# Extended Svg file detection http://svn.apache.org/viewvc?view=revision&revision=1230531 #118529# solve break converters and convert commands for OLEs and images http://svn.apache.org/viewvc?view=revision&revision=1186168 svg: added WaE changes from branch svgreplacement to trunc http://svn.apache.org/viewvc?view=revision&revision=1222974 svg: corrected missing member initialization http://svn.apache.org/viewvc?view=revision&revision=1226134 fix for #118525#: Using primitives for chart sub-geometry visualisation http://svn.apache.org/viewvc?view=revision&revision=1226879 #118898# Adapted ImpGraphic::ImplGetBitmap to correctly convert metafiles to bitmapEx ... http://svn.apache.org/viewvc?view=revision&revision=1293316 fix for #118525#: removed no longer used variable maOriginalMapMode, one more exception eliminated http://svn.apache.org/viewvc?view=revision&revision=1227097 #16758# Added buffering to the VDev usages of the VclProcessor2D derivates... http://svn.apache.org/viewvc?view=revision&revision=1229521 #116758# Secured VDev buffer device to Vcl deinit http://svn.apache.org/viewvc?view=revision&revision=1230574 #116758# added remembering allocated VDevs for VDevBuffer to be able to also delete these when vcl goes down; it should never happen, but You never know http://svn.apache.org/viewvc?view=revision&revision=1230927 #118730# Changed SvgClipPathNode to use MaskPrimitive2D for primitive representation instead of TransparencePrimitive2D http://svn.apache.org/viewvc?view=revision&revision=1231198 #118822# secured 3D geometry creation (slices) by subdividing the 2D source polyPolygon early http://svn.apache.org/viewvc?view=revision&revision=1234749 #118829# enhanced Svg gradient quality, obstacles avoided http://svn.apache.org/viewvc?view=revision&revision=1235361 #118834# Unified usage of TextBreakupHelper as single tooling class for i18n text primitive breakup http://svn.apache.org/viewvc?view=revision&revision=1236110 #118853# added square pixel size limit to conversion of TransparencePrimitive2D to Metafile action http://svn.apache.org/viewvc?view=revision&revision=1237656 #118824# coreccted mirroring and boundrect when the graphicmanager is used for bitmap output http://svn.apache.org/viewvc?view=revision&revision=1240097 #115092# Corrected VclProcessor2D::RenderPolygonStrokePrimitive2D for various optimization scenarios http://svn.apache.org/viewvc?view=revision&revision=1241434 #118783# Corrected errors in ID strings, corrected Svg line/fill export, corrected polygon close state http://svn.apache.org/viewvc?view=revision&revision=1232006 #118796# corrected null-pointer usage in SVG text exporter http://svn.apache.org/viewvc?view=revision&revision=1240262 #118729# Use GraphicStreamUrl and GraphicUrl to allow multi image import with linked graphics, too http://svn.apache.org/viewvc?view=revision&revision=1229962 #118898# corrected error in GDIMetaFile::GetBoundRect in handling MetaFloatTransparentAction http://svn.apache.org/viewvc?view=revision&revision=1293349 #118855# Corrected handling of possibly created empty clipRegions after PolyPolygon clipping http://svn.apache.org/viewvc?view=revision&revision=1237725 #115962# Better (but not yet optimal, see comments in task) handling of MetaFloatTransparentAction in PDF export http://svn.apache.org/viewvc?view=revision&revision=1241078 IP clearance: #118466# This patch removes librsvg, libcroco, libgsf, ... http://svn.apache.org/viewvc?view=revision&revision=1200879 118779# Added svg content streaming in/out to ImpGraphic stream operators http://svn.apache.org/viewvc?view=revision&revision=1231908 linecap: correctons for WaE and mac drawing http://svn.apache.org/viewvc?view=revision&revision=1232793 svg: uses current system Dpi for Svg replacement image creation http://svn.apache.org/viewvc?view=revision&revision=1233948 Patches contributed by Mathias Bauer (and others) gnumake4 work variously http://svn.apache.org/viewvc?view=revision&revision=1394326 http://svn.apache.org/viewvc?view=revision&revision=1396797 http://svn.apache.org/viewvc?view=revision&revision=1397315 http://svn.apache.org/viewvc?view=revision&revision=1394326 Remove duplicate header includes. cws mba34issues01: #i117720#: convert assertion into warning http://svn.apache.org/viewvc?view=revision&revision=1172352 118485 - Styles for OLEs are not saved. Submitted by Armin Le Grand. http://svn.apache.org/viewvc?view=revision&revision=1182166 cws mba34issues01: #i117714#: remove assertion http://svn.apache.org/viewvc?view=revision&revision=1172357 Patch contributed by Jurgen Schmidt add some additional checks to ensure proper reading operations http://svn.apache.org/viewvc?view=revision&revision=1209022 mostly prefer our stream / bounds checking work. Patches contributed by Herbert Duerr #i118816# add clarifying comment regarding Font::*Color*() methods http://svn.apache.org/viewvc?view=revision&revision=1233833 extend macro->string handling for empty strings http://svn.apache.org/viewvc?view=revision&revision=1175801 avoid magic constants for SALCOLOR_NONE http://svn.apache.org/viewvc?view=revision&revision=1177543 initialize slant properly in ImplFontMetricData constructor (author=iorsh) http://svn.apache.org/viewvc?view=revision&revision=1177551 #i118675# make check for extension updates more stable http://svn.apache.org/viewvc?view=revision&revision=1214797 #a118617# remove VBasicEventListener.dll binary There are no known users depending on its CLSID http://svn.apache.org/viewvc?view=revision&revision=1203697 Patches contributed by Ariel Constenla-Haile Fix build breaker on Linux/gcc http://svn.apache.org/viewvc?view=revision&revision=1221104 Fix crash when trying to instantiate css.graphic.GraphicRasterizer_RSVG http://svn.apache.org/viewvc?view=revision&revision=1215559 Patches contributed by Oliver-Rainer Wittmann sw34bf06: #i117962# - method <SwFlyFrm::IsPaint(..)> - consider instances of <SwFlyDrawObj> http://svn.apache.org/viewvc?view=revision&revision=1172120 sw34bf06: #i117783# - Writer's implementation of XPagePrintable - apply print settings to new printing routines http://svn.apache.org/viewvc?view=revision&revision=1172115 gnumake4 work variously from Hans-Joachim Lankenau http://svn.apache.org/viewvc?view=revision&revision=1397315 http://svn.apache.org/viewvc?view=revision&revision=1396797 http://svn.apache.org/viewvc?view=revision&revision=1396782 http://svn.apache.org/viewvc?view=revision&revision=1394707 plus some amount of re-splitting of legacy headers. Patch contributed by Pavel Janik WaE: Remove unused variables. http://svn.apache.org/viewvc?view=revision&revision=1230697 Patches contributed by Takashi Ono mingwport35: i#117795: MinGW port fix for vcl2gnumake http://svn.apache.org/viewvc?view=revision&revision=1172091 mingwport35: i#117795: MinGW port fix for vcl2gnumake http://svn.apache.org/viewvc?view=revision&revision=1172091 Patch contributed by Christian Lippka impress212: #i98044# re enable Text menu for outline and title shapes http://svn.apache.org/viewvc?view=revision&revision=1167639 Patch contributed by Andre Fischer 118674: Made category B code optional and disabled by default. http://svn.apache.org/viewvc?view=revision&revision=1215131 118881: Ignore empty paragraphs after bullets. http://svn.apache.org/viewvc?view=revision&revision=1296205 Patches contributed by Philipp Lohmann ooo340fixes: #i117780# use rtl allocator http://svn.apache.org/viewvc?view=revision&revision=1172087 ooo34gsl02: #i117807# fix an off by one error (index actually inside the pfb section header) http://svn.apache.org/viewvc?view=revision&revision=1167576 various cleanups, related compilation fixes, warning cleanups, re-working of obsolete stl template pieces to use boost instead, changed string classes, re-adapt KDE about data, about dialog, fixing warnings, and other fixes & improvements. Disable svg import / render for about/ branding code-paths for now. Restore full icon theme set. Remove OS/2 conditionals and sources. Remove conflicting gtk/full-screen monitors support. Retain existing svg rasterizer files - temporarily disabled. Standardize stringificaiton and fixup dllpostfix issues. Rename SvgGradientHelper::== to equalTo to avoid overloading issues. Use the flat GdiPlus API for LineCaps calls.
2012-10-09 12:22:23 +01:00
/*
* This file is part of the LibreOffice project.
*
* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/.
*
* This file incorporates work covered by the following license notice:
*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed
* with this work for additional information regarding copyright
* ownership. The ASF licenses this file to you under the Apache
* License, Version 2.0 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of
* the License at http://www.apache.org/licenses/LICENSE-2.0 .
*/
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 "pcrservices.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 "formstrings.hxx"
#include "defaultforminspection.hxx"
#include <propctrlr.h>
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
#include <com/sun/star/beans/PropertyAttribute.hpp>
#include <com/sun/star/util/VetoException.hpp>
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 <cppuhelper/typeprovider.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
extern "C" void createRegistryInfo_FormController()
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
{
::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
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::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::Type;
using ::com::sun::star::util::VetoException;
using ::com::sun::star::beans::PropertyVetoException;
using ::com::sun::star::uno::UNO_QUERY;
namespace PropertyAttribute = css::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
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( const Reference< XComponentContext >& _rxContext, ServiceDescriptor _aServiceDescriptor,
bool _bUseFormFormComponentHandlers )
:OPropertyBrowserController( _rxContext )
,FormController_PropertyBase1( m_aBHelper )
,m_aServiceDescriptor( _aServiceDescriptor )
{
osl_atomic_increment( &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( _bUseFormFormComponentHandlers )),
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
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
}
osl_atomic_decrement( &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
Sequence< Type > SAL_CALL FormController::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
::cppu::OTypeCollection aTypes(
cppu::UnoType<XPropertySet>::get(),
cppu::UnoType<XMultiPropertySet>::get(),
cppu::UnoType<XFastPropertySet>::get(),
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
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
OUString SAL_CALL FormController::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
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
}
Sequence< OUString > SAL_CALL FormController::getSupportedServiceNames( )
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
{
Sequence< OUString > aSupported( m_aServiceDescriptor.GetSupportedServiceNames() );
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
aSupported.realloc( aSupported.getLength() + 1 );
aSupported[ aSupported.getLength() - 1 ] = "com.sun.star.inspection.ObjectInspector";
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 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
}
OUString FormController::getImplementationName_static( )
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
{
return "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
}
Sequence< OUString > FormController::getSupportedServiceNames_static( )
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
{
Sequence< OUString > aSupported { "com.sun.star.form.PropertyBrowserController" };
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 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
}
Reference< XInterface > 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
}
Reference< XPropertySetInfo > SAL_CALL FormController::getPropertySetInfo( )
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,
::cppu::UnoType<OUString>::get(),
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
PropertyAttribute::TRANSIENT
);
aProps[1] = Property(
PROPERTY_INTROSPECTEDOBJECT,
OWN_PROPERTY_ID_INTROSPECTEDOBJECT,
cppu::UnoType<XPropertySet>::get(),
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
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
}
sal_Bool SAL_CALL FormController::convertFastPropertyValue( Any & rConvertedValue, Any & rOldValue, sal_Int32 nHandle, const Any& rValue )
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 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
}
void SAL_CALL FormController::setFastPropertyValue_NoBroadcast(sal_Int32 _nHandle, const Any& _rValue)
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;
}
}
void SAL_CALL FormController::getFastPropertyValue( css::uno::Any& rValue, sal_Int32 nHandle ) const
{
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;
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 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
OUString DialogController::getImplementationName_static( )
{
return "org.openoffice.comp.extensions.DialogController";
}
Sequence< OUString > DialogController::getSupportedServiceNames_static( )
{
Sequence< OUString > aSupported { "com.sun.star.awt.PropertyBrowserController" };
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 aSupported;
}
Reference< XInterface > DialogController::Create(const Reference< XComponentContext >& _rxContext)
{
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 ) );
}
} // namespace pcr
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */