Re: Ui Binder Alternatives

[James Horsley]

Something like Elemento + Elemental 2 seems like a great lightweight choice
in the future.

FWIW I agree with Paul that UiBinder plus some top layer of the widget API
(UIObject, Widget, etc.) will get ported over to work with GWT 3.0 by the
community. There's no reason it can't work with Java APT + JsInterop, just
needs the tech investment. I think this will be a huge help for many teams
doing a gradual upgrade.

On Tue, Jul 26, 2016 at 7:43 AM zakaria amine 
wrote:

> Elemento project sounds like an intersting alternative:
> https://github.com/hal/elemento
>
>
> Le dimanche 24 juillet 2016 03:40:02 UTC+2, N Troncoso a écrit :
>>
>> With GWT 3.0, Widgets and UI Binder is losing support. Even besides that,
>> I'm not a huge fan of UI Binder. I'd really just prefer to use vanilla
>> HTML. With that said, I've been searching for other options and I've only
>> found that alternatives are very limited. Even more so, examples of how to
>> integrate alternatives into GWT are basically non-existent. So, my question
>> is, what can I use instead of Widgets and UI Binder and where can I find
>> examples/tutorials/documentation on how to use them in GWT.
>>
>> I found Errai  as one option. But, this
>> seems to be an entire framework, rather than just a template system.
>>
>> Any insight would be greatly appreciated. Thanks
>>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Ui Binder Alternatives

[zakaria amine]

Elemento project sounds like an intersting 
alternative: https://github.com/hal/elemento

Le dimanche 24 juillet 2016 03:40:02 UTC+2, N Troncoso a écrit :
>
> With GWT 3.0, Widgets and UI Binder is losing support. Even besides that, 
> I'm not a huge fan of UI Binder. I'd really just prefer to use vanilla 
> HTML. With that said, I've been searching for other options and I've only 
> found that alternatives are very limited. Even more so, examples of how to 
> integrate alternatives into GWT are basically non-existent. So, my question 
> is, what can I use instead of Widgets and UI Binder and where can I find 
> examples/tutorials/documentation on how to use them in GWT.
>
> I found Errai  as one option. But, this seems 
> to be an entire framework, rather than just a template system.
>
> Any insight would be greatly appreciated. Thanks
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Ui Binder Alternatives

[Paul Stockley]

I think there is a good chance that Widgets / UiBinder in some form could 
get ported to GWT 3.0. Probably not by google and probably in separate 
projects from the main GWT compiler stack.

On Monday, July 25, 2016 at 7:58:50 PM UTC-4, Gilberto wrote:
>
> Nobody really knows how GWT 3 will be for sure, but I assume GWT 3.0 will 
> be less of a framework and more of a transpiler from Java to Javascript, 
> which other frameworks will be built on top of it.
>
> So I wouldn't expect a simple template engine to replace UiBinder, but 
> full featured frameworks. You'll have to choose one or implement your own.
>
> But that's for 3.0.
>
> Meanwhile, I see Errai as a very good option, since you can use the HTML 
> template right from your designers, with minimal-to-none modifications to 
> link with your logic code. That's something pretty hard to achieve with 
> UiBinder.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Ui Binder Alternatives

[Alain Ekambi]

Errai is the best. Point. Period.

On 26 July 2016 at 01:58, Gilberto  wrote:

> Nobody really knows how GWT 3 will be for sure, but I assume GWT 3.0 will
> be less of a framework and more of a transpiler from Java to Javascript,
> which other frameworks will be built on top of it.
>
> So I wouldn't expect a simple template engine to replace UiBinder, but
> full featured frameworks. You'll have to choose one or implement your own.
>
> But that's for 3.0.
>
> Meanwhile, I see Errai as a very good option, since you can use the HTML
> template right from your designers, with minimal-to-none modifications to
> link with your logic code. That's something pretty hard to achieve with
> UiBinder.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Alain Ekambi

Co-Founder

Ahomé Innovation Technologies

http://www.ahome-it.com/ 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Ui Binder Alternatives

[Gilberto]

Nobody really knows how GWT 3 will be for sure, but I assume GWT 3.0 will 
be less of a framework and more of a transpiler from Java to Javascript, 
which other frameworks will be built on top of it.

So I wouldn't expect a simple template engine to replace UiBinder, but full 
featured frameworks. You'll have to choose one or implement your own.

But that's for 3.0.

Meanwhile, I see Errai as a very good option, since you can use the HTML 
template right from your designers, with minimal-to-none modifications to 
link with your logic code. That's something pretty hard to achieve with 
UiBinder.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Ui Binder Alternatives

[Kay Pac]

I don't want to start a huge discussion necessarily but are Widgets really 
losing support?

On Monday, July 25, 2016 at 10:45:29 AM UTC-7, Paul Stockley wrote:
>
> One option when 2.8 is released would be to use GWT React (
> https://github.com/GWTReact/gwt-react). React is a good substitute for 
> the view layer and can be integrated with existing widgets so you can 
> migrate your way to a UiBinderless approach.
>
> On Saturday, July 23, 2016 at 9:40:02 PM UTC-4, N Troncoso wrote:
>>
>> With GWT 3.0, Widgets and UI Binder is losing support. Even besides that, 
>> I'm not a huge fan of UI Binder. I'd really just prefer to use vanilla 
>> HTML. With that said, I've been searching for other options and I've only 
>> found that alternatives are very limited. Even more so, examples of how to 
>> integrate alternatives into GWT are basically non-existent. So, my question 
>> is, what can I use instead of Widgets and UI Binder and where can I find 
>> examples/tutorials/documentation on how to use them in GWT.
>>
>> I found Errai  as one option. But, this 
>> seems to be an entire framework, rather than just a template system.
>>
>> Any insight would be greatly appreciated. Thanks
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Ui Binder Alternatives

[Paul Stockley]

One option when 2.8 is released would be to use GWT React (
https://github.com/GWTReact/gwt-react). React is a good substitute for the 
view layer and can be integrated with existing widgets so you can migrate 
your way to a UiBinderless approach.

On Saturday, July 23, 2016 at 9:40:02 PM UTC-4, N Troncoso wrote:
>
> With GWT 3.0, Widgets and UI Binder is losing support. Even besides that, 
> I'm not a huge fan of UI Binder. I'd really just prefer to use vanilla 
> HTML. With that said, I've been searching for other options and I've only 
> found that alternatives are very limited. Even more so, examples of how to 
> integrate alternatives into GWT are basically non-existent. So, my question 
> is, what can I use instead of Widgets and UI Binder and where can I find 
> examples/tutorials/documentation on how to use them in GWT.
>
> I found Errai  as one option. But, this seems 
> to be an entire framework, rather than just a template system.
>
> Any insight would be greatly appreciated. Thanks
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: UI Binder why?

[Thomas Broyer]

On Wednesday, October 16, 2013 8:53:36 PM UTC+2, Timothy Spear wrote:

 How would the declarative UiBinder jeopardize browser independence?


I think he's talking about HTMLPanel actually, which is independent from 
UiBinder, but which UiBinder makes it so much easier to use.

BTW, I don't think there's any *guarantee* of browser independence. There's 
a *best effort* in terms of behavior but not really in terms of rendering 
(except for container widgets, but that's part of their behavior 
right?).
When I say *no guarantee*, I say it as if I told you jQuery makes no 
guarantee either.

For rendering, you'll have to use CSS (you won't use one the built-in 
themes, will you?), and you'll hit browser discrepancies there.
GWT's main goal is not to *hide* these discrepancies (it does hide many of 
them, but so do many JS libraries), but to use Java as your programming 
language of choice, allowing you benefit from its static typing, use most 
existing Java tooling, and share code with other Java-based environments 
(server-side Java, desktop Java, JavaFX, Android – and even iOS with 
Google's J2ObjC).
Just like with any platform, you'll have to learn it, and GWT's platform is 
the Web, so it won't free you to learn HTML, JS and CSS.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Re: UI Binder why?

[Timothy Spear]

How would the declarative UiBinder jeopardize browser independence?

Personally, I like UiBinder overall. There are few cases where I find it a 
pain, but overall for any screen which has multiple elements I have found it 
significantly cuts the amount of code required. It also has the benefit of 
making the Java class file significantly shorter making it easier to find the 
logic and not focus ignoring all the wiring of elements. This provides for 
much better separation in my opinion which simplifies code maintenance. 

Since I know it will come up. Here are the major downsides as I see it for 
UiBinder:
-- UiBinder requires two files which have to be maintained in sync.
-- UiBinder hides to much on occasion. This can produce very ugly HTML. You 
really have to learn how UiBinder generates the result (same issue with GWT, 
but adds another layer on top in my opinion).
-- UiBinder is not friendly in terms of using a ClientResourceBundle for CSS. 
(I use addStyleName a lot). So I end up adding most style names via Java code.

Tim

On Oct 16, 2013, at 2:19 PM, Tim McClure tjmcclure0...@gmail.com wrote:

 What is the most used approach in GWT- the native approach where all web code 
 is generated through GWT or the declarative approach where HTML/CSS templates 
 are used and integrated through UIBinder?  It seems the declarative approach 
 was introduced for separation of concerns and allowing graphic designers the 
 ability to contribute to GWT systems.  However could it be argued that the 
 declarative approach jeopardizes the browser independence guaranteed by GWT.  
 We are new to GWT and we are trying to determine which direction we should 
 take - what is the most recommended design pattern?
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Re: UI Binder designer giving exception

[Jens]

Looks like UiBinder does not know how to deal with FlexTable and thus you 
need to set it up yourself in the java file. To do so you would use 
@UiField(provided 
= true) FlexTable myTable and instantiate it before calling 
binder.createAndBindUi(). 
Then you can add child widgets to it programmatically.

If you don't like that then don't use FlexTable. For example you could 
change your SimpleLayoutPanel to an HTMLPanel and then use plain table, 
tr, td tags to build the table. Or instead of table tags use div tags 
along with some Css.

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Re: UI Binder Button Problem

[walker1c]

Hi Alex,

That would be a start.

Does the tag in your post work?  The Javadoc at
http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/CustomButton.html
shows upFace as a sub-node of the PushButton tag. If I'm reading the
UIBinder documentation correctly, upFace can only be an attribute of
the PushButton tag if the class has a method called setUpFace().

As a matter of fact this seems to be really a problem with UiBinder
and PushButton.  I've converted my button to @UiField(provided =
true), and I'm loading the images direct from URLs when I construct
the PushButton, and even then the button isn't rendered.

Thanks for the reply.

Chris


On Aug 16, 3:00 pm, Alex Dobjanschi alex.dobjans...@gmail.com wrote:
 What are you trying to do exactly? Setting the upFace of a PushButton?

 Then go with
 {{{
    g:PushButton ui:field=button
           upFace={img.button} /

 }}}

 (not sure highlight will work)

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder Button Problem

[Alex Dobjanschi]

What are you trying to do exactly? Setting the upFace of a PushButton?

Then go with
{{{
   g:PushButton ui:field=button
  upFace={img.button} /
}}}

(not sure highlight will work)

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/lOs0rJa8_YcJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI binder design mode error

[Eric Clayberg]

Looks like a JDK issue...

http://code.google.com/p/google-web-toolkit/issues/detail?id=4254

If you are using JDK 1.5, give it a try using JDK 1.6.

On Jun 22, 10:31 am, srini malka srini.j...@gmail.com wrote:
 HI folks,

 I created Test.ui.xml UI biner , when i open in design mode i am
 getting  following error:
 i am using eclips 3.6 and For GWT SDK  
 Plugin  http://dl.google.com/eclipse/plugin/3.6
 For GWT Designer  plug in  
 http://dl.google.com/eclipse/inst/d2gwt/latest/3.6

 ERROR:

 GWT Designer encountered unexpected internal error.

 This could be caused by a GWT Designer bug or by a misconfiguration
 issue, conflict, partial update, etc.

 java.lang.VerifyError: (class: com/google/gwt/core/client/Scheduler,
 method: signature: ()V) Illegal constant pool index

 Show stack trace.
 Hide stack trace.

 Stack trace:
 java.lang.VerifyError: (class: com/google/gwt/core/client/Scheduler,
 method: init signature: ()V) Illegal constant pool index
         at
 com.google.gwt.dom.client.StyleInjector.schedule(StyleInjector.java:
 393)
         at com.google.gwt.dom.client.StyleInjector.inject(StyleInjector.java:
 386)
         at com.google.gwt.dom.client.StyleInjector.inject(StyleInjector.java:
 226)
         at com.google.gwt.dom.client.StyleInjector.inject(StyleInjector.java:
 212)
         at
 com.test.jpmc.client.TestDatabinder_TestDatabinderUiBinderImpl_designTime13 
 08752509288_GenBundle_default_InlineClientBundleGenerator
 $1.ensureInjected(TestDatabinder_TestDatabinderUiBinderImpl_designTime13087 
 52509288_GenBundle_default_InlineClientBundleGenerator.java:
 14)
         at
 com.test.jpmc.client.TestDatabinder_TestDatabinderUiBinderImpl_designTime13 
 08752509288.createAndBindUi(TestDatabinder_TestDatabinderUiBinderImpl_desig 
 nTime1308752509288.java:
 34)
         at
 com.test.jpmc.client.TestDatabinder_TestDatabinderUiBinderImpl_designTime13 
 08752509288.createAndBindUi(TestDatabinder_TestDatabinderUiBinderImpl_desig 
 nTime1308752509288.java:
 1)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
 39)
         at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp 
 l.java:
 25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at
 org.eclipse.wb.internal.core.utils.reflect.ReflectionUtils.invokeMethod(Ref 
 lectionUtils.java:
 836)
         at
 com.google.gdt.eclipse.designer.uibinder.parser.UiBinderParser.parse0(UiBin 
 derParser.java:
 122)
         at
 com.google.gdt.eclipse.designer.uibinder.parser.UiBinderParser.access
 $0(UiBinderParser.java:107)
         at com.google.gdt.eclipse.designer.uibinder.parser.UiBinderParser
 $1.run(UiBinderParser.java:94)
         at
 com.google.gdt.eclipse.designer.uibinder.parser.UiBinderContext.runDesignTi 
 me(UiBinderContext.java:
 153)
         at
 com.google.gdt.eclipse.designer.uibinder.parser.UiBinderParser.parse(UiBind 
 erParser.java:
 91)
         at
 com.google.gdt.eclipse.designer.uibinder.editor.UiBinderDesignPage.parse(Ui 
 BinderDesignPage.java:
 93)
         at
 org.eclipse.wb.internal.core.xml.editor.XmlDesignPage.internal_refreshGEF(X 
 mlDesignPage.java:
 409)
         at org.eclipse.wb.internal.core.xml.editor.XmlDesignPage.access
 $2(XmlDesignPage.java:401)
         at org.eclipse.wb.internal.core.xml.editor.XmlDesignPage
 $7$1.run(XmlDesignPage.java:375)
         at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:
 179)
         at
 org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:
 150)
         at org.eclipse.swt.widgets.Display.syncExec(Display.java:4584)
         at org.eclipse.wb.internal.core.xml.editor.XmlDesignPage
 $7.run(XmlDesignPage.java:372)
         at
 org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.ja 
 va:
 464)
         at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:
 372)
         at
 org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.j 
 ava:
 507)
         at
 org.eclipse.wb.internal.core.xml.editor.XmlDesignPage.internal_refreshGEF_w 
 ithProgress(XmlDesignPage.java:
 393)
         at
 org.eclipse.wb.internal.core.xml.editor.XmlDesignPage.internal_refreshGEF(X 
 mlDesignPage.java:
 346)
         at
 org.eclipse.wb.internal.core.xml.editor.UndoManager.refreshDesignerEditor(U 
 ndoManager.java:
 229)
         at
 org.eclipse.wb.internal.core.xml.editor.UndoManager.activate(UndoManager.ja 
 va:
 85)
         at
 org.eclipse.wb.internal.core.xml.editor.XmlDesignPage.setActive(XmlDesignPa 
 ge.java:
 165)
         at
 org.eclipse.wb.internal.core.xml.editor.AbstractXmlEditor.pageChange(Abstra 
 ctXmlEditor.java:
 328)
         at org.eclipse.ui.part.MultiPageEditorPart
 $2.widgetSelected(MultiPageEditorPart.java:290)
         at
 org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:
 234)
         at 

Re: UI Binder Alignment problems

[pete]

I had the same problem just a while ago, even though I had it with
g:VerticalPanel horizontalAlignment=ALIGN_CENTER

The reason in my case at least was, that UiBinder first adds the
children, then sets the attribute horizontalAlignment, but
horizontalAlignment is only taken into account for widgets added after
the property is set, so it has no effect on widgets added in the
template.

This is actually fixed in GWT 2.1.1., because I had version 2.1.0.
running and updated for that. Afterwards it worked as expected... Hope
that helps, since I haven't tried it with g:cell ... and I don't
know if the problems are related...


On Feb 17, 8:58 pm, Philippe Beaudoin philippe.beaud...@gmail.com
wrote:
 I've had tons of problem using Vertical and HorizontalPanel to align
 correctly. In my most recent project I followed the advice from GWT
 documentation and moved away from them. Now I do everything with FlowPanel
 (or HTMLPanel) and careful use of floats. It has made my life much easier. I
 don't know if you can give that approach a spin in the current context?

 Cheers,

    Philippe

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder Alignment problems

[skippy]

One follow up.

I am using GWT 2.0.4 with the eclipse 3.5 and the plug-in

On Feb 17, 9:34 am, skippy al.leh...@fisglobal.com wrote:
 I have the following UI Binder XML:
 g:ScrollPanel ui:field='outerPanel' 
         g:VerticalPanel
             g:Cell verticalAlignment=ALIGN_TOP
                 g:HorizontalPanel ui:field='topPanel'
                     g:cell width=30%
 horizontalAlignment=ALIGN_LEFT // not working and does not show
                         g:SimplePanel ui:field='logoPanel' /
 g:SimplePanel
                     /g:cell
                     g:cell width=70%
 horizontalAlignment=ALIGN_RIGHT     // this looks center
                             g:FlexTable ui:field='bannerArea' /
                     /g:cell
                     /g:HorizontalPanel
             /g:Cell
             g:Cell horizontalAlignment=ALIGN_CENTER
                    g:SimplePanel ui:field='bodyPanel'/
             /g:Cell
             g:Cell verticalAlignment=ALIGN_BOTTOM  // not working
                 g:HTML ui:field=footer/
             /g:Cell
        /g:VerticalPanel
    /g:ScrollPanel

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder Alignment problems

[Philippe Beaudoin]

I've had tons of problem using Vertical and HorizontalPanel to align 
correctly. In my most recent project I followed the advice from GWT 
documentation and moved away from them. Now I do everything with FlowPanel 
(or HTMLPanel) and careful use of floats. It has made my life much easier. I 
don't know if you can give that approach a spin in the current context?

Cheers,

   Philippe

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Nick Apperley]

As it turns out a line was missing in the LoginPage's constructor for
properly initializing itself which is required for UIBinder. This
would explain why an instance of LoginPage couldn't be added to
RootLayoutPanel.

initWidget(uiBinder.createAndBindUi(this));



On Feb 16, 10:30 am, Nick Apperley napper...@gmail.com wrote:
 Something is not being initialized properly (most likely the
 Composite). Shouldn't the server take care of this?

 On Feb 16, 10:23 am, Nick Apperley napper...@gmail.com wrote:

  Based on the exception the problem occurs when the login page (a
  Composite) is being added to the RootLayoutPanel.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Nick Apperley]

Interestingly enough if I adjust the code to only attach a Label to
RootLayoutPanel in the onModuleLoad method no compilation is done, and
nothing is displayed on the web page. This is weird since a minor
change has been made to the code, even if nothing was displayed
Firefox should freeze to indicate that compilation is currently being
done. No error messages are being displayed in Eclipse's Console
window, absolutely nothing to go by.


On Feb 15, 10:51 am, Jeff Larsen larse...@gmail.com wrote:
 Pop open firebug and start drilling down into the DOM and see if you can
 find your code in there. I.e. any of your labels, widgets, panels. If they
 aren't there, then maybe an error is being caught somewhere and not thrown,
 if they are there but not visible, start mucking around with CSS properties
 to see if you've attached stuff correctly.

 Note, if you're using layout panels, you're best case scenario is to use
 layoutpanels from rootpanel all the way through to your top level panels.

 doing something like
 FlowPanel panel = new FlowPanel();
 DockLayoutPanel dockPanel = new DockLayoutPanel();
 //do stuff with docklayoutpanel
 RootLayoutPanel.get().add(panel);

 this will cause nothing to be displayed.

If it is done outside of the onModuleLoad method of an EntryPoint.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Jeff Larsen]

Are you working in offline mode? That happened to me earlier today. 

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Nick Apperley]

Not in offline mode. Anyway I have recreated the project as a new Web
Application (the Google one) project in Eclipse. Compilation works
normally but now I have an exception appearing in development mode,
which didn't occur previously with the old project type (GWT Java).


---
10:11:55.193 [ERROR] [autohome_automator] Unable to load module entry
point class com.darc.autohome.automatortool.client.AutohomeAutomator
(see associated exception for details)

java.lang.AssertionError: This UIObject's element is not set; you may
be missing a call to either Composite.initWidget() or
UIObject.setElement()
at com.google.gwt.user.client.ui.UIObject.getElement(UIObject.java:
528)
at
com.google.gwt.user.client.ui.ComplexPanel.add(ComplexPanel.java:94)
at
com.google.gwt.user.client.ui.AbsolutePanel.add(AbsolutePanel.java:97)
at
com.darc.autohome.automatortool.client.Controller.showLoginPage(Controller.java:
28)
at
com.darc.autohome.automatortool.client.AutohomeAutomator.onModuleLoad(AutohomeAutomator.java:
17)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:
396)
at
com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:
183)
at
com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:
510)
at
com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:
352)
at java.lang.Thread.run(Thread.java:619)
---

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Nick Apperley]

Based on the exception the problem occurs when the login page (a
Composite) is being added to the RootLayoutPanel.


On Feb 16, 10:17 am, Nick Apperley napper...@gmail.com wrote:
 Not in offline mode. Anyway I have recreated the project as a new Web
 Application (the Google one) project in Eclipse. Compilation works
 normally but now I have an exception appearing in development mode,
 which didn't occur previously with the old project type (GWT Java).

 ---
 10:11:55.193 [ERROR] [autohome_automator] Unable to load module entry
 point class com.darc.autohome.automatortool.client.AutohomeAutomator
 (see associated exception for details)

 java.lang.AssertionError: This UIObject's element is not set; you may
 be missing a call to either Composite.initWidget() or
 UIObject.setElement()
     at com.google.gwt.user.client.ui.UIObject.getElement(UIObject.java:
 528)
     at
 com.google.gwt.user.client.ui.ComplexPanel.add(ComplexPanel.java:94)
     at
 com.google.gwt.user.client.ui.AbsolutePanel.add(AbsolutePanel.java:97)
     at
 com.darc.autohome.automatortool.client.Controller.showLoginPage(Controller.java:
 28)
     at
 com.darc.autohome.automatortool.client.AutohomeAutomator.onModuleLoad(AutohomeAutomator.java:
 17)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
 39)
     at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
 25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:
 396)
     at
 com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:
 183)
     at
 com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:
 510)
     at
 com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:
 352)
     at java.lang.Thread.run(Thread.java:619)
 ---

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Nick Apperley]

Something is not being initialized properly (most likely the
Composite). Shouldn't the server take care of this?


On Feb 16, 10:23 am, Nick Apperley napper...@gmail.com wrote:
 Based on the exception the problem occurs when the login page (a
 Composite) is being added to the RootLayoutPanel.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Jeff Larsen]

Are you using layout panels? If so, have you set the doctype to standards 
mode? Also, if you are using layout panels, you need to attach them to 
RootLayoutPanel, not RootPanel. 

Another thing to check is to see if the widgets are attached to the DOM with 
something like firebug. 

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Nick Apperley]

Doc type is set to standards mode and I have switched from RootPanel
to RootLayoutPanel, but it has not changed anything with displaying
the main page. There doesn't appear to be anything in the DOM related
to the application. What should I specifically look for with GWT in
the DOM?


On Feb 15, 10:15 am, Jeff Larsen larse...@gmail.com wrote:
 Are you using layout panels? If so, have you set the doctype to standards
 mode? Also, if you are using layout panels, you need to attach them to
 RootLayoutPanel, not RootPanel.

 Another thing to check is to see if the widgets are attached to the DOM with
 something like firebug.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Jeff Larsen]

Pop open firebug and start drilling down into the DOM and see if you can 
find your code in there. I.e. any of your labels, widgets, panels. If they 
aren't there, then maybe an error is being caught somewhere and not thrown, 
if they are there but not visible, start mucking around with CSS properties 
to see if you've attached stuff correctly. 

Note, if you're using layout panels, you're best case scenario is to use 
layoutpanels from rootpanel all the way through to your top level panels. 

doing something like 
FlowPanel panel = new FlowPanel();
DockLayoutPanel dockPanel = new DockLayoutPanel();
//do stuff with docklayoutpanel
RootLayoutPanel.get().add(panel);

this will cause nothing to be displayed. 

For more information, 
http://code.google.com/webtoolkit/doc/latest/DevGuideUiPanels.html



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder File Not Loaded During Runtime

[Nick Apperley]

After looking at a similar application that does something very
similar (in code) it displays the main page just fine. In the
corresponding DOM the are 3 defined GWT variables (__gwt_SessionID,
__gwt_scriptsLoaded, __gwt_stylesLoaded). With the problematic
application it doesn't have the defined GWT variables, and it does not
compile (no compile error messages appear in Eclipse's Console
window). Hence Firefox doesn't freeze when the application is loaded
the first time.



On Feb 15, 10:51 am, Jeff Larsen larse...@gmail.com wrote:
 Pop open firebug and start drilling down into the DOM and see if you can
 find your code in there. I.e. any of your labels, widgets, panels. If they
 aren't there, then maybe an error is being caught somewhere and not thrown,
 if they are there but not visible, start mucking around with CSS properties
 to see if you've attached stuff correctly.

 Note, if you're using layout panels, you're best case scenario is to use
 layoutpanels from rootpanel all the way through to your top level panels.

 doing something like
 FlowPanel panel = new FlowPanel();
 DockLayoutPanel dockPanel = new DockLayoutPanel();
 //do stuff with docklayoutpanel
 RootLayoutPanel.get().add(panel);

 this will cause nothing to be displayed.

 For more 
 information,http://code.google.com/webtoolkit/doc/latest/DevGuideUiPanels.html

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder and MVP

[jocke eriksson]

RootPanel is a singleton so that should not be the case. Could you share
some code thats shows how the view is created and attached to the RootPanel.

2010/3/24 skippy a...@2lehmans.com

 I am using the UI Binder to build a site.
 I like the MVP design pattern shown in the contacts example.

 However, when I try to put the ui binder in a view and have the
 appControler construct the presenter I get a blank page when ask for
 asWidget.

 I think this is because both the MCP entry point and the UI Binder
 creates a RootPanel.

 An thoughts on this topic?

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To post to this group, send email to google-web-tool...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder and MVP

[davidroe]

the examples of the mvp4g project seem to mix MVP and UiBinder well.

http://code.google.com/p/mvp4g/

On Mar 24, 10:57 am, skippy a...@2lehmans.com wrote:
 I am using the UI Binder to build a site.
 I like the MVP design pattern shown in the contacts example.

 However, when I try to put the ui binder in a view and have the
 appControler construct the presenter I get a blank page when ask for
 asWidget.

 I think this is because both the MCP entry point and the UI Binder
 creates a RootPanel.

 An thoughts on this topic?

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder bugs - maybe config issue on my side(?)

[Kenyth]

This doesn't work for me.

My project has the file layout below:
1. java source path: src/main/java
2. package layout:
- aaa.projectname
- aaa.projectname.modulename
-- contains modulename.gwt.xml
- aaa.projectname.modulename.client
-- contains *.java and *.ui.xml
3. war directory, as default, is war/

I use springsource STS 2.3.0 based on Eclipse 3.5.1, Google Plugin for
Eclipse 3.5 1.3.0.v201003161223, Google App Engine Java SDK 1.3.1
1.3.1.v201002101412, Google Web Toolkit SDK 2.0.3   2.0.3.v201002191036,
and m2eclilpse 0.9.8. My project uses m2eclipse (or maven2) to manage
the dependencies.

I tried all the workarounds mentioned above but in vain. However,
following Google Web application wizard provided by GEP, thus having a
standard project file layout, works perfectly. Currently in my case I
have to disable the @uifield errors/warning report in the preference
dialog.

Any GWT team guys please check on this. Thanks a lot.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder bugs - maybe config issue on my side(?)

[erha]

Have the same problem here...
But it happen suddenly, I believe there is a problem with the eclipse
plug in.

What I did to solve this problem is to copy the old .metadata folder
in the eclipse workspace folder.
And viola..., everything is working again...

Hope this info help.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder paths

[Thomas Broyer]

On Jan 26, 4:49 pm, Ice13ill andrei.fifi...@gmail.com wrote:
 i'm using uibinder to create some widgets with a CSS file and the
 corresponding .java and .ui.xml files.
 Where can i find how the uibinder accesses the required resources ?

 For example, i have my widgets in the package
 com.testapp.client.widgets : MyWidget.java and MyWidget.ui.xml
 The css file is in war/TestApp.css

 how can i access the css file with the   ui:style src=file.css /
 tag?

You can't. CssResource is a compile-time thing, and war/ is only an
output destination. Your CSS should be in your classpath, then you can
use paths relative to the package containing the *.ui.xml.

 if i separate the .java files from .ui.xml files how can i tell where
 to find the ui.xml file when i create the widget ?

Use a @UiTemplate annotation, with a relative path (not tested but I
guess it should work).

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder paths

[Andrei Cosmin Fifiiţă]

i'll try that. 10x!

On Tue, Jan 26, 2010 at 7:46 PM, Thomas Broyer t.bro...@gmail.com wrote:



 On Jan 26, 4:49 pm, Ice13ill andrei.fifi...@gmail.com wrote:
  i'm using uibinder to create some widgets with a CSS file and the
  corresponding .java and .ui.xml files.
  Where can i find how the uibinder accesses the required resources ?
 
  For example, i have my widgets in the package
  com.testapp.client.widgets : MyWidget.java and MyWidget.ui.xml
  The css file is in war/TestApp.css
 
  how can i access the css file with the   ui:style src=file.css /
  tag?

 You can't. CssResource is a compile-time thing, and war/ is only an
 output destination. Your CSS should be in your classpath, then you can
 use paths relative to the package containing the *.ui.xml.

  if i separate the .java files from .ui.xml files how can i tell where
  to find the ui.xml file when i create the widget ?

 Use a @UiTemplate annotation, with a relative path (not tested but I
 guess it should work).

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To post to this group, send email to google-web-tool...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder bugs - maybe config issue on my side(?)

[Peter]

Great,
after clean install of Eclipse, Google plugin and Java I got it
running without errors.

Thank you guys very much for help.

Regards
Peter

On Dec 22, 5:43 pm, Jason Parekh jasonpar...@gmail.com wrote:
 Peter,

 Also, would you mind downloading a fresh copy of Eclipse (with a new
 workspace) for testing purposes?  I imported your project, and the
 @UiFields are not marked as errors for me.  If a fresh Eclipse works,
 it'll help in debugging whether it's a system configuration issue or
 an Eclipse configuration issue.

 Thanks,
 jason

 On Tue, Dec 22, 2009 at 11:08 AM, Thomas Broyer t.bro...@gmail.com wrote:

  On Dec 22, 10:42 am, Peter peterlovi...@gmail.com wrote:
  Sure, thanks for helping hand. Zipped project is here:

  ns.blucina.net/lovisek/tmp/XploreU-inbox.zip

  I also deployed the project 
  here:http://ns.blucina.net/lovisek/tmp/xu/XploreU_inbox.html

  As you can see, onClick handler is never fired despite it should be
  triggered after clicking on button and bold C label.

  You're not attaching your *widget* to the document, only its
  *element*, so events are not sunk:
                 Document.get().getBody().appendChild(b.getElement());

  Use a RootPanel or RootLayoutPanel to add widgets to the page. That's
  GWT 101.

  --

  You received this message because you are subscribed to the Google Groups 
  Google Web Toolkit group.
  To post to this group, send email to google-web-tool...@googlegroups.com.
  To unsubscribe from this group, send email to 
  google-web-toolkit+unsubscr...@googlegroups.com.
  For more options, visit this group 
  athttp://groups.google.com/group/google-web-toolkit?hl=en.



--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder bugs - maybe config issue on my side(?)

[Peter]

Sure, thanks for helping hand. Zipped project is here:

ns.blucina.net/lovisek/tmp/XploreU-inbox.zip

I also deployed the project here:
http://ns.blucina.net/lovisek/tmp/xu/XploreU_inbox.html

As you can see, onClick handler is never fired despite it should be
triggered after clicking on button and bold C label.

Regards
Peter

On Dec 21, 6:59 pm, Jason Parekh jasonpar...@gmail.com wrote:
 Hi Peter,

 Would you mind zipping your project up and hosting it somewhere for me
 to download?

 I tried copying the pasted ui.xml and java file, but I was unable to
 repro the issues you're seeing in my simple project.

 Thanks,
 jason

 On Mon, Dec 21, 2009 at 11:16 AM, Peter peterlovi...@gmail.com wrote:
  Dear all,
  I'm working with UI binder and seems to me I have not completed
  successfully installation or there's something wrong in it. In code
  listed below I can see several things I could not understand:
  1. Project is complied OK and runs. However, having java code opened I
  can see error on lines starting @UiField:
  Field label1 has no corresponding field in template file InboxB.ui.xml
  Field hp has no corresponding field in template file InboxB.ui.xml

  2. Running project shows: A C C  [B]. Which is correct and second 'C'
  proves correct together-sticking of java and XML despite error in (1).

  3. However, no click event is executed ever, clicking at button.

  This is very weird situation and might mean my installation is
  completely screwed up. However, all other stuff work, my 5 previous
  GWT project, too. Did anyone hit this situation before?

  Part of this issue has been described by someone else here:
 http://groups.google.com/group/google-web-toolkit/browse_thread/threa...

  Regards
  Peter

  !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
  ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
         xmlns:g=urn:import:com.google.gwt.user.client.ui
         ui:style
                 .important {
                         font-weight: bold;
                         cursor:pointer;
                 }
         /ui:style

         g:HorizontalPanel ui:field=hp
                 g:LabelA/g:Label
                 g:Label ui:field=label1 styleName={style.important} 
  text=B2/
  g:Label
                 g:LabelC/g:Label
         /g:HorizontalPanel
  /ui:UiBinder

  package com.xploreu.inbox.client;

  import com.google.gwt.core.client.GWT;
  import com.google.gwt.event.dom.client.ClickEvent;
  import com.google.gwt.event.dom.client.ClickHandler;
  import com.google.gwt.uibinder.client.UiBinder;
  import com.google.gwt.uibinder.client.UiField;
  import com.google.gwt.uibinder.client.UiHandler;
  import com.google.gwt.user.client.Window;
  import com.google.gwt.user.client.ui.Button;
  import com.google.gwt.user.client.ui.Composite;
  import com.google.gwt.user.client.ui.HorizontalPanel;
  import com.google.gwt.user.client.ui.Label;
  import com.google.gwt.user.client.ui.Widget;

  public class InboxB extends Composite implements ClickHandler {

         private static InboxBUiBinder uiBinder = GWT.create
  (InboxBUiBinder.class);

         interface InboxBUiBinder extends UiBinderWidget, InboxB {
         }

        �...@uifield Label label1;
        �...@uifield HorizontalPanel hp;
         Button b = new Button(B);

         public InboxB(String firstName) {
                 initWidget(uiBinder.createAndBindUi(this));

                 label1.setText(C);
                 hp.add(b);

                 label1.addClickHandler(this);
                 b.addClickHandler(this);
         }

        �...@override
         public void onClick(ClickEvent event) {
                 Window.alert(Click);
         }
  }

  --

  You received this message because you are subscribed to the Google Groups 
  Google Web Toolkit group.
  To post to this group, send email to google-web-tool...@googlegroups.com.
  To unsubscribe from this group, send email to 
  google-web-toolkit+unsubscr...@googlegroups.com.
  For more options, visit this group 
  athttp://groups.google.com/group/google-web-toolkit?hl=en.



--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder bugs - maybe config issue on my side(?)

[Thomas Broyer]

On Dec 22, 10:42 am, Peter peterlovi...@gmail.com wrote:
 Sure, thanks for helping hand. Zipped project is here:

 ns.blucina.net/lovisek/tmp/XploreU-inbox.zip

 I also deployed the project 
 here:http://ns.blucina.net/lovisek/tmp/xu/XploreU_inbox.html

 As you can see, onClick handler is never fired despite it should be
 triggered after clicking on button and bold C label.

You're not attaching your *widget* to the document, only its
*element*, so events are not sunk:
Document.get().getBody().appendChild(b.getElement());

Use a RootPanel or RootLayoutPanel to add widgets to the page. That's
GWT 101.

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder bugs - maybe config issue on my side(?)

[Jason Parekh]

Peter,

Also, would you mind downloading a fresh copy of Eclipse (with a new
workspace) for testing purposes?  I imported your project, and the
@UiFields are not marked as errors for me.  If a fresh Eclipse works,
it'll help in debugging whether it's a system configuration issue or
an Eclipse configuration issue.

Thanks,
jason

On Tue, Dec 22, 2009 at 11:08 AM, Thomas Broyer t.bro...@gmail.com wrote:


 On Dec 22, 10:42 am, Peter peterlovi...@gmail.com wrote:
 Sure, thanks for helping hand. Zipped project is here:

 ns.blucina.net/lovisek/tmp/XploreU-inbox.zip

 I also deployed the project 
 here:http://ns.blucina.net/lovisek/tmp/xu/XploreU_inbox.html

 As you can see, onClick handler is never fired despite it should be
 triggered after clicking on button and bold C label.

 You're not attaching your *widget* to the document, only its
 *element*, so events are not sunk:
                Document.get().getBody().appendChild(b.getElement());

 Use a RootPanel or RootLayoutPanel to add widgets to the page. That's
 GWT 101.

 --

 You received this message because you are subscribed to the Google Groups 
 Google Web Toolkit group.
 To post to this group, send email to google-web-tool...@googlegroups.com.
 To unsubscribe from this group, send email to 
 google-web-toolkit+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/google-web-toolkit?hl=en.




--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[David Durham]

On Sat, Dec 12, 2009 at 2:06 PM, philippe vonck...@yahoo.fr wrote:
 Using annotations to define the presentation is a bad practice, as
 being able to define the size of components in Java. The best way to
 separate the presentation logic is to give a class name to an element
 and define its presentation in a separate CSS file. See csszengarden
 as reference.

In my case, annotations describe presentation.  The downside of this
is that presentation options have to be well defined beforehand and
implemented somehow, with UIBinder for instance.

One case of where the annotations approach that I've taken does well
IMO, is in describing forms.  Designing a GWT feature or function
within an application that captures user input, often starts by
defining an object to be used for RPC.  So for instance, I have a
registration form that will pass instances of the following class.

class Registration {

  String firstname;
  String lastname;
  String email;
  String username;
  String password;

  ...
}

Let's say that I know I'm storing these in a database so I write all
the persistence code and unit tests and all of that works great.  Now,
I want the actual form.  The approach I've taken is to say, I already
have a portion of the info I need to describe this form, the model,
but I need to add a few hints, this is the approach, I believe, that
Rails and Django take with their models, and results in a very fast
turnaround time for something like an app administration.  So here are
the changes I need to make in order to get a form rendered.

@Form(..)
class Registration {

   @CharField(..)
   String firstname

   @CharField(..)
   String lastname;

   @EmailField(..)
   String email;

   @CharField(..)
   String username;

   @PasswordField(..)
   String password;

..

}

And with a few more lines of client-side GWT code, I have a form
rendered with data-binding.  The data-binding portion means that as a
user enters values into the form, a Registration object in the
background is upgraded with those values.

You can see this working in the demo here:
http://gxtforms.appspot.com/#simpleform

This is just another approach which is similar to other approaches
(django and Rails admin and templating), that I feel adds some value
to GWT.  It does not replace something like UIBinder for complex
layouts.

-Dave

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[philippe]

Using annotations to define the presentation is a bad practice, as
being able to define the size of components in Java. The best way to
separate the presentation logic is to give a class name to an element
and define its presentation in a separate CSS file. See csszengarden
as reference.

Currently on the project I lead in GWT 1.7.0, I use a simple pattern
to separate presentation Java code from logical Java code.

I don't think UiBinder be adapted to most projects. UiBinder is
probably useful in some specific cases, but not in most cases. May be
useful for managing complex components. I think in most cases, coded
as Swing is more appropriate.

I think it would be interesting to propose a reference pattern for
developers to help them get a code of good quality.


On 11 déc, 20:06, David Durham david.durham...@gmail.com wrote:
 On Fri, Dec 11, 2009 at 6:23 AM, Stefan Bachert stefanbach...@yahoo.de 
 wrote:

  The advantage of declarative programming could be reached in Java in a
  much better way.
  Look at the following code, it is pure Java and much more declarative
  then UiBinder.
  It has very less code and is in the end much more flexible since code
  could add any rule you like.

  new DialogCreator()
         .add(localization.account(), account, 100, DialogCreator.lines
  (1)).newLine()
         .add(localization.password(), password, 100, DialogCreator.lines
  (1)).newLine()
         .add(localization.session(), session, 100, DialogCreator.lines
  (1)).newLine()
         .button(ok)
         .button(cancel)

  If you don't like parameters per position, ok, change it to:

  new DialogCreator()
         .add(new DialogItem()
                 .label(localization.account())
                 .item(account)
                 .width(100)
                 .height(DialogCreator.lines(1))
         )
  .newLine().

  What could be done in UiBuilder better/more readable than in java?
  What are your thoughts?

  Stefan Bachert

  PS: It is like Spring. IoC could be done in Java itself. Why to deal
  with this human unreadable XMLs?
   a java compiler is much more flexible and exact as a validation of a
  xml (try the check a mispelling of an java class!)

 Another approach is annotations.  You can see an approach like this in
 my little forms 
 project,http://gxtforms.appspot.com/,http://gxtforms.googlecode.com/.  Be 
 sure to check out the source tabs
 at the bottom.   I could see something like:

 @Style(width=100, height ...)
 class MyDialog() {

 }

 or

 class MyPanel() {

   @Style(width=100, height ...)
   Dialog myDialog = new Dialog()

 Just kind of thinking out loud here.

 -Dave

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[mP]

In all technologies building the equivalent using the approapriate
native language is a pain, it takes a lot more lines to achieve the
same thing. Conciseness is always a good thing. Any complex layout
involving more than a few panels and widgets becomes hard to visualize
when one stares at the code, but is infinitely more easy when one
looks at the UIBinder equivalent. With the former one needs to execute
the code in your mind just to try and imagine the result, because
initially one has no idea where each widget and panel really is.

Using XML to declare UIs is quite popular these days:
* XAML is the new way Microsoft has introduced for defining
Silverlight and WPF applications.
* Apple pioneered a similar approach a long time ago, where developers
use a tool call Interface Builder to achieve similar objectives as
uibinder. (the technology name escapes me).
* Browsers. Technically not XML nevertheless it would be really hard
if all pages were constructed from Dom manipulations without any first
class support for HTML from browsers.
All of these major vendors and systems would not have copied this idea
if it had no merit.

On Dec 13, 7:06 am, philippe vonck...@yahoo.fr wrote:
 Using annotations to define the presentation is a bad practice, as
 being able to define the size of components in Java. The best way to
 separate the presentation logic is to give a class name to an element
 and define its presentation in a separate CSS file. See csszengarden
 as reference.

 Currently on the project I lead in GWT 1.7.0, I use a simple pattern
 to separate presentation Java code from logical Java code.

 I don't think UiBinder be adapted to most projects. UiBinder is
 probably useful in some specific cases, but not in most cases. May be
 useful for managing complex components. I think in most cases, coded
 as Swing is more appropriate.

 I think it would be interesting to propose a reference pattern for
 developers to help them get a code of good quality.

 On 11 déc, 20:06, David Durham david.durham...@gmail.com wrote:

  On Fri, Dec 11, 2009 at 6:23 AM, Stefan Bachert stefanbach...@yahoo.de 
  wrote:

   The advantage of declarative programming could be reached in Java in a
   much better way.
   Look at the following code, it is pure Java and much more declarative
   then UiBinder.
   It has very less code and is in the end much more flexible since code
   could add any rule you like.

   new DialogCreator()
          .add(localization.account(), account, 100, DialogCreator.lines
   (1)).newLine()
          .add(localization.password(), password, 100, DialogCreator.lines
   (1)).newLine()
          .add(localization.session(), session, 100, DialogCreator.lines
   (1)).newLine()
          .button(ok)
          .button(cancel)

   If you don't like parameters per position, ok, change it to:

   new DialogCreator()
          .add(new DialogItem()
                  .label(localization.account())
                  .item(account)
                  .width(100)
                  .height(DialogCreator.lines(1))
          )
   .newLine().

   What could be done in UiBuilder better/more readable than in java?
   What are your thoughts?

   Stefan Bachert

   PS: It is like Spring. IoC could be done in Java itself. Why to deal
   with this human unreadable XMLs?
    a java compiler is much more flexible and exact as a validation of a
   xml (try the check a mispelling of an java class!)

  Another approach is annotations.  You can see an approach like this in
  my little forms 
  project,http://gxtforms.appspot.com/,http://gxtforms.googlecode.com/.  Be 
  sure to check out the source tabs
  at the bottom.   I could see something like:

  @Style(width=100, height ...)
  class MyDialog() {

  }

  or

  class MyPanel() {

    @Style(width=100, height ...)
    Dialog myDialog = new Dialog()

  Just kind of thinking out loud here.

  -Dave

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[Robert Zaleski]

After reading the posts, I just had to chime in.  I would like to
start with UIBinder wasn't on my list of reasons for making our team
jump from 1.7 to 2.0 early, but when I finally had a place to use
UIBinder, I became enamoured with it.

The design for any website boils down to HTML/CSS.  If that is how
your page is laid out, then keeping all of the view related stuff in
one place as possible is the best way to go.  That's what UIBinder
lets you do, all of your HTML and CSS in some XML files, which is the
best way to have your layout.  You have the ability to do any web
layout you want there.  The real bang comes with using MVP.  You can
hide all of your touch points to the view behind interfaces and
bundled in a view interface.  Then UIBinder can generate the view
implementation and pop it in.  Plus you can write your own widgets
that you can pop in to the UIBinder and have extra methods if you need
them.

I can understand wanting to do all of the view coding in Java ala
Swing, and depending on the team you have, and if your design specs
allow it, that would be fine.  I don't see any reason GWT doesn't
allow for that with only GWT JAVA layout code and some optional CSS.
But as soon as you're dropping HTML in your JAVA code, or CSS alone
for styling won't do, I think UIBinder becomes a must.

The one thing that should be avoided is 30% of the layout in HTML, 40%
in CSS, and 30% in Java.  If that's what you end up with to get your
view to look right, then you'd be better off having it 80% in UIBinder
with 20% in some globaly shared CSS resources.  And that is definitely
something UIBinder can give you.

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[Arthur Kalmenson]

I think you just have to try it and see. We're doing that here to
determine if UiBinder is a better way of building user interfaces, or
if we prefer building UI in a Swing like fashion. There are arguments
both ways, but it comes down to taste and preference. UiBinder allows
for web designers to be more involved in the creation of GWT
applications and in many organizations that's a huge benefit. Another
benefit of UiBinder, is that you can use standard HTML elements inside
an HTMLPanel to get higher performance as per Kelly Norton's Google
I/O talk. Now you can do it in a syntax highlighted, code completion
way instead of a Java strings.

--
Arthur Kalmenson



On Fri, Dec 11, 2009 at 7:23 AM, Stefan Bachert stefanbach...@yahoo.de wrote:
 Classical web development urges me to have a multiple personalities.
 That is an disease
 I have to deals with
 - HTML
 - CSS
 - JavaScript
 - Server-Side calls via AjAx
 - Server side implementation in Java or other language
 - and references from one to the other

 Thatfor GWT was good to reduce the number of languages.
 Everything is Java, CSS could be considered as a designer job making
 an other scheme.
 No application (=behaviour,functionality) developer should need to
 create a CSS

 Now UiBinder comes up with a further XML, and mixing up CSS, HTML and
 GWT code.
 Somehow I feel be back at the beginning of webdevelopment, and I feel
 ill ;-).

 The advantage of declarative programming could be reached in Java in a
 much better way.
 Look at the following code, it is pure Java and much more declarative
 then UiBinder.
 It has very less code and is in the end much more flexible since code
 could add any rule you like.

 new DialogCreator()
        .add(localization.account(), account, 100, DialogCreator.lines
 (1)).newLine()
        .add(localization.password(), password, 100, DialogCreator.lines
 (1)).newLine()
        .add(localization.session(), session, 100, DialogCreator.lines
 (1)).newLine()
        .button(ok)
        .button(cancel)

 If you don't like parameters per position, ok, change it to:

 new DialogCreator()
        .add(new DialogItem()
                .label(localization.account())
                .item(account)
                .width(100)
                .height(DialogCreator.lines(1))
        )
 .newLine().

 What could be done in UiBuilder better/more readable than in java?
 What are your thoughts?

 Stefan Bachert

 PS: It is like Spring. IoC could be done in Java itself. Why to deal
 with this human unreadable XMLs?
  a java compiler is much more flexible and exact as a validation of a
 xml (try the check a mispelling of an java class!)


 PS2: Just to avoid the impression I am just negative. GWT is a great
 thing, but surely improvable

 --

 You received this message because you are subscribed to the Google Groups 
 Google Web Toolkit group.
 To post to this group, send email to google-web-tool...@googlegroups.com.
 To unsubscribe from this group, send email to 
 google-web-toolkit+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/google-web-toolkit?hl=en.




--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[John Ivens]

How about a Matisse-like interface that allows you to create the XML by
dragging graphics around, and linking them to code in the .java file?
That's what I want.

On Fri, Dec 11, 2009 at 8:22 AM, Arthur Kalmenson arthur.k...@gmail.comwrote:

 I think you just have to try it and see. We're doing that here to
 determine if UiBinder is a better way of building user interfaces, or
 if we prefer building UI in a Swing like fashion. There are arguments
 both ways, but it comes down to taste and preference. UiBinder allows
 for web designers to be more involved in the creation of GWT
 applications and in many organizations that's a huge benefit. Another
 benefit of UiBinder, is that you can use standard HTML elements inside
 an HTMLPanel to get higher performance as per Kelly Norton's Google
 I/O talk. Now you can do it in a syntax highlighted, code completion
 way instead of a Java strings.

 --
 Arthur Kalmenson



 On Fri, Dec 11, 2009 at 7:23 AM, Stefan Bachert stefanbach...@yahoo.de
 wrote:
  Classical web development urges me to have a multiple personalities.
  That is an disease
  I have to deals with
  - HTML
  - CSS
  - JavaScript
  - Server-Side calls via AjAx
  - Server side implementation in Java or other language
  - and references from one to the other
 
  Thatfor GWT was good to reduce the number of languages.
  Everything is Java, CSS could be considered as a designer job making
  an other scheme.
  No application (=behaviour,functionality) developer should need to
  create a CSS
 
  Now UiBinder comes up with a further XML, and mixing up CSS, HTML and
  GWT code.
  Somehow I feel be back at the beginning of webdevelopment, and I feel
  ill ;-).
 
  The advantage of declarative programming could be reached in Java in a
  much better way.
  Look at the following code, it is pure Java and much more declarative
  then UiBinder.
  It has very less code and is in the end much more flexible since code
  could add any rule you like.
 
  new DialogCreator()
 .add(localization.account(), account, 100, DialogCreator.lines
  (1)).newLine()
 .add(localization.password(), password, 100, DialogCreator.lines
  (1)).newLine()
 .add(localization.session(), session, 100, DialogCreator.lines
  (1)).newLine()
 .button(ok)
 .button(cancel)
 
  If you don't like parameters per position, ok, change it to:
 
  new DialogCreator()
 .add(new DialogItem()
 .label(localization.account())
 .item(account)
 .width(100)
 .height(DialogCreator.lines(1))
 )
  .newLine().
 
  What could be done in UiBuilder better/more readable than in java?
  What are your thoughts?
 
  Stefan Bachert
 
  PS: It is like Spring. IoC could be done in Java itself. Why to deal
  with this human unreadable XMLs?
   a java compiler is much more flexible and exact as a validation of a
  xml (try the check a mispelling of an java class!)
 
 
  PS2: Just to avoid the impression I am just negative. GWT is a great
  thing, but surely improvable
 
  --
 
  You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
  To post to this group, send email to google-web-toolkit@googlegroups.com
 .
  To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
 .
  For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.
 
 
 

 --

 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To post to this group, send email to google-web-tool...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.




--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[Nicanor Cristian]

UI Binder is the step before that. On top of UI Binder it's easier to
write a WYSIWYG GUI editor, than on top of plain java. Also it's very
easy to mantain the MVC structure.

John Ivens wrote:
 How about a Matisse-like interface that allows you to create the XML
 by dragging graphics around, and linking them to code in the .java
 file?  That's what I want.



--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[Sekhar]

UiBinder is actually quite similar to the approach Flex takes
(splitting into MXML and ActionScript). It seems like overkill
initially, but really pays off for larger projects (separating the
design/logic and adding flexibility).

On Dec 11, 7:43 am, Nicanor Cristian nicanor.bab...@gmail.com wrote:
 UI Binder is the step before that. On top of UI Binder it's easier to
 write a WYSIWYG GUI editor, than on top of plain java. Also it's very
 easy to mantain the MVC structure.



 John Ivens wrote:
  How about a Matisse-like interface that allows you to create the XML
  by dragging graphics around, and linking them to code in the .java
  file?  That's what I want.

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[Jonas Huckestein]

Its interesting that you mentioned how multiple personalitites
having to deal with css, html, java etc are harmful to the development
process. I think that while it does make sense to develop all program
logic in one language (particularly server and client code), neither
the GWT 1.7 style UI Java nor declarative java are really suited for
web development. In our team we have a designer who builds mockups in
Dreamweaver and to us it was a huge relief to finally be able to
simply copy and paste from his templates into our program. :D

And as has already been mentioned building an actual GUI editor on
UiBinder is not a huge problem (perhaps we can even integrate it in
Dreamweaver, dear Google?). It is much more dificult to do that on top
of declarative Java :)

Cheers, Jonas

On Dec 11, 1:23 pm, Stefan Bachert stefanbach...@yahoo.de wrote:
 Classical web development urges me to have a multiple personalities.
 That is an disease
 I have to deals with
 - HTML
 - CSS
 - JavaScript
 - Server-Side calls via AjAx
 - Server side implementation in Java or other language
 - and references from one to the other

 Thatfor GWT was good to reduce the number of languages.
 Everything is Java, CSS could be considered as a designer job making
 an other scheme.
 No application (=behaviour,functionality) developer should need to
 create a CSS

 Now UiBinder comes up with a further XML, and mixing up CSS, HTML and
 GWT code.
 Somehow I feel be back at the beginning of webdevelopment, and I feel
 ill ;-).

 The advantage of declarative programming could be reached in Java in a
 much better way.
 Look at the following code, it is pure Java and much more declarative
 then UiBinder.
 It has very less code and is in the end much more flexible since code
 could add any rule you like.

 new DialogCreator()
         .add(localization.account(), account, 100, DialogCreator.lines
 (1)).newLine()
         .add(localization.password(), password, 100, DialogCreator.lines
 (1)).newLine()
         .add(localization.session(), session, 100, DialogCreator.lines
 (1)).newLine()
         .button(ok)
         .button(cancel)

 If you don't like parameters per position, ok, change it to:

 new DialogCreator()
         .add(new DialogItem()
                 .label(localization.account())
                 .item(account)
                 .width(100)
                 .height(DialogCreator.lines(1))
         )
 .newLine().

 What could be done in UiBuilder better/more readable than in java?
 What are your thoughts?

 Stefan Bachert

 PS: It is like Spring. IoC could be done in Java itself. Why to deal
 with this human unreadable XMLs?
   a java compiler is much more flexible and exact as a validation of a
 xml (try the check a mispelling of an java class!)

 PS2: Just to avoid the impression I am just negative. GWT is a great
 thing, but surely improvable

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[Yozons Support on Gmail]

A GUI builder would be a huge advance over UiBinder alone, by my vote!  But
then again, a GUI builder would be best if there were a big widget library
so there would be more to use and layout.

SmartGWT has some nice widgets, but their GUI builder doesn't do GWT, just
JS.

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder, really a good approach?

[David Durham]

On Fri, Dec 11, 2009 at 6:23 AM, Stefan Bachert stefanbach...@yahoo.de wrote:

 The advantage of declarative programming could be reached in Java in a
 much better way.
 Look at the following code, it is pure Java and much more declarative
 then UiBinder.
 It has very less code and is in the end much more flexible since code
 could add any rule you like.

 new DialogCreator()
        .add(localization.account(), account, 100, DialogCreator.lines
 (1)).newLine()
        .add(localization.password(), password, 100, DialogCreator.lines
 (1)).newLine()
        .add(localization.session(), session, 100, DialogCreator.lines
 (1)).newLine()
        .button(ok)
        .button(cancel)

 If you don't like parameters per position, ok, change it to:

 new DialogCreator()
        .add(new DialogItem()
                .label(localization.account())
                .item(account)
                .width(100)
                .height(DialogCreator.lines(1))
        )
 .newLine().

 What could be done in UiBuilder better/more readable than in java?
 What are your thoughts?

 Stefan Bachert

 PS: It is like Spring. IoC could be done in Java itself. Why to deal
 with this human unreadable XMLs?
  a java compiler is much more flexible and exact as a validation of a
 xml (try the check a mispelling of an java class!)

Another approach is annotations.  You can see an approach like this in
my little forms project, http://gxtforms.appspot.com/,
http://gxtforms.googlecode.com/.  Be sure to check out the source tabs
at the bottom.   I could see something like:

@Style(width=100, height ...)
class MyDialog() {
}

or

class MyPanel() {

  @Style(width=100, height ...)
  Dialog myDialog = new Dialog()

Just kind of thinking out loud here.

-Dave

--

You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: UI Binder

[Arthur Kalmenson]

Johan,

The reason the GWT team has not release the UI Binder stuff (AFAIK) is
because UI binder is being donated by another project inside Google.
They need to clean up before releasing it. I'm personally thankful
that the internal project decided to donate their code and I think
everyone needs to be patient about it.

--
Arthur Kalmenson



On Mon, Jan 12, 2009 at 3:53 AM, Johan Rydberg
johan.rydb...@edgeware.tv wrote:

 Zakaluka skrev:

 The UI Binder is currently listed under the Post-1.6 timeframe.
 Seeing as how GWT 1.5.3 is the latest version out there and 1.6 will
 come out in the next 3 months, it'll probably be quite a while before
 we see UI Binder out in a stable form.

 It would had been better if the GWT team hadn't said anything about
 their internal work.  Then maybe something had popped up from the
 community.  Now things are just dead in the sand, waiting for the holy
 grail.

 What happened to release often, release early?

 Just put it in a branch.


 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: UI Binder

[Johan Rydberg]

Zakaluka skrev:

 The UI Binder is currently listed under the Post-1.6 timeframe.
 Seeing as how GWT 1.5.3 is the latest version out there and 1.6 will
 come out in the next 3 months, it'll probably be quite a while before
 we see UI Binder out in a stable form.

It would had been better if the GWT team hadn't said anything about
their internal work.  Then maybe something had popped up from the
community.  Now things are just dead in the sand, waiting for the holy
grail.

What happened to release often, release early?

Just put it in a branch.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: UI Binder

[Zakaluka]

Hi,

The UI Binder is currently listed under the Post-1.6 timeframe.
Seeing as how GWT 1.5.3 is the latest version out there and 1.6 will
come out in the next 3 months, it'll probably be quite a while before
we see UI Binder out in a stable form.

Regards,

z.

ruslanv wrote:
 Hi guys. According to tis blog entry

 http://googlewebtoolkit.blogspot.com/2008/12/whats-ahead-for-google-web-toolkit_10.html

 long-awaited UI Binder extension will be released soon. But the main
 question is WHEN ? Originally October of 2008 was stated as planned
 release date, then after NYE holidays and finally last thing I heard
 was will be released this week. Considering that UI Binder is
 heavily used (according to member of GWT team) inside Google is there
 any real estimate when it's going to be published ? Beta version is
 fine, it's enough to try it out.

 I'm also curious where it will be published - in GWT incubator project
 or as new release of GWT ?

 Thanks.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: UI Binder

[julia]

You might be interested in 
http://code.google.com/p/google-web-toolkit-incubator/wiki/UiBinder.

Julia

ruslanv wrote:
 Hi guys. According to tis blog entry

 http://googlewebtoolkit.blogspot.com/2008/12/whats-ahead-for-google-web-toolkit_10.html

 long-awaited UI Binder extension will be released soon. But the main
 question is WHEN ? Originally October of 2008 was stated as planned
 release date, then after NYE holidays and finally last thing I heard
 was will be released this week. Considering that UI Binder is
 heavily used (according to member of GWT team) inside Google is there
 any real estimate when it's going to be published ? Beta version is
 fine, it's enough to try it out.

 I'm also curious where it will be published - in GWT incubator project
 or as new release of GWT ?

 Thanks.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---