eugenparaschiv
1 Aug 2008, 12:51 AM
I have opened a few threads on various bugs I have found in these classes in the GXT - Help form (I need help with them :)). I will briefly list them here as well, but I will be happy to provide more details
1. NO error warnings whatsoever
- for example: when a CSS style is not found, the code just keeps running, with very weird visual artifacts (like the triggers actually changing place when when I pass with the mouse over them and the ONMOUSEOVER event is fired); the only way to see what the problem is is to do extensive debugging; the idea here is that if a CSS is NOT FOUND the program must evidently not be allowed to continue, or at the very least display some kind of warning message
2. tooltips appearing over the triggers, which is not only NOT intuitive behavior, but makes the buttons hard to click
- discussion: this is of course due to the fact that both these classes extend TextField and so when setting the tooltip, it is set over the whole field, including the two triggers
- two fixes could be possible: one, try to set the tooltip over the input only (I admit I have no idea how to do this, and not for lack of trying) or reimplement the entire widget as something else (the GWT Composite comes to mind, but probably not; anyways something similar)
- by doing this, the client would have individual access to the three elements, especially the text field (which would now be a class instance and not the superclass); this would allow of course much more cleaner code for pretty much every aspect of the class, but it would be a major refactoring process instead of just a little fix...perhaps in time, but for now, the fix :)
3. the styles of the triggers: there is a way (a setter) to set the styles for both the triggers (evidently, if there was not, the class would be completely unusable, because the triggers would always look like the arrow of a dropdown list); the problem is that there are no setters to configure the styles for onmouseover and onmouseout which means that I am stuck with the defauls. Now if I change the image of the trigger, of course I will want to change these styles as well. I admit that out of the three items I listed in this post, I am unsure about this last one (perhaps I just don't know how to do it ... not really well documented, these classes)
That's it for now. Save some minor inconsistencies I noticed between the implementation of the TriggerField and that of the TwinTriggerField (the code for each was probably written some time apart), I will add problems as I bump into them. I would apreciate any answers to any of these problems. Thank you. Eugen .
1. NO error warnings whatsoever
- for example: when a CSS style is not found, the code just keeps running, with very weird visual artifacts (like the triggers actually changing place when when I pass with the mouse over them and the ONMOUSEOVER event is fired); the only way to see what the problem is is to do extensive debugging; the idea here is that if a CSS is NOT FOUND the program must evidently not be allowed to continue, or at the very least display some kind of warning message
2. tooltips appearing over the triggers, which is not only NOT intuitive behavior, but makes the buttons hard to click
- discussion: this is of course due to the fact that both these classes extend TextField and so when setting the tooltip, it is set over the whole field, including the two triggers
- two fixes could be possible: one, try to set the tooltip over the input only (I admit I have no idea how to do this, and not for lack of trying) or reimplement the entire widget as something else (the GWT Composite comes to mind, but probably not; anyways something similar)
- by doing this, the client would have individual access to the three elements, especially the text field (which would now be a class instance and not the superclass); this would allow of course much more cleaner code for pretty much every aspect of the class, but it would be a major refactoring process instead of just a little fix...perhaps in time, but for now, the fix :)
3. the styles of the triggers: there is a way (a setter) to set the styles for both the triggers (evidently, if there was not, the class would be completely unusable, because the triggers would always look like the arrow of a dropdown list); the problem is that there are no setters to configure the styles for onmouseover and onmouseout which means that I am stuck with the defauls. Now if I change the image of the trigger, of course I will want to change these styles as well. I admit that out of the three items I listed in this post, I am unsure about this last one (perhaps I just don't know how to do it ... not really well documented, these classes)
That's it for now. Save some minor inconsistencies I noticed between the implementation of the TriggerField and that of the TwinTriggerField (the code for each was probably written some time apart), I will add problems as I bump into them. I would apreciate any answers to any of these problems. Thank you. Eugen .