When is 2.7 scheduled to release?
On Fri, Sep 5, 2014 at 11:31 AM, Jens wrote:
> Maybe use the xsiframe linker which produces *.cache.js files instead of
> html files. The xsiframe linker will be the default in GWT 2.7 anyways.
>
> -- J.
>
> --
> You received this message because you are subscr
OK, I fixed my problem. I change my DialogBox to a PopupPanel and now the
event are catched like they should be. The button back, next and close are
working.
On Thu, Apr 24, 2014 at 4:15 PM, JoyaleXandre wrote:
> If it may help, I noticed that the problem occur only when Lightbox is
> launch fro
You're right. Strange behavior. It's a feature killer for me.
On Wed, Mar 26, 2014 at 3:51 PM, Marcel K wrote:
> For me it works in FF with durations < 4sec.. looks like FF closes
> notifications automatically if they are not closed manually before.
> Can you confirm that it works for times < 4
I've made my own build.xml file to build my project. I don't understand
that not a lot of person complain about that. It seems to be a major issue.
I wonder if anybody that it's still working uses Eclipse Juno and GWT 2.5.1.
On Fri, Jun 21, 2013 at 6:39 AM, Magallo wrote:
> Have you solved the
What is the impact performance wise?
Le 2 avr. 2013 13:38, "Jens" a écrit :
> The filter will be executed when the url-pattern matches. The example uses
> "/*" as url-pattern which matches all URLs so it will always be executed.
>
> -- J.
>
> --
> You received this message because you are subscri