LGTM + nits
http://gwt-code-reviews.appspot.com/1738803/diff/1/plugins/xpcom/JSRunner.cpp
File plugins/xpcom/JSRunner.cpp (right):
http://gwt-code-reviews.appspot.com/1738803/diff/1/plugins/xpcom/JSRunner.cpp#newcode121
plugins/xpcom/JSRunner.cpp:121: Debug::log(Debug::Error) Get
JSPrincial
On 2012/05/03 22:18:31, acleung wrote:
LGTM
(sorry for the delay: was OOO the past few days)
http://gwt-code-reviews.appspot.com/1701803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
LGTM
http://gwt-code-reviews.appspot.com/1667803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
FYI
can you provide some more context on the problem and why this fixes it?
Note taht FF has poor handling of switching down between incompatible
versions in the same install location. So, if you point 3.6 at a user
directory that had 7 installed, it will ask you to reinstall all your
On 2012/02/13 22:24:15, acleung wrote:
On 2012/02/13 21:21:54, conroy wrote:
FYI
can you provide some more context on the problem and why this fixes
it?
Note taht FF has poor handling of switching down between
incompatible versions
in the same install location. So, if you point 3.6
LGTM
On Mon, Feb 13, 2012 at 5:55 PM, acle...@google.com wrote:
On 2012/02/13 22:41:01, conroy wrote:
On 2012/02/13 22:24:15, acleung wrote:
On 2012/02/13 21:21:54, conroy wrote:
FYI
can you provide some more context on the problem and why this
fixes it?
Note taht FF has
LGTM
http://gwt-code-reviews.appspot.com/1638803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
LGTM
http://gwt-code-reviews.appspot.com/1634803/diff/1/plugins/xpcom/ExternalWrapper.cpp
File plugins/xpcom/ExternalWrapper.cpp (right):
http://gwt-code-reviews.appspot.com/1634803/diff/1/plugins/xpcom/ExternalWrapper.cpp#newcode267
plugins/xpcom/ExternalWrapper.cpp:267: bool remember =
It's generated from xpidl, no? So it's just been unchanging since 36. Not
guaranteed forever, but might be worth making it a build rule for if
GECKO_VERSION in some range, then use this one. If it changes, code will
have to update behind a build rule anyways.
On Fri, Jan 27, 2012 at 6:12 PM, Alan
LGTM with some nits
one day i'll make a pass through all this code to make it style
conformant, but for now just trying to avoid more style violations.
(technically the column limit should be 80, but we'll keep 100 within
this code for consistency for now...)
ping?
On 2012/01/03 16:27:51, conroy wrote:
http://gwt-code-reviews.appspot.com/1620803/diff/1/plugins/common/HostChannel.cpp
File plugins/common/HostChannel.cpp (right):
http://gwt-code-reviews.appspot.com/1620803/diff/1/plugins/common/HostChannel.cpp#newcode322
plugins/common
On 2011/11/14 17:53:37, conroy wrote:
http://gwt-code-reviews.appspot.com/1589803/diff/1/plugins/xpcom/ExternalWrapper.cpp
File plugins/xpcom/ExternalWrapper.cpp (right):
http://gwt-code-reviews.appspot.com/1589803/diff/1/plugins/xpcom/ExternalWrapper.cpp#newcode28
plugins/xpcom
LGTM + nit
http://gwt-code-reviews.appspot.com/1589803/diff/7001/plugins/xpcom/Makefile
File plugins/xpcom/Makefile (right):
http://gwt-code-reviews.appspot.com/1589803/diff/7001/plugins/xpcom/Makefile#newcode141
plugins/xpcom/Makefile:141: endif
nit: you could make these all independent if
http://gwt-code-reviews.appspot.com/1589803/diff/1/plugins/xpcom/ExternalWrapper.cpp
File plugins/xpcom/ExternalWrapper.cpp (right):
http://gwt-code-reviews.appspot.com/1589803/diff/1/plugins/xpcom/ExternalWrapper.cpp#newcode28
plugins/xpcom/ExternalWrapper.cpp:28: #include
Gee, 15 years experience! That's might impressive considering GWT came into
being in 2006! http://code.google.com/p/google-web-toolkit/source/detail?r=1
You have more experience in GWT than the original authors! Why you spend
your time peddling training instead of doing all sorts of interesting
There's no need to escape if you define your CSSResource in a .css file.
On Fri, Oct 7, 2011 at 9:22 AM, Jeff Larsen larse...@gmail.com wrote:
are you escaping the - ?
literal(\-webkit-gradient( linear, left bottom, left top, color-stop(0.23,
rgb(220,106,0)), color-stop(0.62,
Yep, note that CSSResource doesn't grok CSS3 yet, so you'll need to use
literals for CSS3 attributes:
e.g.
background: literal(-webkit-gradient(linear, left top, left bottom,
from(#f5f5f5), to(#e4e4e4)));
On Thu, Oct 6, 2011 at 2:22 PM, benneq benjamin_ma...@lavabit.com wrote:
GWT itself
)
On 2011/10/05 07:34:06, acleung wrote:
On 2011/10/04 23:11:19, conroy wrote:
so, i'm responsible for starting the cascade here, but I think now
would be
a
good opportunity to clean up this section of the makefile by
consolidating
all
the option settings for ff40+ rather than copy pasting
http://gwt-code-reviews.appspot.com/1560803/diff/3001/plugins/xpcom/Makefile
File plugins/xpcom/Makefile (right):
http://gwt-code-reviews.appspot.com/1560803/diff/3001/plugins/xpcom/Makefile#newcode125
plugins/xpcom/Makefile:125: ifeq ($(BROWSER),ff70)
so, i'm responsible for starting the
I've mentioned this in other threads, but I'll repeat here: Under the new
rapid-release model, Mozilla is intentionally breaking binary compatibility
with xpcom components on every release. We are forced to rebuild for every
platform with every release.
Our existing processes for maintaining the
On Mon, Sep 12, 2011 at 3:09 PM, snayrb99 bryan...@comcast.net wrote:
Would it make sense to modify the plugin build to work with any future
of firefox (something like em:maxVersion*/em:maxVersion?) rather
than tie to a specific version of firefox? I understand the reason for
being strict
GWT can't be served off the local filesystem mainly due to browser security
constraints. Try using the embedded Jetty server (In Eclipse with GPE, just
'Run as Web Application'. (Equivalently, you can compile, then launch
devmode and simply strip the gwt.codesvr query fragment from the URL to hit
, but should be more important and easier to fix than
solving problems with FF Changelog due Chrome is also built by Google!
Please help me! There's no comfortable way to debug my GWT projects.
On Aug 26, 4:50 pm, Chris Conroy con...@google.com wrote:
That's more or less it to build against existing
That's more or less it to build against existing source and plugin sdks.
Upgrading to a new version is certainly more involved due to the repackaging
of the original SDK, updating the makefile, manifest, and rdf install
template in the easy case. In the hard case it involves dealing with
breaking
On 2011/08/26 18:59:42, acleung wrote:
On 2011/08/26 18:58:34, acleung wrote:
Thanks! PTAL
BTW, how do I go about verifying the universal binary is built
correctly? Do I
need to grab an older Mac or am I missing something very obvious?
If you have an older mac, then that works.
On 2011/08/26 21:31:29, acleung wrote:
Also, looks like you still need to make the Darwin modifications
Thanks for catching that. I forgot that was only on SVN and wasn't
getting
picked up by rietveld.
LGTM
http://gwt-code-reviews.appspot.com/1523805/
--
in plugin-sdks:
please add the appropriate toplevel README as well as the README for the
Darwin modifications.
speaking of which, I don't see the Darwin modifications. js-config and
mozilla-config need to be made universal using FLAG32BIT.
you're missing libxpcomglue_s.a for Darwin, and all of
FYI Rietveld doesn't show binaries. I can look at the Cl for those though.
On Aug 23, 2011 8:00 PM, acle...@google.com wrote:
On 2011/08/23 23:57:49, acleung wrote:
Hmmm All the binaries are dropped.
http://gwt-code-reviews.appspot.com/1523805/
--
Jason,
Unfortunately, for the time being we're unable to keep pace with Mozilla's
new release schedule since the plugin update process is quite manual. We'll
be sure to announce to the list when FF6 support is ready. In the meantime,
you'll just have to fall back to =FF5 for DevMode.
On Tue, Aug
for web workers in gwt, when there is support for other
HTML5 features like local storage, canvas etc. Does anyone know why it
is the case ? Are people not interested in using multi-threading in
GWT or is GWT not a suitable tool for such an application ?
On Aug 1, 3:54 pm, Chris Conroy con
You definitely don't want to use gears.
You can take a look at how SpeedTracer uses WebWorkers via a custom
DedicatedWebWorker linker:
http://code.google.com/p/speedtracer/source/browse/#svn%2Ftrunk%2Fsrc%2Fclient%2Fui%2Fsrc%2Fcom%2Fgoogle%2Fgwt%2Fwebworker%253Fstate%253Dopen
Note that you
The correct version is 1.0.10401 (you should see this listed in the add-ons
manager) and is compatible with Firefox 3.0-5.0
On Sat, Jul 16, 2011 at 9:17 PM, gwtuser001 freelancejavaco...@gmail.comwrote:
Hello :)
I tried to install GWT Dev Plugin for my FF but it says
Download the GWT
Agreed these are serious issues facing the FF plugin. For the moment, we're
doing a little bit of wait and see to see if this new release strategy
(specifically the forced rebuild of all extensions) actually sticks. If it
does, we'll certainly need to retool how we spin plugin builds for new
Windows is supported. Also, the trunk prebuilt xpi and the one served
through the auto updater are exactly the same (I just double checked this
myself)
For version 1.0.10401, the sha1 sum
is: fdae31ce05d5df5aae55abe62af7bb8f4143e0a8
The only explanation I can think is perhaps you installed an
http://code.google.com/p/google-web-toolkit/wiki/DesignOOPHM gives a decent
overview and specs out the wire protocol.
High level:
The bootstrap page detects the ?gwt.codesvr= fragment, and tries to load the
plugin.
The plugin then validates the permissions. Assuming the permissions are
good, it
On 2011/07/11 15:49:22, codefu wrote:
can you repost this to the original review thread?
http://gwt-code-reviews.appspot.com/1472804/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
On 2011/07/11 15:59:39, codefu wrote:
Still LGTM
http://gwt-code-reviews.appspot.com/1469803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Vlad,
Double check your firewall settings. If you can, try disabling any firewall
that you are running for temporary troubleshooting. Do you see a gray
toolbox when you try to connect via chrome? If you don't see a red toolbox
in the url bar, then go to the extension's options page and whitelist
almost there
http://gwt-code-reviews.appspot.com/1469803/diff/6009/plugins/npapi/LocalObjectTable.h
File plugins/npapi/LocalObjectTable.h (right):
http://gwt-code-reviews.appspot.com/1469803/diff/6009/plugins/npapi/LocalObjectTable.h#newcode166
plugins/npapi/LocalObjectTable.h:166: set( id,
jsIdentitySafe;
On 2011/07/07 16:18:28, codefu wrote:
On 2011/07/07 15:19:54, conroy wrote:
does this really need to be static? it should be fine to test/set
this per
connect
The reason I think connect() was de-emphasized was the changing of the
generated
hosted.html for each project, and thus
jsIdentitySafe;
On 2011/07/07 16:24:11, conroy wrote:
On 2011/07/07 16:18:28, codefu wrote:
On 2011/07/07 15:19:54, conroy wrote:
does this really need to be static? it should be fine to test/set
this per
connect
The reason I think connect() was de-emphasized was the changing
What OS/distro and architecture are you running on? Are you running stock
chrome or chromium, or did you get a repackaging from your distro? (SUSE for
example is known to repackage chromium in an incompatible way\)
On Mon, Jul 4, 2011 at 5:32 AM, Vlad s.mastre...@gmail.com wrote:
I was starting
supporting older chrome versions seems like a blocker issue to
committing this to me.
http://gwt-code-reviews.appspot.com/1469803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
On 2011/07/01 18:28:32, codefu wrote:
We can't rip out the ID hack quite yet-- we'd have to wait until the
fixes roll out to stable users. We need to add some version checking of
chrome to decide if it's safe to do this.
http://gwt-code-reviews.appspot.com/1469803/
--
The production update URL just went live :-) You should get an auto-update
shortly, or you can manually grab the plugin from
http://gwt.google.com/missing-plugin/MissingPlugin.html
I'll note that Mozilla didn't have an OSX 64 bit SDK released until this
morning, and that was a blocker for our
Please discuss that on a separate thread. Short answer: there is some
progress being made on a couple of fronts, but no real performance
improvements to speak of yet.
On Mon, Jun 27, 2011 at 8:48 PM, ialpert ialp...@gmail.com wrote:
The production update URL just went live :-) You should get
Reviewers: codefu,
Description:
Add mac support to the FF50 plugin and package a candidate xpi.
Please review this at http://gwt-code-reviews.appspot.com/1467809/
Affected files:
M plugins/xpcom/Makefile
M plugins/xpcom/prebuilt/extension/chrome.manifest
Index: plugins/xpcom/Makefile
http://gwt-code-reviews.appspot.com/1465807/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
wrote:
On 2011/06/27 19:47:26, conroy wrote:
True, but I don't want that to be a listing of every version we ever
support. Instead, I'll just keep PPC marked as 3.x and the bifurcation
of
platform support can be inferred by the platforms that firefox
supports at
the various versions. I have
This is definitely temporary (and clearly not tested widely) as it only
supports Linux. You saw the extra permission prompt because this build
include's codefu's latest work of making the code server part of the
security model. Thanks for the heads up though. I'll ping back on this
thread when
Reviewers: codefu,
Description:
In the chrome.manifest, list binary components in ascending version
order so that the right choice wins. Unbreaks =FF4 from my previous
change.
Don't conflate debug with debuglevel (really, loglevel). Default to
build binaries without debugging information for
, Jun 24, 2011 at 11:15 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Fri, Jun 24, 2011 at 4:58 PM, Chris Conroy con...@google.com wrote:
This is definitely temporary (and clearly not tested widely) as it only
supports Linux. You saw the extra permission prompt because this build
include's
On 2011/06/24 21:38:20, codefu wrote:
LGTM, well, as good as the ugly vcproj format allows for such a CL to
look :P
http://gwt-code-reviews.appspot.com/1468803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
https://groups.google.com/d/topic/google-web-toolkit/_5UQX3w5zH4/discussion
On Thu, Jun 23, 2011 at 4:28 AM, Evgeny V Mustafin
evgeniy.musta...@gmail.com wrote:
I wanna know when new version of GDev plugin for FF5 will be
available, thanks.
--
You received this message because you are
As I said in my previous mail, there is going to be lag between their
release and our ability to support Firefox 5. They released just yesterday,
and upgrading the plugin sdks and spinning new builds is not the quickest
process in the world. To continue working with GWT Devmode, you should
either
If you have the symbol manifest you could recover a decent amount of
information. Though, the only hooks for that are for deobfuscating
individual stack traces on the server.
If I understand your situation correctly, it's as if someone handed you a
compiled object file with debugging symbols
Given that Mozilla has a very recent track record of making binary
incompatible changes leading up to release (even after claiming they were
frozen), it doesn't make sense for us to invest any time in supporting FF5
until we have at least some notion of the binary interfaces being stable.
On 2011/06/08 02:25:30, zundel wrote:
On Tue, Jun 7, 2011 at 6:13 PM, mailto:sco...@google.com wrote:
http://gwt-code-reviews.appspot.com/1453804/diff/1017/dev/core/test/com/google/gwt/lang/LongLibTestBase.java
File dev/core/test/com/google/gwt/lang/LongLibTestBase.java (right):
LGTM
http://gwt-code-reviews.appspot.com/1449810/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
On 2011/06/01 21:14:56, codefu wrote:
On 2011/06/01 21:11:48, codefu wrote:
Included are the binary files:
gwt-dev-plugin.crx
gwt-dev-plugin.xpi
gwt-dev-plugin.dmg
gwt-dev-plugin-x86.msi
gwt-dev-plugin-x64.msi
While you're tweaking the Chrome DevModeOptions, I think it would be
useful to have
gecko1_8 is the correct user agent for Firefox 4. This is slightly confusing
since FF4 runs Gecko 2.0. However, we only update the user agent permutation
properties when there is new code to select, and all of the FF3.6
permutation specific code is still valid for FF4.
On Thu, May 26, 2011 at
Javascript cannot deal with longs properly since the VM only speaks in terms
of doubles. Longs are emulated in GWT:
http://code.google.com/p/google-web-toolkit/source/browse/trunk/#trunk%2Fdev%2Fcore%2Fsuper%2Fcom%2Fgoogle%2Fgwt%2Flang
The reason this doesn't work is the compiler can only emulate
:38 PM, Chris Conroy con...@google.com wrote:
Javascript cannot deal with longs properly since the VM only speaks in
terms
of doubles. Longs are emulated in GWT:
http://code.google.com/p/google-web-toolkit/source/browse/trunk/#trunk%2Fdev%2Fcore%2Fsuper%2Fcom%2Fgoogle%2Fgwt%2Flang
The plugin ships with an SDK, but that doesn't mean you must use that SDK
with the plugin:
Right click on your project - Google - Web Toolkit Settings - Configure
SDKs.
On Mon, May 2, 2011 at 10:45 AM, tharkun thar...@gmx.de wrote:
Hi,
I am trying to set up a co-worker with my GWT based
Have you made sure to call ensureInjected on your styles (or otherwise
inject all of your styles in your entry point)?
On Fri, Apr 15, 2011 at 1:46 PM, John bradley.r...@gmail.com wrote:
I have several views whose stylings are being completely ignored in dev
mode. If it is a page I can
On Fri, Apr 8, 2011 at 8:23 AM, Diego Lovison diegolovi...@gmail.comwrote:
hello,
I would like to develop an application that the adm of the system
can modify the view, add rules, buttons, fields, and others
I have no idea what an 'adm' is.
ok I can create something like google
Eclipse's debug hooks can sometimes cause pathological slowdowns if you have
a breakpoint set on a method entry point. This can happen for regular java
(read: non-GWT) programs as well. Try removing any breakpoints you have set
(or at least, removing any on the method entry--you can set them just
Thanks Ian, this has been taken care of.
Friendly reminder to everyone on the list, if you spam like the OP, you will
be banned. This is a place to discuss GWT--not a place for recruiters to
troll.
On Mon, Apr 4, 2011 at 12:17 PM, Ian Petersen ispet...@gmail.com wrote:
Hey Mods,
This job
It's used by the bootstrap to know to load the plugin, and then it's used by
the plugin to connect to the code server.
On Sat, Mar 26, 2011 at 3:29 PM, Adib amsl...@gmail.com wrote:
Hello,
I am trying to figure out where the gwt.codesvr parameter gets
processed? I can think of the following
That's not a crash, that's an exception, and it means your deferred binding
for that class isn't set up properly. FF4 should present itself as the
gecko1_8 UA so this should be the same behavior that you see on FF3.6.
On Fri, Mar 25, 2011 at 2:31 PM, mayumi mayumi.liyan...@gmail.com wrote:
I
It can be done, but there are currently hoops and a fair amount of gotchas.
see http://code.google.com/p/google-web-toolkit/issues/detail?id=5577
On Fri, Mar 25, 2011 at 5:49 PM, roschler robert.osch...@gmail.com wrote:
I am a Chrome Extension newbie but a veteran programmer. My
On 2011/03/17 20:25:36, fmalita wrote:
LGTM++
http://gwt-code-reviews.appspot.com/1383803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
GWT speculatively parses anything you put on the source path. If you don't
want something to be included in your module, you need to explicitly say so
in your .gwt.xml.
On Wed, Mar 16, 2011 at 3:35 PM, KD kanwald...@gmail.com wrote:
Ok let me rephrase this.
Say, there is an abstract class
Mark,
This is something we are interested in supporting at some point in the
future. The issue tracking it is here:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5577
On Sun, Feb 20, 2011 at 7:16 PM, Mark Renouf mark.ren...@gmail.com wrote:
Hi all,
I'm just writing to let
You need to point your browser at
http://localhost:?gwt.codesvr=127.0.0.1:9997 (assuming you are running
with the default settings). This URL also shows up in the DevMode tab when
it starts up in Eclipse for you to copy paste or launch your browser.
On Wed, Mar 9, 2011 at 3:23 AM, Andrew
This may just be a bug in chrome developer tools. Verify the size of the
transfer using a packet sniffer or proxy.
On Tue, Mar 8, 2011 at 7:58 AM, kiran kumar kirankumarsm...@gmail.comwrote:
Hi
I have enabled gzip compression on tomcat container level and it is working
fine with Firefox. i
Some distros repackaged libnspr in a way that breaks our linkage to it. Do
you have a /usr/lib/libnspr4.so? If not, see if you have a similarly named
lib and trying making /usr/lib/libnspr4.so symlink to your installed nspr.
On Tue, Mar 8, 2011 at 1:40 PM, Gail ba...@yahoo.com wrote:
Hello
in dev mode.
Could you please take a look?
Thank you:
Kristof
On jan. 26, 21:19, Chris Conroy con...@google.com wrote:
We are pleased to announce that the GWT Developer Plugin now officially
supports Firefox 4 on all platforms that Firefox ships on: Win x86, Linux
x86/x86_64, Mac x86
In general you should avoid doing a lossy conversion from a lossy file.
More than you ever wanted to know about audio encoding:
http://www.hydrogenaudio.org/forums/
On Fri, Mar 4, 2011 at 1:35 PM, Armishev, Sergey sarmis...@idirect.netwrote:
Thank you, Philip!
That works. Took me time to find
http://code.google.com/p/google-web-toolkit/issues/detail?id=6084
On Wed, Mar 2, 2011 at 1:52 PM, Harold Comere harold.com...@gmail.comwrote:
Hi all,
I am under windows 7 64 bit, trying to launch any web app with GWT 2.2.0
under minefield ( firefox 4.0b12 ) and firefox crash with this
Alan,
Thanks for the bug report. This appears to be a Windows specific problem for
beta 12.
On Sun, Feb 27, 2011 at 8:35 AM, Alan Chaney a...@mechnicality.com wrote:
Hmm, Firefox decided to upgrade my Win 7/64 from B11 to B12 this morning.
I'm using GWT 2.1.1
I suspect dev mode is broken
i went ahead and filed it
here: http://code.google.com/p/google-web-toolkit/issues/detail?id=6084
--
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
On 2011/02/23 16:00:20, zundel wrote:
The impetus for this patch was an issue where dev mode had a problem
and stopped
prematurely. We saw no further events to the speedtracer log.
Shouldn't the shutdown event be the catch-all for situations like this?
There's probably value in flushing
http://gwt-code-reviews.appspot.com/1361801/diff/7001/dev/core/src/com/google/gwt/dev/util/log/speedtracer/SpeedTracerLogger.java
File
dev/core/src/com/google/gwt/dev/util/log/speedtracer/SpeedTracerLogger.java
(right):
-reviews.appspot.com/1361801/diff/7001/dev/core/src/com/google/gwt/dev/util/log/speedtracer/SpeedTracerLogger.java#newcode357
dev/core/src/com/google/gwt/dev/util/log/speedtracer/SpeedTracerLogger.java:357:
threadEventQueue.poll(nextFlush - System.currentTimeMillis(),
On 2011/02/23 20:23:10, conroy wrote:
can
relevant chrome bug
http://code.google.com/p/chromium/issues/detail?id=72407
On 2011/02/15 21:55:29, knorton wrote:
Awesome. good to know. I need to figure out how it manages to work.
On Tue, Feb 15, 2011 at 4:52 PM, Chris Conroy
mailto:con...@google.com wrote:
Actually, it does work
Reviewers: jat, fabiomfv, knorton,
Description:
Change the DevModeOptions page to use the xs linker due to recent Chrome
extension permissions changes
Please review this at http://gwt-code-reviews.appspot.com/1356803/show
Affected files:
M
Sorry, didn't see your comment in time for the commit. I just used the
same fix Kelly applied in SpeedTracer. I don't think it really matters
strongly either way.
On Tue, Feb 15, 2011 at 3:56 PM, j...@google.com wrote:
http://gwt-code-reviews.appspot.com/1356803/diff/1/2
File
, Chris Conroy con...@google.com
wrote:
Sorry, didn't see your comment in time for the commit. I just used the
same fix Kelly applied in SpeedTracer. I don't think it really matters
strongly either way.
As I understand it, the xs linker will soon be deprecated since the
xsiframe
linker
without looking too closely, the most obvious thing: rename
hellowmvp.gwt.xml to HelloMVP.gwt.xml
On Fri, Feb 11, 2011 at 10:36 AM, Tonté etno...@yahoo.com wrote:
Hello,
I need help understanding why when I run my gwt app in development
mode it can not find my hellomvp.gwt.xml file; which is
There's been some contention in plugin-futures about allowing plugins
to disable the hang monitors. The current winds are against us in this
cause, and, at least for the short term, this is an annoyance we have
to live with.
I'm assuming you're talking about the chrome plugin here. In that
case,
LGTM when LGTzundel
http://gwt-code-reviews.appspot.com/1336803/diff/1/3
File
dev/core/src/com/google/gwt/dev/util/log/speedtracer/SpeedTracerLogger.java
(right):
http://gwt-code-reviews.appspot.com/1336803/diff/1/3#newcode592
still lgtm + nit
http://gwt-code-reviews.appspot.com/1336803/diff/1003/7002
File
dev/core/src/com/google/gwt/dev/util/log/speedtracer/SpeedTracerLogger.java
(right):
http://gwt-code-reviews.appspot.com/1336803/diff/1003/7002#newcode771
The Chrome plugin model slows down development mode a fair amount. Note that
you can ignore those hang timeout warnings that the Chrome UI surfaces--the
dialog will go away once the codeserver hands control back to JS (e.g. while
waiting for a long refresh).
What NPObject error specifically are
Take a look at gwt-exporter: http://code.google.com/p/gwt-exporter/
On Tue, Feb 1, 2011 at 2:10 PM, Thomas Lefort lefortho...@gmail.com wrote:
Me again, there doesn't seem to be much interest in generating
reusable javascript widgets with GWT. If there is let me know, I'll
try to write
http://code.google.com/p/google-web-toolkit/source/browse/#svn%2Ftrunk%2Fplugins%2Fwireshark
On Tue, Feb 1, 2011 at 3:33 PM, zixzigma zixzi...@gmail.com wrote:
I was thinking of using a Packet Analyzer like Wireshark, to monitor what
is being sent over the wire from client to server and back
of it? Is the
Opera stepson?
On jan. 27, 00:26, Chris Conroy con...@google.com wrote:
We don't support Opera, but we do have a Safari plugin:
http://gwt.google.com/missing-plugin/MissingPlugin.html
On Wed, Jan 26, 2011 at 4:48 PM, jucimarjr junior.juci...@gmail.com
wrote:
Hi,
I'd like
Hi everyone. This has now been fixed. Sorry for the trouble.
--
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
Hi everyone. A repacking of the crx is now live. This should finally fix the
issues for users on Windows.
On Fri, Jan 28, 2011 at 11:54 AM, Tony antony.tr...@gmail.com wrote:
gwt bug report
http://code.google.com/p/google-web-toolkit/issues/detail?id=5941
On Jan 26, 3:54 pm, cri
On 2011/01/28 10:34:18, alexander.mitin wrote:
for full 10.5 compatibility you need build it against 10.5 SDK using
'-isysroot
/Developer/SDKs/MacOSX10.5.sdk' flag
I think to be really pedantic we have to find the Makefile flags that
are equivalent to setting the SDKROOT environment
1 - 100 of 424 matches
Mail list logo
