[gwt-contrib] RR: Merging releases/1.5 into releases/1.6 to pick up reference/dispatch

This is step two of three of committing your event dispatch benchmark. Step one was checking the 1.5 version into releases/1.5/reference/dispatch. Now I'm merging that into releases/1.6. The third and final step will be a patch updating 1.6/reference/dispatch with your event handler changes. I'm no

[gwt-contrib] RR 1.6 (tbr): branch-info.txt updated

Scott, I updated 1.6 branch-info.txt with the event listener change number, figuring you could TBR it. http://code.google.com/p/google-web-toolkit/source/detail?r=4093 rjrjr --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~

[gwt-contrib] [google-web-toolkit commit] r4093 - releases/1.6

Author: [EMAIL PROTECTED] Date: Mon Nov 17 21:06:07 2008 New Revision: 4093 Modified: releases/1.6/branch-info.txt Log: branch-info.txt updated with event handler merge change #. TBR scottb Modified: releases/1.6/branch-info.txt ==

[gwt-contrib] Event handlers committed to 1.6, event listeners deprecated

With r4092, the new event handlers have been committed to the 1.6 branch. rjrjr --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---

[gwt-contrib] [google-web-toolkit commit] r4090 - changes/rjrjr

Author: [EMAIL PROTECTED] Date: Mon Nov 17 19:15:03 2008 New Revision: 4090 Added: changes/rjrjr/ Log: Ray'd changes dir --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~-

[gwt-contrib] Re: RR: Adding .project to gwt-incubator root directory

> What exactly is the reason we can't do the same here? subclipse won't handle linked resources. > Even if it is an > issue, why would we not leave the files in an eclipse subdirectory and have > interested users simply copy them to their trunk directory so we don't trash > any other similarly n

[gwt-contrib] Re: RR: Adding .project to gwt-incubator root directory

On Mon, Nov 17, 2008 at 3:18 PM, Emily Crutcher <[EMAIL PROTECTED]> wrote: > Several months ago we had the discussion of whether it was worth polluting > the root directory of gwt-incubator with eclipse specific project files in > order to make sub-eclipse and/or other subversion plugins to work c

[gwt-contrib] Re: RR: Adding .project to gwt-incubator root directory

No objections :) Fred Sauer [EMAIL PROTECTED] On Mon, Nov 17, 2008 at 1:18 PM, Emily Crutcher <[EMAIL PROTECTED]> wrote: > Several months ago we had the discussion of whether it was worth polluting > the root directory of gwt-incubator with eclipse specific project files in > order to make sub-e

[gwt-contrib] RR: Adding .project to gwt-incubator root directory

Several months ago we had the discussion of whether it was worth polluting the root directory of gwt-incubator with eclipse specific project files in order to make sub-eclipse and/or other subversion plugins to work correctly with the gwt-incubator source. At the time, there was a lot of discussio

[gwt-contrib] [google-web-toolkit commit] r4089 - in branches/1_6_clean_events/reference/code-museum/src/com/google/gwt: event event/shared...

Author: [EMAIL PROTECTED] Date: Mon Nov 17 11:49:13 2008 New Revision: 4089 Added: branches/1_6_clean_events/reference/code-museum/src/com/google/gwt/event/ branches/1_6_clean_events/reference/code-museum/src/com/google/gwt/event/shared/ branches/1_6_clean_events/reference/code-mu

[gwt-contrib] Review of handler map speed test.

Kelly, Could you review this visual benchmark I was using to compute the pros/cons of the different handler maps? Of particular interest is the SimpleJsHandlerMap, to see if there is anything, well, simple we we can do to make it faster. http://code.google.com/p/google-web-toolkit/source/det

[gwt-contrib] History list problem in IE6 - Do I really need to patch GWT's jar

I am using GWT 1.5 and want to manage history. Whenever I call History.newItem(token), Mozilla displays the window title in history list But Internet Explorer shows http://localhost:/com.TestEntry/8DF40326B05334ADE3B6DCA8E9DD3DA2 in the list i.e. URL of my page instead of showing window titl

[gwt-contrib] Re: a patch for legacy argument support

Will review ASAP. Thanks, Freeland. On Mon, Nov 17, 2008 at 12:12 PM, Freeland Abbott < [EMAIL PROTECTED]> wrote: > Yeah, I'd misunderstood the deleteOnExit() doc to imply recursive deletion, > but they're hanging around. Also a small bug, I'd failed to shift my random > number (so I got 5 repe

[gwt-contrib] Re: a patch for legacy argument support

Yeah, I'd misunderstood the deleteOnExit() doc to imply recursive deletion, but they're hanging around. Also a small bug, I'd failed to shift my random number (so I got 5 repeated digits, and a random space of 36 vice 36^5). Both fixes attached... It turns out that a try/finally to do the cleanup

[gwt-contrib] Re: Flurry of Data binding threads

On Mon, Nov 17, 2008 at 6:11 AM, Arthur Kalmenson <[EMAIL PROTECTED]>wrote: > > Hello Rahul, > > Here's some of the projects: > > gwt-data-binding: http://code.google.com/p/gwt-data-binding/ > gwt-validation : > http://code.google.com/p/gwt

[gwt-contrib] Re: a patch for legacy argument support

On Mon, Nov 17, 2008 at 11:15 AM, Freeland Abbott < [EMAIL PROTECTED]> wrote: > Well, if we're going to do that, let's put it into Utility, so we have a > general-purpose mkdtemp equivalent... attached. And, in that case, do we > want such "spontaneous" workDirs to be (best-effort) cleaned up at

[gwt-contrib] Re: a patch for legacy argument support

On Mon, Nov 17, 2008 at 1:15 AM, John Tamplin <[EMAIL PROTECTED]> wrote: > > Shouldn't Link.java:157 refer to Link? > Yes; fixed, and thanks. > > Won't this mean if you just run the precompile step it will automatically > create one if not specified? I think it should fail if you run the steps >

[gwt-contrib] Re: Flurry of Data binding threads

Hello Rahul, Here's some of the projects: gwt-data-binding: http://code.google.com/p/gwt-data-binding/ gwt-validation: http://code.google.com/p/gwt-validation/ I'm working on visibility logic as we speak, I'll make a post when I get the chance. I am also wondering what the status of the GWT te

[gwt-contrib] Re: Proposal: Simplification of ScrollTable

Copy from #190 I like the idea of providing additional default/simple implementations to make constructing a very basic PagingScrollTable easier. Of course, this should be done (if at all possible) without reducing the current flexibility of PST. To address specifics: 1. Consolidating the PST g