|
|||||||
![]() |
|
|
Thread Tools |
|
#1
|
|||
|
|||
|
As we were facing a problem similar to the one described here: http://www.extjs.com/forum/showthrea...extarea+scroll we thought it might be a good idea to switch to using the latest 2.0.x GXT release.
After the required files (.jar, resources) changes and a short review, we noticed the following problems: * Some APIs have changed from 2.0.1 to 2.0.4, which is I think unacceptable for a minor release. For instance in com.extjs.gxt.ui.client.data.MemoryProxy, the encapsulated data object was changed from the generic type D to Object, which of course breaks our code. * The default size for the toolbar buttons is changed such as they overlap now. This can be fixed by calling setSize() for all toolbar buttons, but anyway, this is still not ok. * Finally, the scroll bar issue we had is almost fixed. It doesn't work the first time we drag the scroll bar, but it always for on a second attempt. Any suggestions? Regards, Dan |
|
#2
|
|||
|
|||
|
Hello,
We were trying to get the FileUploadLoad component to work, but it was buggy in IE in version 2.0.1. Which led us to upgrade to 2.0.4. However, version 2.0.4 breaks our app due changes in how GXT is handling toolbars/buttons/sizing. The fixes to deal with these problems prevent us from using a previous version .. So, it is either commit to the changes .. or wait to you bring it back in line with the previous layout. Are these layout issues considered bugs that will be fixed in a future version, or are they the future direction? Is there a document that describes these changes? |
|
#3
|
|||
|
|||
|
There are no braking changes in the layouts. If something is not working, than you should start with posting simple examples of your code that demonstrate exactly what you are doing and implement entrypoint.
|
|
#4
|
|||
|
|||
|
Hi Sven,
Thanks, you were right there are no breaking changes. ![]() The main problem was we were using setStyleName to attach our custom styles to GXT widgets, such as buttons, FieldSets, etc... This worked as expected in versions 2.0.1 and less, but fails in 2.0.2 and greater. It seems by using setStyleName we 'overwrite' the default styles set by GXT. This makes sense, but took a bit of time to figure out. I have worked through these problems. The last problem I am dealing with is Button adding width if it has a menu. In 2.0.1 and less the menu portion of the button was included in the width, now it is added. For example, this code: public class GxtTest implements EntryPoint {
public void onModuleLoad() {
ContentPanel main = new ContentPanel();
main.setHeading("Change in button length with menu");
main.add(new MyButton("One"));
main.add(new MyButton("Two"));
Button btn = new MyButton("Three");
btn.setMenu(new Menu());
main.add(btn);
main.add(new MyButton("Four"));
Viewport viewPort = new Viewport();
viewPort.setLayout(new FitLayout());
viewPort.add(main);
RootPanel.get().add(viewPort);
}
static class MyButton extends Button {
public MyButton(String name) {
super(name);
setWidth(115);
}
}
}
You can see the attached image showing the different results with versions 2.0.1 and 2.0.4. |
![]() |
| Thread Tools | |
|
|