Well, three things:
- There's an impedance mismatch between UiBinder (using XML with
namespaces) and HTML. UiBinder has not been designed to output "namespaced
HTML", and actually there's no such thing as "namespaced HTML" (SVG-in-HTML
hardcodes the "xlink:href" name to translate
On Thursday, February 12, 2015 at 11:25:51 AM UTC+1, Thomas Broyer wrote:
On Thursday, February 12, 2015 at 2:35:36 AM UTC+1, Ali Akhtar wrote:
I have a maven layout, and the ui.xml file is in src/main/resources, in
the same package as the Java class. So I don't think that's the case here.
On Thursday, February 12, 2015 at 2:35:36 AM UTC+1, Ali Akhtar wrote:
I have a maven layout, and the ui.xml file is in src/main/resources, in
the same package as the Java class. So I don't think that's the case here.
Also the file does get picked up, it just requires an SDM restart to pick
Thomas,
As usual, you're right. I was using the maven plugin, and the resources
weren't being updated.
For the moment, I've just created a new run configuration in intellij for
running process-resources , and when I get this error, I just run that
config once, and it fixes the problem.
Still,
In same cases, you can accidentally include of ui.xml files in your build
that will make your regular compile work but SDM will not pick up the
changes. This happens if the ui.xml file is in the classpath but not
included as a resource in the gwt.xml file. I think if we notice that
during
I have a maven layout, and the ui.xml file is in src/main/resources, in the
same package as the Java class. So I don't think that's the case here.
Also the file does get picked up, it just requires an SDM restart to pick
up some of the changes.
On Thu, Feb 12, 2015 at 3:52 AM, 'Goktug Gokdogan'
Update: Seems like this issue applies to all changes made to ui.xml files.
If I have an existing foo.ui.xml file, and I made a change to it, such as
adding the text 'foo' anywhere inside a HtmlPanel, reloading doesn't pick
up the change. A full sdm restart is required.
--
You received this
I'm using the snapshot build, so it might be a recent issue. I'm not sure
if I could've done anything in my project to cause this, I just have a
regular ui binder file / class.
On Wed, Feb 11, 2015 at 4:50 PM, Jens jens.nehlme...@gmail.com wrote:
We are currently using a GWT trunk build from 5.
We are currently using a GWT trunk build from 5. Jan 2015 and don't see
this issue. So either a recent commit causes that behavior or your project
setup is broken.
-- J.
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from
Thanks for your reply Thomas. Preparing a bug report for GPE. Bit puzzled
though cause according to
7230http://code.google.com/p/google-web-toolkit/issues/detail?id=7230
absolute
paths should start with a '/', whereas in this case it's
'com/google/gwt/uibinder/test/client/Menu.css' without
On Saturday, January 19, 2013 8:57:59 PM UTC+1, n.gia...@gmail.com wrote:
Thanks for your reply Thomas. Preparing a bug report for GPE. Bit puzzled
though cause according to
7230http://code.google.com/p/google-web-toolkit/issues/detail?id=7230
absolute
paths should start with a '/',
I believe this is a bug in the Google Plugin for Eclipse; you can simply
ignore it (and/or report it in the GPE issue tracker).
Absolute paths weren't accepted in ui:style until recently in GWT: see
http://code.google.com/p/google-web-toolkit/issues/detail?id=7230
On Friday, January 18, 2013
As soon as we have done that, we can't make changes to UiBinderWriter and
all the other classes the parsers actually talk to, nor can we make sweeping
changes to the code they generate.
If the problem is retrofitting widgets you don't own, would a non-annotation
alternative to UiChild get the job
On Fri, Jun 10, 2011 at 7:22 PM, Ray Ryan rj...@google.com wrote:
As soon as we have done that, we can't make changes to UiBinderWriter and
all the other classes the parsers actually talk to, nor can we make sweeping
changes to the code they generate.
If the problem is retrofitting widgets you
Exactly. And I was thinking we could introduce something like BuildsWidgetW
extends IsWidget extends IsWidget. UiBinder could learn to honor the
setters and such of the underlying widget as well as the BuildsWidget.
On Fri, Jun 10, 2011 at 10:41 AM, Thomas Broyer t.bro...@gmail.com wrote:
On
[+cc google-web-toolkit-contributors]
I don't know why I've been added as a reviewer here, but here are a few
comments. (beware, I'm not in the GWT Team)
http://gwt-code-reviews.appspot.com/1454804/diff/7002/user/src/com/google/gwt/uibinder/elementparsers/AbsolutePanelParser.java
File
Justin, I really appreciate the contribution, and this is a nice
mechanism. But the reason we haven't done something like this already is
that we don't want to lock down the api to the parsers.
In fact at the moment it's in a lot of flux as we add features to
support Cell authors, and as we try
Very nice, as always.
http://gwt-code-reviews.appspot.com/1233803/diff/1/3
File user/src/com/google/gwt/uibinder/elementparsers/TreeItemParser.java
(right):
http://gwt-code-reviews.appspot.com/1233803/diff/1/3#newcode39
user/src/com/google/gwt/uibinder/elementparsers/TreeItemParser.java:39:
Taking this a bit further, if we're going to be playing with interfaces we
might as well go the whole nine yards:
interface IsTreeItem {
TreeItem asTreeItem();
}
interface HasTreeItems {
void addItem(IsTreeItem);
void addItem(Widget);
void addItem(SafeHtml);
/* No addItem(String),
On Wed, Jan 5, 2011 at 12:47 PM, Ray Ryan rj...@google.com wrote:
Taking this a bit further, if we're going to be playing with interfaces we
might as well go the whole nine yards:
interface IsTreeItem {
TreeItem asTreeItem();
}
interface HasTreeItems {
void addItem(IsTreeItem);
There is an existing overload that accepts a string and interprets it as
HTML, so that's not an option. And asking Konstantin to add a new
addItemText(String) method seems too far outside the scope of this patch.
On Wed, Jan 5, 2011 at 10:02 AM, John Tamplin j...@google.com wrote:
On Wed, Jan
On Wed, Jan 5, 2011 at 1:09 PM, Ray Ryan rj...@google.com wrote:
There is an existing overload that accepts a string and interprets it as
HTML, so that's not an option. And asking Konstantin to add a new
addItemText(String) method seems too far outside the scope of this patch.
Ok, we can
http://gwt-code-reviews.appspot.com/1077802/diff/1/3
File user/src/com/google/gwt/uibinder/rebind/DesignTimeUtilsImpl.java
(right):
http://gwt-code-reviews.appspot.com/1077802/diff/1/3#newcode52
user/src/com/google/gwt/uibinder/rebind/DesignTimeUtilsImpl.java:52:
w.write( void handle(String
We shouldn't get hung up on the fact that LengthAttributeParser is misnamed
(ScalarAttributeParser?). Negative support sounds like the right thing to
do. Element parsers that are concerned about negative values could do their
own check for that, although it could be tricky to do correctly.
LGTM
Nice! Thanks.
http://gwt-code-reviews.appspot.com/1094801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
One nit, one point of curiosity. I can submit this as soon as you're
ready with a follow up.
http://gwt-code-reviews.appspot.com/1077802/diff/1/3
File user/src/com/google/gwt/uibinder/rebind/DesignTimeUtilsImpl.java
(right):
http://gwt-code-reviews.appspot.com/1077802/diff/1/3#newcode52
LGTM
I'll submit it this weekend
On 2010/09/07 19:02:03, Konstantin.Scheglov wrote:
http://gwt-code-reviews.appspot.com/834802/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
r8814
http://gwt-code-reviews.appspot.com/834802/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
On Sep 9, 1:45 pm, Konstantin.Scheglov
konstantin.scheg...@gmail.com wrote:
If anyone wants to submit a patch to make it possible to subclass
UiBinderGenerator and tweak its parsers that way, s.t. you can provide an
alternative replace-with rule for your custom subclass, I'd be in favor of
It's not about the lack of a plugin mechanism, it's about discomfort with an
api that requires people to emit lines of java too much, and lack of time to
clean it up.
On Thu, Sep 9, 2010 at 9:22 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Sep 9, 1:45 pm, Konstantin.Scheglov
The 2.1 release branch will be cut from trunk. Trunk does not include a
public api to add new parsers to UiBinder.
If anyone wants to submit a patch to make it possible to subclass
UiBinderGenerator and tweak its parsers that way, s.t. you can provide an
alternative replace-with rule for your
I don't see this patch in SVN yet.
Was it committed?
http://gwt-code-reviews.appspot.com/792801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Thanks! Looks great, just a couple of nits.
http://gwt-code-reviews.appspot.com/715802/diff/1/3
File
user/test/com/google/gwt/uibinder/elementparsers/AbsolutePanelParserTest.java
(right):
http://gwt-code-reviews.appspot.com/715802/diff/1/3#newcode37
1. Should I remove groups only from this AbsolutePanelParser test or
from DesignTimeUtilsTest too?
2. I agree to use sorting methods with tests, however as with formatting
I have one problem. I would like to do this automatically, i.e. just
configure this in Save Actions. And this means that
On Tue, Jul 27, 2010 at 1:38 PM, konstantin.scheg...@gmail.com wrote:
1. Should I remove groups only from this AbsolutePanelParser test or
from DesignTimeUtilsTest too?
I guess you might as well do DesignTimeUtilsTest at the same time. Thanks.
2. I agree to use sorting methods with tests,
Any thoughts about new version of patch?
I have AbsolutePanel support and custom MenuItem and
separatorshttp://code.google.com/p/google-web-toolkit/issues/detail?id=4883support
patches in the queue.
But I can not post them until applying changes of this patch.
Remember attributes values
r8384
On Fri, Jul 16, 2010 at 11:59 AM, Ray Ryan rj...@google.com wrote:
Yup, the svn mirror broke. We're fixing it right now.
On Thu, Jul 15, 2010 at 7:48 PM, Ray Ryan rj...@google.com wrote:
It was committed, and should have hit svn by now. I can't check that
system right now, but can
Konstantin, I just submitted this but I'm starting to wonder about it. There
are lots of custom parsers that consume lots of attributes (e.g. the various
layout panel parsers). Why don't they need to call putAttribute explicitly
the way CellPanelParser did? If they do, and leaving them out was an
The most natural spot to hook in would
be com.google.gwt.uibinder.rebind.XMLElement.consumeAttributeWithDefault(String,
String, JType[]), which I believe is the only way to get the value of an
attribute from the parsed XML.
On Thu, Jul 15, 2010 at 10:29 AM, Ray Ryan rj...@google.com wrote:
The most natural spot to hook in would
be
com.google.gwt.uibinder.rebind.XMLElement.consumeAttributeWithDefault(String,
String, JType[]), which I believe is the only way to get the value of an
attribute from the parsed XML.
Aha!
Yes, using XMLElement.consumeX() methods also will work
It was committed, and should have hit svn by now. I can't check that system
right now, but can look in the morning if it's still wonky.
On Jul 15, 2010 5:41 PM, Konstantin Scheglov
konstantin.scheg...@gmail.com wrote:
The most natural spot to hook in would
be
So... I don't understand what to do now.
Should I prepare patch?
Would be sad to miss GWT 2.1 release.
I believe that UiBinder support in GWT Designer will be ready at the
time when GWT 2.1 will be actual version, so would be good to allow
them play nicely with each other.
Why do you
@rjrjr: What say ye? Have you considered doing something like this before,
and perhaps found a way to generalize it such that we don't have to create a
separate attribute parser for every enum?
Le 22 juin 2010 07:14, konstantin.scheg...@gmail.com a écrit :
Reviewers: jgw,
Description:
It
Le 22 juin 2010 07:03, Konstantin.Scheglov konstantin.scheg...@gmail.com a
écrit :
Pretty much everything we've done so far has been limited to
automatically
exposing the Java-level APIs in all their ugliness. The h/v alignment
values
are implemented somewhat manually, but for things
Pretty much everything we've done so far has been limited to automatically
exposing the Java-level APIs in all their ugliness. The h/v alignment values
are implemented somewhat manually, but for things like enums I really like
the idea that they can be exposed completely automatically.
On
On 2010/06/17 08:52:37, Konstantin.Scheglov wrote:
Thanks, LGTM. Submitted at r8281.
http://gwt-code-reviews.appspot.com/633801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Weird. Can you send a sample?
One other thing to consider -- you haven't by any chance attached the widget
to the document body directly, like this, have you?
Document.get().getBody().appendChild(myWidget.getElement());
I know it sounds a bit strange, but this pops up fairly often. It will
code is opensource ;)
http://juggers.googlecode.com/svn/trunk
add log_level=DEBUG to URL string to enable gwt-log,
clicking on the [inscription] button has no effect. A popup was
expected, and a log tries to trace the handler method
On 22 déc, 14:34, Joel Webber j...@google.com wrote:
Weird.
To be precise, you don't actually need the g:HTML in this example. It
could be simply:
g:HTMLPanel tag=li styleName={style.event}
div
... static HTML code ...
g:ButtonYou can do this too/g:Button
/div
g:Button
ui:field=subscribe styleName={style.button}Inscription/g:Button
You're right, this works fine
just still can't have handlers working with my button, either using
@UiHandler( subscribe ) or a programmatic subscribe.addClickHandler
(...)
strange ... any suggestion to debug this ?
On 21 déc, 16:03, Joel Webber j...@google.com wrote:
To be precise, you don't
Right, I got the warning but did not understand what it related to.
Thanks a lot
On 17 déc, 23:20, John Huss johnth...@gmail.com wrote:
I think you have to escape the css attributes that start with a dash
like this:
\-moz-box-shadow: 2px 2px 5px #000;
You should be getting a warning about
I think you have to escape the css attributes that start with a dash
like this:
\-moz-box-shadow: 2px 2px 5px #000;
You should be getting a warning about it in dev mode if you are not -
making sure you having logging on at a good level.
John
On Dec 17, 6:03 am, nicolas.deloof
Good job on diagnosing the problem. Instead of hacking up IdentValue,
introduce another Value subtype (call it TokenValue) that has this
alternate printing behavior.
http://gwt-code-reviews.appspot.com/87802
--~--~-~--~~~---~--~~
Nice sleuthing John!
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
LGTM
http://gwt-code-reviews.appspot.com/87802
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
On Tue, Oct 6, 2009 at 5:47 PM, Ray Ryan rj...@google.com wrote:
On Tue, Oct 6, 2009 at 8:43 AM, Thomas Broyer t.bro...@gmail.com wrote:
If I understand correctly how UiBinder works, for widgets, I'd still
have to inject the ID myself using
Not a bug. You're in charge of MyExternalBundle, including injecting it.
Note that there is no relationship between the bundle generated for the
ui:style block and your MyExternalBundle instance.
On Wed, Oct 7, 2009 at 3:10 PM, Sami Jaber sami.ja...@gmail.com wrote:
Hi gwitters,
Before
The idea of an IdResource is interesting. I have been looking for a good
sample resource type for a tutorial on extending ClientBundle. I think that
I will work this up while I'm travelling today.
--Bob (Android)
On Oct 5, 2009 12:12 PM, Thomas Broyer t.bro...@gmail.com wrote:
On Mon, Oct 5,
On Tue, Oct 6, 2009 at 4:16 PM, BobV b...@google.com wrote:
I've attached a very simple implementation (with source) of an
IdResource that can be used with ClientBundle. You're welcome to
adapt it to your needs, but I don't see any additional ClientBundle
API making it into GWT 2.0 at this
On Tue, Oct 6, 2009 at 8:43 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Tue, Oct 6, 2009 at 4:16 PM, BobV b...@google.com wrote:
I've attached a very simple implementation (with source) of an
IdResource that can be used with ClientBundle. You're welcome to
adapt it to your needs, but
On 6 oct, 17:47, Ray Ryan rj...@google.com wrote:
On Tue, Oct 6, 2009 at 8:43 AM, Thomas Broyer t.bro...@gmail.com wrote:
If I understand correctly how UiBinder works, for widgets, I'd still
have to inject the ID myself using
theWidget.getElement().setId(bundle.a().toString()) ?
On Mon, Oct 5, 2009 at 5:30 PM, Ray Ryan rj...@google.com wrote:
Not yet, and I'm torn about how to do it.
Wow! pretty reactive! (2 minutes between the question and answer!)
I don't know how it could be done at the generator/rebind level, but
maybe using i18n.client.Constants or rather
That's a flat out bug. Would you mind putting something on the issue
tracker?
On Thu, Sep 24, 2009 at 11:48 AM, Sripathi Krishnan
sripathi.krish...@gmail.com wrote:
I have a custom widget which has a constructor with some fields.
class HelpWidget extends Composite {
//usual interface
Created issue
http://code.google.com/p/google-web-toolkit/issues/detail?id=4075
Thanks!
--Sri
2009/9/24 Ray Ryan rj...@google.com
That's a flat out bug. Would you mind putting something on the issue
tracker?
On Thu, Sep 24, 2009 at 11:48 AM, Sripathi Krishnan
Brett,
I think something like what you propose below would be about what we'd need
for FlexTables, but you're also right to suggest that it would be easier
(and faster at runtime) just to throw all of it directly into HTML. Whenever
that's easy to do, it's almost invariably the *right* thing to
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
Yes, most widgets won't need custom parsers. They'll be covered by
combinations of BeanParser, HasWidgetsParser, etc. Custom parsers come into
play for widgets with no default constructor, or need custom code generated
for their add methods...that kind of thing.
I'm pretty sure HorizontalPanel and
Actually, after I fired off the email, I thought Hey, I can just just
HTMLPanel with tables and rows and cells with colspans. Is that the
usage pattern you guys were thinking of anyway? Certainly I can write
a parser for FlexTable, but it seems it would largely duplicate
tables, yes?
With
No - more like (for example), when it hits a label it always creates
a Google LabelElement - say I want to create a MyLabelElement instead
(which does some extra thing, which in my case it does). I can't do it
without hacking it (which I have done). Happy to file an Issue on
this...
On Aug 27,
It may not be a perfect solution to what you want to do, but because those
are native DOM Elements, which subtype JavaScriptObject, you can cast them
to any other JSO subtype you like. For example:
@UiField Element elem;
MyWidget() {
// ...
// If your element subclasses Element:
Also, have you noticed the @UiField(provided=true) and @UiFactory
annotations? They allow you to take charge of factory duties, instead of
relying on the default GWT.create() behavior.
On Fri, Aug 28, 2009 at 7:30 AM, Joel Webber j...@google.com wrote:
It may not be a perfect solution to what
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
I wouldn't mind some convincing urls to backup this viewpoint if you
have any :-) The entire rest of the team here is saying id id id,
class bad, id good. Searching for html id brittle wasn't very
enlightening :-)
I have also found that there seems to be no way of overriding the
class that is
On Thu, Aug 27, 2009 at 5:29 AM, Richard Vowles richard.vow...@gmail.comwrote:
I wouldn't mind some convincing urls to backup this viewpoint if you
have any :-) The entire rest of the team here is saying id id id,
class bad, id good. Searching for html id brittle wasn't very
enlightening :-)
On Thu, Aug 27, 2009 at 7:49 AM, Joel Webber j...@google.com wrote:
On Thu, Aug 27, 2009 at 5:29 AM, Richard Vowles
richard.vow...@gmail.comwrote:
I wouldn't mind some convincing urls to backup this viewpoint if you
have any :-) The entire rest of the team here is saying id id id,
class
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
Brett,
You should be able to use the already-checked-in LayoutPanel to do anything
you could have done with AbsolutePanel before. And it should be the case
that you can get rid of all of your manual resize code (that's the
intention, anyway). Also, if you run into any problems embedding other
Brett,
We did code splitting across the four major sections of our applications.
Assume we have section A-D, each with their own mediator. We then have an
ApplicationMediator, which is responsible for loading / unloading the four
major sections and sticking them into the viewport. When
Amir,
After your post, I have been investigating PureMVC a bit. Since you
used it, I have a question. In PureMVC, in the typical
ApplicationFacade class there is an initializeController() override
which registers all the commands. How does this fit with code-
splitting? Currently our
Joel,
Will be happy to test new layouts and review API. Unfortunately, I
don't use Dock, Stack, or Split in my app. I do use Absolute. And
because of an interior scrolling area that fills the client, a
sprinkling of resize code (after beating my head against CSS for a few
days). I do use
The situation as I see it is this. The old layout system has two huge
problems:1. Some widgets (e.g., StackPanel) *cannot* be made to work as
expected in standards mode, because of changes to table rendering behavior.
2. It's not really a system, in the sense that it can be highly
unpredictable.
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
Cool. Then another question about the future of the new layout
system. Is the current thinking that eventually it *will* replace all
of the older panels? I mean, is there buy-in at Google that that is a
desired track for this project. Or will the new layout system remain
parallel to the
Amir:
Your answer is very interesting and detailed. Thank you very much for
taking your time to answer my question. I will take a look in PureMVC.
One of my big concerns is the translation of JSR 303 validations to
client side.
Regards.
- Andrés
On 13 ago, 18:36, Amir Kashani
Brett,
I am going to be writing adding custom parsers for the new layout panels
sometime soon. And the new layout system will be de facto in the sense
that I'm updating all the samples to use it (and possibly adding another
sample). We obviously won't be removing the old widgets (e.g., StackPanel)
1 - 100 of 115 matches
Mail list logo
