/browse/trunk/user/super/com/google/gwt/core/translatable/com/google/gwt/core/client/impl/WeakMapping.java
–
a mix of both approaches actually, as newer modules such as
com.google.gwt.regexp use a super subfolder in the src/ branch)
And if you want the full power of Eclipse for super-source
How should this work with a second project?
If I a super/ folder as source and have a gwt.xml in super/emul.gwt.xml
with:
super-source path=/
Then this will not work. The super source must be in a subfolder.
Am Montag, 26. April 2010 11:32:13 UTC+2 schrieb Thomas Broyer:
On Apr 26,
Do you know how to make the file in super-source tag available on compile
time?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi,
in the development of our current project
(Augmented Reality with GWT, the first HOWTO is at
http://jooink.blogspot.com/2012/10/gwt-augmented-reality-howto-step-0.html)
we used super-source tag that works perfectly and helped us in avoiding a
long code 'refactoring' but I am not able
to
Add the root of your super-source folder as a source folder (right-click
the folder, open the Build Path submenu, and click Use as Source
Folder). Eclipse should automatically make the necessary modifications to
the parent source folder, but you might want to check to make sure.
-Abraham
--
Works perfectly :)
Thank you.
Alberto
On Fri, Oct 5, 2012 at 3:28 PM, Abraham Lin atomknight033...@gmail.comwrote:
Add the root of your super-source folder as a source folder (right-click
the folder, open the Build Path submenu, and click Use as Source
Folder). Eclipse should
/trunk/user/super/com/google/gwt/core/translatable/com/google/gwt/core/client/impl/WeakMapping.java
–
a mix of both approaches actually, as newer modules such as
com.google.gwt.regexp use a super subfolder in the src/ branch)
And if you want the full power of Eclipse for super-source classes
code into
separate projects, so this hadn't occurred to me.
And if you want the full power of Eclipse for super-source classes, then
create another Eclipse project where you import the super-source folder as
a Source Folder (again, that's what GWT does:
http://code.google.com/p/google-web
, etc.)
Ah, that's true. I'm used to separating client and server code into
separate projects, so this hadn't occurred to me.
It's not only about client vs. server, it also affects non-GWTTestCase unit
tests of your client code.
And if you want the full power of Eclipse for super-source
On Friday, October 5, 2012 1:46:54 PM UTC-4, Thomas Broyer wrote:
It's not only about client vs. server, it also affects non-GWTTestCase
unit tests of your client code.
This doesn't seem right. Given that your client classes will be relying on
the super-sourced logic at runtime, why
On Friday, October 5, 2012 8:52:50 PM UTC+2, Abraham Lin wrote:
On Friday, October 5, 2012 1:46:54 PM UTC-4, Thomas Broyer wrote:
It's not only about client vs. server, it also affects non-GWTTestCase
unit tests of your client code.
This doesn't seem right. Given that your client
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 20:08, David Given wrote:
[...]
On 26/04/10 10:32, Thomas Broyer wrote:
[...]
You can add the emu subfolder to the Build Path (so that package
declarations match folder hierarchy) and add an exclude filter
(Excludes: **) so that
On 2010-04-26 05:29, branflake2267 wrote:
[...]
It appears that your source isn't in the translatable directories that
would translate to javascript. Anything in project.client.* should
translate into javascript. There should be two packages
tld.domain.client.* and tld.domain.server.
Er, no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 10:32, Thomas Broyer wrote:
[...]
You can add the emu subfolder to the Build Path (so that package
declarations match folder hierarchy) and add an exclude filter
(Excludes: **) so that Eclipse doesn't compile the classes to your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to add some classes to the JRE emulation used by my app.
Right now I have a module in .../src/emu/Emulation.gwt.xml that uses
super-source and my classes in .../src/emu/java/io/Foo.java.
This works fine. However, Eclipse doesn't like it
HI David,
It appears that your source isn't in the translatable directories that
would translate to javascript. Anything in project.client.* should
translate into javascript. There should be two packages
tld.domain.client.* and tld.domain.server. You can use the
webApCreator to setup a project
16 matches
Mail list logo
