[JBoss JIRA] (JBIDE-5135) Support Resources Localization and Versioning in JSF 2
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-5135?page=com.atlassian.jira.plugin... ]
Denis Golovin updated JBIDE-5135:
---------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Support Resources Localization and Versioning in JSF 2
> ------------------------------------------------------
>
> Key: JBIDE-5135
> URL: https://issues.jboss.org/browse/JBIDE-5135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Affects Versions: 3.1.0.M4
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: jsf2, new_and_noteworthy
> Fix For: 4.2.x
>
>
> See JSF 2 Spec "2.6.1.4 Libraries of Localized and Versioned Resources"
> In scope of this issue I planned to do:
> 1) check if variable locale_prefix specifyed in VPE EL, and if such variable is specified use it for calculation resource path;
> 2) for getting jsf2 resources in vpe implement algoritm which pseudo code specification exist in JSF 2 Spec "2.6.1.4 Libraries of Localized and Versioned Resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-3060) VPE template dialog ui suggestions
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3060?page=com.atlassian.jira.plugin... ]
Denis Golovin updated JBIDE-3060:
---------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> VPE template dialog ui suggestions
> ----------------------------------
>
> Key: JBIDE-3060
> URL: https://issues.jboss.org/browse/JBIDE-3060
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: Visual Page Editor core
> Affects Versions: 2.1.2
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> The "custom template" for unknown tags is really useful but extremely well hidden and rather quirky to use
> 1) The shortcut in the context menu just says "Template" ...no indication of what it does.
> I suggest we call it something like "Setup template for <the tag name>..." ; that describes what it does plus has ... to show a dialog will come up
> 2) The actual dialog allow me to type in *any* text for the tag, I instantly tried <button> but that is wrong it should be just button. Help the user here ;)
> I also tried putting rich:calendar but it does not look like it supports template translation, only simple basic tags - then we should just have editable combo list with choices here.
> 3) Give a preview of how the tag will look like in the dialog
> 4) The Template editor in preferences has no instructions and no Add button; at least explain the the tables contain existing prefreences for already configured templates and tell them about the "Setup template.." action in the context menu.
> ....It also contains 2 lines with some names I never setup (i.e. unknowntag-1, unknwontag-2) - remove them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14297) add missing metadata to stacks.yml
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14297?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14297:
-------------------------------------
Re-posting snjezana's comment from related jiras:
Snjezana Peco added a comment - 07/Mar/13 7:48 AM
In order to use stacks.yaml, we have to fix JBIDE-13686.
We also need some other properties in stacks.yaml to download runtimes. They are the following:
license URL
size
disclaimer (true for a community runtime)
requireSso (if https://github.com/jbosstools/jbosstools-base/pull/50 is applied)
These properties can be added as labels.
JBT runtime IDs:
JBoss AS 3.2-7.1:
org.jboss.ide.eclipse.as.runtime.32
org.jboss.ide.eclipse.as.runtime.40
org.jboss.ide.eclipse.as.runtime.42
org.jboss.ide.eclipse.as.runtime.50
org.jboss.ide.eclipse.as.runtime.51
org.jboss.ide.eclipse.as.runtime.60
org.jboss.ide.eclipse.as.runtime.70
org.jboss.ide.eclipse.as.runtime.71
EAP 4.3-6.1 (EPP, SOA-P, EWP use the same IDs):
org.jboss.ide.eclipse.as.runtime.eap.43
org.jboss.ide.eclipse.as.runtime.eap.50
org.jboss.ide.eclipse.as.runtime.eap.60
org.jboss.ide.eclipse.as.runtime.eap.61
I am not sure if there is a JDF jira related to this issue, but will fix the issue when the JDF team names a label property(ies).
> add missing metadata to stacks.yml
> ----------------------------------
>
> Key: JBIDE-14297
> URL: https://issues.jboss.org/browse/JBIDE-14297
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, runtime-detection
> Reporter: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
>
> Current missing:
> * license
> * filesize
> * matching wtp server id
> * ... ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-1600) VPE templates designer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-1600?page=com.atlassian.jira.plugin... ]
Denis Golovin updated JBIDE-1600:
---------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> VPE templates designer
> ----------------------
>
> Key: JBIDE-1600
> URL: https://issues.jboss.org/browse/JBIDE-1600
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor Templates
> Affects Versions: 2.0.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> The idea is to allow developer see how designed element will look like in VPE during creating VPE template.
> It could be split editor as VPE is and shows in preview how elements defined in template will look like in VPE. The source used to show preview could be customized, so template developer is able to set up his own xhtml/jsp source used during preview.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14298) deprecate downloadRuntimes ext. pt., add new extension pt
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14298?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-14298:
--------------------------------
Description:
The downloadRuntimes extension point allows plugins to simply contribute via xml what runtimes are to be exposed via the runtimes preference pages. This is not suitable enough, as it means all runtimes must either be declared in xml, or, available in a web file currently stored at http://download.jboss.org/jbosstools/examples/download_runtimes.xml.
These two should be unified to support an extension point plus API that allows for downloadRuntimeProviders, which may return any set of download runtimes.
Callers of this may generate their list however they want, but, the suggested method would be by depending on jboss stacks and returning a list of runtimes from within the stacks yaml file that fit the component.
So for example, ASTools should get a list of available runtimes from stacks with the "SERVER" type, whereas seam would similarly return those with an appropriate seam tag or label.
> deprecate downloadRuntimes ext. pt., add new extension pt
> ---------------------------------------------------------
>
> Key: JBIDE-14298
> URL: https://issues.jboss.org/browse/JBIDE-14298
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, runtime-detection
> Reporter: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
>
> The downloadRuntimes extension point allows plugins to simply contribute via xml what runtimes are to be exposed via the runtimes preference pages. This is not suitable enough, as it means all runtimes must either be declared in xml, or, available in a web file currently stored at http://download.jboss.org/jbosstools/examples/download_runtimes.xml.
> These two should be unified to support an extension point plus API that allows for downloadRuntimeProviders, which may return any set of download runtimes.
> Callers of this may generate their list however they want, but, the suggested method would be by depending on jboss stacks and returning a list of runtimes from within the stacks yaml file that fit the component.
> So for example, ASTools should get a list of available runtimes from stacks with the "SERVER" type, whereas seam would similarly return those with an appropriate seam tag or label.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Denis Golovin updated JBIDE-2032:
---------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG
>
>
> Wizards with non-working help button attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months