Closed GoogleCodeExporter closed 9 years ago
You wrote:
> Sorry. I am not familiar with GWT-Designer and its interactions with this
project.
>
I understand. That's why I also asked about this in the GWT-Designer Forums.
They are not willing to even look at this. I continue to experiment.
Original comment by vmei...@gmail.com
on 21 Dec 2010 at 3:51
[deleted comment]
Hi,
In fact, when we create a UiBinder document (so 1 Java file + 1 XML file), the
interface is written in the XML file. But this one can't be correctly "opened
with" GWT Designer (may be just in my case): there is no "Design" view
available. In contrary, the WindowBuilder Editor allow the "Design" view for
the XML file.
Finally, is GWT-Designer really the problem ?
Morethan, in WindowBuilder Editor design view, new palettes from gxt-uibinder
don't exist. May be there is way of solution with the "import palette" from the
design view.
Original comment by alexis.r...@gmail.com
on 8 Mar 2011 at 8:53
Import, export or manage palette allowed me to see how Widget can be included
into the Design view. See the attached file, and include it by "import palette"
from the design view of the UiBinder XML file.
The palette I created quickly, has widgets that you described here:
http://code.google.com/docreader/#p=gxt-uibinder&s=gxt-uibinder&t=SupportedWidge
ts
In addition, I put 2 or 3 widgets that you didn't deal with. In example, the
EditorGrid or the color Panel.
But something is strange: when I drag & drop the color panel from my new
palette, it works, and a XML code is correctly generated!
Why ? I thought you just work on some widget... Is that means gxt-uibinder work
with all of Sencha Ext-GWT widgets ?
Try with the attached file, I think it will help you a few.
Original comment by alexis.r...@gmail.com
on 8 Mar 2011 at 11:14
Attachments:
It should be noted that this project (gxt-uibinder) does not create new
widgets. It only provides UiBinder support for the Sencha Ext-GWT widgets.
Many of the widgets from Sencha work, due to this project, even if they're not
documented on my wiki. For example, any widget that is a subclass to
com.extjs.gxt.ui.client.widget.Container can have nested children because my
library added that support.
I would like to think that all Sencha Ext-GWT widgets work, but that is not the
case, due to the different architectural approach Sencha took on some of the
widgets. For those cases, I have attempted to create custom XML that would
provide that support. For example, ContentPanel has setBottomComponent and
setTopComponent. The way I achieved this was to add nested <gxt:topcomponent>
and gxt:bottomcomponent> elements. From this, my custom ElementParser would
call the appropriate setters. With these sorts of customizations, there is a
cost to which the GWT Designer (WindowBuilder) will not support those new XML
elements.
Original comment by jus...@jhickman.com
on 10 Mar 2011 at 3:27
Until the Core GWT offers custom ElementParser registration (without the use of
the gxt-customuibinder project), it's futile attempting to get this to work.
It does appear that the WindowBuilder will parse the page and display
correctly, but doesn't appear to allow any drag-and-drop support for GXT
widgets as it's expecting all of the widgets to conform to the GWT standards
(by implementing special interfaces such as HasWidgets).
Marking issue as WontFix for the time being. May re-open if anything new comes
up.
Original comment by jus...@jhickman.com
on 18 Mar 2011 at 5:08
Original issue reported on code.google.com by
jus...@jhickman.com
on 21 Dec 2010 at 3:18