May 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17230) GTK and BrowserSim web engine issue on Fedora

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17230?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-17230: ------------------------------------ Summary: GTK and BrowserSim web engine issue on Fedora (was: GTK and BrowserSim web engine issue) > GTK and BrowserSim web engine issue on Fedora > --------------------------------------------- > > Key: JBIDE-17230 > URL: https://issues.jboss.org/browse/JBIDE-17230 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > > Here's my bad user experience: > I'm running Fedora19. I've seen GTK3 issues so I always set 'export SWT_GTK3=0' before starting JBDS. > I make a HTML5 app, deploy to EAP 6.2 and then try to view on BrowserSim. But when I start BrowserSim I see an error message stating "WebKitGTK 1.2.0 or newer must be installed and in library load path". I've got libwebkit2gtk 2.0.4 installed so don't know how to resolve this. > After much head scratching I finally remember about BrowserSim GTK preferences and web engine options. Within Window>Preferences>JBoss Tools>BrowserSim/CordovaSim, I see that GTK2 is selected. The GTK2 button label states that this will allow me to use JavaFX which needs Oracle JDK. I don't have Oracle JDK installed as this isn't supported by RH for use with Fedora. Perhaps this is why I see the earlier error message? So I try selecting GTK3. I run BrowserSim again and it starts but then I start to see GTK3 UI issues in BrowserSim. > So I want to use GTK2 and SWT WebKit for BrowserSim on Fedora. Is there a specific reason I can't (other than the IDE won't let me)? > Issues: > 1) Can the first error message be more helpful? > 2) Can the info on the error message wiki link be updated to detail why this error is being seen on Linux? (current info about similar message related to Windows and JRE7 issue - needs updating anyway as suggests using Java 6 as fallback for Windows but JBDS 8 doesn't support Java 6 for running IDE) > 2) Can selecting GTK2 set BrowserSim to use SWT WebKit and then users change web engine preference to JavaFX if they want? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17230) Resolve GTK and BrowserSim web engine paradox

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17230?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-17230: ------------------------------------ Description: Within Window>Preferences>JBoss Tools>BrowserSim/CordovaSim, selecting GTK for BrowserSim seems to be available for Linux-based OS only. I can choose GTK2 or GTK3. I'm running the IDE under GTK2 (export SWT_GTK3=0) to avoid UI issues. So I select to run BrowserSim also under GTK2 - seems sensible. But when I start BrowserSim I see the error message stating was: BrowserSim can be run with 2 web engines: JavaFX or SWT WebKit. On Mac OS X, under preferences I don't see an option to change the web engine for BrowserSim. I assume it is running with JavaFX - is that right? On Windows?? I don't have a windows system to test. On Linux-based OS, the web engine to use depends on the GTK with which BrowserSim is run. GTK2 = JavaFX and GTK3 = SWT WebKit. There are additional restrictions based on OS with respect to this: * JavaFX requires Oracle JDK - this JDK is only supported by Red Hat on RHEL, not Fedora or Ubuntu so this option is pointless for the majority of Linux OS we support * On Fedora at least I have to run the IDE with GTK2 to avoid issues (export SWT_GTK3=0); running BrowserSim with GTK3 I see at least one UI issue in the BrowserSim Preferences window The potential paradox: * We are advising Fedora users to run IDE under GTK2 to avoid seeing UI issues but they must run BrowserSim under GTK3 so see UI issues > Resolve GTK and BrowserSim web engine paradox > --------------------------------------------- > > Key: JBIDE-17230 > URL: https://issues.jboss.org/browse/JBIDE-17230 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > > Within Window>Preferences>JBoss Tools>BrowserSim/CordovaSim, selecting GTK for BrowserSim seems to be available for Linux-based OS only. > I can choose GTK2 or GTK3. > I'm running the IDE under GTK2 (export SWT_GTK3=0) to avoid UI issues. So I select to run BrowserSim also under GTK2 - seems sensible. But when I start BrowserSim I see the error message stating -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17230) GTK and BrowserSim web engine issue

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17230?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-17230: ------------------------------------ Summary: GTK and BrowserSim web engine issue (was: Resolve GTK and BrowserSim web engine paradox) > GTK and BrowserSim web engine issue > ----------------------------------- > > Key: JBIDE-17230 > URL: https://issues.jboss.org/browse/JBIDE-17230 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > > Within Window>Preferences>JBoss Tools>BrowserSim/CordovaSim, selecting GTK for BrowserSim seems to be available for Linux-based OS only. > I can choose GTK2 or GTK3. > I'm running the IDE under GTK2 (export SWT_GTK3=0) to avoid UI issues. So I select to run BrowserSim also under GTK2 - seems sensible. But when I start BrowserSim I see the error message stating -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17232) Usage Stats for used wizards

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-17232: -------------------------------------- Summary: Usage Stats for used wizards Key: JBIDE-17232 URL: https://issues.jboss.org/browse/JBIDE-17232 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: usage Reporter: Alexey Kazakov -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17232) Usage Stats for used wizards

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17232?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17232: -------------------------------------- Assignee: Alexey Kazakov > Usage Stats for used wizards > ---------------------------- > > Key: JBIDE-17232 > URL: https://issues.jboss.org/browse/JBIDE-17232 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17232) Usage Stats for used wizards

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17232?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17232: ----------------------------------- Fix Version/s: 4.2.0.Beta2 > Usage Stats for used wizards > ---------------------------- > > Key: JBIDE-17232 > URL: https://issues.jboss.org/browse/JBIDE-17232 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17232) Usage Stats for used wizards

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17232?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17232: ----------------------------------- Labels: new_and_noteworthy (was: ) > Usage Stats for used wizards > ---------------------------- > > Key: JBIDE-17232 > URL: https://issues.jboss.org/browse/JBIDE-17232 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17231) Migrate Usage to Universal Analytics

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17231?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17231: -------------------------------------- Assignee: Alexey Kazakov > Migrate Usage to Universal Analytics > ------------------------------------ > > Key: JBIDE-17231 > URL: https://issues.jboss.org/browse/JBIDE-17231 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.x > > > https://developers.google.com/analytics/devguides/collection/upgrade/?hl=... > {quote} > Universal Analytics is a set of technological innovations that improve the way data is collected and processed in Google Analytics. > The Universal Analytics Upgrade is a process you can use to upgrade all of your classic Google Analytics properties into Universal Analytics properties without losing any data or changing your account settings. > All Google Analytics properties will soon be required to use Universal Analytics. *Any properties that don’t follow the upgrade process will be auto-transferred to Universal Analytics in the future*.{quote} > The transition from classic Google Analytics to Universal Analytics is happening incrementally over several phases. > The current phase is *Phase 3: Universal Analytics out of beta*. > The next phase is *Phase 4: Universal Analytics is the operating standard for Google Analytics.*: > {quote}All properties have been upgraded into Universal Analytics. > The following features will be deprecated: > ga.js > urchin.js > WAP/server-side snippets > YT / MO > Custom variables > User defined variables > *Data collected from the deprecated features will be processed for a minimum of 2 years*.{quote} > Currently, JBT usage sends requests using ga.js format. We should investigate what's changed in Analytics.js. And get ready to migrate to that new format. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17231) Migrate Usage to Universal Analytics

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17231?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17231: ----------------------------------- Fix Version/s: 4.2.x > Migrate Usage to Universal Analytics > ------------------------------------ > > Key: JBIDE-17231 > URL: https://issues.jboss.org/browse/JBIDE-17231 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.x > > > https://developers.google.com/analytics/devguides/collection/upgrade/?hl=... > {quote} > Universal Analytics is a set of technological innovations that improve the way data is collected and processed in Google Analytics. > The Universal Analytics Upgrade is a process you can use to upgrade all of your classic Google Analytics properties into Universal Analytics properties without losing any data or changing your account settings. > All Google Analytics properties will soon be required to use Universal Analytics. *Any properties that don’t follow the upgrade process will be auto-transferred to Universal Analytics in the future*.{quote} > The transition from classic Google Analytics to Universal Analytics is happening incrementally over several phases. > The current phase is *Phase 3: Universal Analytics out of beta*. > The next phase is *Phase 4: Universal Analytics is the operating standard for Google Analytics.*: > {quote}All properties have been upgraded into Universal Analytics. > The following features will be deprecated: > ga.js > urchin.js > WAP/server-side snippets > YT / MO > Custom variables > User defined variables > *Data collected from the deprecated features will be processed for a minimum of 2 years*.{quote} > Currently, JBT usage sends requests using ga.js format. We should investigate what's changed in Analytics.js. And get ready to migrate to that new format. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17231) Migrate Usage to Universal Analytics

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17231?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17231: ----------------------------------- Priority: Critical (was: Major) > Migrate Usage to Universal Analytics > ------------------------------------ > > Key: JBIDE-17231 > URL: https://issues.jboss.org/browse/JBIDE-17231 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.2.x > > > https://developers.google.com/analytics/devguides/collection/upgrade/?hl=... > {quote} > Universal Analytics is a set of technological innovations that improve the way data is collected and processed in Google Analytics. > The Universal Analytics Upgrade is a process you can use to upgrade all of your classic Google Analytics properties into Universal Analytics properties without losing any data or changing your account settings. > All Google Analytics properties will soon be required to use Universal Analytics. *Any properties that don’t follow the upgrade process will be auto-transferred to Universal Analytics in the future*.{quote} > The transition from classic Google Analytics to Universal Analytics is happening incrementally over several phases. > The current phase is *Phase 3: Universal Analytics out of beta*. > The next phase is *Phase 4: Universal Analytics is the operating standard for Google Analytics.*: > {quote}All properties have been upgraded into Universal Analytics. > The following features will be deprecated: > ga.js > urchin.js > WAP/server-side snippets > YT / MO > Custom variables > User defined variables > *Data collected from the deprecated features will be processed for a minimum of 2 years*.{quote} > Currently, JBT usage sends requests using ga.js format. We should investigate what's changed in Analytics.js. And get ready to migrate to that new format. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2014