Thanks Matt, that does the trick.
Actually I'm just post processing a template host html page with an ant
task before deployment, that solves the decoupling concern.
On 17.12.2009 21:06, Matt Mastracci wrote:
If it's the same error we ran into, it's that there are things that look like
HTML
Hi,
Small question:
Is there a reason why GWT is still using a DTD instead of a schema ?
In Schema's you can put a lot extra information (inline docs) and
eclipse also supports completions with schemas if you put the schema
in the XML repository.
David
On Thu, Dec 17, 2009 at 11:59 PM, Fushion
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
Arthur,
No, we are not closing DevMode. Our client app is not small.
Refreshing DevMode in 2.0 takes 20-30 seconds on a decent multi-core
workstation. Often, we are only able to refresh a handful of times
before we start running into out-of-memory exceptions and browser
crashes (FF 3.5.6). I
Dear Contributors,
Unfortunately, the GWT Contributors Group has been getting a lot of
spam attacks as of late and most spam posts have been making it
through. To fight against these spam attacks, we will be temporarily
moderating messages posted by new members to the group.
The GWT contributor
same problems unfortunately
2009/12/18 Brad Leupen qcomps...@gmail.com
Arthur,
No, we are not closing DevMode. Our client app is not small.
Refreshing DevMode in 2.0 takes 20-30 seconds on a decent multi-core
workstation. Often, we are only able to refresh a handful of times
before we
Reviewers: jgw,
Description:
This is a *really* trivial fix.
Please review this at http://gwt-code-reviews.appspot.com/126812
Affected files:
user/src/com/google/gwt/user/History.gwt.xml
Index: user/src/com/google/gwt/user/History.gwt.xml
Revision: 7334
Author: sco...@google.com
Date: Fri Dec 18 07:07:21 2009
Log: Tagging 2.0.0-rc2.
http://code.google.com/p/google-web-toolkit/source/detail?r=7334
Added:
/tags/2.0.0-rc2
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Revision: 7335
Author: sco...@google.com
Date: Fri Dec 18 07:07:53 2009
Log: Tagging 2.0.0.
http://code.google.com/p/google-web-toolkit/source/detail?r=7335
Added:
/tags/2.0.0
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Reviewers: jgw,
Description:
See
http://groups.google.com/group/google-web-toolkit-contributors/t/a0b141cf7ea77a56
This is done by using com.google.gwt.dom.DOM's TableCellElement and
TableRowElement, so I also changed everything (exception
public/protected APIs) from
On Dec 16, 3:16 pm, Joel Webber j...@google.com wrote:
Thomas,
Your assessment that this is an accidental legacy is basically correct. This
code should definitely be optimized -- if you could file an issue, that
would be helpful. Hopefully it makes little difference in practice, because
of
Thanks for the feedback Brad. We've talked internally about an idea for
instant compile where the workflow would be essentially like hosted mode,
except it would very quickly translate your code into JavaScript with zero
optimizations. It sounds like there might be some interest in this.
(Of
The 2.0.0 release has been tagged. The DTD references should be correct
now. Thanks for pointing this out!
On Thu, Dec 17, 2009 at 10:56 AM, Arthur Kalmenson arthur.k...@gmail.comwrote:
Hey everyone,
I just noticed that the DTD used in the GWT modules generated by the
GEP is incorrect. It
Reviewers: Lex,
Description:
Hi Lex,
could you review this patch for me? It fixes two XML issues in the
CompileReport:
1) There was a bug in the escapeXML method that would let all special
characters after the first one slip through. This is now fixed.
2) Because of the difference in encoding
On Fri, Dec 18, 2009 at 5:09 AM, David david.no...@gmail.com wrote:
Hi,
Small question:
Is there a reason why GWT is still using a DTD instead of a schema ?
In Schema's you can put a lot extra information (inline docs) and
eclipse also supports completions with schemas if you put the schema
Scott,
That sounds great! It's reassuring to know y'all are thinking about
this. I know it's not an easy problem to solve.
Brad
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
shortly, you intend to make a kind of incremental compilationnot of course
in .class but .js. It seems good to me.
2009/12/18 Brad Leupen qcomps...@gmail.com
Scott,
That sounds great! It's reassuring to know y'all are thinking about
this. I know it's not an easy problem to solve.
Brad
--
- Wrap Google Closure Library (http://code.google.com/closure/
library/)
On 16 Dic, 18:01, Bruce Johnson br...@google.com wrote:
Working on a draft one.
What do folks here think is important?
On Wed, Dec 16, 2009 at 7:42 AM, tfreitas tfrei...@gmail.com wrote:
What about roadmap?
--
I'd like to introduce GWT meeting group, so all GWT developers can
meet each other.
See details here: http://www.meetup.com/GWT-developement/
Peter
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Hey Brad,
Sorry about that, I've just seen a number of people in the IRC channel
asking about why DevMode was so slow and it turned out they had been
closing it after each check. I just wanted to throw that comment up
there for those that didn't know. I guess our apps haven't got to that
size
LGTM.
If we work much more on this area, though, here's an alternative
approach. Instead of working around Unicode obscurities, we could
encode strings using a Java-like encoding. For example, 0 would become
\u, and \ would become \\.
Going that way, reading and writing these XML files
On Fri, Dec 18, 2009 at 10:16 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Dec 16, 3:16 pm, Joel Webber j...@google.com wrote:
Thomas,
Your assessment that this is an accidental legacy is basically correct.
This
code should definitely be optimized -- if you could file an issue, that
http://gwt-code-reviews.appspot.com/125803/diff/1/3
File dev/core/src/com/google/gwt/dev/jjs/ast/JProgram.java (right):
http://gwt-code-reviews.appspot.com/125803/diff/1/3#newcode480
Line 480: }
Will do.
http://gwt-code-reviews.appspot.com/125803/diff/1/3#newcode1032
Line 1032:
Has everyone responding in this thread been checking the issue
tracker, staring issues they want to see resolved, and entering new
issues where they don't yet exist in the tracker? I know several of
the requests mentioned in this thread are already in there.
Arthur,
It's a good tip, especially when hot swap tells you that you need to
restart. For our app, we resorted to creating sandbox GWT entry points
to develop widgets in isolation. This gave us usable compile/refresh
times but I still long for the days when I could just press F5 to
refresh the
On Fri, Dec 18, 2009 at 11:25 AM, Brad Leupen qcomps...@gmail.com wrote:
Another wish list item: a less API-invasive approach to protecting
against XSRF attacks (see:
http://groups.google.com/group/Google-Web-Toolkit/web/security-for-gwt-applications
).
It seems to me that XSRF checks could
Thanks, Lex!
I had thought about the approach you suggest here, and maybe that's the
right (safe) way to go -- the only problem with it is that if you have a
unicode character in your string, it wouldn't display properly in the
browser. In other words, for \u00CA you wouldn't see Ê, but rather
Revision: 7336
Author: sp...@google.com
Date: Fri Dec 18 09:13:44 2009
Log: Sort and format.
http://code.google.com/p/google-web-toolkit/source/detail?r=7336
Modified:
/trunk/dev/core/src/com/google/gwt/dev/jjs/impl/SameParameterValueOptimizer.java
Reviewers: bobv,
Description:
Otherwise, it can end up treating, for example, an integer as a long.
Please review this at http://gwt-code-reviews.appspot.com/126814
Affected files:
dev/core/src/com/google/gwt/dev/jjs/impl/SameParameterValueOptimizer.java
LGTM
http://gwt-code-reviews.appspot.com/126814
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
http://gwt-code-reviews.appspot.com/125803/diff/1/3
File dev/core/src/com/google/gwt/dev/jjs/ast/JProgram.java (right):
http://gwt-code-reviews.appspot.com/125803/diff/1/3#newcode1032
Line 1032: allArrayTypes.add(arrayType);
LGTM then. Maybe we could just drop a one-line future-proofer comment
Revision: 7337
Author: r...@google.com
Date: Fri Dec 18 10:10:29 2009
Log: Call servlet.log(message) instead of servlet.log(message, (Throwable)
null)
to avoid NPEs in some servlet containers.
Review by: bobv
http://code.google.com/p/google-web-toolkit/source/detail?r=7337
Modified:
Revision: 7338
Author: sp...@google.com
Date: Fri Dec 18 10:24:21 2009
Log: When SameParameterValueOptimizer substitutes a value
for a parameter, it now casts the value to the type
of the parameter. This prevents, for example,
treating an integer as a long.
Review by: scottb
Revision: 7339
Author: j...@google.com
Date: Fri Dec 18 11:27:58 2009
Log: Add Richard Zschech to CLA-SIGNERS.
http://code.google.com/p/google-web-toolkit/source/detail?r=7339
Modified:
/CLA-SIGNERS
===
--- /CLA-SIGNERSWed May 13 14:19:20 2009
+++
Reviewers: bobv,
Message:
Bob, can you review this please?
Description:
In rare cases, the old code would crash with a null scope.
Please review this at http://gwt-code-reviews.appspot.com/126815
Affected files:
M dev/core/src/com/google/gwt/dev/javac/JSORestrictionsChecker.java
Index:
LGTM
http://gwt-code-reviews.appspot.com/126815
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Revision: 7340
Author: sco...@google.com
Date: Fri Dec 18 14:16:56 2009
Log: Fixes JSORestrictions crash in bad units.
In rare cases, the old code would crash with a null scope.
Review by: bobv
http://code.google.com/p/google-web-toolkit/source/detail?r=7340
Modified:
Comment by m...@google.com:
This doesn't make sense to me. This is a purely mechanical change isn't
it? Why wouldn't this work: rename Widget to BaseWidget; create an
interface Widget that contains all the public methods in BaseWidget; change
BaseWidget to implement Widget; change
Hi all,
I wish the GWT team would focus on all the things that force us to use
such awful third-party libraries as Ext-GWT:
-more appealing built-in themes
-richer components, like data grids with remote pagination
-data binding
Ext-GWT is full of annoyances but it has good looking widgets,
Definitely, the most important thing for me is fix the bugs and above
all publish an excellent documentation and ...
+1 for Databinding Validation
+1 for a nice DataGrid
+1 for nicer widgets
Great job on GWT 2.0
On 16 dez, 10:42, tfreitas tfrei...@gmail.com wrote:
What about roadmap?
--
I would like more control over which classes/packages were actually
sucked into a module for compilation. I appreciate there are
workarounds like sticking diff java files under diff src dirs but
that's ugly.
I don't like how including a particular package also sucks in sub
packages. I
41 matches
Mail list logo
