Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
I'm brand new to GWT-ext and am having problems with the BorderLayout control
as
well. I downloaded both the 0.9.3 and 0.9.2 versions of the gwtext.jar and in
both
jars the create() method is commented out. This causes an error for me when I
call
the BorderLayout constructor. So, for my very first attempt at using this
library I
can't even create my first container to start adding controls to. How is this
working in the Showcase demo that up on the web?
I'm trying to evaluate whether this library is ready for me to base a new
development effort around. I'm scared to see that basic things like this
aren't
working. To boot, it looks like this hasn't been working since 0.9.2 so this
problem has been there for a while and it's still not fixed. So doesn't anyone
use
a BorderLayout control? This give me the impression that very few people are
working with this code and that it is not very well tested. I also see tons of
other places in the code where things are commented out. It doesn't give me
much
confidence that this code is very solid.
Hopefully someone can give me some motivation and reasons to believe that this
library is actually in better shape than I'm assuming at this point. Maybe the
BorderLayout control is no longer a valid control. Maybe I'm not supposed to
call
the constructor the way I am. I hope that's the case. I was very impressed by
the
showcase demo and hoping that this could be a framework I could rely on. If
so, are
there some better samples that I can see? Maybe the sample code for the
Showcase
would be good that shows how the BorderLayout control is supposed to be called.
My single sample file is attached. Here's the error I get in the Toolkit
Debugger
window:
[ERROR] Unable to load module entry point class com.sissonix.client.GWTExtDemo
(see
associated exception for details)
com.google.gwt.core.client.JavaScriptException: JavaScript TypeError exception:
Object expected
at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:481)
at com.google.gwt.dev.shell.ModuleSpace.invokeNativeHandle
(ModuleSpace.java:225)
at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeHandle
(JavaScriptHost.java:89)
at com.gwtext.client.widgets.layout.BorderLayout.create(BorderLayout.java:61)
at com.gwtext.client.widgets.layout.BorderLayout.createBorderLayout
(BorderLayout.java:58)
at com.gwtext.client.widgets.layout.BorderLayout.<init>(BorderLayout.java:48)
at com.sissonix.client.GWTExtDemo.onModuleLoad(GWTExtDemo.java:78)
at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:342)
at com.google.gwt.dev.shell.BrowserWidget.attachModuleSpace
(BrowserWidget.java:326)
at com.google.gwt.dev.shell.ie.BrowserWidgetIE6.access$200
(BrowserWidgetIE6.java:36)
Original comment by marksis...@gmail.com
on 6 Jan 2008 at 7:07
Attachments:
For what it's worth, I figured out my problem (rookie mistake!). I was using
ext-js
version 2.0 instead of ext-js 1.1. Evidently using the more recent version can
cause
type errors.
Hope this helps someone. I found the answer when I discovered the forums :>
Original comment by marksis...@gmail.com
on 8 Jan 2008 at 5:58
Thanks for the update, I'll try to make the Ext version to use more clear in
the docs.
Original comment by sanjiv.j...@gmail.com
on 8 Jan 2008 at 6:03
Original issue reported on code.google.com by
mangrar
on 14 Sep 2007 at 8:06Attachments: