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

Burr Sutter (JIRA) issues at jboss.org
Tue Dec 9 11:07:39 EST 2014


    [ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026356#comment-13026356 ] 

Burr Sutter commented on JBIDE-18177:
-------------------------------------

I would have to personally try it out - it is common to have a 'cancel' button - basically where the end-user did not mean to trigger the dialog or when he/she reads the message determines that it is too uncomfortable to make a change - Cancel means "get me out of here, I do not wish to change anything right now".    

With that said, if the "current mode" is really obvious and by clicking the right button I can remain in the 'current mode' without a problem, perhaps Cancel is unnecessary.


> 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
>             Fix For: 4.2.2.Final, 4.3.0.Alpha1
>
>         Attachments: restart.jpg
>
>
> 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.8#6338)


More information about the jbosstools-issues mailing list