search

nakijun / morisoliver

Automatically exported from code.google.com/p/morisoliver
0 stars 0 forks source link

Add the ability to have dropdowns through the OLIVER WFSTFeatureEditing dialog interface that have manually configured lists of values #115

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
This is Enhancement 2 in Task Order 4

Overview:
When adding or editing a feature it can be useful to constrain the user to 
choose from a pick list of possible values.  This keeps the user from entering 
spelling errors and erroneous values.  This enhancement would enable the 
ability to manually list the values for a given attribute.  We would like for 
each editable layer and for each editable field to be able to optionally list 
values.

Configuration Parameters:
1.  The editable layer name
2.  The editable layer column name
3.  A list of label/value pairs for each item to be selected via a select-box 
when editing layer from #2

Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 23 Jan 2012 at 2:14

GoogleCodeExporter commented 9 years ago 
Implemented using fields option - xtype, store, store_val_labels
ex:
fields : [
 name: "ORGCODE", 
 xtype: 'combo',   
 store_val_labels: [ 
     ["org1","Organization 1 despite a field length of 5"],
     ["org2","Organization 2 despite a field length of 5"]
]

or 

fields : [
 name: "ORGCODE", 
 xtype: 'combo',   
 store: ["Issue 1","Issue 2","Issue 3"]
 ]

Original comment by maric423@gmail.com on 1 Feb 2012 at 9:10

GoogleCodeExporter commented 9 years ago 
It seems that once a value is chosen the full dropdown list cannot be seen 
again.  This is true for both the store and store_val_labels type.
I will send an email with URL for testing.

Original comment by Aleda.Fr...@state.ma.us on 2 Feb 2012 at 9:05

GoogleCodeExporter commented 9 years ago 
1.  The above sample is incorrect - fields is an array of objects, where each 
object contains all the entries for a field - it should read 

fields : [{
 name: "ORGCODE", 
 xtype: 'combo',   
 store: ["Issue 1","Issue 2","Issue 3"]
 }]   

2. As coded, we support most of the non-validation ExtJS field parameters.  As 
such, try adding 
    triggerAction: 'all',
into your field definition.  

ex:
fields: [{
    name: "ISSUE",
    xtype: 'combo',
    triggerAction: 'all',
    store: ["Issue 1","Issue 2","Issue 3"]  
        }]

Original comment by maric423@gmail.com on 3 Feb 2012 at 3:12

GoogleCodeExporter commented 9 years ago

Original comment by Aleda.Fr...@state.ma.us on 3 Feb 2012 at 2:12

GoogleCodeExporter commented 9 years ago 
I found a small issue related to this.  The window that allows editing does not 
allow the middle bar to be slide back and forth.  So, I can create dropdowns 
where the user can't see the full text and there is no way for them to stretch 
the window on the right or the middle or use the scrollbars.  Can this be fixed 
somehow?  Otherwise the use of the dropdowns is limited.  See attachment for 
screenshot.

Original comment by Aleda.Fr...@state.ma.us on 17 Feb 2012 at 9:01

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm talking about the right hand column titled "Editing feature" - there's no 
way to make that wider that I can find..

Original comment by Aleda.Fr...@state.ma.us on 17 Feb 2012 at 9:08

GoogleCodeExporter commented 9 years ago 
Josh made the right side wider and the overall window bigger, I tested it and 
it looks good.  My 40 character dropdown string shows up nicely on the right 
side.

Original comment by Aleda.Fr...@state.ma.us on 21 Feb 2012 at 5:30

Attachments: