Tomas Jelinek has posted comments on this change.

Change subject: userportal,webadmin: type ahead list box
......................................................................


Patch Set 8: (4 inline comments)

....................................................
File 
frontend/webadmin/modules/gwt-common/src/main/java/org/ovirt/engine/ui/common/widget/editor/BaseListModelSuggestBox.java
Line 23: public abstract class BaseListModelSuggestBox<T> extends Composite 
implements EditorWidget<T, TakesConstrainedValueEditor<T>>, 
HasConstrainedValue<T> {
Line 24: 
Line 25:     private TakesConstrainedValueEditor<T> editor;
Line 26: 
Line 27:     private T value;
Well, it is used by both. You could do without it for both and always parse the 
suggestBox on getValue() or you can return this. I just find this more clear.
You have a value stored and than methods to render it and turn an input string 
into it. The fact that for suggest box it is the same value is more or less a 
coincidence - but the generic solution is this (also for other implementations 
of this in the future).
Line 28: 
Line 29:     private SuggestBox suggestBox;
Line 30: 
Line 31:     private ListModelSuggestionDisplay suggestionDisplay = new 
ListModelSuggestionDisplay();


Line 32: 
Line 33:     private ValueChangeHandler<T> handler;
Line 34: 
Line 35:     public BaseListModelSuggestBox(MultiWordSuggestOracle 
suggestOracle) {
Line 36:         suggestBox = new SuggestBox(suggestOracle, new TextBox(), 
suggestionDisplay) {
In the place where it is used currently the suggestions are shown correctly 
without the z-index set. In web admin also the type ahead was shown well. But 
in user portal the type ahead needed the z-index to show up well. It does not 
hurt if it is set and it is more safe I would say.
Line 37:             @Override
Line 38:             public void setText(String text) {
Line 39:                 super.setText(text);
Line 40: 


Line 152:         return value;
Line 153:     }
Line 154: 
Line 155:     @Override
Line 156:     public HandlerRegistration addValueChangeHandler(final 
ValueChangeHandler<T> handler) {
well, this would work. But if you compare it with the patchset 9, I would say 
it is a matter of personal taste which is better.
Line 157:         this.handler = handler;
Line 158:         return asSuggestBox().addValueChangeHandler(new 
ValueChangeHandler<String>() {
Line 159:             @Override
Line 160:             public void onValueChange(ValueChangeEvent<String> event) 
{


Line 166: 
Line 167:     class ListModelSuggestionDisplay extends DefaultSuggestionDisplay 
{
Line 168: 
Line 169:         public ListModelSuggestionDisplay() {
Line 170:             // not not be hidden under the panel
yes :)
Line 171:             getPopupPanel().getElement().getStyle().setZIndex(1);
Line 172:         }
Line 173: 
Line 174:         // just to make it public


-- 
To view, visit http://gerrit.ovirt.org/14936
To unsubscribe, visit http://gerrit.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I956af3c675894c850a1a104a81cec49f4bd62011
Gerrit-PatchSet: 8
Gerrit-Project: ovirt-engine
Gerrit-Branch: master
Gerrit-Owner: Tomas Jelinek <[email protected]>
Gerrit-Reviewer: Daniel Erez <[email protected]>
Gerrit-Reviewer: Einav Cohen <[email protected]>
Gerrit-Reviewer: Frank Kobzik <[email protected]>
Gerrit-Reviewer: Gilad Chaplik <[email protected]>
Gerrit-Reviewer: Lior Vernia <[email protected]>
Gerrit-Reviewer: Michal Skrivanek <[email protected]>
Gerrit-Reviewer: Tomas Jelinek <[email protected]>
Gerrit-Reviewer: Vojtech Szocs <[email protected]>
Gerrit-Reviewer: oVirt Jenkins CI Server
_______________________________________________
Engine-patches mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/engine-patches

Reply via email to