Ext.ux.Multiselect/ItemSelector [v2.2]

[tjstuart]

Version 2.2 now available


Version 2.0 of Ext.ux.Multiselect/ItemSelector now available.

User extension page http://extjs.com/learn/Extension:Multiselect

Demo page http://www.figtreesystems.com/ext/ex...ltiselect.html

Enhancements

General
- Now uses Animal's DDView

ItemSelector
- Move to top/bottom navigation buttons
- When using navigation buttons items remain selected in destination list

Multiselect
- Border dropped when marked invalid for better visuals (less jumping/popping)
- Validation for blank, min length and max length
- Ext.form.Field.getName() now returns correct name

@Animal -- Now using your DDView. Have an issue however:-

When multiple items are dropped anywhere outside a valid drop zone a runtime error occurs (Ext.Element.fly(this.dragData.ddel) has no properties) then drag no longer works.

@Galdaka -- Now using your icons

@andrei.neculau -- Incorporated all your suggestion except the GridEditor stuff. Many thanks for your efforts!

To all those who suggested enhancements that didnt make it in this release ... my apologies. Maybe next one.

Regards,

tjstuart

[justinfalk]

Look great tjstuart! Thanks for all your work on this. One minor thing I noticed was that you have dragable spelled two different ways (draggable, dragable).

Thanks.

Justin

[galdaka]

Woooo! Excellent work!

If you want any styled images contact me please (Three state images in a sprite for example)

Work fine for me in IE6.

Thanks in advance,

[andrei.neculau]

Looks nice

One thing that I need to clear is.. somehow on my system (modified 1.2) I get no flicker/border change as you do on version 2.0 when marking the field invalid.
I'll investigate.

[LATER EDIT]
Has to do with your onValid, onInvalid and the CSS classes. One has border 1px, one border 0.
Not to be self-centric, but I like my way better: without the two onValid, on Invalid and CSS like the following:

.x-combo-list.ux-mselect { border:0; overflow:auto; }
.x-combo-list-inner.ux-mselect-inner { border-bottom:0; }
.ux-mselect-pointer { cursor:pointer; margin:1px;}

[vahrens]

Hello TJ,

do you plan a version for Ext 2.0 in the near future?

Volker

[andrei.neculau]

@tjstuart

One thing that I simply wasn't aware of.. the concept is like this: getValue would return what you see, getRawValue would return the real value.

In this case getValue should have

returnArray.push(this.store.getAt(selectionsArray[i]).get(((valueField != null)? valueField : (this.valueField || this.displayField) )));

and getRawValue should be left alone.

On the other hand this.el should be the hidden field.
HiddenField from the ComboBox has a purpose.. because ComboBox has the displayed text-input with displayField, and can also have a hidden field which relates to valueField, but with your MultiSelect you only have one field, which is the hidden field.

Conclusion: Needs a little bit of re-coding.

[tjstuart]

Looks nice

One thing that I need to clear is.. somehow on my system (modified 1.2) I get no flicker/border change as you do on version 2.0 when marking the field invalid.
I'll investigate.

[LATER EDIT]
Has to do with your onValid, onInvalid and the CSS classes. One has border 1px, one border 0.
Not to be self-centric, but I like my way better: without the two onValid, on Invalid and CSS like the following:

.x-combo-list.ux-mselect { border:0; overflow:auto; }
.x-combo-list-inner.ux-mselect-inner { border-bottom:0; }
.ux-mselect-pointer { cursor:pointer; margin:1px;}

Problem there is that the widget then has no border at all and it is my opinion that this looks crap That's why I implemented the dual valid/invalid class switch so at least there is always a 1px border.

Maybe I'll re-visit this some other time.

Cheers

[tjstuart]

@tjstuart

One thing that I simply wasn't aware of.. the concept is like this: getValue would return what you see, getRawValue would return the real value.

Conclusion: Needs a little bit of re-coding.

I see your point however personally I am unsure of the usefulness of obtaining the display values. I would have thought the typical use of both the Multiselect and ItemSelector is database bound where the underlying value is important not the the display value. Perhaps I'm being narrow minded

I'm now quite busy with my real job and may be a few weeks before I could invest any real time in enhancing these widgets further. Therefore if you or anybody else would like to submit a working patch which addresses these or any other issues then please feel free.

Finally, thanks for your interest and input and helping to make things better

Cheers

[tjstuart]

Hello TJ,

do you plan a version for Ext 2.0 in the near future?

Volker

Probably not until Ext2 is released.

[Magicbob]

Just a word to congrats you and thanks you for this good job

Magicbob