[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ]
Konstantin Marmalyukov commented on JBDS-3263:
----------------------------------------------
Info about JBDS jar size(Standalone without EAP):
Alpha1 with included XulRunner: *509,370,869 bytes*
Locally built Alpha2 without XulRunner: *456,620,525 bytes*.
So what we can do according to [~dgisbert] feedback:
# a. MacOS - remove Visual/Source and Preview tab for xhtml/jsp files like Burr suggested at first
b. Windows - leave evarything as it is
c. Linux - Make HTML5 mode default. Modify dialog to ask user only at first opening xhtml/jsp file if he wants to have good JSF support and don't ask user again. If user wants - do a restart and switch to XulRunner mode, if not - either show error message on preview tab with link to preferences(as it implemented now) or see pt. a.
# Make Visual Editor for xhtml/jsp files available to download from central/update site, as [~dgolovin] suggested. This option will give us an actual amount of users which uses this feature, so we can decide is it ok to remove it or not.
For me both options are fine, but I cannot guarantee that there is enough time to do everything for Alpha2.
> Remove JSF Visual/Source and Preview Tabs
> -----------------------------------------
>
> Key: JBDS-3263
> URL: https://issues.jboss.org/browse/JBDS-3263
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, visual-page-editor-core
> Reporter: Burr Sutter
> Assignee: Konstantin Marmalyukov
> Fix For: 9.0.0.Beta2
>
>
> Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs.
> http://www.screencast.com/t/wettTf6s6cU
> http://www.screencast.com/t/zur1sCXmZ
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-15714:
------------------------------------------------
{quote}I would say if the user has disabled refresh then I would be fine saying he won't get uptodate content assist.{quote}
This can be easily fixed with using preview web browser(what will be actually done), where refresh cannot be disabled. So that's not a problem. The biggest problem which we have is the first content assist. If it is not a problem - so we will have angular CA in Alpha2
> Dynamic content assist for AngularJS expressions in html files
> --------------------------------------------------------------
>
> Key: JBIDE-15714
> URL: https://issues.jboss.org/browse/JBIDE-15714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: Diagram.gliffy, vpe.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-19569:
------------------------------------------------
[~mmalina] yes, but don't remember exactly is this a known issue and can we do anything with such links. Will investigate deeper/try to remember exactly a bit later.
> Unable to switch pages shown in visual preview when editing mobile html5
> ------------------------------------------------------------------------
>
> Key: JBIDE-19569
> URL: https://issues.jboss.org/browse/JBIDE-19569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
>
> I'm not sure if my use case is valid or not.
> But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
> So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
> Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
> But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
> [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBTIS-422) Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-422?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-422:
------------------------------------
Description:
Specify the integration stack discovery artifact:
{code}
./jbdevstudio -vmargs \
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \
-Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \
-Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \
-Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \
-Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA
{code}
then select Software/Update in JBoss Central and open Error Log.
Note that we are able to install all features without any other problem.
was:
Specify the integration stack discovery artifact:
{code}
./jbdevstudio -vmargs \
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \
-Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \
-Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \
-Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \
-Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA
{code}
then select Software/Update in JBoss Central and open Error Log
> Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
> -------------------------------------------------------------------
>
> Key: JBTIS-422
> URL: https://issues.jboss.org/browse/JBTIS-422
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.1.GA
> Reporter: Andrej Podhradsky
> Attachments: error_log.txt
>
>
> Specify the integration stack discovery artifact:
> {code}
> ./jbdevstudio -vmargs \
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \
> -Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \
> -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \
> -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \
> -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA
> {code}
> then select Software/Update in JBoss Central and open Error Log.
> Note that we are able to install all features without any other problem.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19410:
----------------------------------------
[~maxandersen] Did you try the PR? Does it work as you'd like?
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19410:
---------------------------------------------
please stop saying it is a corner-case. it happens for *anyone* launching to test our plugins from PDE. This dialog will block everyone on the whole team. It will also show for users using JBDS to write eclipse plugins so it is even visible for users.
There is zero reason to show the dialog, p2 itself don't complain on startup - neither should we.
Sure, it is a special case, but it is definitely not just an edge case that is not worth fixing properly.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months