Re: Hello Noob question

['Tim Macpherson' via GWT Users]

On the other hand gwt polymer is unmaintained for 6 years. Also it draws in 
elemental, which is nowadays replaced by elemental2. The 2 dependencies didn't 
cause problems previously but maybe someone else can advise.

Yahoo Mail: Search, Organize, Conquer 
 
  On Tue, Mar 12, 2024 at 23:20, Vijay Kishen Hampapur 
wrote:   Thanks , I figured out that the parent webapp didnt have the
dependency called out. Followed by resources of the .nocache.js not
being part of the jetty xml. Fixed and working now

Thanks

On Tue, Mar 12, 2024 at 9:02 AM 'tim_mac...@yahoo.co.uk' via GWT Users
 wrote:
>
> I am hoping to continue using this with upgrade to gwt 2.11.0 , 
> gwt-maven-plugin 1.1.0 , java source level 11.
> I checked it as far as calling
>    Polymer.startLoading()
>    Polymer.importHref( .. )
> No errors so far.
>
> in module.gwt.xml  I presume you have:
>  
>
> did you add the dependency in the -client pom file?
>    
>      com.vaadin.polymer
>      vaadin-gwt-polymer-elements
>      1.9.3.1
>    
>
> On Tuesday, March 12, 2024 at 7:28:15 AM UTC Vijay H wrote:
>>
>> Created a starter using the modular-webapp archetype, and am trying to 
>> change the client module to use polymer elements and running into these sort 
>> of errors. Before I debug too far wanted to check if this is something that 
>> is doable or even recommended. This is for a class project.
>>
>> > Loading inherited module 'com.mycompany.mywebapp.App'
>> > [INFO]      Loading inherited module 'com.vaadin.polymer.Elements'
>> > [INFO]          [ERROR] Unable to find 
>> > 'com/vaadin/polymer/Elements.gwt.xml' on your classpath; could be a typo, 
>> > or maybe you forgot to include a classpath entry for source?
>>
>>
>> thanks
>> Vijay
>
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "GWT Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/google-web-toolkit/DPT5No0b2KI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit/20efcc19-88ce-477f-8976-821357bfb92dn%40googlegroups.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CAKzfLJKmukv3W87cYsrfVwKe7B42ctzxkEa3DZTtkrqt-TFDqw%40mail.gmail.com.
  

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/963665304.5853729.1710286574424%40mail.yahoo.com.

Re: Hello Noob question

[Vijay Kishen Hampapur]

Thanks , I figured out that the parent webapp didnt have the
dependency called out. Followed by resources of the .nocache.js not
being part of the jetty xml. Fixed and working now

Thanks

On Tue, Mar 12, 2024 at 9:02 AM 'tim_mac...@yahoo.co.uk' via GWT Users
 wrote:
>
> I am hoping to continue using this with upgrade to gwt 2.11.0 , 
> gwt-maven-plugin 1.1.0 , java source level 11.
> I checked it as far as calling
> Polymer.startLoading()
> Polymer.importHref( .. )
> No errors so far.
>
> in module.gwt.xml  I presume you have:
>   
>
> did you add the dependency in the -client pom file?
> 
>   com.vaadin.polymer
>   vaadin-gwt-polymer-elements
>   1.9.3.1
> 
>
> On Tuesday, March 12, 2024 at 7:28:15 AM UTC Vijay H wrote:
>>
>> Created a starter using the modular-webapp archetype, and am trying to 
>> change the client module to use polymer elements and running into these sort 
>> of errors. Before I debug too far wanted to check if this is something that 
>> is doable or even recommended. This is for a class project.
>>
>> > Loading inherited module 'com.mycompany.mywebapp.App'
>> > [INFO]   Loading inherited module 'com.vaadin.polymer.Elements'
>> > [INFO]  [ERROR] Unable to find 
>> > 'com/vaadin/polymer/Elements.gwt.xml' on your classpath; could be a typo, 
>> > or maybe you forgot to include a classpath entry for source?
>>
>>
>> thanks
>> Vijay
>
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "GWT Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/google-web-toolkit/DPT5No0b2KI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit/20efcc19-88ce-477f-8976-821357bfb92dn%40googlegroups.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CAKzfLJKmukv3W87cYsrfVwKe7B42ctzxkEa3DZTtkrqt-TFDqw%40mail.gmail.com.

Re: Hello Noob question

['tim_mac...@yahoo.co.uk' via GWT Users]

I am hoping to continue using this with upgrade to gwt 2.11.0 , 
gwt-maven-plugin 1.1.0 , java source level 11.
I checked it as far as calling
Polymer.startLoading()
Polymer.importHref( .. )
No errors so far.

in module.gwt.xml  I presume you have:
  

did you add the dependency in the -client pom file?

  com.vaadin.polymer
  vaadin-gwt-polymer-elements
  1.9.3.1
 

On Tuesday, March 12, 2024 at 7:28:15 AM UTC Vijay H wrote:

> Created a starter using the modular-webapp archetype, and am trying to 
> change the client module to use polymer elements and running into these 
> sort of errors. Before I debug too far wanted to check if this is something 
> that is doable or even recommended. This is for a class project. 
>
> > Loading inherited module 'com.mycompany.mywebapp.App'
> > [INFO]   Loading inherited module 'com.vaadin.polymer.Elements'
> > [INFO]  [ERROR] Unable to find 
> 'com/vaadin/polymer/Elements.gwt.xml' on your classpath; could be a typo, 
> or maybe you forgot to include a classpath entry for source?
>
>
> thanks
> Vijay 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/20efcc19-88ce-477f-8976-821357bfb92dn%40googlegroups.com.

Hello Noob question

[Vijay H]

Created a starter using the modular-webapp archetype, and am trying to 
change the client module to use polymer elements and running into these 
sort of errors. Before I debug too far wanted to check if this is something 
that is doable or even recommended. This is for a class project. 

> Loading inherited module 'com.mycompany.mywebapp.App'
> [INFO]   Loading inherited module 'com.vaadin.polymer.Elements'
> [INFO]  [ERROR] Unable to find 
'com/vaadin/polymer/Elements.gwt.xml' on your classpath; could be a typo, 
or maybe you forgot to include a classpath entry for source?


thanks
Vijay 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/b88cc06f-d6ea-438a-9d0b-42b883f05dc3n%40googlegroups.com.

Re: JsInterop hello world

[Cristiano]

I use gwt-maven-plugin 2.8.0-SNAPSHOT for no reason in particular, 
but if you use 2.7.0 and you want to compile correctly with version 2.8.0 
of GWT, remember to override the plugin configuration like explained in 
this 
page 
https://gwt-maven-plugin.github.io/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html


  org.codehaus.mojo
  gwt-maven-plugin
  2.7.0
  















*  com.google.gwt  
gwt-user  2.8.0-SNAPSHOT
  com.google.gwt  
gwt-dev  2.8.0-SNAPSHOT
  com.google.gwt  
gwt-codeserver  
2.8.0-SNAPSHOT  *


In the fork of your project I used gwt-maven-plugin 2.8.0-SNAPSHOT only to 
avoid adding these explicit dependencies on the plugin (gwt-maven-plugin 
2.7.0 compiles by default with GWT 2.7.0).


It is weird that you get dependencies resolved on nexus.codehaus.org - btw 
codehaus.org has closed so it make sense it does not work, it is weird that 
it uses it...
I don't know which of your dependencies does it trigger resource resolution 
in that repo.
Keep your git repo up-to-date in case so I can check it exactly if you need 
more help.

bye,

Cristiano


Il giorno giovedì 17 settembre 2015 15:07:20 UTC+2, Brian Pedersen ha 
scritto:
>
> It all makes perfectly sense now, thank's a lot for taking your time to 
> clarify your findings.
>
> I like the concept of the sso linker, a pity it doesn't work with super 
> dev mode yet. 
> Using JsInterop with the xsiframe linker in super dev mode works equally 
> bad for me, but maybe that's just me messing things up ;)
>
> For some reason, I can't build your code with the 2.8.0-SNAPSHOT version 
> of the gwt-maven-plugin.
> I can check out and build the plugin sucessfully, but then when I build 
> your projects, it apparently tries to resolve the gwt dependencies through 
> the nexus.codehaus.org 
> 
>  
> repository and fails.
>
> But it all works perfectly when I build it with the 2.7.0 version of the 
> gwt-maven-plugin, as long as I run it with jetty:run and not gwt:run.
>
> What are your reasons for using the 2.8.0 version of the gwt-maven-plugin?
>
> Thanks ...
> /Brian
>
>
> Den torsdag den 17. september 2015 kl. 10.02.13 UTC+2 skrev Cristiano:
>>
>> Update:
>>
>> with the sso linker the project responds as expected: the GWT code is 
>> available as soon as page has loaded
>>
>> You could check it out on this branch:
>> https://github.com/cristcost/jspoc/tree/test_with_sso
>>
>> note that: 
>> - with sso linker super dev mode don't work (I've worked manually 
>> compiling javascript and testing the compiled code directly)
>> - sso works only if you have exactly one permutation, and to obtain 
>> exactly 1 permutation I've removed inheritance of 
>> 'com.google.gwt.user.User' module (in fact your example was not using 
>> anything from that module)
>>
>>
>>
>>
>>
>> Il giorno giovedì 17 settembre 2015 09:18:34 UTC+2, Cristiano ha scritto:
>>>
>>> Hi Brian,
>>>
>>> I had problems similar to you when studying JsInterop, so I've tried 
>>> your code.
>>> I've forked your repo (see https://github.com/cristcost/jspoc) and I 
>>> have made it work but with some considerations to take into account.
>>> Other than the problems on using JsInterop annotations as reported by 
>>> Jens, I've found a script load timing issue:
>>> you execute the the Javascript code in the main page script, but at that 
>>> point GWT has not yet loaded!
>>>
>>> Putting the execution of your javascript code inside window.onload event 
>>> is not again enough: I think this is because of using the xsiframe linker 
>>> (I'm curious to try out with the sso linker).
>>> So I have used a 3 seconds timeout... 
>>>
>>> In the fork I've added some console logging to outline the time each 
>>> part of the Javascript is executed, and the order is:
>>> - first javascript inside main html page is executed
>>> - then javascript inside the window.onload
>>> - finally the GWT entry point
>>>
>>> Your javascript code, with the fixes suggested by Jens, has worked after 
>>> a 3 seconds timeout.
>>>
>>> Of course I don't like this workaround, but a more general approach 
>>> could be to have your application started from the GWT entry point (i.e. 
>>> define a "main" function in javascript, then run it from GWT entry point). 
>>> If you don't like the ping-pong between JS and GWT, you may try different 
>>> solution to detect when GWT has loaded, or - if the problem is the xsiframe 
>>> linker - try another linker.
>>>
>>>
>>> Please note that I've changed totally the pom.xml and copied 
>>> configuration from one of mines: in particular I have added a configuration 
>>> for maven-jetty-plugin, 
>>> so to try it out you need can execute the following commands:
>>>
>>> git clone https://github.com/cristcost/jspoc.git
>>> cd jspoc
>>> mvn clean install
>>> mvn jetty:run
>>>
>>>
>>> After this you should be able to op

Re: JsInterop hello world

[Brian Pedersen]

It all makes perfectly sense now, thank's a lot for taking your time to 
clarify your findings.

I like the concept of the sso linker, a pity it doesn't work with super dev 
mode yet. 
Using JsInterop with the xsiframe linker in super dev mode works equally 
bad for me, but maybe that's just me messing things up ;)

For some reason, I can't build your code with the 2.8.0-SNAPSHOT version of 
the gwt-maven-plugin.
I can check out and build the plugin sucessfully, but then when I build 
your projects, it apparently tries to resolve the gwt dependencies through 
the nexus.codehaus.org repository and fails.

But it all works perfectly when I build it with the 2.7.0 version of the 
gwt-maven-plugin, as long as I run it with jetty:run and not gwt:run.

What are your reasons for using the 2.8.0 version of the gwt-maven-plugin?

Thanks ...
/Brian


Den torsdag den 17. september 2015 kl. 10.02.13 UTC+2 skrev Cristiano:
>
> Update:
>
> with the sso linker the project responds as expected: the GWT code is 
> available as soon as page has loaded
>
> You could check it out on this branch:
> https://github.com/cristcost/jspoc/tree/test_with_sso
>
> note that: 
> - with sso linker super dev mode don't work (I've worked manually 
> compiling javascript and testing the compiled code directly)
> - sso works only if you have exactly one permutation, and to obtain 
> exactly 1 permutation I've removed inheritance of 
> 'com.google.gwt.user.User' module (in fact your example was not using 
> anything from that module)
>
>
>
>
>
> Il giorno giovedì 17 settembre 2015 09:18:34 UTC+2, Cristiano ha scritto:
>>
>> Hi Brian,
>>
>> I had problems similar to you when studying JsInterop, so I've tried your 
>> code.
>> I've forked your repo (see https://github.com/cristcost/jspoc) and I 
>> have made it work but with some considerations to take into account.
>> Other than the problems on using JsInterop annotations as reported by 
>> Jens, I've found a script load timing issue:
>> you execute the the Javascript code in the main page script, but at that 
>> point GWT has not yet loaded!
>>
>> Putting the execution of your javascript code inside window.onload event 
>> is not again enough: I think this is because of using the xsiframe linker 
>> (I'm curious to try out with the sso linker).
>> So I have used a 3 seconds timeout... 
>>
>> In the fork I've added some console logging to outline the time each part 
>> of the Javascript is executed, and the order is:
>> - first javascript inside main html page is executed
>> - then javascript inside the window.onload
>> - finally the GWT entry point
>>
>> Your javascript code, with the fixes suggested by Jens, has worked after 
>> a 3 seconds timeout.
>>
>> Of course I don't like this workaround, but a more general approach could 
>> be to have your application started from the GWT entry point (i.e. define a 
>> "main" function in javascript, then run it from GWT entry point). If you 
>> don't like the ping-pong between JS and GWT, you may try different solution 
>> to detect when GWT has loaded, or - if the problem is the xsiframe linker - 
>> try another linker.
>>
>>
>> Please note that I've changed totally the pom.xml and copied 
>> configuration from one of mines: in particular I have added a configuration 
>> for maven-jetty-plugin, 
>> so to try it out you need can execute the following commands:
>>
>> git clone https://github.com/cristcost/jspoc.git
>> cd jspoc
>> mvn clean install
>> mvn jetty:run
>>
>>
>> After this you should be able to open your browser at 
>> http://localhost:/ and you should see the alert popup (but 3 seconds 
>> after the page load!)
>>
>> Hope this is helpful,
>>
>> Cristiano
>>
>>
>> PS. I'm using gwt 2.8.0-SNAPSHOT and also gwt-maven-plugin 2.8.0-SNAPSHOT 
>> that I have compiled personally, so I don't have added the repo on the 
>> pom.xml,
>> you should re-add it from your pom.xml or compile the two by yourself. 
>> The gwt-maven-plugin 2.8.0-SNAPSHOT is available at 
>> https://github.com/gwt-maven-plugin/gwt-maven-plugin and I compile it 
>> skipping the tests with
>>
>>  mvn clean install -DskipTests 
>>
>>
>>
>>
>>
>>
>>
>>

-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: JsInterop hello world

[Cristiano]

Update:

with the sso linker the project responds as expected: the GWT code is 
available as soon as page has loaded

You could check it out on this branch:
https://github.com/cristcost/jspoc/tree/test_with_sso

note that: 
- with sso linker super dev mode don't work (I've worked manually compiling 
javascript and testing the compiled code directly)
- sso works only if you have exactly one permutation, and to obtain exactly 
1 permutation I've removed inheritance of 'com.google.gwt.user.User' module 
(in fact your example was not using anything from that module)





Il giorno giovedì 17 settembre 2015 09:18:34 UTC+2, Cristiano ha scritto:
>
> Hi Brian,
>
> I had problems similar to you when studying JsInterop, so I've tried your 
> code.
> I've forked your repo (see https://github.com/cristcost/jspoc) and I have 
> made it work but with some considerations to take into account.
> Other than the problems on using JsInterop annotations as reported by 
> Jens, I've found a script load timing issue:
> you execute the the Javascript code in the main page script, but at that 
> point GWT has not yet loaded!
>
> Putting the execution of your javascript code inside window.onload event 
> is not again enough: I think this is because of using the xsiframe linker 
> (I'm curious to try out with the sso linker).
> So I have used a 3 seconds timeout... 
>
> In the fork I've added some console logging to outline the time each part 
> of the Javascript is executed, and the order is:
> - first javascript inside main html page is executed
> - then javascript inside the window.onload
> - finally the GWT entry point
>
> Your javascript code, with the fixes suggested by Jens, has worked after a 
> 3 seconds timeout.
>
> Of course I don't like this workaround, but a more general approach could 
> be to have your application started from the GWT entry point (i.e. define a 
> "main" function in javascript, then run it from GWT entry point). If you 
> don't like the ping-pong between JS and GWT, you may try different solution 
> to detect when GWT has loaded, or - if the problem is the xsiframe linker - 
> try another linker.
>
>
> Please note that I've changed totally the pom.xml and copied configuration 
> from one of mines: in particular I have added a configuration for 
> maven-jetty-plugin, 
> so to try it out you need can execute the following commands:
>
> git clone https://github.com/cristcost/jspoc.git
> cd jspoc
> mvn clean install
> mvn jetty:run
>
>
> After this you should be able to open your browser at 
> http://localhost:/ and you should see the alert popup (but 3 seconds 
> after the page load!)
>
> Hope this is helpful,
>
> Cristiano
>
>
> PS. I'm using gwt 2.8.0-SNAPSHOT and also gwt-maven-plugin 2.8.0-SNAPSHOT 
> that I have compiled personally, so I don't have added the repo on the 
> pom.xml,
> you should re-add it from your pom.xml or compile the two by yourself. The 
> gwt-maven-plugin 2.8.0-SNAPSHOT is available at 
> https://github.com/gwt-maven-plugin/gwt-maven-plugin and I compile it 
> skipping the tests with
>
>  mvn clean install -DskipTests 
>
>
>
>
>
>
>
>

-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: JsInterop hello world

[Cristiano]

Hi Brian,

I had problems similar to you when studying JsInterop, so I've tried your 
code.
I've forked your repo (see https://github.com/cristcost/jspoc) and I have 
made it work but with some considerations to take into account.
Other than the problems on using JsInterop annotations as reported by Jens, 
I've found a script load timing issue:
you execute the the Javascript code in the main page script, but at that 
point GWT has not yet loaded!

Putting the execution of your javascript code inside window.onload event is 
not again enough: I think this is because of using the xsiframe linker (I'm 
curious to try out with the sso linker).
So I have used a 3 seconds timeout... 

In the fork I've added some console logging to outline the time each part 
of the Javascript is executed, and the order is:
- first javascript inside main html page is executed
- then javascript inside the window.onload
- finally the GWT entry point

Your javascript code, with the fixes suggested by Jens, has worked after a 
3 seconds timeout.

Of course I don't like this workaround, but a more general approach could 
be to have your application started from the GWT entry point (i.e. define a 
"main" function in javascript, then run it from GWT entry point). If you 
don't like the ping-pong between JS and GWT, you may try different solution 
to detect when GWT has loaded, or - if the problem is the xsiframe linker - 
try another linker.


Please note that I've changed totally the pom.xml and copied configuration 
from one of mines: in particular I have added a configuration for 
maven-jetty-plugin, 
so to try it out you need can execute the following commands:

git clone https://github.com/cristcost/jspoc.git
cd jspoc
mvn clean install
mvn jetty:run


After this you should be able to open your browser 
at http://localhost:/ and you should see the alert popup (but 3 seconds 
after the page load!)

Hope this is helpful,

Cristiano


PS. I'm using gwt 2.8.0-SNAPSHOT and also gwt-maven-plugin 2.8.0-SNAPSHOT 
that I have compiled personally, so I don't have added the repo on the 
pom.xml,
you should re-add it from your pom.xml or compile the two by yourself. The 
gwt-maven-plugin 2.8.0-SNAPSHOT is available at 
https://github.com/gwt-maven-plugin/gwt-maven-plugin and I compile it 
skipping the tests with

 mvn clean install -DskipTests 







-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: JsInterop hello world

[Brian Pedersen]

Thank's Jens, your help is much appreciated. For now I will definitely go 
for a no-renaming approach.

It must be something with the way I run my code server.

I still get the same error, and when I inspect the generated javascript in 
my browser, it still has the obfuscated format. 
The generated javascript in the war file however, looks much better.

Maybe I just need to get the configuration of my gwt-maven-plugin right.

Thanks...
/Brian

Den tirsdag den 15. september 2015 kl. 23.32.36 UTC+2 skrev Jens:
>
> Ok just played a bit and its like the following:
>
>
> @JsExport // value attribute is ignored here, probably because it acts as 
> a shortcut to apply @JsExport to any static member
> @JsType // required so you also have exported instance members (your 
> sayHello method) and not just static members
> @JsNamespace("poc") // the default namespace, should probably go in a 
> package-info.java file
> public class JsHello {
>  public String sayHello(String name) {
>return "Hello " + name;
>  }
> }
>
> With the above you can do
>
>   
> var hello = new poc.JsHello(); hello.sayHello("World");
>
>
> If you want to rename JsHello to Hello you do
>
> @JsExport
> @JsType
> public class JsHello {
>  
>  @JsExport("poc.Hello") // replaces any @JsNamespace default value so you 
> need to add namespace here
>  public JsHello() {}
>  
>  public String sayHello(String name) {
>return "Hello " + name;
>  }
> }
>
>
> I would try to avoid renaming, as you must repeat the namespace in 
> @JsExport. Just name your classes correctly and stick with the first 
> example with @JsNamespace in a package-info.java file.
>
> -- J.
>

-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: JsInterop hello world

[Jens]

Ok just played a bit and its like the following:


@JsExport // value attribute is ignored here, probably because it acts as a 
shortcut to apply @JsExport to any static member
@JsType // required so you also have exported instance members (your 
sayHello method) and not just static members
@JsNamespace("poc") // the default namespace, should probably go in a 
package-info.java file
public class JsHello {
 public String sayHello(String name) {
   return "Hello " + name;
 }
}

With the above you can do

  
var hello = new poc.JsHello(); hello.sayHello("World");


If you want to rename JsHello to Hello you do

@JsExport
@JsType
public class JsHello {
 
 @JsExport("poc.Hello") // replaces any @JsNamespace default value so you 
need to add namespace here
 public JsHello() {}
 
 public String sayHello(String name) {
   return "Hello " + name;
 }
}


I would try to avoid renaming, as you must repeat the namespace in 
@JsExport. Just name your classes correctly and stick with the first 
example with @JsNamespace in a package-info.java file.

-- J.

-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: JsInterop hello world

[Brian Pedersen]

That didn't seem to make much of a difference, the generated javascript 
still have the wrong identifiers, and the error message is the same :(

I wonder if there is something wrong with my build, it looks to me as if 
the annotations are ignored.
I know that I run gwt 2.8, as I did a lambda to verify that, and I can see 
that the code server is started with '-XjsInteropMode, JS'.

Could I simplify it further, by removing the namespace or something?

Thanks ...

/Brian

Den tirsdag den 15. september 2015 kl. 14.46.01 UTC+2 skrev Brian Pedersen:
>
> So I am doing my first baby-steps in JsInterop, exposing a Java class to 
> javascript, and I can't seem to figure out what I am doing wrong.
>
> *My java class looks like this:*
> @JsExport("poc.Hello") 
> public class JsHello  {
>   public String sayHello(String name) {
> return "Hello " + name;
>   }
> }
>
> *And the javascript in my host page like this:*
> var obj = new poc.Hello();
> alert(obj.sayHello("there"));
>
> *My browser complains about 'poc' being undefined:*
> Uncaught ReferenceError: poc is not defined
>
> *Which is understandable, when looking at the implementation generated:*
> _.sayHello_0_g$ = function Cyb_g$(name_0_g$){
>   return 'Hello ' + name_0_g$;
> }
> ;
> var Ldk_bitwerk_client_JsHello_2_classLit_0_g$ = cDb_g$(
> 'dk.bitwerk.client', 'JsHello', 428, Ljava_lang_Object_2_classLit_0_g$);
>
> I have tried all sorts of things, such using the real package/class name 
> inside @JsExport, omiting the package/class name inside @JsExport and 
> adding @JsType to the class declaration.
> I have also tried annotating a constructor instead of the class.
>
> I am running gwt-2.8.0-snapshot with jsInteropMode=JS, and I have 
> committed the code here: https://github.com/bitwerk/jspoc
>
> Any help will be much appreciated ...
>
> /Brian
>

-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: JsInterop hello world

[Jens]

@JsNamespace("$wnd.poc")
@JsExport("Hello")
@JsType
public class JsHello {
 public String sayHello(String name) {
   return "Hello " + name;
 }
}



I think the above should work. But there is already a commit pending which 
introduces new annotations for JsInterop which should make things a bit 
easier. The above example with new annotations would look like

@JsType(namespace = "poc", name = "Hello", export = true)
public class JsHello {
 public String sayHello(String name) {
   return "Hello " + name;
 }
}


-- J.

-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

JsInterop hello world

[Brian Pedersen]

So I am doing my first baby-steps in JsInterop, exposing a Java class to 
javascript, and I can't seem to figure out what I am doing wrong.

*My java class looks like this:*
@JsExport("poc.Hello") 
public class JsHello  {
  public String sayHello(String name) {
    return "Hello " + name;
  }
}

*And the javascript in my host page like this:*
var obj = new poc.Hello();
alert(obj.sayHello("there"));

*My browser complains about 'poc' being undefined:*
Uncaught ReferenceError: poc is not defined

*Which is understandable, when looking at the implementation generated:*
_.sayHello_0_g$ = function Cyb_g$(name_0_g$){
  return 'Hello ' + name_0_g$;
}
;
var Ldk_bitwerk_client_JsHello_2_classLit_0_g$ = cDb_g$('dk.bitwerk.client', 
'JsHello', 428, Ljava_lang_Object_2_classLit_0_g$);

I have tried all sorts of things, such using the real package/class name 
inside @JsExport, omiting the package/class name inside @JsExport and 
adding @JsType to the class declaration.
I have also tried annotating a constructor instead of the class.

I am running gwt-2.8.0-snapshot with jsInteropMode=JS, and I have committed 
the code here: https://github.com/bitwerk/jspoc

Any help will be much appreciated ...

/Brian

-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Error "Address already in use: JVM_Bind" when running Hello GWT app in NetBeans 7.3 Beta 2

[otosaat]

I went back and read similar posts and realized that they all indicated a 
specific port number. The error in my run does not. I went back and 
reviewed the steps in the instruction, 
http://netbeans.org/kb/docs/web/quickstart-webapps-gwt.html#creating, 
again, I found one mistake: Instead of choosing "Google Web Toolkit" from 
the Framework list, I chose it from the Project dialog box. That was the 
problem. I re-created another Hello project and it works now.


On Saturday, December 8, 2012 1:25:57 PM UTC-5, otosaat wrote:
>
> I followed the instruction from the following link: 
> http://netbeans.org/kb/docs/web/quickstart-webapps-gwt.html#creating 
> and got the following error when I run the project: 
> [gae:run] 
> Monitor failed to start 
> java.net.BindException: Address already in use: JVM_Bind 
> at java.net.DualStackPlainSocketImpl.bind0(Native Method) 
>
> I've searched for a 
> solution<http://forums.netbeans.org/viewtopic.php?t=52648&highlight=#> on 
> the web but could not find one. Would someone please give me some pointer 
> on this? Also, is there a way for me to configure the NetBeans IDE to use a 
> dynamic port everytme I run a web 
> project<http://forums.netbeans.org/viewtopic.php?t=52648&highlight=#>
> ? 
>
> Thank you in advance for your help. 
>
> -Otosaat
>

-- 
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/-/pxGH-WYH_nEJ.
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.

Error "Address already in use: JVM_Bind" when running Hello GWT app in NetBeans 7.3 Beta 2

[otosaat]

I followed the instruction from the following link: 
http://netbeans.org/kb/docs/web/quickstart-webapps-gwt.html#creating 
and got the following error when I run the project: 
[gae:run] 
Monitor failed to start 
java.net.BindException: Address already in use: JVM_Bind 
at java.net.DualStackPlainSocketImpl.bind0(Native Method) 

I've searched for a 
solution on 
the web but could not find one. Would someone please give me some pointer 
on this? Also, is there a way for me to configure the NetBeans IDE to use a 
dynamic port everytme I run a web 
project
? 

Thank you in advance for your help. 

-Otosaat

-- 
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/-/2kjanyk8jDYJ.
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: Hello, please I need your help with "did you forget to inherit a required module"

[Alberto Mancini]

Hi,
afaik java.security is not in the GWT's emulated jre so you should provide
an implementation for SecureRandom
(through super-source, see
https://developers.google.com/web-toolkit/doc/latest/DevGuideOrganizingProjects
)
to be able to use jBCrypt unmodified.


Ciao,
   Alberto


On Mon, Nov 26, 2012 at 1:17 PM, Nicolas Moraes <
nicolas.mor...@mercadolibre.com> wrote:

> Dear all:
>
> When I running my GWT app, I have the following error :
>
> No source code is available for type java.security.SecureRandom; did you
> forget to inherit a required module.
>
> This error occurs after include a security class,
> http://www.mindrot.org/projects/jBCrypt/
>
> I read a lot of different solution however I can't find the solution.
>
> Thank a lot guys, Your help will be very appreciate.
>
> Nicolas.
>
>
>  --
> 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/-/tqdplM8TzoIJ.
> 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.

Hello, please I need your help with "did you forget to inherit a required module"

[Nicolas Moraes]

Dear all: 

When I running my GWT app, I have the following error :

No source code is available for type java.security.SecureRandom; did you 
forget to inherit a required module.

This error occurs after include a security 
class, http://www.mindrot.org/projects/jBCrypt/

I read a lot of different solution however I can't find the solution.

Thank a lot guys, Your help will be very appreciate.

Nicolas.


-- 
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/-/tqdplM8TzoIJ.
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.

GWT tutorial, UiBinder "Hello World" with Eclipse from Ground-up

[infovation Associates]

Hello sir,

posting this link here since i think many newbies will be here hoping to 
learn GWT.

*GWT UiBinder Hello world with Eclipse from Ground-up (without generated 
GWT Sample code project), but here we wont cover installation of Chrome or 
Eclipse or GPE, since there are tons of good tutorials on them out there, 
so thats not a big problem to deal with.
 *.

http://infovation.skyrock.com/3067170683-GWT-tutorial-UiBinder-Hello-World-with-Eclipse-from-Ground-up.html

-- 
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/-/9mrbrYOrp_wJ.
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.

Hello

[Dhruv April]

Hey,I Please Intrt me.:)

-- 
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.

hello

[袁红杰]

hello,i sent so much email,i don´t know why and how to quit!

-- 
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.

help needed in debuging the hello world web application

[thahir hussain]

hi i am getting this error when i run my hello world application in
eclipse

Status: 404 Not Found
 Content-Type: text/html;
charset=utf-8
Cache-Control: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Content-Length: 0
need help pls help

-- 
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: Hello Sample doesn't work in Chrome. Issues with invoking onScriptLoad()

[Thomas Broyer]

On Sep 30, 12:44 pm, Denis Vilyuzhanin  wrote:
> Thanks, it was surprise for me, that chrome has such policy about
> local files.

Scenario:
1. make a request to file:///etc/passwd to grab its content (GET with
XMLHttpRequest, or loading it in an iframe)
2. make a cross-site request (XMLHttpRequest with CORS, or simply a
, or even a 

Re: Hello Sample doesn't work in Chrome. Issues with invoking onScriptLoad()

[Denis Vilyuzhanin]

Thanks, it was surprise for me, that chrome has such policy about
local files.

On Sep 30, 3:11 am, Thomas Broyer  wrote:
> On Sep 30, 10:15 am, Denis Vilyuzhanin  wrote:
>
> > I compiled Hello Sample from GWT SDK and tried to run it in Chrome.
> > But it doesn't work. Only empty page. In IE and Firefox it works fine.
> > After some debugging I found that cause of this.
> > In  last rows of any *.cache.html (not hello.nocache.js) gwt compiler
> > append following code
> >       if ($wnd.hello) $wnd.hello.onScriptLoad();
> > but $wnd.hello is undefined. So onScriptLoad() function isn't invoked.
> > In firefox and IE $wnd.hello equals to hello() function from
> > hello.nocache.js which boots GWT module. hello() function store in
> > itself code which complete module initialization after all js and
> > resources loaded. So if onScriptLoad isn't invoked  the initialization
> > never done.
>
> > Does anybody have this issues with their chrome?
>
> If you're loading the app from your disk, you're actually running into
> a SOP violation. Chrome (and IIRC it'll also be the case for Firefox
> 4) treat each file as coming from a different origin. It'll work if
> you either load the app from a HTTP server, or compile using the
> "cross-site" linker ()

-- 
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: Hello Sample doesn't work in Chrome. Issues with invoking onScriptLoad()

[Thomas Broyer]

On Sep 30, 10:15 am, Denis Vilyuzhanin  wrote:
> I compiled Hello Sample from GWT SDK and tried to run it in Chrome.
> But it doesn't work. Only empty page. In IE and Firefox it works fine.
> After some debugging I found that cause of this.
> In  last rows of any *.cache.html (not hello.nocache.js) gwt compiler
> append following code
>       if ($wnd.hello) $wnd.hello.onScriptLoad();
> but $wnd.hello is undefined. So onScriptLoad() function isn't invoked.
> In firefox and IE $wnd.hello equals to hello() function from
> hello.nocache.js which boots GWT module. hello() function store in
> itself code which complete module initialization after all js and
> resources loaded. So if onScriptLoad isn't invoked  the initialization
> never done.
>
> Does anybody have this issues with their chrome?

If you're loading the app from your disk, you're actually running into
a SOP violation. Chrome (and IIRC it'll also be the case for Firefox
4) treat each file as coming from a different origin. It'll work if
you either load the app from a HTTP server, or compile using the
"cross-site" linker ()

-- 
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.

Hello Sample doesn't work in Chrome. Issues with invoking onScriptLoad()

[Denis Vilyuzhanin]

I compiled Hello Sample from GWT SDK and tried to run it in Chrome.
But it doesn't work. Only empty page. In IE and Firefox it works fine.
After some debugging I found that cause of this.
In  last rows of any *.cache.html (not hello.nocache.js) gwt compiler
append following code
  if ($wnd.hello) $wnd.hello.onScriptLoad();
but $wnd.hello is undefined. So onScriptLoad() function isn't invoked.
In firefox and IE $wnd.hello equals to hello() function from
hello.nocache.js which boots GWT module. hello() function store in
itself code which complete module initialization after all js and
resources loaded. So if onScriptLoad isn't invoked  the initialization
never done.

Does anybody have this issues with their chrome?

-- 
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: Hello.. A gift!!!

[Gal Dolber]

what the hell

2010/6/28 Lei Zhen 

> Dear friend,
> One of my good friend is having his birthday celebration very soon,and
> I bought a digital camera for him as a birthday gift at an
> international trade company  ,I received the goods
> today,it has very good quality and affordable price. The company also
> sells some well-known branded laptop computers,cellphones,game
> consoles and so on,they really have a wide range of products,you can
> go and see if you have interests,thanks!
>
> --
> 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.
>
>

-- 
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.

Hello.. A gift!!!

[Lei Zhen]

Dear friend,
One of my good friend is having his birthday celebration very soon,and
I bought a digital camera for him as a birthday gift at an
international trade company  ,I received the goods
today,it has very good quality and affordable price. The company also
sells some well-known branded laptop computers,cellphones,game
consoles and so on,they really have a wide range of products,you can
go and see if you have interests,thanks!

-- 
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.

Hello

[Brad Stimpson]

http://sites.google.com/site/dfgbn467u5jnbd/ndds5w

-- 
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: The output directory for the project should be set to /Hello/war/WEB-INF/classes

[Nathan Wells]

look at this issue:

http://code.google.com/p/google-web-toolkit/issues/detail?id=3583&q=build%20folder

vote for it, please.

On Oct 26, 1:03 pm, thirdnormal  wrote:
> I am setting up the Hello sample GWT project using the Google Plugin
> for Eclipse. However when I change the output directory for the
> compiled code (in the Eclipse build path configuration) I get the
> following error message in my problems view...
>
> The output directory for the project should be set to /Hello/war/WEB-
> INF/classes
>
> For all other modules in our application we use the /build  directory
> as the destination for the compiled code. Is there a way to change
> this default in the google plugin? It would be very helpful to have a
> consistant project structure across our code base.
>
> I have poked around the configuration dialogs and looked in the usual
> files that eclipse creates for maintaining configuration
> (.project, .classpath, .settings/*, etc) but don't see anything that
> hints at a solution.
>
> Thanks for any ideas.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

The output directory for the project should be set to /Hello/war/WEB-INF/classes

[thirdnormal]

I am setting up the Hello sample GWT project using the Google Plugin
for Eclipse. However when I change the output directory for the
compiled code (in the Eclipse build path configuration) I get the
following error message in my problems view...

The output directory for the project should be set to /Hello/war/WEB-
INF/classes

For all other modules in our application we use the /build  directory
as the destination for the compiled code. Is there a way to change
this default in the google plugin? It would be very helpful to have a
consistant project structure across our code base.

I have poked around the configuration dialogs and looked in the usual
files that eclipse creates for maintaining configuration
(.project, .classpath, .settings/*, etc) but don't see anything that
hints at a solution.

Thanks for any ideas.


--~--~-~--~~~---~--~~
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: HELLO MODERATOR

[Sumit Chandel]

Hi eags,
Sorry for the delay in moderation. Unfortunately I'm the primary moderator
for the forum, and so posting in a different timezone does sometimes add a
bit more delay than I'd like to a post. Perhaps I should try a polyphasic
sleep schedule :-)

Regarding moderated posts - you should be cleared for posting now that your
first post has gone through. I only check the first post for new users
registered to the forum for spam. If that clears, then you become free to
post in the future without moderation. That said, I'm afraid there isn't
much I can do about changing the timestamp on the previously moderated
message. I'm guessing that this post referencing the previous post should
get enough attention on it so that other group members will post up.

Sorry again for the delay,
-Sumit Chandel

On Tue, Jun 9, 2009 at 11:03 AM, eags  wrote:

>
> Hi.  I posted a comment last night starting a new thread called "Very
> basic LoginSecurityFAQ and GWT-RPC questions".  I guess because of the
> moderation it wasn't actually posted until about a half an hour ago
> but the timestamp on it still is for last night which means that it is
> buried in last nights conversations and no one is seeing it.
>
> So I have two questions:
>
> 1. Should I repost?  Or is it possible for you to reset the timestamp
> so it gets seen?
> 2. How do I become a regular user and not get moderated anymore?  Is
> it a certain number of posts?  Or is it a certain average rating on my
> posts?  Thanks.
>
>
> >
>

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

HELLO MODERATOR

[eags]

Hi.  I posted a comment last night starting a new thread called "Very
basic LoginSecurityFAQ and GWT-RPC questions".  I guess because of the
moderation it wasn't actually posted until about a half an hour ago
but the timestamp on it still is for last night which means that it is
buried in last nights conversations and no one is seeing it.

So I have two questions:

1. Should I repost?  Or is it possible for you to reset the timestamp
so it gets seen?
2. How do I become a regular user and not get moderated anymore?  Is
it a certain number of posts?  Or is it a certain average rating on my
posts?  Thanks.


--~--~-~--~~~---~--~~
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: Hello Everybody - need help with an GWT interface

[Sumit Chandel]

Hi Thib'z,

Once you've coded up your GWT application, you would then deploy it by
running the GWT cross-compiler over your source code to generate the
corresponding JavaScript and HTML files.

If you used the applicationCreator script to create your application, there
will be an emitted MyApplication-compile and MyApplication-shell scripts.
The -compile script is the GWT compilation script you can use to invoke the
GWT cross-compiler and generate your application JavaScript and HTML files.
Once these files are generated, all you need to do is host them on a web
server to start serving up your application.

Among the files you'll find a bunch of .cache.js files and a more
properly named MyApplication.nocache.js file. The .nocache.js file is your
GWT application bootstrap file. Add a 

Re: Hello Everybody - need help with an GWT interface

[Thib'z]

I have one remaining question : once the interface is build, what must
I do to put it online ? Which files must I use ?
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Hello Everybody - need help with an GWT interface

[[EMAIL PROTECTED]]

My advise is to look at this website:

http://examples.roughian.com/#Home

also to look at all the sample code and documentation that is provided
on the GWT site:

http://code.google.com/webtoolkit/

You might consider picking up a book or two, I whole heartedly
recommend any of the books available:

http://www.amazon.com/s/ref=nb_ss_gw?url=search-alias%3Daps&field-keywords=gwt

Start there, and then post your example code that isn't working here,
and perhaps the community can come to your assistance.

Later,

Shaffer

On Dec 8, 6:49 am, "Thib'z" <[EMAIL PROTECTED]> wrote:
> Hello everybody, I'm a beginner with GWT and JavaScript, and I would
> like to create a simple interface, with a TabPanel, including 3 tabs,
> and each one including 3 groups of 7 ChekBoxes(Led Controllers), and a
> Button per Tab.
>
> But I having a little trouble declaring the Checkboxes, and including
> them in each tab.
>
> Can somebody help me ? It would save my life... :-D
>
> Thanks, and excuse my english...
>
> Thib'z
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Hello Everybody - need help with an GWT interface

[Thib'z]

Hello everybody, I'm a beginner with GWT and JavaScript, and I would
like to create a simple interface, with a TabPanel, including 3 tabs,
and each one including 3 groups of 7 ChekBoxes(Led Controllers), and a
Button per Tab.

But I having a little trouble declaring the Checkboxes, and including
them in each tab.

Can somebody help me ? It would save my life... :-D

Thanks, and excuse my english...

Thib'z

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Hello~. How about this realtime chatting program by using GWT 1.5 ?

[Macula]

AKA Tost Chatting Programming.

http://tost.rontab.com"; target=_blank>Http://tost.rontab.com




http://tost.rontab.com/com.rontab.tost.chat.Tost/tost.html?
room=Bake width=600 height=500 frameborder=0>

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---