Re: Multiple GWT modules in one Maven module

[Thomas Broyer]

On Tuesday, May 9, 2017 at 1:45:00 PM UTC+2, Frederik Van Hoyweghen wrote:
>
> I tried both the command line (mvn gwt:compile) and via the IntelliJ Maven 
> plugin.
> Indeed, binding the execution to the prepare-package phase and running *mvn 
> gwt:compile@compile-common *works, and I'm glad it does.
>
> If I'm reading what you're saying correctly, this means that there is no 
> way to invoke all the plugin executions with a simple command?
> I personally expected *mvn gwt:compile* to invoke everything it needs (so 
> everything that comes earlier in it's lifecycle, including the executions I 
> bound to the prepare-package phase),
> or am I missing something obvious?
>

"mvn package" (or "mvn prepare-package" if you want, but refer to my second 
rule of thumb)

See 
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html 
(in this case specifically the "a build phase is made up of plugin goals" 
section)

If you'd prefer working with a graph of tasks (like you do in Ant), then 
again have a look at Gradle.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[Frederik Van Hoyweghen]

I tried both the command line (mvn gwt:compile) and via the IntelliJ Maven 
plugin.
Indeed, binding the execution to the prepare-package phase and running *mvn 
gwt:compile@compile-common *works, and I'm glad it does.

If I'm reading what you're saying correctly, this means that there is no 
way to invoke all the plugin executions with a simple command?
I personally expected *mvn gwt:compile* to invoke everything it needs (so 
everything that comes earlier in it's lifecycle, including the executions I 
bound to the prepare-package phase),
or am I missing something obvious?

Thanks again!

On Tuesday, May 9, 2017 at 1:26:28 PM UTC+2, Thomas Broyer wrote:
>
>
>
> On Tuesday, May 9, 2017 at 1:11:04 PM UTC+2, Frederik Van Hoyweghen wrote:
>>
>>
>>
>> On Tuesday, May 9, 2017 at 12:59:17 PM UTC+2, Thomas Broyer wrote:
>>>
>>>
>>> I wouldn't put any  /  into the 
>>> plugin-level , and only put them into the .
>>>
>>
>> That's what I figured, but it seems to be a required property (The 
>> parameters 'moduleName' for goal 
>> net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-7:compile are missing or 
>> invalid, when invoking gwt:compile).
>>
>
> How are you invoking gwt:compile? If on the command-line, then the 
> execution ID matters, and only one such execution will match (the one with 
> default-cli). But starting with Maven 3.3.1 you can specify the 
> execution id on the command-line too: "mvn gwt:compile@compile-common 
> gwt:compile@compile-foo".
>
> See 
> https://maven.apache.org/guides/mini/guide-default-execution-ids.html#Default_executionIds_for_Implied_Executions
>  and 
> https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_executions_Tag
>
> I defined my executions as per your example:
>>
>> 
>> 6
>> true
>> true
>> 
>> 
>> 
>> compile-common
>> compile
>> 
>> com.test.common
>> 
>> 
>>
>>
>> etc.. but it appears the executions aren't triggered (or is this an 
>> effect of the missing moduleName under configuration?). It seems I have 
>> much to learn still.
>>
>
> Rule of thumb: if a goal is (meant to be) bound to a lifecycle phase (such 
> as gwt:compile which is bound by default to the prepare-package phase; see 
> https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html; but not 
> gwt:devmode or gwt:codeserver for example), then invoke the lifecycle 
> phase, not the goal.
> Another rule of thumb: only ever invoke the lifecycle phases "package" and 
> "verify" (and "install" and "deploy" when dealing with libraries, to share 
> them with other projects / people). If you want to skip tests, pass 
> -DskipTests, if you want to skip the compilation of tests too then pass 
> -Dmaven.test.skip.
> If you know what you're doing, then feel free to break those rules; if you 
> know what you're doing.
>
> Also, have a look at Gradle rather than Maven, if that's a possibility for 
> your project(s).
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[Thomas Broyer]

On Tuesday, May 9, 2017 at 1:11:04 PM UTC+2, Frederik Van Hoyweghen wrote:
>
>
>
> On Tuesday, May 9, 2017 at 12:59:17 PM UTC+2, Thomas Broyer wrote:
>>
>>
>> I wouldn't put any  /  into the plugin-level 
>> , and only put them into the .
>>
>
> That's what I figured, but it seems to be a required property (The 
> parameters 'moduleName' for goal 
> net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-7:compile are missing or 
> invalid, when invoking gwt:compile).
>

How are you invoking gwt:compile? If on the command-line, then the 
execution ID matters, and only one such execution will match (the one with 
default-cli). But starting with Maven 3.3.1 you can specify the 
execution id on the command-line too: "mvn gwt:compile@compile-common 
gwt:compile@compile-foo".

See 
https://maven.apache.org/guides/mini/guide-default-execution-ids.html#Default_executionIds_for_Implied_Executions
 and 
https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_executions_Tag

I defined my executions as per your example:
>
> 
> 6
> true
> true
> 
> 
> 
> compile-common
> compile
> 
> com.test.common
> 
> 
>
>
> etc.. but it appears the executions aren't triggered (or is this an effect 
> of the missing moduleName under configuration?). It seems I have much to 
> learn still.
>

Rule of thumb: if a goal is (meant to be) bound to a lifecycle phase (such 
as gwt:compile which is bound by default to the prepare-package phase; 
see https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html; but not 
gwt:devmode or gwt:codeserver for example), then invoke the lifecycle 
phase, not the goal.
Another rule of thumb: only ever invoke the lifecycle phases "package" and 
"verify" (and "install" and "deploy" when dealing with libraries, to share 
them with other projects / people). If you want to skip tests, pass 
-DskipTests, if you want to skip the compilation of tests too then pass 
-Dmaven.test.skip.
If you know what you're doing, then feel free to break those rules; if you 
know what you're doing.

Also, have a look at Gradle rather than Maven, if that's a possibility for 
your project(s).

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[Frederik Van Hoyweghen]

On Tuesday, May 9, 2017 at 12:59:17 PM UTC+2, Thomas Broyer wrote:
>
>
> I wouldn't put any  /  into the plugin-level 
> , and only put them into the .
>

That's what I figured, but it seems to be a required property (The 
parameters 'moduleName' for goal 
net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-7:compile are missing or 
invalid, when invoking gwt:compile).

I defined my executions as per your example:


6
true
true



compile-common
compile

com.test.common




etc.. but it appears the executions aren't triggered (or is this an effect 
of the missing moduleName under configuration?). It seems I have much to 
learn still.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[Thomas Broyer]

On Tuesday, May 9, 2017 at 12:33:57 PM UTC+2, Frederik Van Hoyweghen wrote:
>
> This indeed seems to be what I was looking for, thank you.
> Are there any obvious downsides to doing it like this, with multiple 
> executions?
>

Each module compilation will fork a new GWT compiler process, rather than 
use a single process compiling all modules (assuming that's how you're 
doing it in Ant), so it'll probably take more time (but possibly less 
memory).
That's all I can think of.
 

> Does it matter which specific moduleName I specify within the 
>  tag, or should I just pick 1 arbitrary one there and put 
> the others within the  tag?
>

I wouldn't put any  /  into the plugin-level 
, and only put them into the .

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[Frederik Van Hoyweghen]

This indeed seems to be what I was looking for, thank you.
Are there any obvious downsides to doing it like this, with multiple 
executions?

Does it matter which specific moduleName I specify within the 
 tag, or should I just pick 1 arbitrary one there and put 
the others within the  tag?

I very much appreciate the responses and the patience ;)

On Tuesday, May 9, 2017 at 12:22:40 PM UTC+2, Thomas Broyer wrote:
>
>
>
> On Tuesday, May 9, 2017 at 11:27:25 AM UTC+2, Frederik Van Hoyweghen wrote:
>>
>> Thanks for the replies.
>>
>> I already took a look at the issue on the plugin's github: 
>> https://github.com/tbroyer/gwt-maven-plugin/issues/57 
>> 
>> Sadly, this was closed and recently labeled with a wontfix, hence me 
>> asking for help here :)
>>
>
> My first comment on this issue tells you how to do it. In case it isn't 
> clear, what I meant there is:
>
> 
>   
> compile-module1
> 
>   compile
> 
> 
>   com.example.module1.Module1
>   module1
> 
>   
>   
> compile-module1
> 
>   compile
> 
> 
>   com.example.module2.Module2
>   module2
> 
>   
> 
>
> Another possibility (if you really do want to fork one and only one GWT 
> compiler process) is to use the exec-maven-plugin's exec goal (though you 
> would have to declare your source roots as resources dirs to get your 
> sources copied to target/classes so they're present in the computed 
> ).
> (I suppose you could get something working by "hacking" into the 
> , and probably then true 
> as you'd have the staleness check only take the module configured in 
> / into account; I would discourage such "hack" 
> though)
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[Thomas Broyer]

On Tuesday, May 9, 2017 at 11:27:25 AM UTC+2, Frederik Van Hoyweghen wrote:
>
> Thanks for the replies.
>
> I already took a look at the issue on the plugin's github: 
> https://github.com/tbroyer/gwt-maven-plugin/issues/57 
> 
> Sadly, this was closed and recently labeled with a wontfix, hence me 
> asking for help here :)
>

My first comment on this issue tells you how to do it. In case it isn't 
clear, what I meant there is:


  
compile-module1

  compile


  com.example.module1.Module1
  module1

  
  
compile-module1

  compile


  com.example.module2.Module2
  module2

  


Another possibility (if you really do want to fork one and only one GWT 
compiler process) is to use the exec-maven-plugin's exec goal (though you 
would have to declare your source roots as resources dirs to get your 
sources copied to target/classes so they're present in the computed 
).
(I suppose you could get something working by "hacking" into the 
, and probably then true 
as you'd have the staleness check only take the module configured in 
/ into account; I would discourage such "hack" 
though)

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[Frederik Van Hoyweghen]

Thanks for the replies.

I already took a look at the issue on the plugin's github: 
https://github.com/tbroyer/gwt-maven-plugin/issues/57 

Sadly, this was closed and recently labeled with a wontfix, hence me asking 
for help here :)


On Tuesday, May 9, 2017 at 9:55:15 AM UTC+2, DavidN wrote:
>
> In my project I have many modules. What I did is simple create a gwt-lib 
> maven module per GWT module. Those modules served different purposes so it 
> made sense to split them in smaller artifacts.
>
> In some cases I moved the code around so that I join multiple modules into 
> one big module instead.
>
> Another solution you could try is to have one module that inherits all the 
> other modules. But I don't like that approach because it means you have 
> manually maintain that gwt.xml file and those other gwt.xml files as well, 
> while with the gwt-lib approach the gwt maven plugin will take care of 
> adding the inherits tags automatically (if you have the gwt-lib in your 
> dependency section).
>

I was hoping to (for the time being) avoid this exact approach. I realize 
this is the way to go, but I'm also expected to maintain full compatibility 
with our old ant build (until the maven build is as good as ready).

Should I take a look at the legacy Mojo maven plugin, or can I expect to 
come across the same hurdles with that one given my project layout?


-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[David]

In my project I have many modules. What I did is simple create a gwt-lib
maven module per GWT module. Those modules served different purposes so it
made sense to split them in smaller artifacts.

In some cases I moved the code around so that I join multiple modules into
one big module instead.

Another solution you could try is to have one module that inherits all the
other modules. But I don't like that approach because it means you have
manually maintain that gwt.xml file and those other gwt.xml files as well,
while with the gwt-lib approach the gwt maven plugin will take care of
adding the inherits tags automatically (if you have the gwt-lib in your
dependency section).

On Mon, May 8, 2017 at 6:17 PM Frederik Van Hoyweghen <
frederik.vanhoyweg...@chapoo.com> wrote:

> Hey everyone,
>
> We are currently migrating our project away from using Ant, to Maven.
>
> Along with this migration, we also tried to follow some of the project
> structuring that is recommended for a maven project.
>
> Our *Maven* GWT module contains multiple GWT modules, but I'm struggling
> with making this work using Thomas Broyer's GWT plugin:
> https://github.com/tbroyer/gwt-maven-plugin
> I feel like this was designed specifically with the idea of having only 1
> GWT module inside a Maven module (please correct me if I'm wrong).
>
>
> At first I tried this plugin configuration:
>
> 
> true
> 
> 
> A
> B
> C
> D
> 
> 
> 
>
>
>
> This doesn't work because ModuleName has to be underneath the
>  tag.
> Listing the modules underneath the  tag also doesn't work,
> running gwt:compile only compiles the last module in the list:
>
> 
> A
> B
> C
> D
> true
> 
>
>
>
>
> Does anyone have any experience with this?
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple GWT modules in one Maven module

[Thomas Broyer]

On Monday, May 8, 2017 at 6:18:06 PM UTC+2, Frederik Van Hoyweghen wrote:
>
> Hey everyone,
>
> We are currently migrating our project away from using Ant, to Maven.
>
> Along with this migration, we also tried to follow some of the project 
> structuring that is recommended for a maven project.
>
> Our *Maven* GWT module contains multiple GWT modules, but I'm struggling 
> with making this work using Thomas Broyer's GWT plugin: 
> https://github.com/tbroyer/gwt-maven-plugin
> I feel like this was designed specifically with the idea of having only 1 
> GWT module inside a Maven module (please correct me if I'm wrong).
>

That's right.
 

> At first I tried this plugin configuration:
>
> 
> true
> 
> 
> A
> B
> C
> D
> 
> 
> 
>
>
>
> This doesn't work because ModuleName has to be underneath the 
>  tag.
> Listing the modules underneath the  tag also doesn't work, 
> running gwt:compile only compiles the last module in the list:
>
> 
> A
> B
> C
> D
> true
> 
>
>
>
>
> Does anyone have any experience with this?
>

See https://github.com/tbroyer/gwt-maven-plugin/issues/57 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple gwt modules using

[Thomas Broyer]

Answered on SO: http://stackoverflow.com/q/13972343/116472

On Thursday, December 20, 2012 2:16:10 PM UTC+1, Ahmad Igbaria wrote:
>
> I have a GWT component that i want to integrate with my GWT application, 
> but unfortunately this component takes about 40 sec to load, this means in 
> DevMode each time i refresh the page i should to wait about 40 sec to be 
> able to work. this is caused by only using the tag for this component.
>
> I thought about inheriting using tag for the component instead of adding 
> tag in the gwt.xml file. in production mode, it works but in development 
> mode i get the following error:
>
> [ERROR] [ModuleA] - Unable to find 'ModuleA.gwt.xml' on your classpath; 
> could be a typo, or maybe you forgot to include a classpath entry for 
> source?
>
> The solution that i have come up with is:
> 1. create a GWT module that inherits the component
> 2. create a native method that create a function to call the component api:
> $wnd.externalJS = $entry(@com.ModuleA::loadData(Ljava/lang/String;));
> 3. compile the module
> 4. add script in module B 
>
> Thank you
> Ahmad Igbaria
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/fP2Dh6qV3fcJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: multiple gwt modules

[Ed]

I would also use cookies, but be careful as the cookie info is send
back and forward to the server, so don't put too much info in it.
I do the same. Start another gwt app with info in the cookie.
I do this because with code-splitting the left over is getting too big
such that I have to split my gwt app's in separate gwt apps instead.

- Ed

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: multiple gwt modules

[Ali Jalal]

Hi

1. You can use Cookie in client-side to save/load information in same
domain. So if your modules are in same domain there shouldn't be any
problem.
2. You can also load/save informations from/to server if serialization of
information in cookies is cumbersome.


On Thu, Aug 11, 2011 at 9:52 PM, Daemon Zak  wrote:

> I want to able to load a gwt module from another gwt module  for eg:
> if i click a button ,the new module should be loaded in a new
> browser ,with the same session attributes. how do we communicate
> between modules i.e . if i want to pass some information from one
> module to another and vice versa . any help is greatly appreicated
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: multiple gwt modules

[dreamer]

GWT module is a simply a javascript bundle.

I guess you are looking to open a component in another window.

you can use  "Window.Open(..)".

This gives better info regarding modules

http://code.google.com/webtoolkit/doc/1.6/DevGuideOrganizingProjects.html#DevGuideModules



On Aug 11, 7:38 pm, Daemon Zak  wrote:
> hi juan! I'm aware of that ! I want to be able to load a module in a
> new browser window from another module by some action ...say by
> clicking a button
>
> On Aug 11, 10:14 pm, Juan Pablo Gardella 
> wrote:
>
>
>
>
>
>
>
> > You sure use the module: 
>
> > This module is define in gwt-user.jar. Check how is it do. Is this do you
> > need?
>
> > 2011/8/11 Daemon Zak 
>
> > > I want to able to load a gwt module from another gwt module  for eg:
> > > if i click a button ,the new module should be loaded in a new
> > > browser ,with the same session attributes. how do we communicate
> > > between modules i.e . if i want to pass some information from one
> > > module to another and vice versa . any help is greatly appreicated
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to google-web-toolkit@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: multiple gwt modules

[Daemon Zak]

hi juan! I'm aware of that ! I want to be able to load a module in a
new browser window from another module by some action ...say by
clicking a button

On Aug 11, 10:14 pm, Juan Pablo Gardella 
wrote:
> You sure use the module: 
>
> This module is define in gwt-user.jar. Check how is it do. Is this do you
> need?
>
> 2011/8/11 Daemon Zak 
>
>
>
>
>
>
>
> > I want to able to load a gwt module from another gwt module  for eg:
> > if i click a button ,the new module should be loaded in a new
> > browser ,with the same session attributes. how do we communicate
> > between modules i.e . if i want to pass some information from one
> > module to another and vice versa . any help is greatly appreicated
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > To post to this group, send email to google-web-toolkit@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-web-toolkit+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-web-toolkit?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: multiple gwt modules

[Juan Pablo Gardella]

You sure use the module: 

This module is define in gwt-user.jar. Check how is it do. Is this do you
need?


2011/8/11 Daemon Zak 

> I want to able to load a gwt module from another gwt module  for eg:
> if i click a button ,the new module should be loaded in a new
> browser ,with the same session attributes. how do we communicate
> between modules i.e . if i want to pass some information from one
> module to another and vice versa . any help is greatly appreicated
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Multiple GWT modules are compiling really slow!!

[rjcarr]

If I understand what you are saying correctly, then what you describe
is expected.  I think this *might* have changed in GWT 1.7, but I'm
not entirely sure.

If you have one large module then at most all of your code will be
compiled (i.e., translated) once.  However, let's say you have 10
modules and 3 entry points.  If all 3 entry points share, say, 3
common modules, then those common modules will need to be recompiled
for each entry point.  Does this make sense?

On Dec 9, 9:28 am, soc  wrote:
> Hi,
>
> I'm currently spliting up my code base (since it has gotten qute
> large) and i have found something odd, that i was wondering if someone
> could clarify?
>
> I have multiple java projects with GWT modules in each. I then build
> these into a jar  (around 8-9 seperate jars) that can be added to my
> main GWT application's classpath and inherited in the gwt.xml
> descriptor file.
>
> When i use this approach the compile time is anything up to 200+
> second but if i bundle all the code into my main app it compiles in
> less than 40? Even with the localWorkers flags set i can't get it
> below 200 seconds. I've tried compiling for one browser only and some
> other optimizations but i still can't match the single projects speed
> in compilation. I thought it my be a compiler linking performance
> issue?
>
> info: GWT 1.7.1

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Multiple GWT modules and dependencies

[Paul Robinson]

If you can use GWT trunk or wait for GWT 2.0, then what you're
describing sounds very much like code splitting and the associated story
of your compile:
http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting

Paul


Jan Ehrhardt wrote:
> Hi,
>
> I'd like to create a page, which requires different GWT applications,
> but which is dependent to the logged in user. So it doesn't make any
> sence to load one GWT module, which containes hundreds of GWT
> applications, even when only two are required.
> I know, that I can compile each application on it's own and than
> dynamically load the required apps, but this points me to a dependency
> problem. If I use HashMap in one application, it will be compiled as
> other dependencies too into the application's nocache-file and loaded
> at runtime, but if I'm using HashMap in a second application, it will
> be compiled a second time and the resulting JavaScript will be loaded
> into the browser a second time.
>
> This behaviour will make it impossible to create any common libraries,
> which are used by all applications.
>
> A simple example would be the following:
> I've got an application, which shows some content to the user, so a
> normal user will get a slim version of this application. If someone
> also has admin rights, he'll be able to open an admin console and now
> the trouble starts. The way I would like to go is, the slim version
> will be loaded and a further tab for administration will be displayed,
> but until the admin user opens this tab, the part of the application,
> which contains the adminstration *functionality* shouldn't be loaded.
> This would allow me to serve the admin user the slim application as
> fast as all other users and serve the admin application on demand. The
> problem I have is that I want the admin application to use compiled
> code allready loaded with the slim version.
>
> E. g. in Dojo JavaScript framework this problem is solved by using
> dynamic loading of different JavaScript files.
>
> Is there any way to enable GWT for doing something similar?
>
> Jan Ehrhardt
>
>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---