RR : Make @url and gwt-image work with nested ClientBundles
11 views
Skip to first unread message
bo...@google.com
unread,
Dec 15, 2009, 12:19:56 AM12/15/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to rj...@google.com, google-web-tool...@googlegroups.com
Reviewers: Ray Ryan,
Message:
Review requested.
Description:
This patch makes @url and the gwt-image property of @sprite blocks
accept dot-path values so that they can be used with nested
ClientBundles.
Affected files:
M dev/core/src/com/google/gwt/core/ext/typeinfo/JClassType.java
M user/src/com/google/gwt/resources/css/Spriter.java
M user/src/com/google/gwt/resources/css/SubstitutionReplacer.java
M user/src/com/google/gwt/resources/css/ast/CssNodeCloner.java
M user/src/com/google/gwt/resources/css/ast/CssProperty.java
M user/src/com/google/gwt/resources/css/ast/CssSprite.java
M user/src/com/google/gwt/resources/css/ast/CssUrl.java
M user/src/com/google/gwt/resources/ext/ResourceGeneratorUtil.java
M user/src/com/google/gwt/resources/rg/CssResourceGenerator.java
M user/test/com/google/gwt/resources/client/CSSResourceTest.java
M user/test/com/google/gwt/resources/client/test.css
rj...@google.com
unread,
Dec 15, 2009, 12:37:46 AM12/15/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bo...@google.com, google-web-tool...@googlegroups.com
I could use this in UiBinder if I had some control over its ordering. My
specific need is "breadth first", with myself and my interfaces at the
head of the list, and then the same treatment for each super class and
super interface. That is:
http://gwt-code-reviews.appspot.com/126802/diff/1/9#newcode328 Line 328: throw new NotFoundException();
Rather than doing your own logging, why not define your own exception
type and let callers decide what to do wrt logs and the exception's
message? Or perhaps stick with NotFoundException and promise a decent
message?