Issue 3729 was opened.
On Jun 4, 11:13 am, Rajeev Dayal rda...@google.com wrote:
It would be great if you could file the RFE :).
On Tue, Jun 2, 2009 at 3:07 PM, Igor Moochnick
igor.moochn...@gmail.comwrote:
Guilty as charged. I was on the road for some time and had no chance
to
It would be great if you could file the RFE :).
On Tue, Jun 2, 2009 at 3:07 PM, Igor Moochnick igor.moochn...@gmail.comwrote:
Guilty as charged. I was on the road for some time and had no chance
to file the RFE.
Should I still do it?
On May 29, 6:11 pm, Rajeev Dayal rda...@google.com
Guilty as charged. I was on the road for some time and had no chance
to file the RFE.
Should I still do it?
On May 29, 6:11 pm, Rajeev Dayal rda...@google.com wrote:
Hi Abby,
No, I don't think that an RFE has been filed for this. Would you mind filing
one?
Yes, the best workaround right
Hi Abby,
No, I don't think that an RFE has been filed for this. Would you mind filing
one?
Yes, the best workaround right now would be to place the images in the same
package as the Bundle interface (or the Bundle interface in the same package
as the images).
Rajeev
On Wed, May 27, 2009 at
Did anyone open a RFE for this?
Also, is the best workaround now having the images in same package as
the Bundle interface?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this
I like the fallback idea (I forgot about the back compatibility ;-)
One other approach may be by creating another annotation (that
inherits from the original one) so the ImageBundle compiler can
differentiate between them.
On May 15, 5:20 pm, Rajeev Dayal rda...@google.com wrote:
This would
Hi Igor,
The problem is that the resource annotation will only understand either:
1) A file name relative to the package. This must only be a file name, not a
path
2) A fully qualified path
The problem is that you're using a relative path for the file, which will
not work. You have to use the
Interesting ... In fact I was actually trying to use the relative
path.
The goal was to put the images (part of the application ImageBundles)
with the classes/widgets that are using them and then extra /images
folder (relative to the widget folder).
Then, if I put a full path, what are the best
You are correct - if you end up refactoring, you'll have to change the
references in the @Resource annotation. The only other way around this is to
place the images themselves in the same package as your ImageBundle, and
then you can use relative references.
You can file a Request for Enhancement
You mean PACKAGE or MODULE? In fact I do use PACKAGEs.
Because I'm actually using packages for my widgets and, in fact,
that's what broken.
This is how I've structured my code:
com.myserver.client - all the usual client code
com.myserver.client.widgets - here I put
Hi Igor,
Responses inline:
On Fri, May 15, 2009 at 3:47 PM, Igor Moochnick igor.moochn...@gmail.comwrote:
You mean PACKAGE or MODULE? In fact I do use PACKAGEs.
I mean package.
Because I'm actually using packages for my widgets and, in fact,
that's what broken.
This is how I've
This would work, except for backwards compatibility. If we put in this
change, then all of those people that were using fully-qualified names
without the leading slash would run into problems. Another way to handle
this might be to add another piece data to the annotation to indicate that
the path
The forward slash (/) doesn't work on Windows.
On May 4, 5:21 pm, Rajeev Dayal rda...@google.com wrote:
Actually, the documentation says that GWT uses ClassLoader.getResource(..)
to locate images. As a result, the syntax that you use in the annotation
*should* be OS-agnostic. You should
This is the error I'm getting on the Jetty (hosted) server when
opening my application:
[DEBUG] Loading an instance of module 'mymodule'
[DEBUG] Rebinding com.mymodule.Myclient.Images
[DEBUG] Invoking generate-with
class='com.google.gwt.user.rebind.ui.ImageBundleGenerator'/
[DEBUG] Analyzing
Actually, the documentation says that GWT uses ClassLoader.getResource(..)
to locate images. As a result, the syntax that you use in the annotation
*should* be OS-agnostic. You should always use forward slashes ( / ) to
separate path components.
Is that not working for you?
On Fri, May 1, 2009
I have a relative path use in the @Resource attribute on my image
bundle. Apparently the direction of the slashes are important and
depend on what OS I'm building my project.
On Windows it has to be \ and on Linux - /.
public interface Images extends ImageBundle
{
16 matches
Mail list logo
