• Vladimir Glazounov's avatar
    INTEGRATION: CWS pbrwuno (1.2.158); FILE MERGED · 65e5029f
    Vladimir Glazounov yazdı
    2005/11/02 11:43:37 fs 1.2.158.11: #i10000# exception specifications
    2005/10/25 12:13:05 fs 1.2.158.10: #i53095# cache the enum converter
    2005/10/24 08:41:39 fs 1.2.158.9: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
    2005/10/13 13:00:58 fs 1.2.158.8: #i53095# introduce an XObjectInspector/Model
    2005/10/11 13:28:54 fs 1.2.158.7: #i53095# phase 3:
    introduced XPropertyHandler and XObjectInspectorUI
    same open issues as in previous phase
    (plus probably some more, since not everything is tested, yet :-\)
    2005/10/05 06:51:30 fs 1.2.158.6: RESYNC: (1.2-1.3); FILE MERGED
    2005/08/18 12:44:26 fs 1.2.158.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:38:57 fs 1.2.158.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
    2005/08/12 16:30:08 fs 1.2.158.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:43 fs 1.2.158.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:56 fs 1.2.158.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
    65e5029f
cellbindinghandler.hxx 6.37 KB