H. Guess not a lot of demand then. Will hold off doing any more work on
this.
Cheers
Sam
On Wednesday, July 17, 2013 9:04:53 AM UTC+1, salk31 wrote:
https://github.com/salk31/gwt-rf-queue
I've been allowed to open source this and given two hours a week to work
on it...
I thought it
FYI, I still haven't found the time to look at it…
On Thursday, July 18, 2013 9:26:35 AM UTC+2, salk31 wrote:
H. Guess not a lot of demand then. Will hold off doing any more work
on this.
Cheers
Sam
On Wednesday, July 17, 2013 9:04:53 AM UTC+1, salk31 wrote:
Ho k... I'll be very interested to hear your thoughts... If you think it is
fixable maybe GAE demo with some UI may be next step for me?
On Thursday, July 18, 2013 9:49:47 AM UTC+1, Thomas Broyer wrote:
FYI, I still haven't found the time to look at it…
On Thursday, July 18, 2013 9:26:35 AM
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
I'm also quite interested but haven't had time to look.
On 18 July 2013 10:00, salk31 sal...@gmail.com wrote:
Ho k... I'll be very interested to hear your thoughts... If you think it
is fixable maybe GAE demo with some UI may be next step for me?
On Thursday, July 18, 2013 9:49:47 AM
Thanks!
[ERROR] Line 6: No source code is available for type
com.google.gwt.user.server.rpc.RemoteServiceServlet; did you forget to
inherit a required module?
This error disappeared after I had removed source path=server/ from my
Project.gwt.xml file
On Tuesday, March 23, 2010 9:44:33 PM
Well, the patch for issue GWT 7139 solved the problem.
This is the issue
http://code.google.com/p/google-web-toolkit/issues/detail?id=7139can=4colspec=ID%20Type%20Status%20Owner%20Milestone%20Summary%20Stars
This is the link to the patch:
https://github.com/nmorel/gwt-issue7139/wiki
I've edited
Jens, even with source maps in Chrome, I've been unable to get stack traces
to work. They still print out poorly in production when an exception is hit
- the exceptions ignore the source maps entirely. I asked previously if
there is a way around it, but apparently it's a known issue - so I
On Thursday, July 18, 2013 3:21:59 PM UTC+2, RyanZA wrote:
Jens, even with source maps in Chrome, I've been unable to get stack
traces to work. They still print out poorly in production when an exception
is hit - the exceptions ignore the source maps entirely. I asked previously
if there
Hi Thomas,
It would be great if you (or anybody who understands how to set it up)
could add a small article on gwtproject.org about setting up the different
methods of getting stack traces in production on exceptions?
Thanks!
Ryan
On Thu, Jul 18, 2013 at 3:30 PM, Thomas Broyer
Oh dear, that's an assumed stale...
I have the problem on IE9/IE10.
It basically blocks me from doing anything interesting in custom cells in
IE9/10
I will try out the proposed solution and if it works we will need to see if
this can be fixed somehow in the next GWT build.
David
On Thu, Jul 18,
That article was the third result in a Google search for gwt web mode
exceptions:
http://www.summa-tech.com/blog/2012/06/11/7-tips-for-exception-handling-in-gwt/
I agree that
http://www.gwtproject.org/doc/latest/DevGuideLogging.html#Remote_Logging needs
to be expanded.
On Thursday, July 18,
Hi.
In order to change maximum size of a bundle i have to change
gwt.imageResource.maxBundleSize property.
The thing is, when I use
set-property name=gwt.imageResource.maxBundleSize value=1000 /
in gwt.xml, server doesn't even go up.
Also, where I can find all available properties?
Any advices
What GWT needs here is something closer to what you get with proguard - a
mapping file created during compilation that could be used to run the
obfuscated/javascript exception through a utility to give the correct stack
trace with zero overheads.
I'm not entirely sure on how proguard
Very cool. Bob Vawter and I (and I think a couple more people) worked on
this a long time ago, and there's definitely a lot of room for improvement.
Nice to see someone tackle this!
On Wednesday, July 17, 2013 4:56:40 PM UTC-4, Alex Epshteyn wrote:
Dear fellow GWT users,
I would like to
Doh. Looked to see how long it would take to put it up on GAE and only took
ten minutes to actually do it.
http://gwt-rf-queue.appspot.com/
So good old DynaTableRf but with gwt-rf-queue but with the Transport
replaced and a bit of extra UI.
--
You received this message because you are
Not an answer to your problems, but other people in the past have followed
the same road. Have a look at
http://code.google.com/p/google-web-toolkit/issues/detail?id=6401
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from
In response to some of the concerns expressed in this thread, I'd like to
clarify that by using my patch, you will not be making any trade-offs
versus what you previously had with GWT's old implementation: my patch will
give you all pros and no cons.
Here's why:
There are two ways to get
On Thursday, July 18, 2013 3:21:59 PM UTC+2, RyanZA wrote:
Jens, even with source maps in Chrome, I've been unable to get stack
traces to work. They still print out poorly in production when an exception
is hit - the exceptions ignore the source maps entirely. I asked previously
if there
That article was the third result in a Google search for gwt web mode
exceptions:
http://www.summa-tech.com/blog/2012/06/11/7-tips-for-exception-handling-in-gwt/
I agree that
http://www.gwtproject.org/doc/latest/DevGuideLogging.html#Remote_Logging needs
to be expanded.
On Thursday, July 18,
What GWT needs here is something closer to what you get with proguard - a
mapping file created during compilation that could be used to run the
obfuscated/javascript exception through a utility to give the correct stack
trace with zero overheads.
I'm not entirely sure on how proguard
In response to some of the concerns expressed in this thread, I'd like to
clarify that by using my patch, you will not be making any trade-offs
versus what you previously had with GWT's old implementation: my patch will
give you all pros and no cons.
Here's why:
There are two ways to get
22 matches
Mail list logo
