February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19208) BrowserSim / CordovaSim New and Noteworthy for 4.3.0.Alpha1

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19208?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19208: -------------------------------- Summary: BrowserSim / CordovaSim New and Noteworthy for 4.3.0.Alpha1 (was: BrowserSim / CordovaSiim New and Noteworthy for 4.3.0.Alpha1) > BrowserSim / CordovaSim New and Noteworthy for 4.3.0.Alpha1 > ----------------------------------------------------------- > > Key: JBIDE-19208 > URL: https://issues.jboss.org/browse/JBIDE-19208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim, cordovasim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If BrowserSim is not listed here check if there are issues that should be added and add them. > Document the ones relevant for BrowserSim by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19223) Revise support status in support matrix doc

by Martin Malina (JIRA)

Martin Malina created JBIDE-19223: ------------------------------------- Summary: Revise support status in support matrix doc Key: JBIDE-19223 URL: https://issues.jboss.org/browse/JBIDE-19223 Project: Tools (JBoss Tools) Issue Type: Task Components: website Affects Versions: 4.2.2.Final Reporter: Martin Malina Assignee: Nick Boldt This doc contains a column called "Supported?": https://developer.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec... All of the version since JBDS/RHDS 1 say they are supported. This is not true. It seems that currently what is supported is JBDS 6 and up. But this needs verification. Do we need that column at all? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov edited comment on JBIDE-18177 at 2/11/15 7:22 AM: ------------------------------------------------------------------------- Everything is pushed into master. [~vpakan], info about testing: This issue is for Linux only. Try to start Alpha1 build under GTK2 and GTK3, with loadxulrunner flag and without it. Steps for each mode: 1. Open html5 page, choose HTML5 option in dialog. Check that page renders correctly. 2. Open html5 page, choose JSF option in dialog. Check that page renders incorrectly(cause html5 features is not available in xulrunner). 3. Open xhtml page, choose JSF option in dialog. Check that page renders correctly(only in GTK2 mode without loadxulrunner flag - otherwise no dialog(and no options in preferences page) and error message in visual part). 4. Open xhtml page, choose HTML5 option in dialog. Check that error message appears. This issue needs to be verified completely. After verification it will be applied in 4.2.x branch. was (Author: kmarmaliykov): Everything is pushed into master. [~vpakan], info about testing: This issue is for Linux only. Try to start Alpha1 build under GTK2 and GTK3, with loadxulrunner flag and without it. Steps for each mode: 1. Open html5 page, choose HTML5 option in dialog. Check that page renders correctly. 2. Open html5 page, choose JSF option in dialog. Check that page renders incorrectly(cause html5 features is not available in xulrunner). 3. Open xhtml page, choose JSF option in dialog. Check that page renders correctly(only in GTK2 mode without loadxulrunner flag - otherwise no dialog(and no options in preferences page) and error message in visual part). 4. Open xhtml page, choose HTML5 option in dialog. Check that error message appears. > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, new_and_noteworthy, requirements > Fix For: 4.3.0.Alpha1 > > Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-18177: ------------------------------------------------ Everything is pushed into master. [~vpakan], info about testing: This issue is for Linux only. Try to start Alpha1 build under GTK2 and GTK3, with loadxulrunner flag and without it. Steps for each mode: 1. Open html5 page, choose HTML5 option in dialog. Check that page renders correctly. 2. Open html5 page, choose JSF option in dialog. Check that page renders incorrectly(cause html5 features is not available in xulrunner). 3. Open xhtml page, choose JSF option in dialog. Check that page renders correctly(only in GTK2 mode without loadxulrunner flag - otherwise no dialog(and no options in preferences page) and error message in visual part). 4. Open xhtml page, choose HTML5 option in dialog. Check that error message appears. > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, new_and_noteworthy, requirements > Fix For: 4.3.0.Alpha1 > > Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19222) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19222?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19222: ------------------------------------------------ TODO for x branch: fix compile error in vpe PR caused by imports from browser.initializer bundles, cherry-pick fix of tabbed preferences page from base > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19222 > URL: https://issues.jboss.org/browse/JBIDE-19222 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, new_and_noteworthy, requirements > Fix For: 4.2.3.Beta1 > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-18177: ------------------------------------------- Fix Version/s: (was: 4.2.3.Beta1) > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, new_and_noteworthy, requirements > Fix For: 4.3.0.Alpha1 > > Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19222) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19222?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19222: ------------------------------------------- Fix Version/s: (was: 4.3.0.Alpha1) > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19222 > URL: https://issues.jboss.org/browse/JBIDE-19222 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, new_and_noteworthy, requirements > Fix For: 4.2.3.Beta1 > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19222) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-19222: ---------------------------------------------- Summary: Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner Key: JBIDE-19222 URL: https://issues.jboss.org/browse/JBIDE-19222 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: visual-page-editor-core, xulrunner Affects Versions: 4.2.0.CR1 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Priority: Critical Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) if he says okey - we set a flag somewhere to not start xulrunner. user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19208) BrowserSim New and Noteworthy for 4.3.0.Alpha1

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19208?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19208: -------------------------------- Component/s: cordovasim > BrowserSim New and Noteworthy for 4.3.0.Alpha1 > ---------------------------------------------- > > Key: JBIDE-19208 > URL: https://issues.jboss.org/browse/JBIDE-19208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim, cordovasim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If BrowserSim is not listed here check if there are issues that should be added and add them. > Document the ones relevant for BrowserSim by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18900: -------------------------------- Labels: new_and_noteworthy (was: ) > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, FHshortcuts.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 February 2015