Re: Image Anchor widget.

Filed a bug for this: http://code.google.com/p/google-web-toolkit/issues/detail?id=3080 On Sep 29, 7:33 am, Marcelo Emanoel [EMAIL PROTECTED] wrote: try this: code import com.google.gwt.dom.client.AnchorElement; import com.google.gwt.dom.client.DivElement; import

Re: Native GWT Compiler

Hi Sumit, This multithreaded compiler sounds intriguing. Could you provide some guidance about how to get it and use it? Thanks, Alex On Oct 13, 1:08 pm, Sumit Chandel [EMAIL PROTECTED] wrote: Hi Rauf, There are currently no plans to rewrite the GWT compiler as a native compiler. There are

Re: Native GWT Compiler

is available in trunk if you're interested use it : like the google web toolkit . regards . Le mercredi 12 novembre 2008 à 10:56 -0800, Alex Epshteyn a écrit : Hi Sumit, Thismultithreadedcompiler sounds intriguing.  Could you provide some guidance about how to get it and use it? Thanks

Re: Your opinion sought: Jetty or Tomcat?

Bruce, I might be too late in replying to this thread, but I want to phrase my objections to what you've proposed. A. Regarding Jetty: I think this will be a waste of time for everyone. Switching underlying servers is a no value added task (using Six Sigma vocabulary). 1). Many developers

Re: Your opinion sought: Jetty or Tomcat?

at 3:54 PM, Alex Epshteyn [EMAIL PROTECTED] wrote: Bruce, I might be too late in replying to this thread, but I want to phrase my objections to what you've proposed. A. Regarding Jetty: I think this will be a waste of time for everyone. Switching underlying servers is a no value added

Re: Your opinion sought: Jetty or Tomcat?

I've been mulling this over the past couple of weeks, and now I want to retract my initial objection about Jetty :) Mainly because, as Arthur and others pointed out, it's expected to speed up unit tests (which would be a huge win). And you don't need -noserver for most of the unit tests you

Re: Native GWT Compiler

. Is there a command-line switch to turn on multiple threads? On Nov 12, 10:56 am, Alex Epshteyn [EMAIL PROTECTED] wrote: Hi Sumit, This multithreadedcompilersounds intriguing.  Could you provide some guidance about how to get it and use it? Thanks, Alex On Oct 13, 1:08 pm, Sumit Chandel

Re: Multithreaded GWT Compiler

(Just changing the title of this thread to match actual discussion subject). On Dec 10, 2:50 am, Alex Epshteyn [EMAIL PROTECTED] wrote: Does anyone know the answer to this question asked by Dobes: I checked out the trunk and I'm running thecompilerfrom it, but I'm not seeing any

Re: Native GWT Compiler

number greater than 1, depending on how many threads you want to use to compile your GWT application. Sorry for not mentioning this earlier. Hope that helps, -Sumit Chandel On Tue, Dec 9, 2008 at 11:50 PM, Alex Epshteyn alexander.epsht...@gmail.com wrote: Does anyone know the answer

Re: GWT hosted mode in infinity loop when debugging

Matic, I just started having the exact same problem! I'm using IntelliJ not Eclipse, though. The debugger just keeps looping. When I forcibly pause the process, I see that it's always somewhere in the RPC service instantiation process and never finishes it (i.e. GWT.create()). I don't think

Re: GWT hosted mode in infinity loop when debugging

I think I just solved the problem by reverting my IntelliJ project files to an earlier state. It wasn't any new code that I had written - looks like just the project files got out of whack somehow. Good to back those up often. On Thu, Dec 11, 2008 at 8:34 PM, Alex Epshteyn alexander.epsht

Re: Who's Using GWT?

http://play.typeracer.com Too many tips and tricks to enumerate here :) On Dec 11, 8:39 pm, Sumit Chandel sumitchan...@google.com wrote: Hello everyone, We've recently updated the GWT homepage to include a page displaying a non-exhaustive list of applications that are built with GWT. We

Re: Problem in developing opensocial application in GWT

Hi Yasser, I'm actually not using GWT in directly my OS gadget - I have an iframe inside the gadget that loads my GWT app. However, I'm sure you can use GWT RPC quite easily in the gadget - as long as your compiled JS has the same URL as your RPC server. Best, Alex (I'm CC-ing this message to

Re: Problems with ImageBundle in IE8 when not in compatibility mode

BE CAREFUL when copying code from this page - Thomas Broyer's comment has an error. The correct meta tag to add is meta http-equiv=X-UA-Compatible content=IE=EmulateIE7 / be sure the first attribute is http-equiv, not name! (wasted 20 minutes on this) I can confirm that this tag fixes the

How to override module stylesheet definitions

Surprisingly was unable to find any prior discussions about this... I'm optimizing my app's load time by merging all my stylesheets into a single CSS file (then minifying it with YUI compressor), to reduce the number of HTTP requests. I'd like to also concatenate all the stylesheets from third

Re: How to override module stylesheet definitions

the extra HTTP round trip for gwt-dnd.css incurred by the stylesheet src=.../ configuration you mention below. Hope that helps. Fred On Mon, Aug 17, 2009 at 10:39 PM, Alex Epshteyn alexander.epsht...@gmail.com wrote: Surprisingly was unable to find any prior discussions about this... I'm

Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

One of the big problems with deployed GWT apps has always been the impossibility of tracing JavaScript exceptions back to the Java source code. What we need is a true equivalent of Java stack traces. There was an effort made by the GWT team a couple years ago to solve this problem (

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

Thanks for your comment. Let me respond to your points: 1) I've seen this point discussed before, and the standard counter-argument is that the spirit of OSS is free as in freedom, not beer. Lots of developers get paid to work on OSS projects. 2) This is actually one of the reasons I'm

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

info in the future, it's almost certain that their stack trace formats will all be different, so we'll have to patch GWT every time a new browser adds the support. My proposed project will leave us in good shape to be able to do that easily. On Wed, May 22, 2013 at 5:53 PM, Alex Epshteyn

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

23, 2013 at 5:13 AM, Thomas Broyer t.bro...@gmail.com wrote: On Wednesday, May 22, 2013 11:53:47 PM UTC+2, Alex Epshteyn wrote: Thanks for your comment. Let me respond to your points: 1) I've seen this point discussed before, and the standard counter-argument is that the spirit of OSS

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

Fair enough, but I'm curious to know why leaving the code that supports legacy browsers would interfere with implementing new features. For example, if you want to implement a new widget called XPanel, it think it's perfectly fine to say that this widget doesn't support IE6/7/8, and leave it up

I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

Dear fellow GWT users, I would like to announce that I have finally solved what I always thought to be GWT's greatest weakness: its lack of debugging information for client-side exceptions in production. With my patch, your deployed app will be able to report stack traces like this:

Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

:) Thanks guys. Any other questions? (I'm really excited to be having this discussion with all of you, after working on it in isolation for so long). - Alex Epshteyn On Wednesday, July 17, 2013 10:48:02 PM UTC-4, mark.e...@gmail.com wrote: If you use emulated stack traces (including line

Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

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

Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

Alfredo: thanks for your $25 contribution! I've just emailed you my patch along with a small demo project. Would be great if we could get more people to pitch in with some funding. Any corporate takers? Johannes: IndieGoGo asked me to come up with perks to offer to people who contribute

Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

-based UI code that I would NEVER found otherwise. Let's get this capability into GWT by the end of the year. Please donate! Thanks, Alex On Wednesday, July 17, 2013 4:56:40 PM UTC-4, Alex Epshteyn wrote: Dear fellow GWT users, I would like to announce that I have finally solved what I

Re: [gwt-contrib] Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

Hi Colin, please find my answers inline: On Tue, Aug 20, 2013 at 11:35 PM, Colin Alworth niloc...@gmail.com wrote: I got a tweet from you asking for a donation (or rather a 'partner', which apparently means 'money'), but couldn't frame a useful response in 140 chars, so since this thread is

Re: Development Mode will not be supported in Firefox 27+

As of now, quite sadly, the GWT plugin is no longer supported in the latest of versions of Firefox nor Chrome (starting with 35). I've been using GWT since 2006, and I think it's a sad state of affairs that after so much work went into GWT's OOPHM (a.k.a Development Mode), we're back to

Re: Google Chrome 35 GWT plugin incompatibility

Although the GWT plugin for Chrome can no longer be installed from the chrome store since version 35, you can still install it manually (at least under Windows) and it works just fine. I posted the instructions here: https://groups.google.com/d/msg/google-web-toolkit/QSEjbhhHB4g/tQSwltonVMIJ

Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

d like to continue this effort and port this over to the latest GWT branch, I'll do my best to help! On Wednesday, July 17, 2013 at 4:56:40 PM UTC-4, Alex Epshteyn wrote: > > Dear fellow GWT users, > > I would like to announce that I have finally solved what I always thought > to be GW

Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

> file (containing only the differences to the GWT SDK) or only the modified > classes? > > Am Mittwoch, 8. November 2017 04:30:20 UTC+1 schrieb Alex Epshteyn: >> >> This project is now on GitHub: >> https://github.com/aepshteyn/gwt-stack-trace-kit >> >> You ca

Why was benchmarking removed in GWT 2.6?

This seemed like a very useful feature back in the day, and I'm really curious to know the reasoning behind its removal in release 2.6.0 (RC1) . Does anyone remember? -- You received this message because you are subscribed

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

How exactly does the svninfo task contribute to the build? I'm still getting a gwt-windows-0.0.0 directory as output. Would be nice to have a revision number there instead. On Jan 12, 11:00 pm, Freeland Abbott gwt.team.fabb...@gmail.com wrote: I've actually never had trouble getting a

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

:42 pm, Alex Epshteyn alexander.epsht...@gmail.com wrote: How exactly does the svninfo task contribute to the build?  I'm still getting a gwt-windows-0.0.0 directory as output.  Would be nice to have a revision number there instead. On Jan 12, 11:00 pm, Freeland Abbott gwt.team.fabb...@gmail.com

[gwt-contrib] Re: RR : Pluggable CompilePerms workers

think about using the external workers for modules and threads for permutations. Alex On Jan 21, 6:45 pm, Alex Epshteyn alexander.epsht...@gmail.com wrote: This stuff looks great, guys.  Is there any chance of actually setting up a distributed build cluster using this code? Back when I had

[gwt-contrib] Proposal: Lightweight GWT-RPC implementation for OpenSocial and Gadgets

Background: OpenSocial containers provide the method gadget.io.makeRequest because gadget scripts aren't able to use XHR due to the SOP. Furthermore, I believe, OpenSocial containers don't expose the _IG_GetCachedUrl(url) method that the gwt-gadgets library uses. Now, regarding the gwt-gadgets

[gwt-contrib] Re: Proposal: Lightweight GWT-RPC implementation for OpenSocial and Gadgets

and RemoteServiceProxy subclasses. I will continue testing and polishing those and will share them later. Alex On Thu, Jan 22, 2009 at 5:17 PM, Alex Epshteyn alexander.epsht...@gmail.com wrote: Yes, the option to extend RPC and gadgets are two separate ideas. Code generation is one

[gwt-contrib] Re: Proposal: Lightweight GWT-RPC implementation for OpenSocial and Gadgets

the JRE code, since finding out a complete list of all these magic variables and exactly what they do is often difficult. GWT's idiom is usually to embed build specific switches via deferred binding properties. -Ray On Thu, Jan 22, 2009 at 8:27 PM, Alex Epshteyn alexander.epsht...@gmail.com wrote

[gwt-contrib] I've implemented Java stack trace support for web mode

I have a working implementation which produces stack traces representing the original Jave source code when Javascript exceptions occur in web mode. I plan to deploy this in production on my site, typeracer.com in my next release. I'd like to polish up my implementation over the next few

[gwt-contrib] Re: I've implemented Java stack trace support for web mode

Are there any new developments on this front in the core GWT code? The reason I ask is to be sure that I'm not duplicating your efforts and wasting my time. On Tue, May 5, 2009 at 4:31 PM, Alex Epshteyn alexander.epsht...@gmail.com wrote: I have a working implementation which produces stack

[gwt-contrib] Re: I've implemented Java stack trace support for web mode

com.google.gwt.core.client.impl.StackTraceCreator (in trunk). If I'm understanding your proposal correctly, there may be a great deal of overlap there. Cheers, joel. On Tue, May 5, 2009 at 6:47 PM, Alex Epshteyn alexander.epsht...@gmail.com wrote: Are there any new developments on this front in the core GWT

[gwt-contrib] Re: I've implemented Java stack trace support for web mode

limitations with your approach? Perhaps there is some area where my technique could provide better information to the programmer? Thanks, Alex On Wed, May 6, 2009 at 4:22 PM, BobV b...@google.com wrote: On Wed, May 6, 2009 at 4:15 PM, Alex Epshteyn alexander.epsht...@gmail.com wrote: Yes, we

[gwt-contrib] Re: I've implemented Java stack trace support for web mode

complementary to the existing implementation. That's what I was hoping. Thanks, Alex On Thu, May 7, 2009 at 9:50 AM, BobV b...@google.com wrote: On Wed, May 6, 2009 at 4:49 PM, Alex Epshteyn alexander.epsht...@gmail.com wrote: I'm using static code rewriting at the Java source level

[gwt-contrib] Re: I've implemented Java stack trace support for web mode

to ask. jay On May 7, 1:24 pm, Alex Epshteyn alexander.epsht...@gmail.com wrote: Hi Bob, Could you provide some numbers in terms of raw and gzipped before/after bytes? This is the OBF compiled js size of a TypeRacer module before and after instrumentation (raw/gz): 382/118 vs. 505/142

[gwt-contrib] RPC payload question: Why use fully qualified class names?

Hi guys, I'm sorry I'm not up-to-date on recent GWT development efforts, but does the current version of the GWT-RPC serialization scheme still use fully qualified class names in the payload string? (e.g. com.example.foo.Foo in the method signature part of the payload, and then again as

[gwt-contrib] Linker bug with useSourceMaps

I'm trying to fix a bug ( https://code.google.com/p/google-web-toolkit/issues/detail?id=8100 ), and I could use some expert advice. I'm a long time GWT user (7 years), but only recently started hacking the internals, and I need help on this one. Background:

[gwt-contrib] Re: Linker bug with useSourceMaps

the patch to the Rietveld instance at http://gwt-code-reviews.appspot.com/; whereas I'm seeing all the messages in this group coming from a system called Gerrit at https://gwt-review.googlesource.com/ On Apr 10, 2:39 am, Alex Epshteyn alexander.epsht...@gmail.com wrote: I'm trying to fix a bug

Re: [gwt-contrib] Re: Linker bug with useSourceMaps

command line examples of the whole process using git, starting from checking out the code to submitting a patch for review? Thanks in advance. I'm eager to get started! On Wed, Apr 10, 2013 at 3:39 PM, Matthew Dempsky mdemp...@google.comwrote: On Wed, Apr 10, 2013 at 12:22 PM, Alex Epshteyn

Re: [gwt-contrib] Re: Linker bug with useSourceMaps

Thanks Thomas! I appreciate it. I'll give it a try! On Wed, Apr 10, 2013 at 5:01 PM, Thomas Broyer t.bro...@gmail.com wrote: On Wednesday, April 10, 2013 9:22:18 PM UTC+2, Alex Epshteyn wrote: Thanks Thomas! Is it possible to still use SVN by any chance? I haven't made the leap over

[gwt-contrib] I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

Dear fellow GWT users, I would like to announce that I have finally solved what I always thought to be GWT's greatest weakness: its lack of debugging information for client-side exceptions in production. With my patch, your deployed app will be able to report stack traces like this:

[gwt-contrib] Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

:) Thanks guys. Any other questions? (I'm really excited to be having this discussion with all of you, after working on it in isolation for so long). - Alex Epshteyn On Wednesday, July 17, 2013 10:48:02 PM UTC-4, mark.e...@gmail.com wrote: If you use emulated stack traces (including line

[gwt-contrib] Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

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

Re: [gwt-contrib] Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

I do not think you will get very far trying to ransom your bug fixes. I get that Kickstarter/etc. is great for new/potential projects, but you're basically saying well, I already built/fixed this, but crap, it would have been nice to get paid for it I can appreciate how it might

[gwt-contrib] Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

-based UI code that I would NEVER found otherwise. Let's get this capability into GWT by the end of the year. Please donate! Thanks, Alex On Wednesday, July 17, 2013 4:56:40 PM UTC-4, Alex Epshteyn wrote: Dear fellow GWT users, I would like to announce that I have finally solved what I

Re: [gwt-contrib] Re: I'm enhancing GWT to provide Java stack traces for clientside exceptions in production

Hi Colin, please find my answers inline: On Tue, Aug 20, 2013 at 11:35 PM, Colin Alworth niloc...@gmail.com wrote: I got a tweet from you asking for a donation (or rather a 'partner', which apparently means 'money'), but couldn't frame a useful response in 140 chars, so since this thread is