[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-11602 at 2/27/13 3:03 PM:
------------------------------------------------------------------
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) is able to be run with JBT 4.1.x and Kepler without a change of VJet plug-ins.
The only change required is the adding of VJet Orbit dependencies to JBT Target Platform (see patch attached). Similar minimalistic changes are to be done due to run VJet plug-ins along with JBDS 7.0-based builds.
The VJet CA works in many cases for JS/HTML Files. JS dependencies are supported in many cases:
||comment||Content Assist Invoked||Result of insertion||
|Any JS file|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg!|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg!|
|JS file in Ticket Monster|!vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg!|!vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg!|
|HTML file 1|!vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg!|!vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg!|
|HTML file 2-1|!vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg!|!vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg!|
|HTML file 2-2|!vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg!|!vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg!|
was (Author: vrubezhny):
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) is able to be run with JBT 4.1.x and Kepler without a change of VJet plug-ins.
The only change required is the adding of VJet Orbit dependencies to JBT Target Platform (see patch attached). Similar minimalistic changes are to be done due to run VJet plug-ins along with JBDS 7.0-based builds.
The VJet CA works in many cases for JS/HTML Files. JS dependencies are supported in many cases:
||comment||Content Assist Invoked||Result of insertion||
|Any JS file|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg!|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg!|
|col B1|col B2|col B3|
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
> Attachments: jbosstools-add-vjet-dependencies-patch.patch
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-11602:
-----------------------------------------
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) is able to be run with JBT 4.1.x and Kepler without a change of VJet plug-ins.
The only change required is the adding of VJet Orbit dependencies to JBT Target Platform (see patch attached). Similar minimalistic changes are to be done due to run VJet plug-ins along with JBDS 7.0-based builds.
The VJet CA works in many cases for JS/HTML Files. JS dependencies are supported in many cases:
||comment||Content Assist Invoked||Result of insertion||
|Any JS file|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg!|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg!|
|col B1|col B2|col B3|
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13413:
-----------------------------------------------
http://view.jquerymobile.com/1.3.0/docs/widgets/textinputs/
22. Text with all variations
Wizard
Type: text/search/textarea/email/password/color/file etc.
Label:
ID:
Clear Button:
Placeholder:
Mini:
Disabled:
Hide Label:
Theme:
Result
Type=text
<label for="text-3">Text input: data-clear-btn="true"</label>
<input data-clear-btn="true" name="text-3" id="text-3" value="" type="text">
Type=search
<label for="search-1">Search:</label>
<input name="search-1" id="search-1" value="" type="search">
Type=textarea
<label for="textarea-1">Textarea:</label>
<textarea cols="40" rows="8" name="textarea-1" id="textarea-1"></textarea>
and so on.
> jQuery Mobile Widget Palette
> ----------------------------
>
> Key: JBIDE-13413
> URL: https://issues.jboss.org/browse/JBIDE-13413
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.x
>
> Attachments: CSS-Preview.png, Dialog.png, DialogWizBan.png, Images.zip, jQueryMobile.png, jQueryMobile.png, jQueryMobile.png, Listview.png, ListviewWizBan.png, NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewCheckboxWizard.png, NewCheckboxWizard.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png, PaletteThinLines.png, Palette_1.png, Palette_2.png, Palette_3.png, withwithoutpreview.bmml, withwithoutpreview.png
>
>
> http://jquerymobile.com/test/
> See my proposal regarding the content of jQuery Mobile palette below.
> Also I have an idea to add a live preview into each wizard.
> We could try to add a browser to the wizard which will show how the widget is going to look.
> !jQueryMobile.png!
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13628) Only one JBoss Central Configurator is selected for display
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13628?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-13628 at 2/27/13 1:39 PM:
----------------------------------------------------------------------
Wizards are not supposed to be added to central by other plugins. Only wizards that comes in via jboss way/jboss developer framework. In JBT 4.0/JBDS 6 these are a fixed set.
In JBT 4.1.x/JBDS 7 we want to add to central the option of showing wizards for things that are not even installed - i.e. "Teiid Project" which will tell user to install Teiid Plugin to get this. Thus the dependency is the other way around.
Thus i'm going to reject this as "work as expected".
was (Author: maxandersen):
Wizards are not supposed to be added to central by other plugins. Only wizards that comes in via jboss way/jboss developer framework. In JBT 4.0/JBDS 6 this are fixed.
In JBT 4.1.x we want to add to central the option of showing wizards for things that are not even installed - i.e. "Teiid Project" which will tell user to install Teiid Plugin to get this. Thus the dependency is the other way around.
Thus i'm going to reject this as "work as expected".
> Only one JBoss Central Configurator is selected for display
> -----------------------------------------------------------
>
> Key: JBIDE-13628
> URL: https://issues.jboss.org/browse/JBIDE-13628
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Reporter: Paul Richardson
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.1.0.Alpha1
>
>
> I wanted to contribute Teiid Designer's 'new model project' wizard as a link in the 'Create Projects' section of JBoss Central. [link|http://www.phantomjinx.co.uk/stuff/jboss-central.png]
> However, I found that the list of project wizards is hard-coded in the default configurator [1]. Thus, the only way I can contribute this link is by extending the default configurator and using the configurators extension point[2] to load my configurator.
> This works correctly but if another project decides to do the same thing then their configurator 'could' be loaded instead of mine due to the following logic in [3]:
> {code:title=ProjectExamplesActivator.java|borderStyle=solid}
> // ... ~ Line 1163
> IExtension extension = extensions[0];
> IConfigurationElement[] configurationElements = extension.getConfigurationElements();
> for (int j = 0; j < configurationElements.length; j++) {
> IConfigurationElement configurationElement = configurationElements[j];
> if (CONFIGURATOR.equals(configurationElement.getName())) {
> try {
> configurator = (IJBossCentralConfigurator) configurationElement.createExecutableExtension("class");
> } catch (CoreException e) {
> ProjectExamplesActivator.log(e);
> continue;
> }
> break;
> }
> }
> // ...
> {code}
>
> Thought an alternative configurator that aggregates all extension-pointed configurators and displays the content of each accordingly.
> Happy to provide a patch if required.
> [1] org.jboss.tools.project.examples.configurators.DefaultJBossCentralConfigurator
> [2] org.jboss.tools.project.examples.configurators
> [3] org.jboss.tools.project.examples.ProjectExamplesActivator.java
--
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
13 years, 1 month
[JBoss JIRA] (JBDS-494) Welcome Screen Still shows at the end of Seam New Project Wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-494?page=com.atlassian.jira.plugin.s... ]
Max Rydahl Andersen closed JBDS-494.
------------------------------------
Resolution: Out of Date
> Welcome Screen Still shows at the end of Seam New Project Wizard
> ----------------------------------------------------------------
>
> Key: JBDS-494
> URL: https://issues.jboss.org/browse/JBDS-494
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Affects Versions: 2.0.0.beta1
> Reporter: Jim Tyrrell
> Fix For: LATER
>
> Attachments: Why not the default screen instead o fthe landing screen after new Create Seam Project.png
>
>
> After successfully completing the generation of the New Seam Project Wizard I am brought back to the Welcome page as seen in the attached screen shot. This is not to me the correct behavior.
> It would be nice to have my workspace opened with the projects on the left hand side, servers open on the bottom. It might also be nice to ask if I want to start the JBoss Server bound to this project...and I might even consider starting and deploying the home page so it is viewable in a web browser after the wizard completes. Or should all of this start in the background, or should you prompt the user to do all of this. Thoughts?
--
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
13 years, 1 month
[JBoss JIRA] (JBDS-494) Welcome Screen Still shows at the end of Seam New Project Wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-494?page=com.atlassian.jira.plugin.s... ]
Max Rydahl Andersen commented on JBDS-494:
------------------------------------------
closing this as central is the new way of doing this.
> Welcome Screen Still shows at the end of Seam New Project Wizard
> ----------------------------------------------------------------
>
> Key: JBDS-494
> URL: https://issues.jboss.org/browse/JBDS-494
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Affects Versions: 2.0.0.beta1
> Reporter: Jim Tyrrell
> Fix For: LATER
>
> Attachments: Why not the default screen instead o fthe landing screen after new Create Seam Project.png
>
>
> After successfully completing the generation of the New Seam Project Wizard I am brought back to the Welcome page as seen in the attached screen shot. This is not to me the correct behavior.
> It would be nice to have my workspace opened with the projects on the left hand side, servers open on the bottom. It might also be nice to ask if I want to start the JBoss Server bound to this project...and I might even consider starting and deploying the home page so it is viewable in a web browser after the wizard completes. Or should all of this start in the background, or should you prompt the user to do all of this. Thoughts?
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13628) Only one JBoss Central Configurator is selected for display
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13628?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-13628.
-----------------------------------------
Fix Version/s: 4.1.0.Alpha1
Resolution: Won't Fix
Added https://issues.jboss.org/browse/JBIDE-12962 to have the new feature tracked and visible.
> Only one JBoss Central Configurator is selected for display
> -----------------------------------------------------------
>
> Key: JBIDE-13628
> URL: https://issues.jboss.org/browse/JBIDE-13628
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Reporter: Paul Richardson
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.1.0.Alpha1
>
>
> I wanted to contribute Teiid Designer's 'new model project' wizard as a link in the 'Create Projects' section of JBoss Central. [link|http://www.phantomjinx.co.uk/stuff/jboss-central.png]
> However, I found that the list of project wizards is hard-coded in the default configurator [1]. Thus, the only way I can contribute this link is by extending the default configurator and using the configurators extension point[2] to load my configurator.
> This works correctly but if another project decides to do the same thing then their configurator 'could' be loaded instead of mine due to the following logic in [3]:
> {code:title=ProjectExamplesActivator.java|borderStyle=solid}
> // ... ~ Line 1163
> IExtension extension = extensions[0];
> IConfigurationElement[] configurationElements = extension.getConfigurationElements();
> for (int j = 0; j < configurationElements.length; j++) {
> IConfigurationElement configurationElement = configurationElements[j];
> if (CONFIGURATOR.equals(configurationElement.getName())) {
> try {
> configurator = (IJBossCentralConfigurator) configurationElement.createExecutableExtension("class");
> } catch (CoreException e) {
> ProjectExamplesActivator.log(e);
> continue;
> }
> break;
> }
> }
> // ...
> {code}
>
> Thought an alternative configurator that aggregates all extension-pointed configurators and displays the content of each accordingly.
> Happy to provide a patch if required.
> [1] org.jboss.tools.project.examples.configurators.DefaultJBossCentralConfigurator
> [2] org.jboss.tools.project.examples.configurators
> [3] org.jboss.tools.project.examples.ProjectExamplesActivator.java
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13674) provide a way for wizards on central to show up even if their plugin are not available
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-13674:
-------------------------------------------
Summary: provide a way for wizards on central to show up even if their plugin are not available
Key: JBIDE-13674
URL: https://issues.jboss.org/browse/JBIDE-13674
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Provide a mechanism in Central to declare a wizard with icon, description etc. that can show up even without the required plugin is available.
If the plugin is available the wizard just start/works as expected.
If the plugin is not available user should be explained what needs to be installed and ask if they want it. Then attempt to install via the provided IU's and/or central connector id, ask for restart and once restart is completed and central is started again and the plugin is available - open dialog saying "You started XYZ Wizard - it is now installed. Want to start it ?"
If the plugin still is not available that is an error situation and should be told to the user.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13628) Only one JBoss Central Configurator is selected for display
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13628?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13628:
---------------------------------------------
Wizards are not supposed to be added to central by other plugins. Only wizards that comes in via jboss way/jboss developer framework. In JBT 4.0/JBDS 6 this are fixed.
In JBT 4.1.x we want to add to central the option of showing wizards for things that are not even installed - i.e. "Teiid Project" which will tell user to install Teiid Plugin to get this. Thus the dependency is the other way around.
Thus i'm going to reject this as "work as expected".
> Only one JBoss Central Configurator is selected for display
> -----------------------------------------------------------
>
> Key: JBIDE-13628
> URL: https://issues.jboss.org/browse/JBIDE-13628
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Reporter: Paul Richardson
> Assignee: Max Rydahl Andersen
> Priority: Minor
>
> I wanted to contribute Teiid Designer's 'new model project' wizard as a link in the 'Create Projects' section of JBoss Central. [link|http://www.phantomjinx.co.uk/stuff/jboss-central.png]
> However, I found that the list of project wizards is hard-coded in the default configurator [1]. Thus, the only way I can contribute this link is by extending the default configurator and using the configurators extension point[2] to load my configurator.
> This works correctly but if another project decides to do the same thing then their configurator 'could' be loaded instead of mine due to the following logic in [3]:
> {code:title=ProjectExamplesActivator.java|borderStyle=solid}
> // ... ~ Line 1163
> IExtension extension = extensions[0];
> IConfigurationElement[] configurationElements = extension.getConfigurationElements();
> for (int j = 0; j < configurationElements.length; j++) {
> IConfigurationElement configurationElement = configurationElements[j];
> if (CONFIGURATOR.equals(configurationElement.getName())) {
> try {
> configurator = (IJBossCentralConfigurator) configurationElement.createExecutableExtension("class");
> } catch (CoreException e) {
> ProjectExamplesActivator.log(e);
> continue;
> }
> break;
> }
> }
> // ...
> {code}
>
> Thought an alternative configurator that aggregates all extension-pointed configurators and displays the content of each accordingly.
> Happy to provide a patch if required.
> [1] org.jboss.tools.project.examples.configurators.DefaultJBossCentralConfigurator
> [2] org.jboss.tools.project.examples.configurators
> [3] org.jboss.tools.project.examples.ProjectExamplesActivator.java
--
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
13 years, 1 month