[
https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugi...
]
Konstantin Marmalyukov edited comment on JBIDE-19773 at 5/15/15 6:58 AM:
-------------------------------------------------------------------------
To know which browser is currently used we should parse userAgent string with javascript.
Here is userAgent string examples which is returned by SWT browsers:
* Lunix
** webkit : Mozilla/5.0 (Macintosh; Intel Mac OS X) AppleWebKit/538.1 (KHTML, like Gecko)
Safari/538.1
** embedded XulRunner(v1.9) : Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.19pre)
Gecko
** XulRunner24 : Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/ /24.0
** XulRunner10 : Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/ /10.0.4
* Windows
** IE : Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
To make this detection possible we need to include SWT which comes with Eclipse 4.5 RC1
because of [this
bug|https://bugs.eclipse.org/bugs/show_bug.cgi?id=465757].
[~mickael_istria], [~nickboldt], will we have Mars RC1 bundles in target platform for
Beta1 release? If not, we can create browser function for detecting browser, but this is
not very good solution.
was (Author: kmarmaliykov):
To know which browser is currently used we should parse userAgent string with javascript.
Here is userAgent string examples which is returned by SWT browsers:
* Lunix
** webkit : Mozilla/5.0 (Macintosh; Intel Mac OS X) AppleWebKit/538.1 (KHTML, like Gecko)
Safari/538.1
** embedded XulRunner(v1.9) : Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.19pre)
Gecko
** XulRunner24 : Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/ /24.0
** XulRunner10 : Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/ /10.0.4
* Windows
** IE : Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
To make this detection possible we need to include SWT which comes with Eclipse 4.5 RC1
because of [this
bug|https://bugs.eclipse.org/bugs/show_bug.cgi?id=465757].
[~mickael_istria], [~nickboldt], will we have Mars RC1 bundles in target platform for
Beta2 release? If not, we can create browser function for detecting browser, but this is
not very good solution.
Can Central tell the user what's wrong if gtk/swt/webkit not
available so they know what to do?
-----------------------------------------------------------------------------------------------
Key: JBIDE-19773
URL:
https://issues.jboss.org/browse/JBIDE-19773
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.3.0.Alpha2
Reporter: Nick Boldt
Assignee: Konstantin Marmalyukov
Priority: Critical
Fix For: 4.3.0.Beta1
It was suggested today on build.next call by Max that it would be great if when
gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify
the user what when wrong and suggest a solution.
Context:
{quote}
* No more handles with install-grinder
https://issues.jboss.org/browse/JBIDE-19750 and
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g...
* SWT problem? GTK problem? xvnc/xvfb problem?
* missing webkit package on RHEL7 ?
* @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages)
* what about x86 bundles for x86_64 platform? -
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_...
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)