UX debug mode in chrome
Hi, This is a warning for everyone using Chrome to run in debug mode for GWT debugging. As of Chrome 35, the plugin will no longer work under linux. It will simply say it no longer works. So if you see a Chrome update available and you want to debug, don't apply it. Alexander
And if you've already upgraded, we found Chrome 33 here: ftp://ftp.pbone.net/mirror/ftp.sourceforge.net/pub/sourceforge/s/sn/snowbird/yum/sb20/google-chrome-stable-33.0.1750.117-1.x86_64.rpm Google doesn't appear to maintain an archive of old versions. ----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: devel@ovirt.org Sent: Wednesday, May 21, 2014 3:44:36 PM Subject: [ovirt-devel] UX debug mode in chrome
Hi,
This is a warning for everyone using Chrome to run in debug mode for GWT debugging. As of Chrome 35, the plugin will no longer work under linux. It will simply say it no longer works.
So if you see a Chrome update available and you want to debug, don't apply it.
Alexander _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
----- Original Message -----
From: "Greg Sheremeta" <gshereme@redhat.com> To: awels@redhat.com Cc: devel@ovirt.org Sent: Thursday, May 22, 2014 2:14:14 PM Subject: Re: [ovirt-devel] UX debug mode in chrome
And if you've already upgraded, we found Chrome 33 here: ftp://ftp.pbone.net/mirror/ftp.sourceforge.net/pub/sourceforge/s/sn/snowbird/yum/sb20/google-chrome-stable-33.0.1750.117-1.x86_64.rpm
Google doesn't appear to maintain an archive of old versions.
Alternatively, you can tell rpm to exclude Chrome package from being updated by editing /etc/yum.conf and adding something like this under [main] section: # Prevent Chrome update due to GWT Developer Plugin exclude=google-chrome* Vojtech
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: devel@ovirt.org Sent: Wednesday, May 21, 2014 3:44:36 PM Subject: [ovirt-devel] UX debug mode in chrome
Hi,
This is a warning for everyone using Chrome to run in debug mode for GWT debugging. As of Chrome 35, the plugin will no longer work under linux. It will simply say it no longer works.
So if you see a Chrome update available and you want to debug, don't apply it.
Alexander _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: devel@ovirt.org Sent: Wednesday, May 21, 2014 9:44:36 PM Subject: [ovirt-devel] UX debug mode in chrome
Hi,
This is a warning for everyone using Chrome to run in debug mode for GWT debugging. As of Chrome 35, the plugin will no longer work under linux. It will simply say it no longer works.
Thanks for sharing this info. oVirt UI currently uses GWT SDK version 2.5.1 where Super Dev Mode (debugging via browser using source maps) is still experimental and cannot be used at the moment [1]. [1] http://gerrit.ovirt.org/#/c/26093/ My understanding is that GWT team slowly abandons Classic Dev Mode (debugging via Java IDE using browser plugin) in favor of Super Dev Mode. Next time we'll upgrade GWT SDK version, we will definitely check if Super Dev Mode works for our applications, and prefer this style of debugging over the classic one. In any case, GWT 3.0 is coming and it has the potential to bring in a whole lot of new features and, most importantly, improvements to existing development cycle [2]. [2] http://blog.xam.de/2014/02/gwt-is-coming-back-in-2015.html
So if you see a Chrome update available and you want to debug, don't apply it.
You can always setup some VM with browser(s) used for GWT debugging.
Alexander _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
participants (3)
-
Alexander Wels -
Greg Sheremeta -
Vojtech Szocs