On 5 Mrz., 04:38, Deepak Khosla dkho...@x-iss.com wrote:
Hi,
Is there a way to tell if the checkin
abovehttp://code.google.com/p/google-web-toolkit/source/detail?r=9659made
it into the latest GWT 2.2?
We have been having issues with our 'large' application using sencha
GXT with
http://code.google.com/p/google-web-toolkit/issues/detail?id=624
On Sep 23, 12:30 am, Thad thad.humphr...@gmail.com wrote:
Has anyone experienced a problem with History.back() misbehaving in
Firefox after a FormPanel.submit()? I'm showing a pop-up dialog with
several options, among the
Updated the patch to only add a createHandlerManager which gets called
by ensureHandlers.
On 12 Feb., 04:22, John LaBanca jlaba...@google.com wrote:
Alright, lets go with createHandlerManager() for now. Thanks for all the
feedback.
@sven -
Would you like to update the patch by reverting
Yes, many times its too hard to customize things. Sometimes it make
sense to use private or package protected. But i think the
HandlerManager gets used so widely that it should be customizable
On 9 Feb., 23:57, Nathan Wells nwwe...@gmail.com wrote:
As a developer I absolutely agree with Mr. Ryan
Reviewers: jgw, jlabanca,
http://gwt-code-reviews.appspot.com/139801/diff/1/3
File
user/src/com/google/gwt/user/client/ui/impl/RichTextAreaImplIE6.java
(right):
http://gwt-code-reviews.appspot.com/139801/diff/1/3#newcode96
Line 96: if
The danger is that if you add handlers, and than later in your code
call setHandlerManager with a new HandlerManager. If we dont check for
a prior existing HandlerManager, all old HandlerRegistration's will be
lost. If you dont know what happened, you will search forever why your
old handlers are
On 2010/02/09 16:46:27, Ray Ryan wrote:
Sorry, I came in mid-conversation. My -1 was in defense of
setHandlerManager(),
seeing no harm in allowing a widget to swap around its HM if it wants
to.
I'm totally in favor of allowing a custom HM to be used.
For the ListModel also an own
handlermanager (which is the goal in the end).
On Tue, Feb 9, 2010 at 9:11 AM, Sven Brunken
sven.brun...@googlemail.comwrote:
The danger is that if you add handlers, and than later in your code
call setHandlerManager with a new HandlerManager. If we dont check for
a prior existing HandlerManager
/browse_thread/thread/631b8c3177930913/ff6c1c7e5d059a1a?
And what I can say, Mark will also vote for it ;)
We worked together to find the real exception that is occurring in the
posted example (stack overflow due to infinite loop)
Sven Brunken
On 19 Okt., 22:28, Bruce Johnson br...@google.com wrote
say you all?
joel.
On Wed, Aug 5, 2009 at 12:07 PM, Sven Brunken s...@extjs.com wrote:
The current implementation of the ImageResourceGenerator works very
well for most of the browsers. However in IE6 you have the problem
that it will convert everything to the PNG format (also
Dropping transparency support in IE6 is a bad idea. Too many business
people just still use IE6. Also saying that developers that need
transparent images in IE6 should not use ImageBundle is that good.
When writing my app I don’t want to care where it is running after I
finished it. It should
11 matches
Mail list logo
