EditFeatureWidgets - remove scrollbars, have buttons only

[adube]

Currently

If more than one edit widget of a specific type is detected, instead of adding a button to the toolbar, it add a dropdown list with resources in it.

This method is pretty unintuitive and should be changed.

Enhancements

• Remove the drop-down lists. Add the button directly to the toolbar
• Make sure that the buttons are grouped by resource rather than type :
  • not : C-R1, C-R2, U-R1, U-R2, D-R1, D-R2
  • have : C-R1, U-R1, D-R1, C-R2, U-R2, D-R2
• Have the possibility to customize the icons per resource per widget
• Have the possibility to customize the tooltip per resource per widget
• Since we don't need to have 1 edit widget per resource, having to define them in the toolbar by widget name is obsolete. We still need a way to say 'have the edit widgets here'. For that, we could support a new <widget> node value for the toolbar :

  __editwidget__
  

• editfeature widgets from different resources should have a separator between them (default behavior, have an option for that)

[adube]

r971, featuring

• editfeature widgets updates :
  • are no longer added to a dropdown list
  • are added to a global variable instead, grouped by resources : goEditFeatureActions
  • currently all have the same button and auto-generated tooltips (we'll change this)
  • documentation updated
• GeoExtToolbar widget updates :
  • new "separateEditFeatureWidgets" option
  • new widget value to include all editfeature widgets :

    __editfeature__
    

  • now reads the above value and the goEditFeatureActions variable to put the editfeature widgets in its items
  • documentation updated
• all sample config (XML and PGSQLMapContextConfig) updated accordingly

[adube]

remaining to do :

• unique icons per editwidget + resource
• unique tooltip per editwidget + resource

For both these new features, we'll use the "MapContext" model of thinking, i.e. we'll use resource options to configure the widgets accordingly, but instead of linking them in the php core, we'll do it in the xslt.

[adube]

r974, featuring :

• all 3 edit feature widgets can now have unique 'iconCls' defined using an according resource option
• new resource options :
  • iconClsCreate
  • iconClsDelete
  • iconClsUpdate
• documentation added
• sample modified to show this feature (editfeature/xsmlmapcustomform)

[adube]

r978, featuring :

• all 3 edit feature widgets can now have unique 'tooltip' values defined using the according resource option
• new resource options, supported in all configs and also support i18n values :
  • tooltipTextCreate
  • tooltipTextUpdate
  • tooltipTextDelete
• documentation added
• samples mofified to show this feature :
  • editfeature/xsmlmapcustomform

All tasks in this ticket are now completed.

• editfeature/pgsqllegacycustomform