Changes between Initial Version and Version 1 of Ticket #393


Ignore:
Timestamp:
Jan 10, 2012, 8:41:16 AM (12 years ago)
Author:
adube
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #393

    • Property Keywords bis-1.2.0 added
  • Ticket #393 – Description

    initial v1  
    1 c'est ce qu'on fait déjà dans le PGSQLMapContextConfig
    2 le workspace s'est comme coupé en deux : mapcontext et application
    3 mapcontext : liste des resources
    4 application : liste des widgets
    5 et on lie les 2
     1'''Currently'''
    62
    7 comme ça, tu contrôles ce dont tu as besoins sans avoir à toujours redéfinir tes widgets dans chaque workspace
    8 donc oui, c'est une bonne idée de pouvoir les définir dans le workspace
    9 genre par défaut, si pas défini, tous les ajouter
    10 sinon, c'est 1 par 1
    11 mais seulement les widgets non associés aux resources
    12 comme le mappanel, layertree, geoexttoolbar, etc.
    13 (vu que ceux à lier sont déjà à définir dans le tag widgets de la resource du workspace)
     3When using the XMLWorkspaceConfig, widgets that do not need to be linked to resources are always added to the UI.  This is not always wanted.
     4
     5'''Historical facts'''
     6
     7We used to link all widgets to resources, regardless if that was useful or not, thus was a mean to control what we wanted or not.
     8
     9This was really annoying because you needed to be sure that the resource linking them were always added (ACL read rights) otherwise the widgets were excluded.  This was the case for widgets such as the toolbar, zoomslider, measuretools, etc.
     10
     11An other way to include them was to have a dummy resource for that, but that was really annoying too.
     12
     13This behavior disappeared when widgets received their "getMandatoryResourceOptionList" method. When it returns NULL, the widget doesn't need to be linked to resources, thus you no longer need to do so in the config. The only drawback is that from that moment on, they were always added to the UI.
     14
     15'''Proposed fix'''
     16
     17The XMLConfig driver doesn't need to be fixed.
     18
     19For the XMLWorkspaceConfig driver, we could have a 'widgets' tag added to the workspace.  When set, it defines the list of widgets to include. Only the widgets that don't need to be linked to resources would be added that way since those that required to do so are already listed in the resources.
     20
     21When not set, add all widgets (as currently being done). This would stay the default behavior.