Hi Bruce,
The goals you stated have been long sought by developers everywhere
(including me) and I hope you guys achieve it. In fact our last-gen
web tool/framework choice was based on this principle of roles
separation - but in all my years I have just never seen this work
(yet) - I am
Ray,
I take it back, it doesn't work. Not for me anyway:
gwt:UiBinder ...
xmlns:res='urn:with:my.package.Bundle'
...
gwt:Button res:addStyleNames=formCss.error /
Results in
[ERROR] In gwt:Button res:addStyleNames='formCss.error', class Button has
no appropriate setAddStyleNames()
I think you've found a bug with addStyleNames, which gets special handling.
Do you mind filing an issue?
The new syntax hasn't been committed yet, it's in review. Although now that
I think about it, it just might accidentally fix this problem. Which is
nice.
On Fri, Aug 28, 2009 at 9:34 AM, Amir
Accidental bug fixes are always welcome!
Issue 3994http://code.google.com/p/google-web-toolkit/issues/detail?id=3994
*
*
http://code.google.com/p/google-web-toolkit/issues/detail?id=3994*- Amir
*
On Fri, Aug 28, 2009 at 7:07 AM, Ray Ryan rj...@google.com wrote:
I think you've found a bug with
Finally, GWT is all about finding coding patterns with which tools (IDEs in
particular) are useful. UiBinder's XHTML syntax makes it easier to write
good tools because it isn't as expressive as full-blown code: more
restrictive language means more ability to analyze it statically, which is
One of the things I have noticed with the UIBinder is that you can't
set the id on the fields - which is pretty important for css styling
and testing. I seem to have to set them in code.
g:TextBox ui:field=tbWhatever id=some-name/
causes it to fail to compile. I know id is an attribute of
The biggest problem here is that ids have to be unique within a document,
and UiBinder has no way of enforcing this.
If you want to use it for styling, you're probably better off with
CssResource (we're working on updating the samples to reflect what we
believe to be the best pattern for doing
And you can set the debug id via ui.xml:
gwt:Label debugId='joe'Hiya, pal./gwt:Label
If you're not going to use CssResource, there is nothing you can do with an
id selector that you can't do with a class selector. I really discourage the
use of id selectors, they're brittle.
rjrjr
On Wed, Aug
On Wed, Aug 26, 2009 at 5:21 AM, Konstantin.Scheglov
konstantin.scheg...@gmail.com wrote:
Finally, GWT is all about finding coding patterns with which tools (IDEs
in
particular) are useful. UiBinder's XHTML syntax makes it easier to write
good tools because it isn't as expressive as
While we're on the topic, it doesn't seem that the BundleAttributeParser
catches these special attributes. Specifically,
gwt:Button res:addStyleNames=css.myCssClass /
doesn't seem to work.
- Amir
On Wed, Aug 26, 2009 at 8:56 AM, Ray Ryan rj...@google.com wrote:
And you can set the debug id
Will Google Plugin provide text editor for *.ui.xml files?
Is there any place where I can ask to make this editor embeddable
into MultiPageEditorPart?
This would allow us to compose corresponding Java, ui.xml and
WYSIWYG Design pages into single editor.
For example Eclipse Java
It works. What does your xmlns line look like?
BTW, this is about to change. I'm implementing the expression language stuff
mentioned in the wiki entry (
http://code.google.com/p/google-web-toolkit-incubator/wiki/UiBinder). So
that line will become something like:
gwt:Button
Hmm, I don't have it handy but it's the name xmlns I use for all other
resource injection, and those work fine. I'll give it another shot later
today. I'm sure you're right and I just messed something up.
+1 for the expression language. Will res be required to be a subclass of one
of the resource
On Wed, Aug 26, 2009 at 5:23 PM, Amir Kashani amirkash...@gmail.com wrote:
Hmm, I don't have it handy but it's the name xmlns I use for all other
resource injection, and those work fine. I'll give it another shot later
today. I'm sure you're right and I just messed something up.
+1 for the
Oh, carry on then. Good show!
- Amir
On Wed, Aug 26, 2009 at 3:13 PM, Ray Ryan rj...@google.com wrote:
On Wed, Aug 26, 2009 at 5:23 PM, Amir Kashani amirkash...@gmail.comwrote:
Hmm, I don't have it handy but it's the name xmlns I use for all other
resource injection, and those work fine.
Hi Sony,
I just wanted to clarify that UiBinder is based on XHTML not merely to make
coding more succinct vs. Java code. I agree that we could in theory provide
fluent APIs that could make Java imperative UI code much more succinct than
it is now. But there are three other big motivations for
Extras...
Are there any plans to build a ui tool (maybe in swing) so designers
can drag n drop available widgets and have the view instantly updated?
Other kool features might include save the file etc.
Some of the extra features in interface builder.
Thoughts...?
On 26/08/2009, at 2:14 AM,
No plans to do drag-n-drop or anything wysiwyg. We'll probably
continue to focus on the basics.
On Tuesday, August 25, 2009, Miroslav Pokorny
miroslav.poko...@gmail.com wrote:
Extras...
Are there any plans to build a ui tool (maybe in swing) so designers can drag
n drop available widgets and
One point I have tried injecting into the GWT community is the
importance of fluent APIs. GWT's Java API is currently quite
cumbersome for layouts and it seems folks immediately jumped to the
conclusion that Java doesn't work and have gone the route of using XML
for layouts. I am not against
Hey Gary,
I can't speak more generally about GWT, but can give you some info on the
plugin.
We'll need more than just an XML schema (though we'll still have a simple
schema defining the legal top-level elements, for example). The
autocomplete choices will be too dynamic to be included in a
Sounds great.
Is there enough information in the classes for new GEP functionality
or is extra information in going to need to be provided. Eg. the
capabilities of the com.google.gwt.uibinder.parsers classes.
There might be an opportunity to solve the custom widget parsing issue
and the GEP auto
21 matches
Mail list logo
