MessagesWithLookup

[stuckagain]

In a special case in my application I need the extra functionality of 
Messages but I need something like the behavior of ConstantsWithLookup.
 
I understand that Messages do not provide a lookup functionality for 
performance reasons, however sometimes it would be useful to have something 
like MessagesWithLookup. (I need to be able to support PluralCount and 
SafeHtml results, which are not supported by ConstantsWithLookup).
 
I wanted to try and create such a thing myself, however most code of the 
com.google.gwt.i18n.rebind is package private.
 
So, any plans to add it (or allow a patch for that feature) ?
 
 

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

Using multiple UiRenderer types in one CellRenderer

[stuckagain]

I'm trying to use multiple UiRenderer types in one CellRenderer. One 
annoying feature is that you are supposed to use the same base file name 
for the ui.xml file as the class in which the UiRenderer is defined.
In my case I actually want to use multiple UiRenderer interfaces and 
UiBinder interfaces. Is there some trick to make this possible ? My 
CellRenderer needs to render differently based on some property of the 
object it is showing.

I also noticed that the UiRenderer interface is marked as experimental ... 
is this still the case what is the future of this with respect to GWT 3.0 ?


-- 
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+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: Using @UiChild with Elements not widgets, is this even possible?

[stuckagain]

Hi,
 
I would love seeing some improvements to UiBinder that it would allow 
String of SafeHtml for children. I don't want my templates to be full of 
HTMLPanel when just a String or SafeHtml would do. Specifying these 
"children" using attributes is not really a great idea since I don't want 
to escape html in an attribute in a UiBinder file.
 
David
 

On Saturday, October 5, 2013 11:48:17 PM UTC+2, Seth wrote:

> Hi Thomas,
>
> Just one last thing, are there still no plans for uibinder element parsing 
> functionality extension like the patch in this issue 
> ? 
> Would be preeetty awesome.
>
> On Saturday, October 5, 2013 10:54:36 PM UTC+2, Thomas Broyer wrote:
>>
>> Ah sorry, hadn't looked carefully at your code: with 
>> @UiChild(tagname="div"), UiBinder expects a  ("my" being the same 
>> as the containing widget):
>>
>> 
>>   
>> 
>>   foo
>> 
>>   
>> 
>>
>> That doesn't change the problem though: apparently (looking at the code), 
>> only widgets are allowed. With the above XML, the "my:div" only exists to 
>> call the @UiChild method, passing the HTMLPanel as argument.
>>
>> On Saturday, October 5, 2013 10:49:11 PM UTC+2, Thomas Broyer wrote:
>>>
>>> Looks like I was wrong and you can only use widgets (there's an explicit 
>>> "isImportedElement" test that checks the element is within a namespace 
>>> whose URI starts with “urn:import:”)
>>>
>>> BTW, isn't the error message rather “Expected child from a urn:import 
>>> namespace, found ” ?
>>>
>>> On Saturday, October 5, 2013 9:56:14 PM UTC+2, GWTter wrote:

 Hi all,

 Although the doc 
 
  does 
 say "...add a child widget to..." in my searching it seems as if you can 
 also use UiChild with DOM elements that extend 
 com.google.gwt.dom.client.Element class. Thomas Broyer gives a brief 
 description here 
 .
  
 Since it's Thomas I'm thinking this should indeed work, however for the 
 life of me I can't get it to. It always ends up in "found unexpected child 
 element: " when the child is a div element. 

 From the comments and the doc it seems that this is the setup you're 
 supposed to have:

 @UiChild(tagname = DivElement.TAG)
 public void addDiv(DivElement div) {  //note: I've even tried "adddiv" 
 just to be sure
   //do something 
 }

 and in uibinder:

 
   foo
 


 Do I just have code tunnel vision or is this not possible? Thanks in 
 advance.

 -Seth

>>>

-- 
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+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: How to display an ampersand using UiBinder?

[stuckagain]

It turns out that my custom widget was the root of the problem.
 
It implements HasHTML but not HasSafeHtml (I thought I had it implemented). 
It is strange that the » was properly showing, but not & or & 
that threw me off a bit.
 
David

On Wednesday, May 21, 2014 9:45:25 AM UTC+2, stuckagain wrote:

> I have to revive this thread. I just stumbled on the same problem in my 
> UiBinder file. This really looks like a bug in GWT UiBinder.
>  
> I am using a different widget than Label (my own custom Button class that 
> extends HasHTML and HasSafeHtml).
>  
> I include the entity line:
> http://dl.google.com/gwt/DTD/xhtml.ent";>
>  
> and then I have this in my UiBinder:
> View and manage all user roles (own & 
> delegated) »
>  
> The » is properly showing the right double arrow sign, the & is not 
> properly showing.
> I also tried to use & instead of & but it gets printed as "&"
>  
> So, this must be a bug in GWT UiBinder (not in SafeHtmlBuilder I tried 
> that one already).
> David
>  
>
> On Thursday, December 16, 2010 1:07:23 AM UTC+1, Hilco Wijbenga wrote:
>
>> On 15 December 2010 15:06, Nick Newman  wrote:
>> > You say that using A & B & C obviously fails (because the ampersand is
>> > illegal in the XML).  Does using a CDATA section to make it legal work?
>>
>> :-) Nice one! Yes, GWT finds that acceptable.
>>
>> Unfortunately, I still need to use g:HTML instead of g:Label as Mauro
>> indicated. It's not a very big deal since the generated HTML is the
>> same except for the CSS class name used. I just wish I could treat all
>> labels the same.
>>
>>

-- 
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+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: How to display an ampersand using UiBinder?

[stuckagain]

I have to revive this thread. I just stumbled on the same problem in my 
UiBinder file. This really looks like a bug in GWT UiBinder.
 
I am using a different widget than Label (my own custom Button class that 
extends HasHTML and HasSafeHtml).
 
I include the entity line:
http://dl.google.com/gwt/DTD/xhtml.ent";>
 
and then I have this in my UiBinder:
View and manage all user roles (own & 
delegated) »
 
The » is properly showing the right double arrow sign, the & is not 
properly showing.
I also tried to use & instead of & but it gets printed as "&"
 
So, this must be a bug in GWT UiBinder (not in SafeHtmlBuilder I tried that 
one already).
David
 

On Thursday, December 16, 2010 1:07:23 AM UTC+1, Hilco Wijbenga wrote:

> On 15 December 2010 15:06, Nick Newman > 
> wrote:
> > You say that using A & B & C obviously fails (because the ampersand is
> > illegal in the XML).  Does using a CDATA section to make it legal work?
>
> :-) Nice one! Yes, GWT finds that acceptable.
>
> Unfortunately, I still need to use g:HTML instead of g:Label as Mauro
> indicated. It's not a very big deal since the generated HTML is the
> same except for the CSS class name used. I just wish I could treat all
> labels the same.
>
>

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

UiBinder and writing custom parsers

[stuckagain]

I need to write a custom widget that is to be used in UiBinder to easily 
layout a form of properly aligned fields (in multiple columns).

I tried to avoid using a custom widget by defining some resusable 
stylenames, but it would be much nicer if I could just abstract away 
whether you need a DIV/TABLE/TR/TD/SPAN/LABEL or any other HTML tag.
I gets complicated very quickly and if you have many screens there should 
be a lot more reuse possible.

I basically just want that the developer can do something like:


  Title
  Label
  Label 2


So I need to be able to mix some plain HTML tags with some custom defined 
ones.

The only subject I found on how to do this is 
here: 
http://stackoverflow.com/questions/11782171/gwt-uibinder-how-to-make-a-custom-absolutepanel-which-uses-the-at-element/11785903#11785903

Is this the officially supported way of doing this ? There is no developer 
documentation available on this topic. 

David

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

Using GWTTestCase to do integration testing on GWT-RPC calls

[stuckagain]

Hi,
 
I'm trying to create an integration test that checks if a GWT-RPC service 
is working with our integration test servers.
My initial thought was to just use a GWTTestCase and point the GWT-RPC 
ServiceDefTarget to the real server.
 
It did not work:

32 [JS executor for com.gargoylesoftware.htmlunit.WebClient@3afb2359] ERROR 
com.gargoylesoftware.htmlunit.javascript.background.JavaScriptJobManagerImpl 
- Job run failed with unexpected 
RuntimeException: Wrapped java.lang.RuntimeException: No permitted 
"Access-Control-Allow-Origin" header. 
net.sourceforge.htmlunit.corejs.javascript.WrappedException: Wrapped java.
lang.RuntimeException: No permitted "Access-Control-Allow-Origin" header. 

 at net.sourceforge.htmlunit.corejs.javascript.Context.
throwAsScriptRuntimeEx(Context.java:1889) 
 at com.gargoylesoftware.htmlunit.javascript.host.xml.XMLHttpRequest.doSend(
XMLHttpRequest.java:681) 
 at com.gargoylesoftware.htmlunit.javascript.host.xml.XMLHttpRequest.access0
(XMLHttpRequest.java:94) 
 at com.gargoylesoftware.htmlunit.javascript.host.xml.XMLHttpRequest$1.run(
XMLHttpRequest.java:603) 
 at net.sourceforge.htmlunit.corejs.javascript.Context.call(Context.java:602
) 
 at net.sourceforge.htmlunit.corejs.javascript.ContextFactory.call(
ContextFactory.java:507) 
 at com.gargoylesoftware.htmlunit.javascript.background.
JavascriptXMLHttpRequestJob.run(JavascriptXMLHttpRequestJob.java:36) 
 at com.gargoylesoftware.htmlunit.javascript.background.
JavaScriptJobManagerImpl.runSingleJob(JavaScriptJobManagerImpl.java:328) 
 at com.gargoylesoftware.htmlunit.javascript.background.
DefaultJavaScriptExecutor.run(DefaultJavaScriptExecutor.java:162) 
 at java.lang.Thread.run(Thread.java:724) 
Caused by: 
java.lang.RuntimeException: No permitted "Access-Control-Allow-Origin"header
. 
 ... 9 more
 
I tried using a Filter that sets the Access-Control-Allow-Origin header to 
*, but it does not seem to work.
Is there a better way to perform this kind of integration test with GWT 
code ? Or is there a way to disable this check in HtmlUnit ?
 

-- 
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+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: GWT 2.6.0 now available

[stuckagain]

Great news.

I have a question on the included thirtparty products. I see that there is 
a guava version in there.

Is this version impacted by the JDK 1.7.0 update 51 issue reported here:
https://code.google.com/p/guava-libraries/issues/detail?id=1635

Maybe you are not using the features that cause the incompatiblity, but I 
am just checking since we plan to migrate to this version of java in our 
build environment.

David

On Thursday, January 30, 2014 11:23:45 PM UTC+1, Matthew Dempsky wrote:
>
> Hi GWT community,
>
> We're excited to announce the GWT 2.6.0 release!  Many of you noticed it 
> was uploaded a few days ago, but if you missed it, you can download 
> it 
> here.
>  
>  This release has also been uploaded to Maven Central with the version 
> string of "2.6.0".
>
> GWT 2.6.0 contains over 100 new bug fixes since GWT 2.5.1, more than 400 
> changes in total, and greater than 20% of all contributions came from the 
> community.  Thanks so much to everyone who reported issues and/or submitted 
> patches!
>
> For a summary of user-visible changes, please see the GWT release 
> notes. 
>  And as always, please report any issues using the GWT issue 
> tracker
> .
>
> Happy hacking!
>
> -Matthew, on behalf of the GWT developers
>

-- 
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+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/groups/opt_out.

SingleSelectionModel with KeyProvider does not update selected object when data is refreshed

[stuckagain]

Hi,

I noticed an issue in the SingleSelectionModel when used in combination 
with a KeyProvider and updating the cell table with new data.

The idea is that I want to retain selection, and that seems to work. What 
does not work is when I use the getSelectedObject method I get an older 
version of the object instead of the refreshed version.
Is that the way it is supposed to work ? Wouldn't it be smarter to 
recalculate selection when the data in the table is updated ?

I currently implemented a workaround that uses the KeyProvider to find the 
item in the table that has the same key as the previous selection.

David

-- 
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+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/groups/opt_out.

Re: IncompatibleRemoteServiceException after new deployment

[stuckagain]

Magnus,
 
What is also often causing this is that you don't have caching setup 
correctly. 
One thing people tend to overlook is (besides the *.cache.* and *.nocache.* 
files) is that the host HTML page should disable caching.
 
David

On Wednesday, November 13, 2013 1:01:05 PM UTC+1, Jens wrote:

> This is always happening if you modify any serializable class that is used 
> by any of your GWT-RPC service. A modification will change the filenames of 
> all the *.rpc files and users that are already logged in while you do the 
> update will still use the old hash name. The server then can not find the 
> old *.rpc files for the old hash and will throw the above exception.
>
> To solve this we first started to catch the exception and treated it as 
> "app has been updated" notification which causes the app to reload. But 
> since then we moved to a dynamic host page. That means we can now embed any 
> data in JSON format into the host page and the app reads this data on 
> initialization. With this in place we now add an app version to the host 
> page and send this app version to the server on each request (HTTP header). 
> A ServletFilter on the server checks the app version, compares it to the 
> server version and if the client is outdated it sends back a HTTP 409 
> CONFLICT response with the status APP_OUTDATED. The client app checks for 
> this response, notifies the user and reloads the app.
>
> In addition we also reload the app if a split point could not be 
> downloaded. This can happen sometimes after an app update, if permutation 
> names have changed and the logged in user tries to load a split point 
> without doing a GWT-RPC request beforehand.
>
> So far it works pretty well for us.
>
> -- J.
>
 
 

-- 
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+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/groups/opt_out.

GWT DevMode latest version (1.25 ?) crashes FireFox 24 ESR

[stuckagain]

Hi,
 
I am trying to run devmode on FireFox 24 ESR release, Plugin version says 
1.25.
When FireFox starts it crashes, when I delete the GWT DevMode plugin 
FireFox works again.
 
I can not upgrade to a newer version of FireFox since this is the version 
that our customers will use and so I want to debug in this version.
 
David

-- 
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+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/groups/opt_out.

Re: GWT RPC and DevMode

[stuckagain]

I will be responding to myself,

It looks like the rubber duck approach really works. If figured it out just 
after writing down my question :-S.

I just had to compare the contents of the .gwt.rpc files from the deployed 
ear/war and what DevMode was creating in the work directory.

There I found an extra little class from the gwt-user.jar, that was the 
cause. The DevMode setup  was still referring to an old gwt-user.jar from 
GWT 2.0 (while it also included the gwt2.5.1 jars).

So if anybody sees this gwt.rpc issue again in DevMode: locate the gwt.rpc 
files and compare them, it can give you a very good idea what is wrong!

David

On Friday, September 27, 2013 11:48:25 AM UTC+2, stuckagain wrote:
>
> Hi,
>
> I am failing to get DevMode working with a huge project. The main issue is 
> that as soon as I do a first RPC call I get a 
> IncompatibleRemoveServiceException.
> I cannot use the build in Jetty (this project uses EJBs, MQ, and zillions 
> of other technologies that require a full J2EE stack to run the server 
> side). I just need to be able to perform work on the GUI, which is 
> impossible unless I have DevMode working from Eclipse).
>
> I am assuming (since that has always been the case in other more simple 
> projects) that the root cause is that my sourcepath is different then when 
> the EAR was build. So I must be missing some serializable classes.
>
> Is there a way to find out what I am missing to make this work ? I get an 
> error that RPCMap was not assignable (while it certainly is). Can I easily 
> find out what subclasses of RPCMap devmode is expecting vs what the 
> compiled version was using ?
>
> I really would love to see GWT-RPC be replaced with something that does 
> not require a perfectly in sync client and server codebase!
>
> David
>

-- 
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+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/groups/opt_out.

GWT RPC and DevMode

[stuckagain]

Hi,

I am failing to get DevMode working with a huge project. The main issue is 
that as soon as I do a first RPC call I get a 
IncompatibleRemoveServiceException.
I cannot use the build in Jetty (this project uses EJBs, MQ, and zillions 
of other technologies that require a full J2EE stack to run the server 
side). I just need to be able to perform work on the GUI, which is 
impossible unless I have DevMode working from Eclipse).

I am assuming (since that has always been the case in other more simple 
projects) that the root cause is that my sourcepath is different then when 
the EAR was build. So I must be missing some serializable classes.

Is there a way to find out what I am missing to make this work ? I get an 
error that RPCMap was not assignable (while it certainly is). Can I easily 
find out what subclasses of RPCMap devmode is expecting vs what the 
compiled version was using ?

I really would love to see GWT-RPC be replaced with something that does not 
require a perfectly in sync client and server codebase!

David

-- 
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+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/groups/opt_out.

getting access to min-width of an element

[stuckagain]

Hi,

I am trying to get access to the min-width style property on some widget to 
be able to properly implement a layout.

When I use:
widget.getElement().getStyle().getProperty("minWidth") I always get "" as a 
result.

The min-width style is set like this:
.myclass {
  min-width: 200px;
}

...

I noticed that when I define the min-width as a style attribute then it 
works.
...

What I really need is a way to know what the computed value should be... 
and this should work on IE8+ and other browsers as well.

Anybody has a solution for this ?

David

-- 
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+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/groups/opt_out.

Re: TabLayoutPanel that dynamically resizes to selected tab content

[stuckagain]

Thanks for the suggestions. I will try the approach of using the 
TabLayoutPanel for just the tab bar and I will put a SimplePanel underneath 
to show the contents. That should be a minor change.
I need 2 kind of TabPanels in my application, sometimes it has to resize 
with the browser window and sometimes it needs to resize with the contents, 
it depends on the context.


On Friday, September 6, 2013 3:27:17 PM UTC+2, Thomas Broyer wrote:
>
> AFAICT, the problem of TabPanel is that it's based on a VerticalPanel with 
> a (customized) TabBar on the upper cell and a (customized) DeckPanel on the 
> lower cell; and the TabBar is given a width of 100% and the cell containing 
> the DeckPanel a height of 100%. This is what's likely to break in standards 
> mode (note: it's only about the rendering).
>
> BTW, TabBar has a similar problem (even though it's not documented).
>
> But well, the problem is mostly (if not uniquely) about the rendering, so 
> I'd say try it and if it works for you, then keep it. Otherwise roll your 
> own (the old KitchenSink sample used to have its own implementation of a 
> tab panel).
>
> As a workaround, maybe you could use a TabLayoutPanel with empty tabs to 
> work as a "tab bar", and a separate DeckPanel? (note: the TabLayoutPanel's 
> tab bar is simply a FlowPanel, and each tab is a SimplePanel with 
> a CommonResources.getInlineBlockStyle() style and a ClickHandler)
>
> On Friday, September 6, 2013 1:10:16 PM UTC+2, stuckagain wrote:
>>
>> Hi,
>>
>> I'm in the middle of moving from QuirksMode to Standards mode. And I am 
>> having an issue to emulate the old TabPanel with TabLayoutPanel.
>>
>> What I need is a TabLayoutPanel that resizes depending on the tab 
>> contents. The original TabPanel had that behaviour, 
>> but the TabLayoutPanel needs a fixed size.
>>
>> I found this thread in stackoverflow: 
>> http://stackoverflow.com/questions/5170324/tablayoutpanel-dynamic-resizing
>>
>> But I don't really like the proposed solution(s).
>>
>> 1) DecoratedTabPanel or TabPanel are not supposed to be used in standards 
>> mode (javadoc of TabPanel says so).
>> 2) hacking the TabLayoutPanel element styles is a bit messy since that is 
>> playing with the internals of the Widget.
>>
>> Any idea on how to implement this behaviour in a post QuirksMode 
>> environment, without risk of breaking when 2.6 or 3.0 
>> comes out ? I could create my own tabpanel implementation, but this seems 
>> such a basic requirement. With old GWT quirksmode I 
>> actually had to fight to get the opposite effect with the tabpanel.
>>
>> David
>>
>>

-- 
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+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/groups/opt_out.

Re: HeaderPanel not setting height of the Content widget

[stuckagain]

Patrick,

No, I don't know the height of the header, and I certainly don't want to 
set it in pixel sizes in the code either. (I even have the header change 
height depending on what the user is doing in there).
The question was about the content widget not being resized in a 
HeaderPanel, not the header that one works really well.

But the tip from Jens fixed it for me. I now enforce relative to the 
content container and force top,bottom,left,right at 0px. This removes the 
need for code to do size calculations and the content is resized and 
onResize is properly called automatically when the browser window resizes.

The only problem I have is that it is a bit a hack on the HeaderPanel, 
possible breaking in the future. It is not easy to implement a custom 
LayoutPanel since if you look at the implementation of HeaderPanel it is 
depending on quite a lot of internals of the Layout classes.


On Friday, September 6, 2013 2:17:24 PM UTC+2, Patrick Tucker wrote:
>
> If you have a set size for your header, you most likely should be using a 
> DockLayoutPanel.  The HeaderPanel should be used when you do not want to 
> restrict your header or footer to a particular size and allow it to be 
> whatever size it ends up being.

-- 
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+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/groups/opt_out.

TabLayoutPanel that dynamically resizes to selected tab content

[stuckagain]

Hi,

I'm in the middle of moving from QuirksMode to Standards mode. And I am 
having an issue to emulate the old TabPanel with TabLayoutPanel.

What I need is a TabLayoutPanel that resizes depending on the tab contents. 
The original TabPanel had that behaviour, 
but the TabLayoutPanel needs a fixed size.

I found this thread in 
stackoverflow: 
http://stackoverflow.com/questions/5170324/tablayoutpanel-dynamic-resizing

But I don't really like the proposed solution(s).

1) DecoratedTabPanel or TabPanel are not supposed to be used in standards 
mode (javadoc of TabPanel says so).
2) hacking the TabLayoutPanel element styles is a bit messy since that is 
playing with the internals of the Widget.

Any idea on how to implement this behaviour in a post QuirksMode 
environment, without risk of breaking when 2.6 or 3.0 
comes out ? I could create my own tabpanel implementation, but this seems 
such a basic requirement. With old GWT quirksmode I 
actually had to fight to get the opposite effect with the tabpanel.

David

-- 
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+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/groups/opt_out.

HeaderPanel not setting height of the Content widget

[stuckagain]

Hi,
 
I am trying to use the HeaderPanel to set a Header/Footer and an resizing 
ContentPanel (which contains a CellTable).
 
The problem is that unlike other LayoutPanel classes the vertical size is 
not enforced on the content widget, its width is set to 100% but the height 
is not set.
I don't really want to set width/height to 100% either since that would 
make it impossible to have a scrollbar.
 
Right now I have a solution in that I override the onResize method of the 
widget that gets inserted as the content panel. 
But that is not really nice in a framework where I have lots of reusable 
widgets, and I don't know which will be inserted in a HeaderPanel or not.
 
Any reason why this Layout Panel is not enforcing the height and width in 
pixels like other layout panels do on their children ?
 
David
 

-- 
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+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/groups/opt_out.

DataGrid and using Event.setCapture to implement column resizing.

[stuckagain]

Hi,
 
I'm currently implementing column resizing on DataGrid but I stumbled upon 
2 problems. Maybe somebody from the GWT team can help me out to solve this ?
It looks to me that those are bugs/features of the current 
DatatGrid/CellTable(s) ... but it would be great if I can get a complete 
working solution instead.
 
Problem 1: Event.setCapture does not seem to work when used in a Header.
 
My solution is to have a custom header that consumes mousedown,mouseup and 
mousemove events.
I check if a mousedown is happening on the last pixels of the column I use 
setCapture on the Element.
But, the capture does not work, events are still dispatched as if I did not 
call the setCapture.
I get the mousemove events in the other header cells instead of only on the 
capturing column header.
 
Is there a solution that allows me to capture all events when resizing the 
column ? The user has to be careful right now not to go outside the table 
header.
 
Problem 2: setColumnWidth does not force an onResize on the DataGrid.
 
To force a column resize I invoke the setColumnWidth method. My DataGrid 
table is wider than the allowed space, and so it needs an horizontal 
scrollbar.
However the scrollbar does not adjust automatically when I call the 
setColumnWidth method. It does however update when I resize the window.
 
I did a workaround by forcing onResize after calling the setColumnWidth, 
but shouln't the DataGrid do this automatically ?
 
David
 

-- 
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+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/groups/opt_out.

DataGrid sorting and using setList in ListDataProvider

[stuckagain]

Hi,
 
I just lost 2 hours on getting sorting to work correctly in my DataGrid 
backed by a ListDataProvider.
 
I was calling setList( rows ) on the DataProvider to update the table and 
that works... but sorting was not working (I could not even see the sort 
indicator on the table header cells).
Then it struct me: The ColumnSortEvent$ListHandler class takes a List as 
argument instead of the ListDataProvider.
When you call setList() on the DataProvider a new wrapper is created and my 
ListHandler is looking at the wrong one.
 
Wouldn't it be better that the ListHandler would keep a reference to the 
ListDataProvider instead ? Then it can call getList() on it when a sort is 
needed.
 
It is now a bit asymetric: calling setList() updates the table rows, but 
the sorter does not know... I am sure many people fall in this trap!
 
David

-- 
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+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/groups/opt_out.

Re: GWT website moved to gwtproject.org

[stuckagain]

Hi,

Not being search indexable is a bit a weak spot for GWT right now, although 
I guess there have been some solutions ... maybe a good tutorial on how to 
do this would be nice in the documentation.

The docs are not reloading that was my mistake. I am just losing track a 
bit because the table of contents on the left do not stay in place. This is 
sometimes a bit disorienting when the menu scrolls away when I click on a 
link in the docs.

David


On Wednesday, July 3, 2013 11:22:57 AM UTC+2, Daniel Kurka wrote:
>
> Thanks for your feedback David. 
>
> The webpage need to be search index able, this is why we decided to go 
> with plain HTML, but it uses GWTQuery to do progressive enhancement so the 
> page should not load entirely if you have javascript enabled.
> It will change the URL though by using the html5 history API.
>
> If this is reloading for you please file a bug.
>
> - Daniel
>
>
> On Wed, Jul 3, 2013 at 10:59 AM, stuckagain 
> > wrote:
>
>> Great work!
>>  
>> Wouldn't it be nice if the online docs would have been created as a GWT 
>> application as well ? 
>> Right now navigation in the documentation is a bit '90s style where I 
>> always lose track of the index since the whole page is reloaded when I 
>> click on a subject.
>>  
>> It could be a very nice tutorial on how to support site navigation and 
>> even integrate search functionality in a GWT application
>>  
>> David
>>
>> On Tuesday, July 2, 2013 10:57:49 PM UTC+2, Daniel Kurka wrote:
>>
>>> Today we finally flipped the switch and moved all the GWT content from 
>>> developers.google.com to gwtproject.org. The old homepage will redirect 
>>> to gwtproject.org so there should be no broken links. However if you 
>>> encounter any missing content or broken links please file a 
>>> bug<https://code.google.com/p/google-web-toolkit/issues/entry>
>>> .
>>>
>>> Why did we do this?
>>>
>>> GWT is now an open source project and we wanted to enable people to 
>>> contribute to the website and documentation as well. Since 
>>> developers.google.com can only be updated by Google employees we needed 
>>> another home.
>>>
>>> - Daniel, on behalf of the GWT team
>>
>>  -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Google Web Toolkit" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-web-toolkit/-YmZuKDLdS4/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-web-toolkit+unsubscr...@googlegroups.com .
>> To post to this group, send email to 
>> google-we...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>
>
> -- 
> Google Germany GmbH
> *Dienerstr. 12*
> *80331 München*
>
> Registergericht und -nummer: Hamburg, HRB 86891
> Sitz der Gesellschaft: Hamburg
> Geschäftsführer: Graham Law, Katherine Stephens
>  

-- 
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+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/groups/opt_out.

Re: GWT website moved to gwtproject.org

[stuckagain]

Great work!
 
Wouldn't it be nice if the online docs would have been created as a GWT 
application as well ? 
Right now navigation in the documentation is a bit '90s style where I 
always lose track of the index since the whole page is reloaded when I 
click on a subject.
 
It could be a very nice tutorial on how to support site navigation and even 
integrate search functionality in a GWT application
 
David

On Tuesday, July 2, 2013 10:57:49 PM UTC+2, Daniel Kurka wrote:

> Today we finally flipped the switch and moved all the GWT content from 
> developers.google.com to gwtproject.org. The old homepage will redirect 
> to gwtproject.org so there should be no broken links. However if you 
> encounter any missing content or broken links please file a 
> bug
> .
>
> Why did we do this?
>
> GWT is now an open source project and we wanted to enable people to 
> contribute to the website and documentation as well. Since 
> developers.google.com can only be updated by Google employees we needed 
> another home.
>
> - Daniel, on behalf of the GWT team

-- 
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+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/groups/opt_out.

Re: Issue 8166 created RPC issue in Chrome

[stuckagain]

Aha,

It seems to be caused by this bug:
https://code.google.com/p/google-web-toolkit/issues/detail?id=6194
and another related one:
https://code.google.com/p/google-web-toolkit/issues/detail?id=6130

Yep again bugs with low Hollywood star ratings, that made me loose half a 
day of searching.

David


On Wednesday, May 29, 2013 4:43:53 PM UTC+2, stuckagain wrote:
>
> Hi,
>
> I stumbled upon a strange RPC serialisation error with GWT 2.5.1:
> https://code.google.com/p/google-web-toolkit/issues/detail?id=8166
>
> For some reason an int is serialized as a float in some very specific case 
> in my application.
> The result is an IncompatibleRemoteService exception being thrown.
>
> Note that this seems to only happen in Chrome (IE8, FireFox seems to be 
> working fine).
>
> Is there specific code for Chrome to serialize RPC payloads ? I did not 
> really find it...
> Is this a bug in GWT or Chrome ?
>
> David
>
>
>

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Issue 8166 created RPC issue in Chrome

[stuckagain]

Hi,

I stumbled upon a strange RPC serialisation error with GWT 2.5.1:
https://code.google.com/p/google-web-toolkit/issues/detail?id=8166

For some reason an int is serialized as a float in some very specific case 
in my application.
The result is an IncompatibleRemoteService exception being thrown.

Note that this seems to only happen in Chrome (IE8, FireFox seems to be 
working fine).

Is there specific code for Chrome to serialize RPC payloads ? I did not 
really find it...
Is this a bug in GWT or Chrome ?

David


-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

GWT Window Managers ?

[stuckagain]

Hi,

I need a window manager for a GWT application that was using GXT. It seems 
like all development stopped somewhere in 2010 since both GWT Window 
Manager and GWT Mosaic stopped being updated since then (and a lot of other 
GWT libraries as well). It does not seem like a big job to support 
resizable dialogs now that there are LayoutPanels in GWT.

Are there plans to implement a window manager in GWT now that this is in 
the hands of the steering committee ?

David

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to centre fixed size panel inside another layout panel or screen

[stuckagain]

Hi Jens,
 
Great, it works exactly as I want! Such a simple approach as well, it 
should be part of GWT though.
 
David

On Thursday, February 2, 2012 1:23:57 AM UTC+1, espinosa_cz wrote:

> Hi guys, 
>
> I manage to put my context panel to the middle of the browser page in 
> Vaadin. Seem my screenshots. It is done purely in Java code, the only 
> CSS used is for setting colors and font sizes. 
> Now I wondering how to make something similar with vanilla GWT. 
>
> In Vaadin it is one line command! 
> ((VerticalLayout)outerContentPanel).setComponentAlignment(contextPanel, 
> Alignment.MIDDLE_CENTER); 
> What is the GWT equivalent? 
>
> How to centre a fixed size panel (LayoutPanel) inside resizable parent 
> container, let's say RootLayoutPanel as it is in this picture? 
>
> http://espinosa.s3-website-eu-west-1.amazonaws.com/vvregform2/vvregform/vvregform_progress_2011-01-24_-_screenshot_1.png
>  
>
> The central panel (form) can grow, see here: 
>
> http://espinosa.s3-website-eu-west-1.amazonaws.com/vvregform2/vvregform/vvregform_progress_2011-01-24_-_screenshot_3.png
>  
> so the solution  must be flexible, accommodate any change in the 
> central panel. 
>
> Preferably programmatically (no UiBinding) and ideally without special 
> CSS tricks. 
>
> I made some progress with encapsulated LayoutPanels and setting 
> WidgetLeftRight and WidgetTopBottom. But I cannot figure out what 
> values make it centered for any particular inner contextPanel sizes: 
>
> // “parent”, outer content panel, make it fill whole screen (page) 
> LayoutPanel outerContentPanel = new LayoutPanel(); 
> outerContentPanel.setStyleName("outerContextPanel"); 
> outerContentPanel.setHeight("100%"); 
> outerContentPanel.setWidth("100%"); 
>
> // inner content panel 
> LayoutPanel contentPanel = new LayoutPanel(); 
> outerContentPanel.add(contentPanel); 
> contentPanel.setStyleName("contextPanel"); 
> contentPanel.setSize("300px", "300px"); 
>
> // make it centered () 
> outerContentPanel.setWidgetLeftRight(contentPanel, 50, Unit.PCT, 0, 
> Unit.PCT); 
> outerContentPanel.setWidgetTopBottom(contentPanel, 50, Unit.PCT, 0, 
> Unit.PCT); 
>
> // put some fancy content iside 
> HTML html = new HTML("Hello world centered!"); 
> contentPanel.add(html); 
>
> // set as 
> RootLayoutPanel.get().add(outerContentPanel) 
>
> As values I tried 50% from all directions sides, it makes central 
> contextPanel nicely centred but also invisible, clipped completely. 
> When I use 50% from top and left only, 0% from bottom and right, the 
> left top corner of the inner panel is centered, nice, but i need to 
> get centered by its center. 
>
> I am out of my wits now 
> Any hints welcome 
> Thank you 
> Espinosa 
>

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to centre fixed size panel inside another layout panel or screen

[stuckagain]

Hi,
 
Maybe you should file a bug report, a center layout or something would be 
great! Or indeed support for Alignment.MIDDLE.
 
I'm in the progress of updating and old code base to standards compliant 
mode and centering widget on the window is used all over the place. 
Before I could just set the height of a table to 100% and using 3 columns, 
and let the browser figure out row distribution, but this no longer works 
in standards mode.
 
David

On Thursday, February 2, 2012 9:16:10 PM UTC+1, espinosa_cz wrote:

> Lets look at it from a different angle. 
> There is a familiar example in GWT documentation: 
>
> http://code.google.com/webtoolkit/doc/latest/DevGuideUiPanels.html#LayoutPanels
>  
>
> Widget child0, child1, child2; 
> LayoutPanel p = new LayoutPanel(); 
> p.add(child0); p.add(child1); p.add(child2); 
>
> p.setWidgetLeftWidth(child0, 0, PCT, 50, PCT);  // Left panel 
> p.setWidgetRightWidth(child1, 0, PCT, 50, PCT); // Right panel 
>
> p.setWidgetLeftRight(child2, 5, EM, 5, EM); // Center panel 
> p.setWidgetTopBottom(child2, 5, EM, 5, EM); 
>
> How to define the center panel using flexible percents (PCT) and not 
> fixed size? 
> Why is there exactly 5 EM by the way? 
>
> Espinosa

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Java 7

[stuckagain]

Java 6 is still used a lot in enterprise developments, I am actually more 
looking forward to Java 8 support due to project lambda which could have a 
very nice impact on readability of all these async operations we tend to 
chain together in GWT client applications.

On Tuesday, April 16, 2013 9:12:55 AM UTC+2, Ed wrote:
>
> I invite you to contribute the java support 7. You can do this together 
> with your "teammates"
> Why not? 
>
> It's all a matter of priorties, vote an issue in the issue tracker and it 
> will get a higher priority
> Wouldn't it be nice that you could latter say that you were responsibly 
> for the jdk 7 support in gwt?
>
>
>
> On Tue, Apr 16, 2013 at 7:28 AM, Gilberto 
> > wrote:
>
>> It's just my opinion, but in my mind making the JDK compliance to 1.6 and 
>> call that "fully compatible with JDK 7" is not... well... what I was 
>> expecting (at least).
>>
>> I understand that tweaking the compiler to actually and truly support 
>> Java 7 is not easy and demand time. But Java 7 is around for ... uh... 
>> years? (since July - 2011 according to Wikipedia). I understand that GWT is 
>> now handled by a committee, since last year. And still, there's no public 
>> roadmap of when we are going to have the real Java 7 support (and I'm not 
>> even talking about Java 8). So, eh, am I wrong on asking such things? 
>> Should I recommend other frameworks to my teammates for new projects or 
>> still wait for news from GWT?
>>
>> I understand we have to wait till you guys commit the code to 
>> Gerrit/GitHub, to organize the project, to mavenize it, to deal with 
>> contributors, Google itself and so on. But till when?
>>
>> Sorry for my impatience, but at this stage I don't really feel 
>> comfortable with the situation. Maybe it's only me.
>>
>> On Wednesday, April 3, 2013 5:09:35 AM UTC-3, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Wednesday, April 3, 2013 8:15:03 AM UTC+2, Max Völkel wrote:

 How well does this play together with AppEngine 1.7.7? From their 
 release notes: "The Java runtime now defaults to Java7. If you still 
 need to use the Java6
   runtime, please use the --use_java6 flag when deploying your app. We 
 encourage
   you to move to Java7 as soon as possible."

 It sounds I should compile for a 1.7 target. So I should *not* set 
 maven.compiler.source to 1.6, right?

>>>
>>> I don't know how AppEngine's Java runtime works, but my 7 and 8 JREs are 
>>> very well capable of running classes compiled with -target 1.6 or earlier, 
>>> and mixing classes compiled with different -target (you'd never be able to 
>>> use Maven, or pretty much any third-party dependency actually, if that 
>>> wasn't the case; btw GWT is compiled with -target 1.6 and is fully 
>>> compatible with a JDK 7, and we haven't yet heard of anyone having issues 
>>> using RPC or RequestFactory on AppEngine)
>>>
>>>  -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Google Web Toolkit" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-web-toolkit/dM8D9imIvAI/unsubscribe?hl=en
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-web-toolkit+unsubscr...@googlegroups.com .
>> To post to this group, send email to 
>> google-we...@googlegroups.com
>> .
>> Visit this group at 
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GWT issues while waiting for gwtproject ?

[stuckagain]

I glanced at the CellWidgets and Cell.Context class and it does look too 
much row/column based to me.

I am still not convinced that this is what I need, but I will try and setup 
some proof of concept to use CellWidgets. On the other hand, this is really 
mostly a client side technology, while I need the ability to also render 
serverside, used for reporting or for slower browsers.

I'm rendering a form defined in a XSD, the XSD can be a few megabytes big, 
so we are talking about huge forms here. And the layout needs to be 
flexible, not constraint to row/column positioning like in a table or tree. 
Although a tree does come very close to what I need, so if I can finetune 
the CellTree maybe I can get close to what I want. if only we had a 
CellTreeTable with scrolling, resizeable columns, ... etc. 

David

On Tuesday, April 16, 2013 9:00:45 AM UTC+2, Ümit Seren wrote:
>
> Well you can use a CellWidget (
> http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/cellview/client/CellWidget.html
> ). 
> The nice thing is that you can actually create a custom cell that you can 
> use inside a DataGrid/CellTable/CellList/CellTree and also use it outside 
> of these via a CellWidget.
>
> On Monday, April 15, 2013 5:37:04 PM UTC+2, stuckagain wrote:
>>
>> Hi,
>>
>> The HTML that is being put in the HTMLPanel is generated and inserted as 
>> one big HTML string.
>> The HTML can either be generated in Javascript or on the server.
>>
>> If CellWidgets are an alternative then I am certainly interested in 
>> checking them out, but I though they were only useful in CellTable and 
>> CellTree.
>>
>> David
>>
>> On Monday, April 15, 2013 4:36:23 PM UTC+2, Ümit Seren wrote:
>>>
>>> Any reason for not using CellWidgets instead of HTMLPanels ? 
>>>
>>>
>>> On Monday, April 15, 2013 4:18:33 PM UTC+2, stuckagain wrote:
>>>>
>>>> Hi,
>>>>
>>>> Are we allowed to add bugs in the bugtracking in the middle of the 
>>>> migration to gwtproject ?
>>>> I recently added a few and I hope that sometimes they will be sorted 
>>>> out.
>>>>
>>>> My last one was a performance bottleneck on HTMLPanel with many widgets 
>>>> being added 
>>>> (due to the very inefficient WidgetCollection implementation).
>>>> https://code.google.com/p/google-web-toolkit/issues/detail?id=8105
>>>>
>>>> After looking at my reported bugs, I can see that most of my bug 
>>>> reports never made it to being implemented or even accepted or rejected 
>>>> (one got fixed quickly since I contributed the change)
>>>> I hope that the gwtproject will improve on this - it is a really 
>>>> frustrating feeling and makes me wonder if I should stick on using GWT and 
>>>> reorient to non google technologies instead (Axing Google Reader will 
>>>> probably drive me over the edge if I don't find a decent alternative 
>>>> pretty 
>>>> soon). 
>>>>
>>>> David
>>>>
>>>

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GWT issues while waiting for gwtproject ?

[stuckagain]

Jens,

That would be an understatement :-) 

I am still positive that the bug triage disaster gets fixed because that is 
fundamental to the success of opensource. And I saw in the gwt-steering 
news group that they are going for some interesting roadmap, so I live in 
hope.
I would love to contribute, but only if I can be sure that it will get 
accepted (most of the time).

I can not keep on defending the usage of GWT to my boss/company if we don't 
get some minimal feedback and support. I need to do a technology assessment 
right now, and I really don't know how to defend the choice right now.
Some people have talked about AngularJS, Dart and other interesting 
technologies, but that is Google tech as well, so potentially subject to be 
scrapped much faster than what we like.

As for Feedly: it does not work in IE. I need Chrome, iOS and IE support 
for a feed reader. But let's not dwell on this subject in this newsgroup. 

David

On Monday, April 15, 2013 5:00:24 PM UTC+2, Jens wrote:
>
> You can still file bugs to the tracker. I guess its just missing men power 
> to keep the tracker up-to-date and verify/triage issues. Also the tracker 
> is pretty huge and issues can be missed easily, especially if they are not 
> up-voted. 
>
> Regarding Google Reader: I switched to feedly and it works pretty well.
>
> -- J.
>

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GWT issues while waiting for gwtproject ?

[stuckagain]

Hi,

The HTML that is being put in the HTMLPanel is generated and inserted as 
one big HTML string.
The HTML can either be generated in Javascript or on the server.

If CellWidgets are an alternative then I am certainly interested in 
checking them out, but I though they were only useful in CellTable and 
CellTree.

David

On Monday, April 15, 2013 4:36:23 PM UTC+2, Ümit Seren wrote:
>
> Any reason for not using CellWidgets instead of HTMLPanels ? 
>
>
> On Monday, April 15, 2013 4:18:33 PM UTC+2, stuckagain wrote:
>>
>> Hi,
>>
>> Are we allowed to add bugs in the bugtracking in the middle of the 
>> migration to gwtproject ?
>> I recently added a few and I hope that sometimes they will be sorted out.
>>
>> My last one was a performance bottleneck on HTMLPanel with many widgets 
>> being added 
>> (due to the very inefficient WidgetCollection implementation).
>> https://code.google.com/p/google-web-toolkit/issues/detail?id=8105
>>
>> After looking at my reported bugs, I can see that most of my bug reports 
>> never made it to being implemented or even accepted or rejected (one got 
>> fixed quickly since I contributed the change)
>> I hope that the gwtproject will improve on this - it is a really 
>> frustrating feeling and makes me wonder if I should stick on using GWT and 
>> reorient to non google technologies instead (Axing Google Reader will 
>> probably drive me over the edge if I don't find a decent alternative pretty 
>> soon). 
>>
>> David
>>
>

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

GWT issues while waiting for gwtproject ?

[stuckagain]

Hi,

Are we allowed to add bugs in the bugtracking in the middle of the 
migration to gwtproject ?
I recently added a few and I hope that sometimes they will be sorted out.

My last one was a performance bottleneck on HTMLPanel with many widgets 
being added 
(due to the very inefficient WidgetCollection implementation).
https://code.google.com/p/google-web-toolkit/issues/detail?id=8105

After looking at my reported bugs, I can see that most of my bug reports 
never made it to being implemented or even accepted or rejected (one got 
fixed quickly since I contributed the change)
I hope that the gwtproject will improve on this - it is a really 
frustrating feeling and makes me wonder if I should stick on using GWT and 
reorient to non google technologies instead (Axing Google Reader will 
probably drive me over the edge if I don't find a decent alternative pretty 
soon). 

David

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: IE Anchor Issue

[stuckagain]

Hi,
 
All I do is cancel the default handling of the ClickEvent
I'm not using the anchor widget but the element directly but I assume it 
should work the same.
 
anchor.addClickHandler() { new ClickHandler() {
   public void onClick( ClickEvent event ) {
 event.preventDefault();
   }
});
 

On Sunday, March 3, 2013 7:30:45 PM UTC+1, Lars wrote:

> I'm running into the problem with Anchor widgets trying to reload the 
> browser when clicked... After searching the forums I've seen the various 
> workaround people are using but none seem applicable. Maybe someone has any 
> ideas?
>
> What I have is a Composite that implements HasClickHandlers... This 
> Composite basically contains some textual display info and an edit link and 
> are created and added by its parent widget and presented to the user. As a 
> parent creates these composites it adds a click handler to them and to see 
> if the user hits the edit button. 
>
> Relevant code:
>
> public class CategoryPromoLink extends Composite implements 
> HasClickHandlers {
>...
>...
>// constructor:
>CategoryPromoLink(String categoryDirectoryName, String 
> categoryDisplayName, String heading, String annotation, String startTime, 
> int rank) {
>
> this.categoryDirectoryName = categoryDirectoryName;
> this.categoryDisplayName = categoryDisplayName;
>
> this.heading = heading;
> this.annotation = annotation;
> this.startTime = startTime;
> this.rank = rank;
>
> this.initWidget(this.root);
>
> this.display = new InlineLabel("- " + 
> (categoryDisplayName.trim().equals("") ? "[UNKNOWN CATEGORY]" : 
> categoryDisplayName));
> this.root.add(this.display);
>
> Anchor edit = new Anchor("(edit)");
> edit.addClickHandler(new ClickHandler() {
>
>   @Override
>   public void onClick(ClickEvent event) {
> CategoryPromoLink.this.fireEvent(event);
>   }
>
> });
>
> this.root.add(edit);
>
>   }
>   
>...
>...
>
>   @Override
>   public HandlerRegistration addClickHandler(ClickHandler handler) {
> return this.addHandler(handler, ClickEvent.getType());
>   }
>
>
> }
>
>
> Works fine in all but IE, where when the "edit" anchor is clicked it tries 
> to reload page (in my case since i'm using GWT Activities with an 
> "onMayStop" implementation its asking the user if they want to leave or 
> stay on this page).
>
> Should i not be using ClickHandlers and/or Anchors this way?
>
> Thanks.
>
>

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GWT RPC future ?

[stuckagain]

Hi,
 
I guess they could improve by making these object lazy, that would provide 
a better synergy between runtime performance and serialisation performance.
BigInteger and Long could keep a reference to the String representation (or 
something other efficient) and just convert to the internal representation 
when absolutely needed (when doing calculations).
 
That is basically what I did for the BigInteger issue I had. But I just 
implemented my own BigInteger and custom serializer that just disable all 
methods except a few. I don't need calculations on these objects, but 
changing the 2000+ references is not an option - nobody ever listens to 
remarks of the GUI guys but we are always blamed when the appcation is not 
responsive.
 
David
On Monday, March 4, 2013 1:10:55 AM UTC+1, Evan Ruff wrote:

> Guys,
>
> On the heels of David's post, I was going through my application and 
> noticed some poor RPC performance as well... much poorer than I remember. I 
> went through my code and noticed that I'm using Longs in every object, as 
> that's the default @Id for Objectify on AppEngine.  Is there a simple way 
> to get the GWT-RPC to serialized these differently by default? I'd really 
> like to keep everything as is without having to swap out everything, as the 
> Android and AppEngine Servlets are working great.
>
> Thanks!
>
> E
>
> On Tuesday, February 26, 2013 4:55:56 AM UTC-5, stuckagain wrote:
>>
>> People,
>>
>> Just to post some feedback on my problem, I actually found a working 
>> solution and I think there is a lesson in here that it warrant me writing 
>> back in this thread.
>>
>> I managed to implement my own custom serialisation based on the flickr 
>> post. I managed to double the performance and I implemented it so that I 
>> don't use recursion to make it possible to move to an incremental approach 
>> to avoid stack overflows.
>>
>> But x2 is still too long to be acceptable so I ran it through the IE9 
>> profiler and I noticed that most of the time was actually spent in 
>> BigInteger and Long methods...
>>
>> That made me remember the discussion a long time ago that longs are 
>> emulated in GWT and we should avoid them unless absolutely needed. I 
>> switched to sending a byte array for these id fields and I got a 10x speed 
>> increase (and that is with the regular GWT serialisation, not my own 
>> version). I did not realize that Longs were that costly (on IE).
>>
>> So, that resolves the performance issue for me. Sure, another round of 
>> thinking is needed to avoid sending such large object trees in the first 
>> place, but this offers an acceptable solution for now - and since browsers 
>> like Chrome and FireFox (and even IE) are becoming much faster I might not 
>> even need to further improve it.
>>
>> David
>>
>> On Wednesday, February 13, 2013 5:31:10 PM UTC+1, stuckagain wrote:
>>>
>>> Thomas,
>>>
>>> I just read the article on how they improved parsing time in flickr ... 
>>> really simplistic and a big surprise that the split trick is as fast as 
>>> native json parsing! 
>>> Would such an approach be usable for a generic object 
>>> serialisation/deserialisation approach ? 
>>>
>>> David
>>>
>>> On Wednesday, February 6, 2013 5:17:33 PM UTC+1, Thomas Broyer wrote:
>>>>
>>>>
>>>>
>>>> On Wednesday, February 6, 2013 4:37:35 PM UTC+1, stuckagain wrote:
>>>>>
>>>>> Hi,
>>>>>  
>>>>> Not sure where to ask this question, but I was wondering if the GWT 
>>>>> devs every plan to fix the inefficient GWT-RPC ?
>>>>> The problem happens mostly on IE (all versions), although I assume 
>>>>> other browsers might benefit as well since a lot of cpu cycles are wasted 
>>>>> on things that should be trivial for a browser.
>>>>>  
>>>>> I had to improve multiple GWT apps that all stumble on these 3 
>>>>> problems:
>>>>> - deserialisation is terribly inefficient - it can take many seconds 
>>>>> to serialize small sets of data,
>>>>> - on IE I can get slow script warnings
>>>>> - I sometimes get stack over flows with deeply nested structures.
>>>>>  
>>>>> For example when I send over a tree of 1 nodes (takes 20ms to 
>>>>> create), it takes 5 seconds or more to deserialize. (I can give you a 
>>>>> demo 
>>>>> app that shows the problem)
>>>>>  
>>>&g

Re: GWT RPC future ?

[stuckagain]

People,

Just to post some feedback on my problem, I actually found a working 
solution and I think there is a lesson in here that it warrant me writing 
back in this thread.

I managed to implement my own custom serialisation based on the flickr 
post. I managed to double the performance and I implemented it so that I 
don't use recursion to make it possible to move to an incremental approach 
to avoid stack overflows.

But x2 is still too long to be acceptable so I ran it through the IE9 
profiler and I noticed that most of the time was actually spent in 
BigInteger and Long methods...

That made me remember the discussion a long time ago that longs are 
emulated in GWT and we should avoid them unless absolutely needed. I 
switched to sending a byte array for these id fields and I got a 10x speed 
increase (and that is with the regular GWT serialisation, not my own 
version). I did not realize that Longs were that costly (on IE).

So, that resolves the performance issue for me. Sure, another round of 
thinking is needed to avoid sending such large object trees in the first 
place, but this offers an acceptable solution for now - and since browsers 
like Chrome and FireFox (and even IE) are becoming much faster I might not 
even need to further improve it.

David

On Wednesday, February 13, 2013 5:31:10 PM UTC+1, stuckagain wrote:
>
> Thomas,
>
> I just read the article on how they improved parsing time in flickr ... 
> really simplistic and a big surprise that the split trick is as fast as 
> native json parsing! 
> Would such an approach be usable for a generic object 
> serialisation/deserialisation approach ? 
>
> David
>
> On Wednesday, February 6, 2013 5:17:33 PM UTC+1, Thomas Broyer wrote:
>>
>>
>>
>> On Wednesday, February 6, 2013 4:37:35 PM UTC+1, stuckagain wrote:
>>>
>>> Hi,
>>>  
>>> Not sure where to ask this question, but I was wondering if the GWT devs 
>>> every plan to fix the inefficient GWT-RPC ?
>>> The problem happens mostly on IE (all versions), although I assume other 
>>> browsers might benefit as well since a lot of cpu cycles are wasted on 
>>> things that should be trivial for a browser.
>>>  
>>> I had to improve multiple GWT apps that all stumble on these 3 problems:
>>> - deserialisation is terribly inefficient - it can take many seconds to 
>>> serialize small sets of data,
>>> - on IE I can get slow script warnings
>>> - I sometimes get stack over flows with deeply nested structures.
>>>  
>>> For example when I send over a tree of 1 nodes (takes 20ms to 
>>> create), it takes 5 seconds or more to deserialize. (I can give you a demo 
>>> app that shows the problem)
>>>  
>>> I only get 2 seconds to impress my users, and I need to do quite a lot 
>>> of operations besides sending the RPC.
>>>  
>>> I've heared the reactions multiple times: don't send soo much data over, 
>>> but bytewise this is not soo much. It is highly compressible (just a few K 
>>> in fact) data. We want to process complex data structures in the client, we 
>>> don't want to create intermediate data structures to bypass the RPC 
>>> inefficiencies.
>>>  
>>> There have been multiple attempts from google to write something better 
>>> (DeRPC whichi is now deprecated, and RequestFactory which is very badly 
>>> documented so I don't even know if I could reuse this one for generic RPC 
>>> calls).
>>>
>>
>> Indeed RequestFactory can be used for "generic RPC".
>> Have a look at http://tbroyer.posterous.com/gwt-211-requestfactory and 
>> http://tbroyer.posterous.com/gwt-211-requestfactory-part-ii
>> It's rather old and might be inaccurate in a few places (hasn't been 
>> updated for GWT 2.4's use of annotation-processing at compile-time, for 
>> instance).
>>  
>>
>>>  
>>> Is it not time to start using json as the base format for GWT RPC ? I 
>>> would even like to help out to get this working! It is really a pitty that 
>>> somehow RPC is a selling point for GWT but in reality it often becomes the 
>>> bottleneck of your application.
>>>
>>  
>>> Can't we maybe put GWT RPC on the framework for request factory ?
>>>  
>>> One issue I also have with GWT RPC (but less pressing as the 
>>> performanceissue) is the fact that it is not very friendly for mixing 
>>> different client technologies. If it were a simple json REST payload 
>>> (without obfuscation and lots of secret numbers) then we could easily reuse 
>>> it eve

Re: GWT RPC future ?

[stuckagain]

Thomas,

I just read the article on how they improved parsing time in flickr ... 
really simplistic and a big surprise that the split trick is as fast as 
native json parsing! 
Would such an approach be usable for a generic object 
serialisation/deserialisation approach ? 

David

On Wednesday, February 6, 2013 5:17:33 PM UTC+1, Thomas Broyer wrote:
>
>
>
> On Wednesday, February 6, 2013 4:37:35 PM UTC+1, stuckagain wrote:
>>
>> Hi,
>>  
>> Not sure where to ask this question, but I was wondering if the GWT devs 
>> every plan to fix the inefficient GWT-RPC ?
>> The problem happens mostly on IE (all versions), although I assume other 
>> browsers might benefit as well since a lot of cpu cycles are wasted on 
>> things that should be trivial for a browser.
>>  
>> I had to improve multiple GWT apps that all stumble on these 3 problems:
>> - deserialisation is terribly inefficient - it can take many seconds to 
>> serialize small sets of data,
>> - on IE I can get slow script warnings
>> - I sometimes get stack over flows with deeply nested structures.
>>  
>> For example when I send over a tree of 1 nodes (takes 20ms to 
>> create), it takes 5 seconds or more to deserialize. (I can give you a demo 
>> app that shows the problem)
>>  
>> I only get 2 seconds to impress my users, and I need to do quite a lot of 
>> operations besides sending the RPC.
>>  
>> I've heared the reactions multiple times: don't send soo much data over, 
>> but bytewise this is not soo much. It is highly compressible (just a few K 
>> in fact) data. We want to process complex data structures in the client, we 
>> don't want to create intermediate data structures to bypass the RPC 
>> inefficiencies.
>>  
>> There have been multiple attempts from google to write something better 
>> (DeRPC whichi is now deprecated, and RequestFactory which is very badly 
>> documented so I don't even know if I could reuse this one for generic RPC 
>> calls).
>>
>
> Indeed RequestFactory can be used for "generic RPC".
> Have a look at http://tbroyer.posterous.com/gwt-211-requestfactory and 
> http://tbroyer.posterous.com/gwt-211-requestfactory-part-ii
> It's rather old and might be inaccurate in a few places (hasn't been 
> updated for GWT 2.4's use of annotation-processing at compile-time, for 
> instance).
>  
>
>>  
>> Is it not time to start using json as the base format for GWT RPC ? I 
>> would even like to help out to get this working! It is really a pitty that 
>> somehow RPC is a selling point for GWT but in reality it often becomes the 
>> bottleneck of your application.
>>
>  
>> Can't we maybe put GWT RPC on the framework for request factory ?
>>  
>> One issue I also have with GWT RPC (but less pressing as the 
>> performanceissue) is the fact that it is not very friendly for mixing 
>> different client technologies. If it were a simple json REST payload 
>> (without obfuscation and lots of secret numbers) then we could easily reuse 
>> it everwhere, it would also make it soo much easier for loadtesting. Not a 
>> lot of tools support GWT RPC easily.
>>
>
> RequestFactory can easily be used in-process within tests, and ships with 
> a pure-Java client (usable on Android for instance). It comes with 2 
> "dialects" under the same API: its own RequestFactory protocol (JSON-based) 
> that deals with batching of method calls and sending only diffs for 
> entities, and JSON-RPC. The server-side component only supports the former 
> dialect though, the latter is only about using existing JSON-RPC services 
> (such as Google APIs) from a Java or GWT app.
>
> That said, I doubt RequestFactory would perform better for your 1 
> nodes use-case (I think we can even say it will perform much worse than 
> RPC; this can probably be improved by doing more codegen at compile-time 
> and less reflection at runtime, but I'm not sure it'd even be better than 
> RPC; this is mostly about the server-side though, and possibly DevMode too; 
> it should be an all different story if you use the JSON-RPC dialect).
>
> An alternative to RPC and RF, using (a slightly modified) JSON-RPC 
> protocol with an RPC-like API is gwt-json-rpc, used by Gerrit: 
> https://gerrit.googlesource.com/gwtjsonrpc/ You'll find the JAR in a 
> Maven repo at https://gerrit-maven-repository.googlecode.com/svn/ (Gerrit 
> itself references https://gerrit-maven.commondatastorage.googleapis.comso I 
> think the googlecode repo is an old one; the 
> commondatastorage.googleapis one is not browsable though so it'

Re: GWT RPC future ?

[stuckagain]

Thomas and Paul,
 
Thanks for all the info, I will certainly look into these alternatives. 
 
The only problem is that somehow GWT should include a fast generic RPC 
mechanism. I hate having to depend on 3rd party alternatives that are often 
writen by one individual to solve his own issue and never maintained. I am 
writing banking software and we have some strict requirements on what 
products we are allowed to use since we have some very tight end-user 
licenses that requires us to fix issues very quickly. 
 
But somehow RPC is fundamental to AJAX apps build on GWT and it is a shame 
that we have almost no support for JSON-REST kind of APIs since that is 
what most people seem to be using.
 
David

On Wednesday, February 6, 2013 5:17:33 PM UTC+1, Thomas Broyer wrote:

>
>
> On Wednesday, February 6, 2013 4:37:35 PM UTC+1, stuckagain wrote: 
>>
>> Hi,
>>  
>> Not sure where to ask this question, but I was wondering if the GWT devs 
>> every plan to fix the inefficient GWT-RPC ?
>> The problem happens mostly on IE (all versions), although I assume other 
>> browsers might benefit as well since a lot of cpu cycles are wasted on 
>> things that should be trivial for a browser.
>>  
>> I had to improve multiple GWT apps that all stumble on these 3 problems:
>> - deserialisation is terribly inefficient - it can take many seconds to 
>> serialize small sets of data,
>> - on IE I can get slow script warnings
>> - I sometimes get stack over flows with deeply nested structures.
>>  
>> For example when I send over a tree of 1 nodes (takes 20ms to 
>> create), it takes 5 seconds or more to deserialize. (I can give you a demo 
>> app that shows the problem)
>>  
>> I only get 2 seconds to impress my users, and I need to do quite a lot of 
>> operations besides sending the RPC.
>>  
>> I've heared the reactions multiple times: don't send soo much data over, 
>> but bytewise this is not soo much. It is highly compressible (just a few K 
>> in fact) data. We want to process complex data structures in the client, we 
>> don't want to create intermediate data structures to bypass the RPC 
>> inefficiencies.
>>  
>> There have been multiple attempts from google to write something better 
>> (DeRPC whichi is now deprecated, and RequestFactory which is very badly 
>> documented so I don't even know if I could reuse this one for generic RPC 
>> calls).
>>
>
> Indeed RequestFactory can be used for "generic RPC".
> Have a look at http://tbroyer.posterous.com/gwt-211-requestfactory and 
> http://tbroyer.posterous.com/gwt-211-requestfactory-part-ii
> It's rather old and might be inaccurate in a few places (hasn't been 
> updated for GWT 2.4's use of annotation-processing at compile-time, for 
> instance).
>  
>
>>  
>> Is it not time to start using json as the base format for GWT RPC ? I 
>> would even like to help out to get this working! It is really a pitty that 
>> somehow RPC is a selling point for GWT but in reality it often becomes the 
>> bottleneck of your application.
>>
>   
>> Can't we maybe put GWT RPC on the framework for request factory ?
>>  
>> One issue I also have with GWT RPC (but less pressing as the 
>> performanceissue) is the fact that it is not very friendly for mixing 
>> different client technologies. If it were a simple json REST payload 
>> (without obfuscation and lots of secret numbers) then we could easily reuse 
>> it everwhere, it would also make it soo much easier for loadtesting. Not a 
>> lot of tools support GWT RPC easily.
>>
>
> RequestFactory can easily be used in-process within tests, and ships with 
> a pure-Java client (usable on Android for instance). It comes with 2 
> "dialects" under the same API: its own RequestFactory protocol (JSON-based) 
> that deals with batching of method calls and sending only diffs for 
> entities, and JSON-RPC. The server-side component only supports the former 
> dialect though, the latter is only about using existing JSON-RPC services 
> (such as Google APIs) from a Java or GWT app.
>
> That said, I doubt RequestFactory would perform better for your 1 
> nodes use-case (I think we can even say it will perform much worse than 
> RPC; this can probably be improved by doing more codegen at compile-time 
> and less reflection at runtime, but I'm not sure it'd even be better than 
> RPC; this is mostly about the server-side though, and possibly DevMode too; 
> it should be an all different story if you use the JSON-RPC dialect).
>
> An alternative to RPC and RF, using (a slightly modified) JSON-RPC 
> 

GWT RPC future ?

[stuckagain]

Hi,
 
Not sure where to ask this question, but I was wondering if the GWT devs 
every plan to fix the inefficient GWT-RPC ?
The problem happens mostly on IE (all versions), although I assume other 
browsers might benefit as well since a lot of cpu cycles are wasted on 
things that should be trivial for a browser.
 
I had to improve multiple GWT apps that all stumble on these 3 problems:
- deserialisation is terribly inefficient - it can take many seconds to 
serialize small sets of data,
- on IE I can get slow script warnings
- I sometimes get stack over flows with deeply nested structures.
 
For example when I send over a tree of 1 nodes (takes 20ms to create), 
it takes 5 seconds or more to deserialize. (I can give you a demo app that 
shows the problem)
 
I only get 2 seconds to impress my users, and I need to do quite a lot of 
operations besides sending the RPC.
 
I've heared the reactions multiple times: don't send soo much data over, 
but bytewise this is not soo much. It is highly compressible (just a few K 
in fact) data. We want to process complex data structures in the client, we 
don't want to create intermediate data structures to bypass the RPC 
inefficiencies.
 
There have been multiple attempts from google to write something better 
(DeRPC whichi is now deprecated, and RequestFactory which is very badly 
documented so I don't even know if I could reuse this one for generic RPC 
calls).
 
Is it not time to start using json as the base format for GWT RPC ? I would 
even like to help out to get this working! It is really a pitty that 
somehow RPC is a selling point for GWT but in reality it often becomes the 
bottleneck of your application.
 
Can't we maybe put GWT RPC on the framework for request factory ?
 
One issue I also have with GWT RPC (but less pressing as the 
performanceissue) is the fact that it is not very friendly for mixing 
different client technologies. If it were a simple json REST payload 
(without obfuscation and lots of secret numbers) then we could easily reuse 
it everwhere, it would also make it soo much easier for loadtesting. Not a 
lot of tools support GWT RPC easily.
 
David
 

-- 
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+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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GWT MVP Architecture

[stuckagain]

Why does the view need to be a singleton ?
 
Anyway, when you are done with the presenter, then you need to tell it so.
In that case it can unregister any installed handlers.
 
David

On Thursday, September 13, 2012 8:09:30 PM UTC+2, Aryan wrote:

> Hi all,
>  
> lets look at the code:
>  
> public class MyView implements IMyView {
>  
> Button click;
> .
> public HasClickHandlers getClick(){
>   return click;
>  }
>  
> }
>  
>  
> public class MyPresenter {
>  
>public interface IMyView {
>   public HasClickHandlers getClick();
> }
>  
> private IMyView view; 
>  
> public MyPresenter(IMyView view){
>   this.view = view;
>   bind();
> }
>  
> private void bind(){
>view.addClickHandler(new ClickHandler(){
> public void onClick(ClickEvent e){
> Window.alert("heeo");
>  
> }
> }//binds end
>  
>  }// class ends
>  
> //(We are not using Activities or any MVP framework)
>  
> ok tats it. Now in applicaton the view is singleton. but the presenter are 
> not, so they are made as and when needed like :
>  
> MyPresenter p = new MyPresenter(view); //view is singleton throughout the 
> application; assume getting it by some factory 
>  
> Now suppose after a while if I have created *10 MyPresenter *instance 
> that will add *10 clickHandler *to button "c*lick" . So one click event 
> will be handled 10 times by 10 different handlers.*
> ** 
> I can see here it as happening when click the button I get 10 times alert 
> window. 
>  
> So where I misunderstood the MVP architecture, what I am missing. 
> please help
> ** 
> Thanks in advance.
>  
>  
>  
>

-- 
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/-/kqPCgpq2N1IJ.
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: Large memory leak in IE8 when GWT runs on a new Window

[stuckagain]

Hey,
 
I seem to be seing similar issues when putting a GWT application in an 
IFrame and then removing the IFrame. It looks like the entire GWT 
application leaks.
 
I saw your bug report in the bug tracker of GWT. I added my comment there 
with a suggestion on how they could maybe fix this issue without impacting 
the few that would want to install a onwindowclosing handler that calls 
setMessage. This will ofcourse need a fix in GWT (the sooner the better 
since we are leaking about 40MB everytime we close the IFrame, and 
unfortunately we need to do this often in one browser session).
 
David
 

On Friday, February 11, 2011 9:12:25 PM UTC+1, Reuben S wrote:

> We have a number of fairly large GWT/GXT screens in our application, 
> most of them run 'embedded' in our application main window, which 
> includes a mix of 'legacy' client code and areas of GXT code. 
> Navigating to and away from pages containing GWT code does not show 
> any significant memory leaks in IE8. 
>
> Now some of our screens pop up a new Window running complex GXT code. 
> In those applications the top GWT-generated code attaches to the 
> RootPanel. 
> Closing the window associated with such an application leaks typically 
> 80 MB (!!!) in IE8. 
>
> We found a workaround by having IE run the new Window in a new 
> process, in which case the huge leak still exists, but IE eventually 
> kills the new process within 60 seconds of closing the Window. 
>
> Now we have scenarios in which we need to run the pop-up window in- 
> process. 
> I wonder if someone can think of a reason for the large leak in this 
> scenario. 
>
> We are using GWT 2.0 with GXT 2.2. 
> This issue reproduces (at least) on Windows 7/64 bit (with IE in both 
> 32 and 64 bit mode) and on Windows XP (we don't test Vista). 
> No leaks are observed on Firefox, even though FF runs new windows in 
> the same process. 
>
> Any help will be greatly appreciated. 
>
>  Thanks, 
>
>Reuben

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

Leaks with IFrames and JSONP

[stuckagain]

Hi,
 
I have been spending now 5 days trying to track down memory leaks in my big 
GWT application. 
 
I noticed that every time I call a JSONP service that I am leaking (size 
depends on the data received from that service).
I also noticed that when I put GWT in an IFrame and remove that IFrame 
there is a big leak as well. GWT does not seem to ever cleanup its expandos 
when the IFrame is being disposed - I assume that that results in a ref 
cycle between JS and the DOM ?
 
I tried many workarounds I found on the internet but it just keeps on 
leaking. 
 
It seems that the JSONP leak is well know since bugs have been reported on 
jQuery and Dojo at a certain point in time and some blogs have been written 
about this as well. But the strange thing is: I tried these workarounds 
(using a garbage bin in IE, clearing attributes, ... etc) but the problems 
remains. In my application I lose upto 10 MB per iteration which makes the 
memory footprint grow very quickly to 500MB or more, which is not really 
acceptable. So is there something specific to GWT that keeps a ref to the 
script and its contents ?
 
It leaks both on IE8 and FireFox 10 (I don't have access to other browser 
from my dev machine). 
Reloading the root page does not clear all the memory. I tried using tools 
like sIEve but that one gave me no results ... no leaks except the __ 
expando fields that GWT applications install.
 
Anybody have some extra ideas I might try out to solve this issue ? Is 
there some shutdown method available that I could start in the IFrame to 
make GWT detach completely from the DOM ?
 
David

-- 
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/-/DLTWoZF9XtsJ.
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: GWT 2.4 breaks JDK 5 compile support

[stuckagain]

The documentation getting started still says JDK 1.5 ... at the start of 
the page. 
The release note does not say that Java 6 is REQUIRED.
 
http://code.google.com/webtoolkit/gettingstarted.html
 
A lot of servers are still using Java 5.
 
David

-- 
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/-/nFT0goEJ-0gJ.
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: Developers, please don't ignore reported GWT issues.

[stuckagain]

I have been frustrated with this as well and voiced my concern before. But 
all they keep on doing is adding features that most of us don't need.
 
GWT is great, but there is a lot of old stuff in there that is half baked 
and nobody in the GWT team seems to be concerned with actually fixing bugs.
 
When I complained about it the only answer (if any) I get is: you are free 
to send us a patch.
Most of us don't have the time, or even the right to spend our time on 
working on code for google during our day jobs. And in the evening we need 
to take care of our family so fixing anything taking more than a few lines 
of code is totally impossible.
 
I managed to patch one of the issues I reported, but some things are hard to 
fix unless you really know the GWT internals very well. There is a bug in 
the Event dispatching after opening a popup in IE and I really don't know 
how to fix this one since it goes really deep into the root event handling 
implementation. There is no developer docs available that explains the 
architecture and the devs that created the code in the first place are doing 
other things. I filed the bug report, I wrote in GWT and GWT contrib 
newsgroups and got 0 responses...
 
This is the one:
http://code.google.com/p/google-web-toolkit/issues/detail?id=4938
 
>From what I read on google culture it seems like you only get rewarded for 
writing new stuff, not fixing old stuff (unless it affects a google product 
launch).
 

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

javac problem in annotation when moving from GWT 2.3 to GWT 2.4.

[stuckagain]

Hi,

After I switched to GWT 2.3 I suddenly have a custom annotation that fails 
to compile with the Oracle javac 

I'm totally puzzled on how this can happen but maybe the GWT team have some 
insight on what might me happening in GWT 
that could cause this ? could this be caused by a misbehaving annotation 
processors in GWT ?

The annotation in question is this one:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.METHOD)
public @interface BuildEditorModelWith {
public String value();
public String datadir() default "test/data/editormodelbuilder";
Class presentations() default 
StructuralPresentationFactory.class;
}

The bold line fails with an error that indicates that the 
PresentationFactoryImpl.class is not compatible (but it is!)
jar.pretest:
[mkdir] Created dir: 
/scm/vobs/srcSAG/mek/modules/editorweb/build/test-classes
[javac] Compiling 61 source files to 
/scm/vobs/srcSAG/mek/modules/editorweb/build/test-classes
[javac] 
/scm/vobs/srcSAG/mek/modules/editorweb/test/java/com/swift/editor/shared/model/test/BuildEditorModelWith.java:38:
 
incompatible types
[javac] found   : 
java.lang.Class
[javac] required: java.lang.Class
[javac] abstract Class presentations() 
default StructuralPresentationFactory.class;

[javac] 

^
[javac] 1 error

When I change the line to use  to accept all classes everything is fine 
(but I have to typecast in my tests where I use this annotation).

I really don't see how GWT 2.4 could cause this problem in my unit test 
code, but the fact is: with GWT 2.3 in the classpath it works fine, with GWT 
2.4 it no longer compiles.

I'm running JDK 1.6.0_22 (I can not upgrade it, enterprise bs) and it 
happens on both SUN and Windows XP.

David

-- 
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/-/qzQbd34REQsJ.
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: Aw: Xpath in GWT

[stuckagain]

I am interested in this! We need better support for XML and XPath in GWT 
(and it needs to work fast).
The standard GWT wrapper on top of the browser XML support is very much 
incomplete.
 
But I see that totoe does not allow modifying the document.
Is it planned to implement this in the forseable future ?
 

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

FormPanel and protection against injection attacks ?

[stuckagain]

I need to use a regular HTTP POST in a specific case in my application and I 
am having a problem in chosing the right approach to guard me against 
injection attacks.
 
Due to browser limitations I am forced to send back text/html, which 
ofcourse means that the HTML I generate in my servlet must properly escape 
user contributed data.
The FormPanel.SubmitCompleteHandler only allows me to access the results as 
a string, not as a document, so that makes it hard to find back the data in 
the response to use in the rest of the GWT code.
 
The reason why this is hard is because I need to decode the result, while if 
I would have access to the dom tree I could just find the correct node by ID 
and get the innerText and the browser would have un-escaped the data for me.
 
How is the rest of us handling these challenges ?
 
I created an issue in the GWT issue tracker for this issue, I think it is a 
severe limitation that I don't get access to the DOM tree or that I can not 
send back text/plain or some other format where I can easily guard against 
injection attacks.
 
http://code.google.com/p/google-web-toolkit/issues/detail?id=6707
 
David

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

Why is the XMLParser not returning a org.w3c.dom.Document ?

[stuckagain]

Hello,
 
XML support in GWT is quite substandard. Why did the GWT devs not base the 
implementation on the org.w3c.dom interfaces ? Just like the JRE emulation 
classes they could have done that and make it possible to share code between 
client and server when using Documents. 
 
Namespace support in the current implementation is also lacking. I know that 
the native browser XML support is very minimal, but it would have been very 
easy to add Namespace aware operations from org.w3c.dom (depending on the 
browser).
 
Any idea if there will be a more focus on improving this part of GWT ? Not 
everything is working with JSON or GWT-RPC.
 
I created an issue for this:
http://code.google.com/p/google-web-toolkit/issues/detail?id=6467
 
David
 

-- 
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/-/ki7cPrZ8WRcJ.
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: GWT plugin compile can not ignore a source directory

[stuckagain]

Hi,
 
Not an ideal solution (since I have lots of support classes which do not 
follow some naming convention), but it will do.
 
Thanks,
David

-- 
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/-/Sfb-XsLYvm4J.
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: Awesome testing with IsWidget interface :) -> Embedded View pattern

[stuckagain]

Thanks for the info! Yes indeed, it would be nice to have widgets use 
interfaces instead of classes ...

-- 
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/-/FWy6Ssm8R-sJ.
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 plugin compile can not ignore a source directory

[stuckagain]

Is there a possibility in the GWT plugin to configure a source folder NOT to 
be included when doing a GWT compile ?

I have a separate source folder in eclipse where I put my unit tests. 

These unit tests are put in the same package so that I can gain access to 
package private classes.

These classes do not need to be GWT compiled, it slows down the compilation 
and they cause many errors to be reported.

When I use DevMode I can specify the classpath to not include my test 
directory ... I need something similar in the GWT Compile.

David

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

InternalCompilerException: Already seen an implementing JSO subtype

[stuckagain]

 Hi,
 
Is this error something I have to fix in my code or is it really a bug in 
the compiler ? 
I have an Interface that needs to be implemented JavaScriptObject subclasses 
... is this not allowed for JSOs ?
 
David
 
[ERROR] Unexpected

com.google.gwt.dev.jjs.InternalCompilerException: Already seen an 
implementing JSO subtype (Schema) for interface (ISchemaVisitee) while 
examining newly-added type (SchemaAttribute). This is a bug in 
JSORestrictionsChecker.

at 
com.google.gwt.dev.javac.typemodel.TypeOracle.computeSingleJsoImplData(TypeOracle.java:797)

at com.google.gwt.dev.javac.typemodel.TypeOracle.finish(TypeOracle.java:685)

at 
com.google.gwt.dev.javac.typemodel.TypeOracleBuilder.finish(TypeOracleBuilder.java:64)

at 
com.google.gwt.dev.javac.TypeOracleMediator.addNewTypes(TypeOracleMediator.java:425)

at 
com.google.gwt.dev.javac.TypeOracleMediatorFromSource.addNewUnits(TypeOracleMediatorFromSource.java:54)

at 
com.google.gwt.dev.javac.CompilationState.assimilateUnits(CompilationState.java:164)

at 
com.google.gwt.dev.javac.CompilationState.(CompilationState.java:82)

at 
com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:409)

at 
com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:299)

at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:325)

at com.google.gwt.dev.Precompile.precompile(Precompile.java:507)

at com.google.gwt.dev.Precompile.precompile(Precompile.java:492)

at com.google.gwt.dev.Precompile.precompile(Precompile.java:405)

at com.google.gwt.dev.Compiler.run(Compiler.java:215)

at com.google.gwt.dev.Compiler.run(Compiler.java:187)

at com.google.gwt.dev.Compiler$1.run(Compiler.java:159)

at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:87)

at 
com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:81)

at com.google.gwt.dev.Compiler.main(Compiler.java:166)

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

How can I unit test some basic JavaScript overlay objects with the need for a Servlet and GWTTestCase ?

[stuckagain]

I have a few JavaScriptObject overlay types that I need to check for correct 
behaviour.
 
They basically represent data that I receive from a JSONP request.
 
I tried adding a servlet for testing that would serve the JSONP following 
the JUnit testing docs of GWT but 
I noticed that it does not start the servlet that I configured in the 
MyTest.gwt.xml file and I don't want to 
expose this testing servlet in the web.xml of my application.
 
Any ideas on how I could do this as a real unittest (without GWTTestCase). 
I can easily generate the json payload but that is using code that is not 
GWT compilable.
I have no way to instantiate the JavaScript overlay object (because it gives 
an error that it could not bind the native methods)... 
 
is there a way that I could somehow let this run with Rhino ? I just need to 
be able to check that my overlays are compatible with the data that I 
generate.
 
David

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

GWT Eclipse Plugins gives errors in eclipse error log. As a consequence I can not disable certain other plugins (not from google).

[stuckagain]

Hi,
 
My log in eclipse is full with errors about the GWT Eclipse Plugin:
"One Import statement is incorrect: Both feature and plug-in ID are either 
null or specified. Feature location: 
file:/C:/Development/eclipse/features/com.google.gdt.eclipse.suite.e36.feature_2.2.0.v201102111811/feature.xml"
 
This is really annoying because I need to disable a few features from the 
Oracle Enterprise Pack but because there seems to be something wrong with 
the GWT plugin eclipse helios sr2 fails to disable the features.
 
What can I do to avoid this problem (besides removing the GWT Plugin ? )
 
David

-- 
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: Announcing GPE/GWT 2.2 RC1

[stuckagain]

What features in Java 6 would be so fundamental to GWT that 1.5 becomes 
deprecated ?
 

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

Download GWT DevMode browser plugins directly

[stuckagain]

Hi,
 
Is there a URL that I can go to to download the GWT DevMode plugins directly 
(so no shell exe that reconnects to google) ?
My dev machine is not connected to the Internet so I need to be able to 
install these plugins offline.
 
David

-- 
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: CellTable as a replacement for incubator ?

[stuckagain]

Hi John,

On Nov 2, 6:50 pm, John LaBanca  wrote:
> CellTable isn't a complete replacement of PagingScrollTable, but we put a
> lot of work into the API to make it more clear and extensible.  We'd like to
> create a full featured enterprise CellTable, but we also have a lot of other
> projects going on and don't have the dev time to do it right now.

And what would be the right time ? I agree that the design looks
sound, but scrolling a table is really something that should be
standard in a table. People working on applications don't want to
spend time writing their own table implementation. And currently there
is still no table available that really uses GWT the way it should.
I've seen multiple enterprise projects that went for GXT mostly
because of the mature set of widgets that just look good without much
effort. This is very nice for prototypes and having a short time to
market ... but for bigger applications these widget sets have a lot of
limitations and can not be easily combined with other widget sets. So
after the prototype phase many realize that they need something else.

> in IE8 I see 3-4 seconds 100% CPU just to let the browser calculate
>
> mouse over row highlighting, when showing a lot of rows.
>
> Have you tried looking at it with SpeedTracer?  We tested with large tables
> (100 rows), and the hover code is pretty straight forward.  In past
> applications, we've seen performance problems when hovering due
> to descendent style selectors because of the way they are implemented in
> browser.

I was using the standard google user theme
(com.google.gwt.user.theme.standard.Standard) with no custom styling
at all.

As far as I know speedtracer can not be used in IE ... or did that
change in this release ? I checked with DynaTrace and that one is
telling me that IE is stuck in reflow calculations.

I posted a few messages in GWT contributors a few weeks ago because I
had similar issues on our custom build scrolling table. I was using
decendent styles in their, but after removing them I did not see any
improvement. One thing that did improve the performance by a factor of
10, is to stop using addStyleName or setStyleName in the mouseover and
using the getStyle().setBackgroundColor directly. So maybe it would
already be a big improvement if we could somehow override that way
mouseover and selection styles are applied. Most people only want to
change the background color in mouseover.

Alternatively their could be some changes in CssResource that would
allow us to put some styling code in the CssResource instead, which
would keep a better separation between the presentation and view.

Or we could just wait for IE9 to become the standard browser on
Windows... but in the banking sector many of our clients are reluctant
to move away from IE6 since they still have a lot of sites that only
work in that browser and they don't want to spend money on migrating
these applications.

> And you have a CellTable that is NOT myRandomWidget, then changing the hover
> style of the row will cause IE to walk up from every TD in the CellTable
> trying to match the style definition.  In the degenerate case, where
> CellTable is not myRandomWidget, this means walking up to the body element.
>  This is a native browser implementation, and the only solution is to avoid
> descendent style selectors.

I know, I never use descendant styles only really simple styles, with
the expense that I need to have a large set of stylenames, but with
CssResource all this is very easy to manage and group. So that is
really a very good feature of GWT.

David

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

CellTable as a replacement for incubator ?

[stuckagain]

Hi,

I have waited a long time to finally get the Incubator table out of my
dependencies ... and now with GWT 2.1 release I realize that my
waiting has been a total waste of time!

The CellTable is a very small subset of the incubator table... I would
rather call it a CellGrid.

in IE8 I see 3-4 seconds 100% CPU just to let the browser calculate
mouse over row highlighting, when showing a lot of rows.

Or am I using it wrongly ? Did I mis some setters or decorator classes
that makes the CellTable something useful beyond the expenses demo ?

David

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

CssResources and inheritance

[stuckagain]

Hi,

I wanted to post this to GWT contribs, but lets try this newsgroup
first.

I have create my own button widget (based on a A href='#' tag) that
allows me to specify the styles through a CssResource called
ButtonCss.

I needed many different type of buttons in one application so I
thought, well simple I just define the button styles multiple times in
different .css files and such through different entries in the
ClientBundle.

For example I have the following:

interface ButtonCss {
 String button();
 String disabled();
}

Resources extends ClientBundle {

}

-- 
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: GWT eat your own dogfood ? Future of GWT ?

[stuckagain]

David,

On Aug 26, 7:54 pm, David Chandler  wrote:
> David,
>
> At this time, there is a lot of activity around the 2.1 release, and
> you can get some sense of this by watching the SVN trunk. In addition,
> the GWT team has considerably stepped up maven support (see recent

I've been looking at all the checkins. I'm aware of what is coming,
but we already have
build a fast table with cell renderers, incremental rendering with
multi TBODYs to get the fastest renderings,
so we are not really waiting for the new features. It's nice that
there will finally be a better table, but will it be
extendible enough ? Will all bugs be fixed quickly ? You can not
expect the community to fix every bug, especially
if the problem is somewhere deep inside the compiler or event
dispatching code (like the one I reported on PopupPanel in IE).

> blog posts), which was one of the top issues in the issue tracker. As
> always, addressing particular bugs is a question of priorities, but
> rest assured that the GWT team is well aware that no one wants to see
> new features added at the expense of stability.

Then why is there so little progress on fixing bugs ? It looks like
the whole team is working on 2.1.
When I look at New issues in the tracker I can see over 900 bugs that
are still marked as new, it takes me back all the way to November
2006.
There are indeed a lot enhancements but there are quite a lot of bugs
as well... like stack overflows with the RPC... in 2.0 DeRPC was
released, but with a big warning that it was not stable yet. Will it
be 100% for 2.1 ? Or is there a newer system used by the data aware
widgets ?

> As for the @CssResource issue, if this is still unresolved for you,
> please star issue 4903 (http://code.google.com/p/google-web-toolkit/
> issues/detail?id=4903) and we'll revisit it.

I read through the newsgroup thread but I must say I don't agree with
everything that was said there. CssResources are really great, just
too bad that they were not retrofitted to the existing widgets.

But I guess that the main goal would be for the declarative UI system?
What I do agree upon is that the build in widgets of GWT are very
limited in extendability (button in the titlebar of a dialog ... who
would not want it ?) and they are not supporting CssResource directly
so I have to fallback to @external which takes away a few nice
features of using a CssResource.

David

> /dmc
> David Chandler
> Google Web Toolkit Team
>
> On Aug 26, 4:40 am, stuckagain  wrote:
>
>
>
> > Hi,
>
> > Since I get no response from the GWT dev-team on reported bugs I am
> > beginning to wonder about the future of GWT. It looks like stability
> > of the existing features is not very high on the list. I've heard
> > excuses in all the previous release that you guys were going to sort
> > out long-standing bugs after the next major release ... but years have
> > passed now and the collection of open and even new issues is going in
> > the wrong direction.
>
> > So I have to ask the obvious question:
> > Is Google going to abandon it now that Google Wave has been axed ?
>
> > The focus of 2.1 seems to be fast app development for enterprise apps,
> > which is very good... but one of the major requirements in enterprises
> > when selecting a toolkit is the maturity and stablity of the toolkits,
> > how much support do you get, how fast are bugs fixed ... etc... right
> > now I find it harder every day to sell GWT for newer projects.
>
> > From that perspective I'm not that sure that I would want to rely on
> > the Spring-Roo and Data aware widgets.
>
> > When we report bugs on other opensource projects (like struts in the
> > past or eclipse and many others) the new bug reports are quickly
> > detected and you get some basic feedback... right now the issue
> > tracker seems like you guys are using the SUN bug database. There are
> > still important bugs open from the beginning years of Java!
>
> > One other remark about dogfood:
> > How come I can not use CssResource with the standard widgets of GWT ?
> > They all rely on primary stylename and style dependent names to switch
> > states ... which makes it impossible to optimize the CSS with
> > CssResource. Are we really supposed to write our own widgets ? Writing
> > our own widgets is not too hard, but I hate it when I can not even use
> > the most fundamental UI widgets.
>
> > Again: I'm sounding very negative above, but that is just because I
> > care about the success of GWT! I want it to succeed but it needs to
> > grow up.
>
> > David

-- 
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: GWT eat your own dogfood ? Future of GWT ?

[stuckagain]

The @external part is what I don't like. This makes it impossible to
obfuscate and thus optimize the generated code.

The CssResource stuff also has the added benefit that you can not make
a mistake in stylenames since it is checked at compile time.

> For the rest of your email, I just want to say that I entirely
> disagree. I really like what the GWT team is doing and how the
> framework is progressing. Keep up the good work guys!

Don't get me wrong: I like GWT. But I'm frustrated that bug fixing
does not seem to be a high priority.
And I am not talking about functional enhancements, I'm talking about
issues in event handling not working, leaks in IFrames, ... etc.

David

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

GWT eat your own dogfood ? Future of GWT ?

[stuckagain]

Hi,

Since I get no response from the GWT dev-team on reported bugs I am
beginning to wonder about the future of GWT. It looks like stability
of the existing features is not very high on the list. I've heard
excuses in all the previous release that you guys were going to sort
out long-standing bugs after the next major release ... but years have
passed now and the collection of open and even new issues is going in
the wrong direction.

So I have to ask the obvious question:
Is Google going to abandon it now that Google Wave has been axed ?

The focus of 2.1 seems to be fast app development for enterprise apps,
which is very good... but one of the major requirements in enterprises
when selecting a toolkit is the maturity and stablity of the toolkits,
how much support do you get, how fast are bugs fixed ... etc... right
now I find it harder every day to sell GWT for newer projects.

>From that perspective I'm not that sure that I would want to rely on
the Spring-Roo and Data aware widgets.

When we report bugs on other opensource projects (like struts in the
past or eclipse and many others) the new bug reports are quickly
detected and you get some basic feedback... right now the issue
tracker seems like you guys are using the SUN bug database. There are
still important bugs open from the beginning years of Java!

One other remark about dogfood:
How come I can not use CssResource with the standard widgets of GWT ?
They all rely on primary stylename and style dependent names to switch
states ... which makes it impossible to optimize the CSS with
CssResource. Are we really supposed to write our own widgets ? Writing
our own widgets is not too hard, but I hate it when I can not even use
the most fundamental UI widgets.

Again: I'm sounding very negative above, but that is just because I
care about the success of GWT! I want it to succeed but it needs to
grow up.

David

-- 
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: Found bug in PopupPanel in IE6/7/8

[stuckagain]

Nobody seems to care about bugs nowadays ?

On May 20, 9:17 am, stuckagain  wrote:
> People,
>
> I reported a new issue on GWT in IE (6/7/8) where I no longer get
> keyboard events when closing down aPopupPanelby clicking on a
> textbox.
>
> In case somebody is bored and wants to fix it ? I looked through the
> code, but I don't quite see where the problem might be coming from.
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=4938&sor...
>
> Anybody wants to star the bug so that this finally gets fixed ?
>
> David
>
> --
> 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 
> athttp://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.

Found bug in PopupPanel in IE6/7/8

[stuckagain]

People,

I reported a new issue on GWT in IE (6/7/8) where I no longer get
keyboard events when closing down a PopupPanel by clicking on a
textbox.

In case somebody is bored and wants to fix it ? I looked through the
code, but I don't quite see where the problem might be coming from.

http://code.google.com/p/google-web-toolkit/issues/detail?id=4938&sort=-id%20-type&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Stars

Anybody wants to star the bug so that this finally gets fixed ?

David

-- 
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: Intergrating other GWT projects in eclipse

[stuckagain]

Hi,

It's actually very simple:

Just make sure that you create a jar that contains all the sources and
classes.
The compiler will need access to the sources, a regular jar with just
the .class files is not enough.

If you look at the gwt-user.jar you will notice that the exact same
thing is done there.

David

On May 9, 12:58 am, "Donald.W.Long" 
wrote:
> Ok,
>
> What I really wish to do is create a set of widgets and publish them
> as a jar file so others can use them.  How does one setup the jar file
> for GWT.  What does the jar file need?
>
> Thanks
>
> On May 7, 8:37 am, "Donald.W.Long" 
> wrote:> When you create a project in eclipse for a widget, do you create a gwt
> > project or just a normal java project.
>
> > I still can not make the below work, it states can not find
> > the .gwt.xml file for the widget, even if I add this in the path.
>
> > From what I have seen its very hard to create a widget outside your
> > normal GWT project.
>
> > Has anyone done this before, I am sure they have.
>
> > Any documentation on creating a widget for GWT that you would publish
> > to others in a jar, that would help a lot.
>
> > thanks
>
> > On May 6, 8:04 pm, sim123  wrote:
>
> > > If I am understanding your problem correctly, you are trying to
> > > inherit a module.
>
> > > This is what I did to inherit another module, when both projects are
> > > in my eclipse environment :
>
> > > Go to Project Properties > Java Build Path > Libraries > Add External
> > > Class Folder > Add source folder of your widget project.
>
> > > You could Add the widget project to refer the classes instead of
> > > creating and using a jar file.
>
> > > I hope it helps.
>
> > > On May 6, 5:41 pm, "Donald.W.Long" 
> > > wrote:
>
> > > > Hi all,
>
> > > > I need a bit of help with the following.
>
> > > > I am using the latest 1.6. GWT tools.
>
> > > > I created a java project and created a new widget.  I then exported
> > > > the widget via eclipse to a jar file.  At this point I then created a
> > > > full GWT project and attempted to use the jar file in the project.
>
> > > > I can not figure out how to use this jar file in my eclipse GWT
> > > > project.  I can make it an external jar file for eclipse and the
> > > > eclipse env is happy.  When I try to run the application from eclipse
> > > > I get all sorts of errors.
>
> > > > I added an inherits in the xml file for the jar file and also added
> > > > the jar file to the run classpath.
>
> > > > When I launched the program I always get that it can not find the jar
> > > > file.
>
> > > > How do you use a jar file from another project in a GWT 1.6 project.
>
> > > > NOTE: I even tried moving the jar file to the war\WEB-INF\lib and this
> > > > did not work.
>
> > > > HELP HELP
>
> > > > Thanks Donald W. Long- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---