Friday, July 31, 2015

Re: celllist multi select opens current page in new window?

Me again...

This code seems to work (and I'm posting it here in case it helps someone else).  If anyone thinks this will cause issues somewhere else, and is kind enough to respond, I appreciate it!
        // trap the shift-click || ctrl-click launch of a new browser window.
        cellList.addCellPreviewHandler(new CellPreviewEvent.Handler()
        {
            @Override
            public void onCellPreview(final CellPreviewEvent event)
            {
                NativeEvent evt = event.getNativeEvent();

                //shift-click || ctrl-click
                if ((BrowserEvents.CLICK.equals(evt.getType())) &&
                        ((evt.getShiftKey()) || (evt.getCtrlKey())) )
                {
                    //Window.alert("Shift-Click Event");

                    event.setCanceled(true);
                    event.getNativeEvent().stopPropagation();
                    event.getNativeEvent().preventDefault();
                }
            }
        });

-AJ

--
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 google-web-toolkit+unsubscribe@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: celllist multi select opens current page in new window?

So..upon further review...this appears to be a general event handled by "current" browsers.  Shift-Click a link and it opens in a new tab/window.

So I guess I would like to trap the event before it gets to the DOM/window layer?  I tried adding a CellPreviewHandler and checking whether it's a shift-click, and if so, canceling the event and stopPropagation() on the NativeEvent, but this doesn't seem to have any effect.  Is there a different handler/place that I should be trapping the shift (and ctrl) click events?

Thanks,
AJ

--
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 google-web-toolkit+unsubscribe@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.

celllist multi select opens current page in new window?

I would think I tested this before, but during some testing of my gwt page today I noticed that when I try to multi-select from my cellist, "something" is firing and opening a new window/tab with my current page.

My multiselect for the celllist is simple:
        // Add a selection model using the same keyProvider.
        final MultiSelectionModel<docWithId> selectionModel = new MultiSelectionModel(keyProvider);
        cellList.setSelectionModel(selectionModel);


When I try to "shift-select" or "ctrl-select" in Chrome or IE11 (on Windows 8), a new window launches!

If anyone has any ideas where to start troubleshooting this, I would appreciate it.

-AJ

--
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 google-web-toolkit+unsubscribe@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: GWT release prioritization

+1

On Fri, Jul 31, 2015 at 7:29 PM, Michael Joyner <michael@newsrx.com> wrote:
+1 to the +1
On 07/31/2015 09:24 AM, Ed wrote:
+1

organizations can be very hesitant to use non-GA versions of libraries. In particular it would be a big win to have a "done" version of JsInterop v1 and clear guidance on using the current version of elemental.



--
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 google-web-toolkit+unsubscribe@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.



--
Nagin Kothari
Co-founder,
Zilicus Solutions
www.zilicus.com

--
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 google-web-toolkit+unsubscribe@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: GWT release prioritization

+1 to the +1
On 07/31/2015 09:24 AM, Ed wrote:
+1

organizations can be very hesitant to use non-GA versions of libraries. In particular it would be a big win to have a "done" version of JsInterop v1 and clear guidance on using the current version of elemental.



Re: GWT release prioritization

+1

On Fri, Jul 31, 2015 at 5:37 AM, James Horsley <james.horsley@gmail.com> wrote:
Firstly, I am very much looking forward to the next generation j2cl compiler for GWT and think the new compiler vision is great. That said, I think the community would benefit greatly with the steering committee placing a higher priority on closing out on the 2.8 release. I know that the current 2.8 is considered usable for production but 2.8 isn't feature complete and organizations can be very hesitant to use non-GA versions of libraries. In particular it would be a big win to have a "done" version of JsInterop v1 and clear guidance on using the current version of elemental.

I, and I'm sure the rest of the GWT community, would greatly appreciate a clearer view on current release expectations and prioritization; is there anything you guys can share on that front?

Again, really appreciate the recent work and love the plans for GWT 3.0.

Cheers,
James

--
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 google-web-toolkit+unsubscribe@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.

--
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 google-web-toolkit+unsubscribe@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.

GWT release prioritization

Firstly, I am very much looking forward to the next generation j2cl compiler for GWT and think the new compiler vision is great. That said, I think the community would benefit greatly with the steering committee placing a higher priority on closing out on the 2.8 release. I know that the current 2.8 is considered usable for production but 2.8 isn't feature complete and organizations can be very hesitant to use non-GA versions of libraries. In particular it would be a big win to have a "done" version of JsInterop v1 and clear guidance on using the current version of elemental.

I, and I'm sure the rest of the GWT community, would greatly appreciate a clearer view on current release expectations and prioritization; is there anything you guys can share on that front?

Again, really appreciate the recent work and love the plans for GWT 3.0.

Cheers,
James

--
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 google-web-toolkit+unsubscribe@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.

Thursday, July 30, 2015

Re: Using Lightbox with GWT (some events not catched)

Hi, Xandre,
Could you pls share me your sample code ? I am figuring out how to use it in  my project. 

TIA

On Friday, April 25, 2014 at 4:15:23 AM UTC+8, JoyaleXandre wrote:
If it may help, I noticed that the problem occur only when Lightbox is launch from a DialogBox with Glass enabled.

Le mardi 22 avril 2014 18:20:47 UTC-4, JoyaleXandre a écrit :
Hello!

I'm trying to use Lightbox with the HTML widget in GWT. I manage to make the example from a standard HTML page in my GWT code.
Here is the example: http://lokeshdhakar.com/projects/lightbox2/.

Everything is good when I try to navigate with the keyboard, but when I want to quit by clicking the X button or got next with the arrow image, nothing happen. The mouse events seem to be missing. I can't even right click and see the Firefox context menu.

Do you have any idea where the problem may be?

Alexandre

--
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 google-web-toolkit+unsubscribe@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: [GWT] [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core'

I just had the same error message and it turned out to be my GWTUnit test classes being named SomeNameTest instead of GwtTestSomeName. 
Ending on Test the GWTUnit test classes were picked up by the Surefire plugin instead of the GWT plugin. Removing the Test postfix and adding the GwtTest prefix solved that. 


On Thursday, April 23, 2015 at 9:06:15 AM UTC+2, Danish Khan wrote:
Hi all, 

I am upgrading to GWT 2.7.0 / Smartgwt 5, and I am seeing the following error when I try to build it through maven: 

[GWT]    [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core' either directly or indirectly (most often by inheriting module 'com.google.gwt.user.User')

Here is my gwt.xml. Please let me know if you have any suggestions to fix this error. 

<?xml version="1.0" encoding="UTF-8"?>
<module rename-to='dregtool'>
<inherits name='com.google.gwt.user.User'/> 
<inherits name="com.google.gwt.core.Core" />
<inherits name="com.google.gwt.user.History"/> 
<inherits name="com.dreg.tools.ui.GWTFramework" />
<inherits name="com.dreg.at.atcommon.ATCommon" />
<inherits name="com.dreg.at.atcommon.smartgwt.Components" />
<inherits name="com.gwtext.GwtExt" />
<inherits name="com.dreg.ajax.smartgwt.dregSmartGwt" />
<inherits name="com.googlecode.gchart.GChart" />
<inherits name="com.dreg.i18n.dregI18n" />

  <source path='ui'/>
  <stylesheet src='css/dreg-tool.css'/>
  <entry-point class='com.dreg.at.ui.Main'/>
 
  <set-property name="gwt.suppressNonStaticFinalFieldWarnings" value="true" />
  <add-linker name="xsiframe"/>
</module>

--
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 google-web-toolkit+unsubscribe@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: GWT 2.7.0 is here

Hi, it's awesome.
On september I will migrate for 2.5.1 to 2.7.0 but i wonder if do you have a scheduler for the next stable release? for go to the next on september?

Thanks a lot for your awesome work.

Alex Sanz

El jueves, 20 de noviembre de 2014, 11:59:06 (UTC+1), Daniel Kurka escribió:
Today we are excited to announce the GWT 2.7.0 release.  Thanks to everyone who contributed to this release, especially our non-Google open source contributors.

One major feature of this release is a new super fast compilation path in Super Dev mode that replaces the old dev mode.
For a run-down of all changes since GWT 2.6.1, read the release notes.

The release is available for download here or on maven central.

If you find any issues with this release, please file a bug in our issue tracker.

Daniel,
on behalf of the GWT team at Google

--
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 google-web-toolkit+unsubscribe@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.

Wednesday, July 29, 2015

GWT

Hi Team,

I am getting the below exception while loading my project. Please tell me the solution for the same.

error com.google.web.bindery.requestfactory.shared.ServerFailure@778e3d5c

Thanks & Regards,
SUBBAREDDY

--
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 google-web-toolkit+unsubscribe@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.

Follow grantgoddess, VIJETAMUSIC and devon on Twitter!

Here are some people we think you might like to follow:
grantgoddess  @grantgoddess
  Follow
VIJETAMUSIC  @vijetamusic
  Follow
devon  @freshon
  Follow

Re: gwt-maven-archetypes multiple project setup



On Wednesday, July 29, 2015 at 2:52:57 PM UTC+2, William Davis wrote:
So I figured out that if I do a maven install a war is generated in the server project, however my servlet classes from the libraries were not copied into the war. Still looking into that...

"'mvn install' is an antipattern". 'mvn package' (or 'mvn verify' to also run integration tests) will work the same (without the "install' side-effects).

--
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 google-web-toolkit+unsubscribe@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: gwt-maven-archetypes multiple project setup



On Wednesday, July 29, 2015 at 4:05:24 PM UTC+2, William Davis wrote:
So I found a solution, but I am a little unclear why it works and what is the best practice. Before when it wasn't working I had this dependency in my server project:
<dependency>
     <groupId>com.gwt.library</groupId>
     <artifactId>library-core-server</artifactId>
     <version>1.0.0-SNAPSHOT</version>
     <type>gwt-lib</type>
</dependency>

When I removed the <type>gwt-lib</type> and rebuilt, it put the library-core-server.jar in the web-inf/lib directory which was put in the war and that made it work when I deployed the war.

Am I incorrectly using the  <type>gwt-lib</type>?

Yes.
gwt-lib is for client-side JARs where the sources are also packaged inside the JAR.
Rule of thumb: you should only use <type>gwt-lib</type> in POMs with <packaging>gwt-lib</packaging> or <packaging>gwt-war</packaging>, there's no reason to use them anywhere else (unless you use the gwt-maven-plugin without the gwt-lib/gwt-app lifecycles)
 
Is there a better way to make sure that jar gets put in the war?

No. The proper way to declare server-side dependencies is to use <type>jar</type> (or omit the <type> as "jar" is the default)
 
Will anything not work correctly if I don't put in the  <type>gwt-lib</type>?

For server-side modules, no.

--
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 google-web-toolkit+unsubscribe@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: gwt-maven-archetypes multiple project setup

So I found a solution, but I am a little unclear why it works and what is the best practice. Before when it wasn't working I had this dependency in my server project:
<dependency>
     <groupId>com.gwt.library</groupId>
     <artifactId>library-core-server</artifactId>
     <version>1.0.0-SNAPSHOT</version>
     <type>gwt-lib</type>
</dependency>

When I removed the <type>gwt-lib</type> and rebuilt, it put the library-core-server.jar in the web-inf/lib directory which was put in the war and that made it work when I deployed the war.

Am I incorrectly using the  <type>gwt-lib</type>?
Is there a better way to make sure that jar gets put in the war?
Will anything not work correctly if I don't put in the  <type>gwt-lib</type>?

Thanks,
Will

On Wednesday, July 29, 2015 at 9:41:05 AM UTC-4, William Davis wrote:
It is probably something simple but what do I need to do to get maven to put the jars of the libraries into the target/[app_name]/WEB-INF/lib directory, for building the war?

On Wednesday, July 29, 2015 at 8:52:57 AM UTC-4, William Davis wrote:
So I figured out that if I do a maven install a war is generated in the server project, however my servlet classes from the libraries were not copied into the war. Still looking into that...

On Tuesday, July 28, 2015 at 10:27:34 AM UTC-4, William Davis wrote:
So the good news is that everything is running well, the incremental compile is working for all the libraries client and server side. I am very impressed with the plugin Thomas.

One last question, what is the correct way to package the whole app into a war for production. I tried to run gwt:package-app on the parent project, the one containing the client, shared, and server projects in the modular-webapp archetype, however when I put the war on tomcat it didn't work. Should I install the projects and libraries in a certain order? What am I doing wrong?

Once again, great work Thomas, this is really excellent.
Thanks for the help,
Will

On Friday, July 24, 2015 at 10:42:19 AM UTC-4, Thomas Broyer wrote:


On Friday, July 24, 2015 at 4:13:45 PM UTC+2, William Davis wrote:
I think I figured something out. In the "base" project, in the parent pom, I only defined the three modules in that project like this:
<modules>
    <module>base-client</module>
    <module>base-shared</module>
    <module>base-server</module>
  </modules>

but I changed it to add the client library like this:
<modules>
    <module>base-client</module>
    <module>../library-core/library-core-client</module>
    <module>base-shared</module>
    <module>base-server</module>
  </modules>

and now the incremental compile works when I make changes to the library client.
Is this the correct/best way to do this?

With your initial setup, the library-core-client (and its transitive dependencies) come from your local repository, and you have to "mvn install" the library each time you make a change to it.
With your final setup, it's all one reactor project (you should include the library-core-shared and library-core-server too BTW), so the gwt-maven-plugin will look at the MavenProject from the reactor build to get its sources.

Your initial setup is OK if you intend to release library-core-* separately from the "base" webapp.
Your final setup is OK if you intend to release everything at once. I'd have rather put everything inside one big project with many submodules (organized into subfolders), but in the end it's up to you to decide.
Note that there's a way to get things working with your initial "2 separate projects" approach though: create a POM file somewhere that lists all modules as submodules (note: you can just list the 2 root modules of your 2 projects and thus get the submodules recursively) and from which one you can run the tomcat7:run and gwt:codeserver goals.

This is all "standard Maven", independent of the gwt-maven-plugin (you'd get the same behavior for server-side code with the tomcat-maven-plugin, not seeing changes to your library-core-shared and library-core-server until you "mvn install" them and restart Tomcat).

--
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 google-web-toolkit+unsubscribe@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: gwt-maven-archetypes multiple project setup

It is probably something simple but what do I need to do to get maven to put the jars of the libraries into the target/[app_name]/WEB-INF/lib directory, for building the war?

On Wednesday, July 29, 2015 at 8:52:57 AM UTC-4, William Davis wrote:
So I figured out that if I do a maven install a war is generated in the server project, however my servlet classes from the libraries were not copied into the war. Still looking into that...

On Tuesday, July 28, 2015 at 10:27:34 AM UTC-4, William Davis wrote:
So the good news is that everything is running well, the incremental compile is working for all the libraries client and server side. I am very impressed with the plugin Thomas.

One last question, what is the correct way to package the whole app into a war for production. I tried to run gwt:package-app on the parent project, the one containing the client, shared, and server projects in the modular-webapp archetype, however when I put the war on tomcat it didn't work. Should I install the projects and libraries in a certain order? What am I doing wrong?

Once again, great work Thomas, this is really excellent.
Thanks for the help,
Will

On Friday, July 24, 2015 at 10:42:19 AM UTC-4, Thomas Broyer wrote:


On Friday, July 24, 2015 at 4:13:45 PM UTC+2, William Davis wrote:
I think I figured something out. In the "base" project, in the parent pom, I only defined the three modules in that project like this:
<modules>
    <module>base-client</module>
    <module>base-shared</module>
    <module>base-server</module>
  </modules>

but I changed it to add the client library like this:
<modules>
    <module>base-client</module>
    <module>../library-core/library-core-client</module>
    <module>base-shared</module>
    <module>base-server</module>
  </modules>

and now the incremental compile works when I make changes to the library client.
Is this the correct/best way to do this?

With your initial setup, the library-core-client (and its transitive dependencies) come from your local repository, and you have to "mvn install" the library each time you make a change to it.
With your final setup, it's all one reactor project (you should include the library-core-shared and library-core-server too BTW), so the gwt-maven-plugin will look at the MavenProject from the reactor build to get its sources.

Your initial setup is OK if you intend to release library-core-* separately from the "base" webapp.
Your final setup is OK if you intend to release everything at once. I'd have rather put everything inside one big project with many submodules (organized into subfolders), but in the end it's up to you to decide.
Note that there's a way to get things working with your initial "2 separate projects" approach though: create a POM file somewhere that lists all modules as submodules (note: you can just list the 2 root modules of your 2 projects and thus get the submodules recursively) and from which one you can run the tomcat7:run and gwt:codeserver goals.

This is all "standard Maven", independent of the gwt-maven-plugin (you'd get the same behavior for server-side code with the tomcat-maven-plugin, not seeing changes to your library-core-shared and library-core-server until you "mvn install" them and restart Tomcat).

--
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 google-web-toolkit+unsubscribe@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: gwt-maven-archetypes multiple project setup

So I figured out that if I do a maven install a war is generated in the server project, however my servlet classes from the libraries were not copied into the war. Still looking into that...

On Tuesday, July 28, 2015 at 10:27:34 AM UTC-4, William Davis wrote:
So the good news is that everything is running well, the incremental compile is working for all the libraries client and server side. I am very impressed with the plugin Thomas.

One last question, what is the correct way to package the whole app into a war for production. I tried to run gwt:package-app on the parent project, the one containing the client, shared, and server projects in the modular-webapp archetype, however when I put the war on tomcat it didn't work. Should I install the projects and libraries in a certain order? What am I doing wrong?

Once again, great work Thomas, this is really excellent.
Thanks for the help,
Will

On Friday, July 24, 2015 at 10:42:19 AM UTC-4, Thomas Broyer wrote:


On Friday, July 24, 2015 at 4:13:45 PM UTC+2, William Davis wrote:
I think I figured something out. In the "base" project, in the parent pom, I only defined the three modules in that project like this:
<modules>
    <module>base-client</module>
    <module>base-shared</module>
    <module>base-server</module>
  </modules>

but I changed it to add the client library like this:
<modules>
    <module>base-client</module>
    <module>../library-core/library-core-client</module>
    <module>base-shared</module>
    <module>base-server</module>
  </modules>

and now the incremental compile works when I make changes to the library client.
Is this the correct/best way to do this?

With your initial setup, the library-core-client (and its transitive dependencies) come from your local repository, and you have to "mvn install" the library each time you make a change to it.
With your final setup, it's all one reactor project (you should include the library-core-shared and library-core-server too BTW), so the gwt-maven-plugin will look at the MavenProject from the reactor build to get its sources.

Your initial setup is OK if you intend to release library-core-* separately from the "base" webapp.
Your final setup is OK if you intend to release everything at once. I'd have rather put everything inside one big project with many submodules (organized into subfolders), but in the end it's up to you to decide.
Note that there's a way to get things working with your initial "2 separate projects" approach though: create a POM file somewhere that lists all modules as submodules (note: you can just list the 2 root modules of your 2 projects and thus get the submodules recursively) and from which one you can run the tomcat7:run and gwt:codeserver goals.

This is all "standard Maven", independent of the gwt-maven-plugin (you'd get the same behavior for server-side code with the tomcat-maven-plugin, not seeing changes to your library-core-shared and library-core-server until you "mvn install" them and restart Tomcat).

--
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 google-web-toolkit+unsubscribe@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: gwtgallery.appspot.com dead ?



On Wednesday, July 29, 2015 at 11:00:07 AM UTC+2, STB Land wrote:
GWT Gallery site seems to be dead, unfortunately it's referenced twice by GWT official site in Resources section.

This message just for the purpose of informing or administrators

Thanks, but we're already aware and planning updates ;-)
https://groups.google.com/d/msg/google-web-toolkit-contributors/y7qf1uqQ2Hg/_DfsuXWmF6wJ
(feel free to contribute patches!) 

--
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 google-web-toolkit+unsubscribe@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.

gwtgallery.appspot.com dead ?

GWT Gallery site seems to be dead, unfortunately it's referenced twice by GWT official site in Resources section.

This message just for the purpose of informing or administrators

--
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 google-web-toolkit+unsubscribe@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: What's the latest GWT version usable with GWT-Ext?

That sounds suspiciously like a project I used to work on! Thankfully I am at a different company now and don't have to worry about it anymore, last I heard they were throwing it all away and re-writing using PHP/pure JS.

From memory, GWT-Ext wasn't the best implementation (but you have probably found that) and I suspect you aren't going to have much luck moving to a more recent GWT :(

On Tuesday, 28 July 2015 17:16:24 UTC+1, walker1c wrote:
I have the unenviable task of resurrecting and modifying a project that was last touched about six years ago.  The project uses GWT 1.5.3 and makes extensive use of the GWT-EXT widget toolkit that ceased active development when 1.5.3 was current. 

There is currently no budget for replacing GWT-EXT with an alternative, so I have to work with what I've got, but I would very much like to update the GWT version, both to take advantage of GWT improvements, and to avoid having to set up a development environment with historic versions of Eclipse, Maven, and associated plugins.

What's the latest GWT version anyone has succeeded is using with GWT-EXT?  Any links to crib-sheets for this kind of environment would be most appreciated, as they could save me a lot of time.

Chris

--
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 google-web-toolkit+unsubscribe@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.

Tuesday, July 28, 2015

Re: GWT CellTable-How to Move the Sorting Arrow from Left to Right side

Thanks Thomas for your reply i am able to do with this setSortIconStartOfLine  but having one more issue there is lot of space between the Label and icon its because of fixed inline styling(i can override this but cant have handle because of label length).

--
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 google-web-toolkit+unsubscribe@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: GWT Celltable-Sorting on Multiple Column

http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTable


Den onsdag 29 juli 2015 kl. 06:55:57 UTC+2 skrev Mohammed Sameen:

How to perform sorting on multiple column Using GWT Celltable. I didnt find any example code for this? See the below image

enter image description here

I need to Perform sorting on multiple column.How to Achieve this using GWT Celltable any clue?

--
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 google-web-toolkit+unsubscribe@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.

GWT Celltable-Sorting on Multiple Column

How to perform sorting on multiple column Using GWT Celltable. I didnt find any example code for this? See the below image

enter image description here

I need to Perform sorting on multiple column.How to Achieve this using GWT Celltable any clue?

--
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 google-web-toolkit+unsubscribe@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.

GWT client with jwebsocket

personal anyone have any examples of an app or sample GWT client using the jwebsocket api, grateful to those who can help me

--
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 google-web-toolkit+unsubscribe@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.

@tamminsursok1 tweeted: Shooting #setlife

Followed by Emily Stoll, Nick Cannon and AshleyTisdaleFrench.
Taylor Swift  @taylorswift13
 
"So I'm ready..." -Dilemma

Behind the scenes of the Bad Blood music video with @SerayahLove

instagram.com/p/5sEHNPDvKU/
View on Twitter
Followed by AshleyTisdaleFrench.
The Haute Mess @TheHauteMess
 
Two is better than one and @TheGarsowTwins really know how to shake things up. Get ready for them on #TheHauteMess
View on Twitter
Followed by Fab Foodie, Nick Cannon and Demi Lovato.
Serena Williams  @serenawilliams
 
Love my #Berlei bras!!
#MasterTheBounce @BerleiUK
View on Twitter
Followed by AshleyTisdaleFrench.
Ryan Pinkston  @Ryan_Pinkston
 
TUNE IN & DVR AN ALL NEW EPISODE OF @ClippedTBS! WE HAVE A VERY SPECIAL GUEST STAR!

TONIGHT ON @tbs_tv
10pm/9c!
View on Twitter
Liam  @Real_Liam_Payne
 
Super sick nighties RnB sound @LAUVsongs youtu.be/HNjX6o7t6NU can't wait to hear more
View on Twitter