Monday, October 31, 2016

Re: Show next item and previous item button when overflow

Why reeinvent the wheel. There are bunch of js libs that  do this with ease


Am 31.10.2016 12:01 PM schrieb "Vassilis Virvilis" <vasvir2@gmail.com>:
Some observations

1) What you describe is a scrollbar...

2) What you want is not GWT specific. If you can do it with html/css/js then you can also do it in GWT.

Now if don't want to use scrollbar and you want to rely on the (way to deprecation) GWT widget framework you can try something in the following lines

a) Use a ResizePanel to host your HTMLPanel in order to get resize events for your container. Note that this may require significant changes to your page layout and structure,

b) If you have the size of the container and the min width of your items to be displayed you can do calculation to decide what to show...

Hope that helps

     Vassilis


On Mon, Oct 31, 2016 at 7:58 AM, 'Shuo Weng' via GWT Users <google-web-toolkit@googlegroups.com> wrote:
Hi all,

Does anyone have an idea on how to make this happen GWT:

I have a HTMLPanel which contains 8 cards. The cards are placed horizontally and their min-width are set.  I want to show a previous item button in the left and a next item button in the right when screen cannot show the total 8 cards.

Any idea on how to implement this?

Thanks.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.



--
Vassilis Virvilis

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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

Re: Show next item and previous item button when overflow

Some observations

1) What you describe is a scrollbar...

2) What you want is not GWT specific. If you can do it with html/css/js then you can also do it in GWT.

Now if don't want to use scrollbar and you want to rely on the (way to deprecation) GWT widget framework you can try something in the following lines

a) Use a ResizePanel to host your HTMLPanel in order to get resize events for your container. Note that this may require significant changes to your page layout and structure,

b) If you have the size of the container and the min width of your items to be displayed you can do calculation to decide what to show...

Hope that helps

     Vassilis


On Mon, Oct 31, 2016 at 7:58 AM, 'Shuo Weng' via GWT Users <google-web-toolkit@googlegroups.com> wrote:
Hi all,

Does anyone have an idea on how to make this happen GWT:

I have a HTMLPanel which contains 8 cards. The cards are placed horizontally and their min-width are set.  I want to show a previous item button in the left and a next item button in the right when screen cannot show the total 8 cards.

Any idea on how to implement this?

Thanks.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.



--
Vassilis Virvilis

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Sunday, October 30, 2016

Show next item and previous item button when overflow

Hi all,

Does anyone have an idea on how to make this happen GWT:

I have a HTMLPanel which contains 8 cards. The cards are placed horizontally and their min-width are set.  I want to show a previous item button in the left and a next item button in the right when screen cannot show the total 8 cards.

Any idea on how to implement this?

Thanks.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Saturday, October 29, 2016

Re: jqm4gwt ver. 1.4.7 released



On Saturday, October 29, 2016 at 4:12:00 PM UTC+3, Alain wrote:

Thanks, I see lots of gwt-user dependencies:  Widget, ClickHandler, JavaScriptObject.
I agree better to have 100% interop solution.


--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: jqm4gwt ver. 1.4.7 released


On 29 October 2016 at 14:37, Kirill Prazdnikov <pkirill@gmail.com> wrote:
Where did you find JSNI ?

On Saturday, October 29, 2016 at 11:36:25 AM UTC+3, Alain wrote:
Great work. 
Any plans to move to JS Interop ? 

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.



--

Alain Ekambi

Co-Founder

Ahomé Innovation Technologies

http://www.ahome-it.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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: jqm4gwt ver. 1.4.7 released

Where did you find JSNI ?

On Saturday, October 29, 2016 at 11:36:25 AM UTC+3, Alain wrote:
Great work. 
Any plans to move to JS Interop ? 

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: HowTo use GWT EvenBus to schedule OpenEvent -> CloseEvent sequence

Another example from GWTP https://github.com/ArcBees/GWTP/blob/master/gwtp-core/gwtp-mvp-client/src/main/java/com/gwtplatform/mvp/client/proxy/PlaceManagerImpl.java, as Jens said, having a manager controlling the ordering of the events seems a good idea. And PlaceManager control the ordering of various event fired in the eventBus like FireRequestInternalEvent, LockInteractionEvent and NavigationEvent. LockInteractionEvent is a dual event, one for lock start, and the second for the lock ends, which looks similar to your case.

On Thu, Oct 27, 2016 at 2:22 AM vitrums <vitrums@gmail.com> wrote:
Thank you for quick responses. It seems that we all resorted to Scheduler and control our custom events by tweaking the intrinsic logic of browser's event loop. I thought I could completely miss some obvious solution.


On Wednesday, October 26, 2016 at 7:51:19 PM UTC+3, vitrums wrote:
[ Original post on StackOverflow http://stackoverflow.com/questions/40130383/howto-use-gwt-evenbus-to-schedule-openevent-closeevent-sequence ]

Say we have few handlers for both events. The goal is to make sure, that all OpenEvent handlersfinish before any of CloseEvent handlers start their job. The old EventBus had a reverse order flag, which sometimes helped greatly in these particular cases. I.e. a handler, responsible for launching some process which leads to CloseEvent being fired (i.e. event emitter), usually registers itself to a bus first.

Now, due to a synchronous nature of javascript each handler of OpenEvent ends his job before the next handler starts. In my app the first OpenHandler added to a bus is a CloseEvent emitter. Therefore I get an undesirable sequence of calls: 1st handler of OpenEvent -> all CloseEvent handlers -> the rest of OpenEvent handlers.

My question is: what's the best practice to establish the desirable behavior? So far as a workaround I use Scheduler.scheduleDeferred(Scheduler.ScheduledCommand cmd) to enqueueEventBus.fireEventFromSource(Event event, Object source) of CloseEvent call to the next browser's event loop tick.

p.s. My current thoughts are as follows. I don't want to rely of Timer or Scheduler (though it might be the only option, which I'm not sure about). Also I have no interest in introducing any flag variables, responsible for tracking which event occurred first. Instead, if one looks closer into theSimpleEventBus code, there's a firingDepth counter variable, which only works to delayaddHandler(...) and removeHandler(...) calls. It would be great, if same logic could be applied to order call sequences of handlers for different events.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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

Re: How to bind essential singletons in multi-module GIN app and avoid duplicate binding


On Thu, Oct 27, 2016 at 7:48 AM Thomas Broyer <t.broyer@gmail.com> wrote:
I don't know if it's supported by GIN but Guice has a requireBinding to prevent the second case. And if the user of your lib has to use GIN it's not abnormal to ask them to bind a few things. You can provide GinModules that bind them if you like so they only have to compose them in their Ginjector without the need to write the bindings themselves.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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

Re: jqm4gwt ver. 1.4.7 released

Great work. 
Any plans to move to JS Interop ? 

On 29 October 2016 at 10:28, Ali Jalal <ali.jalaal@gmail.com> wrote:
Thank you for contribution and helping open source community.

On Sat, Oct 29, 2016 at 3:00 AM, Slava Pankov <pankovs@gmail.com> wrote:
jqm4gwt is an advanced wrapper over the jQuery Mobile framework

GWT 2.8 is supported, see here https://github.com/jqm4gwt/jqm4gwt

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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



--

Alain Ekambi

Co-Founder

Ahomé Innovation Technologies

http://www.ahome-it.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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: jqm4gwt ver. 1.4.7 released

Thank you for contribution and helping open source community.

On Sat, Oct 29, 2016 at 3:00 AM, Slava Pankov <pankovs@gmail.com> wrote:
jqm4gwt is an advanced wrapper over the jQuery Mobile framework

GWT 2.8 is supported, see here https://github.com/jqm4gwt/jqm4gwt

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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

Friday, October 28, 2016

jqm4gwt ver. 1.4.7 released

jqm4gwt is an advanced wrapper over the jQuery Mobile framework

GWT 2.8 is supported, see here https://github.com/jqm4gwt/jqm4gwt

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Unchanged transient field received as null on server using RequestFactory - how to force to send?

Ok - our code has a default finder used generically for all calls, though some locators override it.  I hadn't been very aware of it - it was this that was causing the issue.

Once I overrode the finder to fill in transient values, my problems went away.

Thanks for pointing me in the right direction!

- Tim

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Bazel rules now available for GWT

Cool! Nice job!

On Thursday, October 27, 2016 at 2:10:54 PM UTC-7, Erik Kuefler wrote:
In case anyone is looking into using Bazel as part of a GWT project, there are now some simple GWT rules available in the Bazel repositories at https://github.com/bazelbuild/rules_gwt. These rules have been updated to support GWT 2.8 and define a build target that creates a .war file containing the GWT-compiled artifacts and a run target that executes Super Dev Mode. Please report any problems on the issue tracker.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

What version of Eclipse, mars or neon? Was there an earlier version installed? 

If GPE was previously installed and you're replacing it with the GWT Eclipse Plugin V3 there is a possibility there are some left over bits from the previous install causing issues. I added a conflict, although there are cases I've seen where the uninstall wasn't perfect. Check your plugins list, and be sure any previous plugins that were owned by GPE were removed before install. 

If that doesn't work, I'd suggest installing a clean version of Eclipse and installing the plugin. I haven't seen any issues with a clean install, at least not yet. You're should be ok to use the same working directory. 

Would that help? 

On Friday, October 28, 2016 at 2:26:54 AM UTC-7, Thomas Lacroix wrote:

Le jeudi 27 octobre 2016 16:42:57 UTC+2, Brandon Donnelson a écrit :
I'm not sure why the SDBG plugin failed to install. Those artifacts come from another repo. I would try again. 

 
It looks like my eclipse has a problem with installing the SGBD plugin, I don't know why yet.
I have opened a thread on the SGBD group for their input.
In the meantime, when I install the GWT Eclipse Plugin V3 without SGBD it seems to work fine.
It says it could not create the view: com.google.gwt.eclipse.DevModeView but I am able to debug in the browser dev tool.
Thomas 

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWTReact release

I have pushed new versions of the GWTReact projects to support the final release of GWT2.8

The versions of the individual JS projects they depend on have also been updated as follows:

react 15.3.2,
react-dom 15.3.2
redux 3.5.2,
react-redux 4.4.5
redux-undo 1.0.0-beta
react-router 2.4.1
mobx 2.5.2
mobx-react 3.5.6
mobx-react-devtools 4.2.6

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Code splitting and interfaces

Hi All,

I have a some problems with the GWT code splitting in the case that one module calls a method from another module that expect an interface.

Lets say that we two modules in our project named ModuleA and ModuleB. 
ModuleA is executing a method from ModuleB which expect an interface.
Now ModuleA is providing an implementation for that interface and calling ModuleB.

Here a very simple example: 

    
public class ModuleA {

   
public void execute() {
        GWT
.runAsync(ModuleA.class, new RunAsyncCallback() {
           
@Override
            public void onFailure(Throwable throwable) {}

           
@Override
            public void onSuccess() {
                executeInternal
();
           
}
       
});
   
}

   
private void executeInternal() {
        ModuleAFunc moduleAFunc = new ModuleAFunc();
        moduleAFunc.doSomething();

       
ModuleB.Callback callback = new ModuleB.Callback() {
           
@Override
            public void done() {
               
ModuleAFunc moduleAFunc = new ModuleAFunc();
                moduleAFunc
.doSomething();
           
}
       
};

        ModuleB moduleB = new ModuleB();
       moduleB.execute(callback);
   
}
}

public class ModuleB {

   
public void execute(Callback callback) {
        GWT
.runAsync(ModuleB.class, new RunAsyncCallback() {
           
@Override
            public void onFailure(Throwable throwable) {}

           
@Override
            public void onSuccess() {
               
ModuleBFunc moduleBFunc = new ModuleBFunc();
                moduleBFunc
.doSomething();
               
callback.done();
           
}
       
});
   
}

   
public interface Callback {
       
void done();
   
}
}

I would expect that the code of "ModuleAFunc" will be put into the splite point "ModuleA" and the code of "ModuleBFunc" will be added to the splite point "ModuleB".

But this is not the case. The code of the class "ModuleAFunc" will be moved into the left over code because the GWT compiler thinks that "ModuleAFunc.doSomething" is also accessible from ModuleB because
ModuleB is executing the interface method Callback.done(). 
Somebody and idea how to handle this problem???

BR
Rocco


--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Problem with GWT RPC and Enhanced classes that are not.

I have recently run into a problem with GWT RPC.  I use Hibernate and I send my entities over the wire using GWT-RPC.  Object graphs are transformed before they are sent to the client to snip unwanted references and replace lazy loading collections, similar to Gilead if my understanding is correct.  At any rate, the object graph being sent over RPC is intended to be a graph of POJO's, and this has seemingly worked well for several months until I unexpectedly received a deserialization error on the server.  I won't post the specifics of this error here or why it suddenly occurred; I have debugged it and the cause of the problem appears to be:

1.  My POJO's are also Hibernate Entities and are annotated with @Entity
2.  This annotation triggers the GWT-RPC SerializableTypeOracleBuilder to determine my class as "Maybe Enhanced"
3.  Being "maybe enhanced" triggers the GWT serialization framework to look for set() methods for setting fields and, where found, to use these in preference to direct field access when deserializing a graph.
4.  My classes are not enhanced (and if they were, I would not want them treated the way GWT RPC currently does; I find the implemented solution to enhanced classes makes me queasy).
5.  The implementation, as it stands, can call methods on partially deserialized objects.  I believe this has been a long standing issue with GWT-RPC which has been noted before with respect to Object.hashCode and Object.equals being called on partially deserialized objects while populating collections.  I wonder if RPC deserialization should proceed in two passes; one to construct all objects and silently set all fields on those objects and a second pass to allow collections and perhaps this bizarre Enhanced mechanism to call methods on these objects to finalize the graph.  However, this question is not the nature of my post.

My issue with this is that I am unable to find a satisfactory way to disable this "enhanced" class detection and subsequent serialization behaviour that it triggers.  What I want is field based serialization and deserialization.  My options for disabling this "feature" seem to be:
1.  Remove the @Entity annotation from by entity beans and declare them as entities in xml.  Not appealing to me; I like the simplicity and cleanliness of using annotations.
2.  Modify the set() methods on my Entity beans so that they avoid generating exceptions by accessing fields which may not have been deserialized yet.  This is one workaround, but it's not appealing either: I really don't want methods being called on my objects until they are fully deserialized, and I don't want to litter my code with checks which otherwise would not be there.  I already have a specific HashMap implementation I use for GWT serialization which avoids calling hashCode() or equals() during deserialization, but at least this is self-contained.
3.  Hammer the GWT ServiceInterfaceProxyGenerator to stop it declaring my classes enhanced.  I did this with some success - I use a custom SIPG which inherits from the GWT standard SIPG, and I forcibly unset the enhanced setting on all JClassType instances in an overridden generateTypeHandlers() method.  This works well - at least the .gwt.rpc files do not have @ClientFields entries in them, and RPC works fine.  However it is obviously horrible and not a permanent solution, but it is better to me than the alternatives.  Unfortunately, and more critically, it does not seem to work in SuperDev mode, which I use extensively.  Does anyone have any suggestions why this might be or how I can fix it?  Happy to post in detail about the errors experienced here if someone feels they might be able to shed light on it.

What I would really like is a way of turning off this enhanced class detection feature which works throughout the GWT toolchain...

Any help most gratefully received

- Will


--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars


Le jeudi 27 octobre 2016 16:42:57 UTC+2, Brandon Donnelson a écrit :
I'm not sure why the SDBG plugin failed to install. Those artifacts come from another repo. I would try again. 

 
It looks like my eclipse has a problem with installing the SGBD plugin, I don't know why yet.
I have opened a thread on the SGBD group for their input.
In the meantime, when I install the GWT Eclipse Plugin V3 without SGBD it seems to work fine.
It says it could not create the view: com.google.gwt.eclipse.DevModeView but I am able to debug in the browser dev tool.
Thomas 

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Thursday, October 27, 2016

Re: Unchanged transient field received as null on server using RequestFactory - how to force to send?

Ah, ok - I didn't realize that I was able to provide my own modification of the locator method.  In my debugging of our code, I saw the RF framework do a direct to an EntityManager.find() method.  For some reason I didn't see that this was something we could modify.  I also wasn't aware of @PostLoad.  I'll look into both of those then, thanks!

- Tim

On Thursday, October 27, 2016 at 2:36:54 PM UTC-7, Jens wrote:

 But when RF looks up the current value to compare, it will always be null because the regular lookup doesn't set the transient value.

RF expects a correctly filled entity after loading it from the DB using the entity locator methods (because RF only sends changed data). It's your job to provide a correctly filled entity. You must update your entity locator method to fill the @Transient field or you have to use JPA @PostLoad to "automatically" fill the @Transient field once the entity has been loaded from DB.

Otherwise use a ValueProxy as it does not has a DB identity and thus all values will be send by the client.

-- 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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Bazel rules now available for GWT

Ah, I found one here. 
https://github.com/bazelbuild/rules_gwt/tree/master/example/src/main/java/io/bazel/sample

On Friday, October 28, 2016 at 12:25:00 AM UTC+2, Kirill Prazdnikov wrote:
Hi, this sounds interesting. 
are you planning to add an example ? 
I was looking here, but did not found one

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Bazel rules now available for GWT

Hi, this sounds interesting. 
are you planning to add an example ? 
I was looking here, but did not found one

https://github.com/bazelbuild/bazel/tree/master/examples


--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

unsetting draggable

I have a widget that I set draggable with

    widget.getElement().setDraggable(Element.DRAGGABLE_TRUE);

and register a DragStartHandler. Later there comes a time when I want to unregister the handler, as well as disable dragging with 

    widget.getElement().setDraggable(Element.DRAGGABLE_FALSE);

However the widget is still draggable. When I look in Chrome Dev Tools, draggable="true" is still present. I've also tried

    widget.getElement().removeAttribute("dragable");

but draggable="true" is still present.

Is it not possible to remove draggable? I am using GWT 2.7.0 and running Chrome 54.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

unsetting draggable

I have a widget that I set draggable with

widget.getElement().setDraggable(Element.DRAGGABLE_TRUE);

and register a DragStartHandler. Later there comes a time when I want to unregister the handler and disable dragging with 

    widget.getElement().setDraggable(Element.DRAGGABLE_FALSE);

However the widget is still draggable. When I look in Chrome Dev Tools, draggable-"true" is still present. I've also tried

    widget.getElement().removeAttribute("dragable");


--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 released

The doc/javadoc directory is incomplete. It is missing the index.html and the other files to complete it. Will these be added to the gwt-2.8.0.zip?

On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote:
Hi all,

I am very happy to announce GWT 2.8.0 on behalf of the GWT steering committee and the GWT team at Google.

You can download the release from http://www.gwtproject.org/download.html or from maven central.


Daniel,
on behalf of the GWT team

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Unchanged transient field received as null on server using RequestFactory - how to force to send?


 But when RF looks up the current value to compare, it will always be null because the regular lookup doesn't set the transient value.

RF expects a correctly filled entity after loading it from the DB using the entity locator methods (because RF only sends changed data). It's your job to provide a correctly filled entity. You must update your entity locator method to fill the @Transient field or you have to use JPA @PostLoad to "automatically" fill the @Transient field once the entity has been loaded from DB.

Otherwise use a ValueProxy as it does not has a DB identity and thus all values will be send by the client.

-- 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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Bazel rules now available for GWT

In case anyone is looking into using Bazel as part of a GWT project, there are now some simple GWT rules available in the Bazel repositories at https://github.com/bazelbuild/rules_gwt. These rules have been updated to support GWT 2.8 and define a build target that creates a .war file containing the GWT-compiled artifacts and a run target that executes Super Dev Mode. Please report any problems on the issue tracker.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Compiler error

Hi, I have a static method

public class PolygonEditor {
public static void create(
PropertyInspector inspector) {
    PropertyInspector.PropertyRollup rollup = inspector.createRollup("PolygonEditor");
    rollup.addButton("switch water on selected", () -> {
Logger.log("string");
});
}
}

It compiles and works.
But when I do this :

if (false) rollup.addButton("switch water on selected", () -> {
Logger.log("string");
});

I'm getting the following error, what can it be ?

[INFO] Caused by: java.lang.NullPointerException  [INFO] 	at com.google.gwt.dev.jjs.impl.Pruner.transformToNullMethodCall(Pruner.java:608)  [INFO] 	at com.google.gwt.dev.jjs.impl.Pruner$CleanupRefsVisitor.endVisit(Pruner.java:184)  [INFO] 	at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:268)  [INFO] 	at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)  [INFO] 	at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)  [INFO] 	... 32 more  [INFO]          [ERROR] at PolygonEditor.java(53): PolygonEditor.lambda$3()  [INFO]             com.google.gwt.dev.jjs.ast.JMethodCall  [INFO]          [ERROR] at PolygonEditor.java(53): PolygonEditor.lambda$3()  [INFO]             com.google.gwt.dev.jjs.ast.JExpressionStatement  [INFO]          [ERROR] at PolygonEditor.java(53): {  [INFO]   PolygonEditor.lambda$3();  [INFO] }  [INFO]             com.google.gwt.dev.jjs.ast.JBlock  [INFO]          [ERROR] at PolygonEditor.java(53): {  [INFO]   PolygonEditor.lambda$3();  [INFO] }  [INFO]             com.google.gwt.dev.jjs.ast.JMethodBody  [INFO]          [ERROR] at PolygonEditor.java(53): delightex.client.editors.PolygonEditor$lambda$3$Type.run()V  [INFO]             com.google.gwt.dev.jjs.ast.JMethod  [INFO]          [ERROR] at PolygonEditor.java(53): delightex.client.editors.PolygonEditor$lambda$3$Type (final extends Object implements Runnable)  [INFO]             com.google.gwt.dev.jjs.ast.JClassType  [INFO]       [ERROR] Unrecoverable exception, shutting down



--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Unchanged transient field received as null on server using RequestFactory - how to force to send?

... or maybe an improvement, whereby fields marked @Transient would always be sent, and not use the usual lookup/compare workflow?

I'm surprised it works the way it does - when the original value is fetched, we set the @Transient values when returned to the client.  But when RF looks up the current value to compare, it will always be null because the regular lookup doesn't set the transient value.  So it would be comparing null to the value the client currently has - why wouldn't that cause it to send the value?  Or, I guess, the value is compared on the server, and since the client perceives that the value hasn't changed, it's comparing (null == null), I guess that's it, eh?

Anyway, some way to force it to send a value would be nice.

- Tim

On Wednesday, October 26, 2016 at 10:59:43 PM UTC-7, Thomas Broyer wrote:
Assuming an EntityProxy here, if the field is left unchanged, then it's not sent to the server. On the server side, the entity is loaded by the Locator and then the diff is applied. So if the Locator gets a null field, it'll be left null.
You may have to use a ValueProxy here…

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Unchanged transient field received as null on server using RequestFactory - how to force to send?

Sorry, yes, it was an EntityProxy.

My ideas to solve it were:

1) Use a ValueProxy instead of an EntityProxy
2) Use a ValueProxy for the @Transient String value (dunno how a transient value, expressed as a ValueProxy within an EntityProxy, would be handled, or if it's allowed)
3) Pass the changing/unchanging value as a separate String argument in the RF call
4) Intuit it is unchanged BECAUSE it is null, since the client always sets it to something, but never to null

I think #3 is the easiest in this case.

Is there any possibility that, in future releases (we're one release behind current), an individual field in a proxy can be set to 'changed'?  That is, override the default returned by isChanged()?  I think that could be very useful, and I don't see it as causing any hiccups in the way things already work.

- Tim

On Wednesday, October 26, 2016 at 10:59:43 PM UTC-7, Thomas Broyer wrote:
Assuming an EntityProxy here, if the field is left unchanged, then it's not sent to the server. On the server side, the entity is loaded by the Locator and then the diff is applied. So if the Locator gets a null field, it'll be left null.
You may have to use a ValueProxy here…

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.