[JBoss JIRA] (JBIDE-18673) when livereload server is running browsersim/cordovasim should automatically enable livereload
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18673?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18673:
------------------------------------------------
{quote}today when enable livereload is chosen browsersim says "no livereload server available" so it already knows where it should be so why not check that when starting up in separate thread and if it is there enable it.{quote}
we just check connection to livereload server(connect to localhost:$livereloadPort). If server returns OK code - everything is fine, if not - popup is shown. It was the only thing we can do without adding dependency to livereload.
> when livereload server is running browsersim/cordovasim should automatically enable livereload
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18673
> URL: https://issues.jboss.org/browse/JBIDE-18673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Reporter: Max Rydahl Andersen
> Assignee: Konstantin Marmalyukov
>
> when livereload is running on standard port livereload should be automatically be enabled on cordovasim/browsersim.
> Users should be able to disable it too but it gets tedious having to manually enable it always.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17818?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17818:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.3.x)
> Visual Editor: Need to handle external html / htm files
> -------------------------------------------------------
>
> Key: JBIDE-17818
> URL: https://issues.jboss.org/browse/JBIDE-17818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> Now VPE / HTML Preview can handle only workspace's files. Need to add external files support
> When I open html pages outside eclipse workspace I get an error stating VPE preview cannot open the file.
> That is not ok.
> preview should be able to just fine preview the html no matter where the content is from and if it is because some current limitation about preview then users should at least be able to edit files even if external to the workspace.
> by external to workspace I mean what is opened with File > Open File...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17818?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17818:
---------------------------------------------
this needs to be fixed - it is rather severe we have such limit on opening a html file in eclipse.
> Visual Editor: Need to handle external html / htm files
> -------------------------------------------------------
>
> Key: JBIDE-17818
> URL: https://issues.jboss.org/browse/JBIDE-17818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> Now VPE / HTML Preview can handle only workspace's files. Need to add external files support
> When I open html pages outside eclipse workspace I get an error stating VPE preview cannot open the file.
> That is not ok.
> preview should be able to just fine preview the html no matter where the content is from and if it is because some current limitation about preview then users should at least be able to edit files even if external to the workspace.
> by external to workspace I mean what is opened with File > Open File...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18673) when livereload server is running browsersim/cordovasim should automatically enable livereload
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18673?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18673:
---------------------------------------------
why would there need to be any dependency ?
today when enable livereload is chosen browsersim says "no livereload server available" so it already knows where it should be so why not check that when starting up in separate thread and if it is there enable it.
> when livereload server is running browsersim/cordovasim should automatically enable livereload
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18673
> URL: https://issues.jboss.org/browse/JBIDE-18673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Reporter: Max Rydahl Andersen
> Assignee: Konstantin Marmalyukov
>
> when livereload is running on standard port livereload should be automatically be enabled on cordovasim/browsersim.
> Users should be able to disable it too but it gets tedious having to manually enable it always.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18679) JBDS IDE for Creating New Openshift Application does not differentiate between cartridges that support scaling and cartridges that do not support scaling.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18679?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18679:
------------------------------------------
Hi Aakanksha Singh
I agree that we can/should do the checks upfront rather than letting the user fail. But this requires us to be able to know, which I'd have to investigate first (dont know so far).
> JBDS IDE for Creating New Openshift Application does not differentiate between cartridges that support scaling and cartridges that do not support scaling.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18679
> URL: https://issues.jboss.org/browse/JBIDE-18679
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR2
> Environment: JBDS IDE CR02 release, Open Shift Wizard - to create new openshift applications.
> Reporter: Aakanksha Singh
> Priority: Minor
> Fix For: 4.3.x
>
>
> When I create a new openshift application using Openshift Application wizard, the application creation fails.
> If i choose a cartidge without knowing if it is scalable, my application is not created due to the following reasons.
> 1. I choose a cartridge, for example diy-0.1 and proceed to select the "Enable scaling " feature in the wizard. My app is not created as the cartiridge is not scalable.
> Error message:
> "Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: The cartridge 'diy-0.1' does not support being made scalable."
> 2. I choose a cartridge, for example haproxy-1.4 and proceed without selecting the "Enable scaling " feature in the wizard. My app is not created as the cartiridge is scalable.
> Error message:
> 1]Error Message:
> "Could not create application aakanksha
> Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: haproxy-1.4 cannot be added to existing applications. It is automatically added when you create a scaling application."
> Change requested:
> Somewhere in the UI the "enable scaling" and the list of cartridges should be linked.
> So If user selects a cartridge is not scalable and selects "Enable scaling" feature, the UI shows a warning sign.
> OR
> Once user selects "Enable scaling", only the list of cartridges that are scalable should be displayed in the UI and viceversa.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18679) JBDS IDE for Creating New Openshift Application does not differentiate between cartridges that support scaling and cartridges that do not support scaling.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18679?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18679:
-------------------------------------
Fix Version/s: 4.3.x
> JBDS IDE for Creating New Openshift Application does not differentiate between cartridges that support scaling and cartridges that do not support scaling.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18679
> URL: https://issues.jboss.org/browse/JBIDE-18679
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR2
> Environment: JBDS IDE CR02 release, Open Shift Wizard - to create new openshift applications.
> Reporter: Aakanksha Singh
> Priority: Minor
> Fix For: 4.3.x
>
>
> When I create a new openshift application using Openshift Application wizard, the application creation fails.
> If i choose a cartidge without knowing if it is scalable, my application is not created due to the following reasons.
> 1. I choose a cartridge, for example diy-0.1 and proceed to select the "Enable scaling " feature in the wizard. My app is not created as the cartiridge is not scalable.
> Error message:
> "Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: The cartridge 'diy-0.1' does not support being made scalable."
> 2. I choose a cartridge, for example haproxy-1.4 and proceed without selecting the "Enable scaling " feature in the wizard. My app is not created as the cartiridge is scalable.
> Error message:
> 1]Error Message:
> "Could not create application aakanksha
> Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: haproxy-1.4 cannot be added to existing applications. It is automatically added when you create a scaling application."
> Change requested:
> Somewhere in the UI the "enable scaling" and the list of cartridges should be linked.
> So If user selects a cartridge is not scalable and selects "Enable scaling" feature, the UI shows a warning sign.
> OR
> Once user selects "Enable scaling", only the list of cartridges that are scalable should be displayed in the UI and viceversa.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18679) JBDS IDE for Creating New Openshift Application does not differentiate between cartridges that support scaling and cartridges that do not support scaling.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18679?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18679:
-------------------------------------
Issue Type: Enhancement (was: Feature Request)
> JBDS IDE for Creating New Openshift Application does not differentiate between cartridges that support scaling and cartridges that do not support scaling.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18679
> URL: https://issues.jboss.org/browse/JBIDE-18679
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR2
> Environment: JBDS IDE CR02 release, Open Shift Wizard - to create new openshift applications.
> Reporter: Aakanksha Singh
> Priority: Minor
>
> When I create a new openshift application using Openshift Application wizard, the application creation fails.
> If i choose a cartidge without knowing if it is scalable, my application is not created due to the following reasons.
> 1. I choose a cartridge, for example diy-0.1 and proceed to select the "Enable scaling " feature in the wizard. My app is not created as the cartiridge is not scalable.
> Error message:
> "Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: The cartridge 'diy-0.1' does not support being made scalable."
> 2. I choose a cartridge, for example haproxy-1.4 and proceed without selecting the "Enable scaling " feature in the wizard. My app is not created as the cartiridge is scalable.
> Error message:
> 1]Error Message:
> "Could not create application aakanksha
> Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: haproxy-1.4 cannot be added to existing applications. It is automatically added when you create a scaling application."
> Change requested:
> Somewhere in the UI the "enable scaling" and the list of cartridges should be linked.
> So If user selects a cartridge is not scalable and selects "Enable scaling" feature, the UI shows a warning sign.
> OR
> Once user selects "Enable scaling", only the list of cartridges that are scalable should be displayed in the UI and viceversa.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months