[JBoss JIRA] (JBIDE-17199) HTML5 Palette: New Widget wizards are not modal
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17199?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17199:
-----------------------------------
Fix Version/s: 4.2.0.Beta2
> HTML5 Palette: New Widget wizards are not modal
> -----------------------------------------------
>
> Key: JBIDE-17199
> URL: https://issues.jboss.org/browse/JBIDE-17199
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: Ubuntu 14.04
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
>
> 1. Open any HTML5 file with JBoss HTML editor
> 2. Click on any JQM item in JQM Palette
> 3. A dialog is shown.
> 4. Don't close the dialog. Close the editor.
> 5. Press Finish on the dialog:
> {code}
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:413)
> at org.eclipse.swt.widgets.Control.toDisplay(Control.java:1463)
> at org.eclipse.draw2d.SWTEventDispatcher.setHoverSource(SWTEventDispatcher.java:524)
> at org.eclipse.draw2d.SWTEventDispatcher.updateHoverSource(SWTEventDispatcher.java:605)
> at org.eclipse.draw2d.SWTEventDispatcher.updateFigureUnderCursor(SWTEventDispatcher.java:576)
> at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:381)
> at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4425)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3773)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3393)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-7004) Add support for externalization of all string from web page
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7004?page=com.atlassian.jira.plugin... ]
Alexey Kazakov updated JBIDE-7004:
----------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Add support for externalization of all string from web page
> -----------------------------------------------------------
>
> Key: JBIDE-7004
> URL: https://issues.jboss.org/browse/JBIDE-7004
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 3.3.0.M1
> Reporter: Maxim Areshkau
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: LATER
>
> Attachments: Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.png, JBIDE7004-CONTEXT_MENU.png, JBIDE7004-PAGE1_BROWSE.png, JBIDE7004-PAGE1_LIST.png, JBIDE7004-PAGE2_STRINGS.png, JBIDE7004-PAGE3_BUNDLE.png
>
>
> The dialog to externalize all strings contains 3 pages.
> After user has selected "Externalize all strings.. " menu item
> !JBIDE7004-CONTEXT_MENU.png|width=400px!
> the dialog will appear:
> 1) On "Page1" user selects the bundle's *.properties file from the project
> !JBIDE7004-PAGE1_BROWSE.png|width=400px!
> All the properties from that file are shown in the table
> !JBIDE7004-PAGE1_LIST.png|width=400px!
> 2) Then "Page2" shows the list of all not-externalized strings along with generated keys for them. User can edit key directly in the table
> !JBIDE7004-PAGE2_STRINGS.png|width=400px!
> Validation for keys and values is performed instantly.
> 3) On the last "Page3" user selects the way how to register the resource bundle on the page: manually, in faces-config, via f:loadBundle
> !JBIDE7004-PAGE3_BUNDLE.png|width=400px!.
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-9741) Restore text selection in VPE when a Mylyn task is activated
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9741?page=com.atlassian.jira.plugin... ]
Alexey Kazakov updated JBIDE-9741:
----------------------------------
Fix Version/s: LATER
(was: 4.0.x)
> Restore text selection in VPE when a Mylyn task is activated
> ------------------------------------------------------------
>
> Key: JBIDE-9741
> URL: https://issues.jboss.org/browse/JBIDE-9741
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Affects Versions: 3.3.0.M3
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Labels: new_and_noteworthy
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> *Actual behavior*
> Now when a Mylyn task is activated, the text cursor in VPE is set to the beginning of file regardless of the previous selection.
> *Desired behavior*
> Text cursor and text selection in VPE should be restored.
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-7004) Add support for externalization of all string from web page
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7004?page=com.atlassian.jira.plugin... ]
Alexey Kazakov reassigned JBIDE-7004:
-------------------------------------
Assignee: Alexey Kazakov (was: Konstantin Marmalyukov)
> Add support for externalization of all string from web page
> -----------------------------------------------------------
>
> Key: JBIDE-7004
> URL: https://issues.jboss.org/browse/JBIDE-7004
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 3.3.0.M1
> Reporter: Maxim Areshkau
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.png, JBIDE7004-CONTEXT_MENU.png, JBIDE7004-PAGE1_BROWSE.png, JBIDE7004-PAGE1_LIST.png, JBIDE7004-PAGE2_STRINGS.png, JBIDE7004-PAGE3_BUNDLE.png
>
>
> The dialog to externalize all strings contains 3 pages.
> After user has selected "Externalize all strings.. " menu item
> !JBIDE7004-CONTEXT_MENU.png|width=400px!
> the dialog will appear:
> 1) On "Page1" user selects the bundle's *.properties file from the project
> !JBIDE7004-PAGE1_BROWSE.png|width=400px!
> All the properties from that file are shown in the table
> !JBIDE7004-PAGE1_LIST.png|width=400px!
> 2) Then "Page2" shows the list of all not-externalized strings along with generated keys for them. User can edit key directly in the table
> !JBIDE7004-PAGE2_STRINGS.png|width=400px!
> Validation for keys and values is performed instantly.
> 3) On the last "Page3" user selects the way how to register the resource bundle on the page: manually, in faces-config, via f:loadBundle
> !JBIDE7004-PAGE3_BUNDLE.png|width=400px!.
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-9741) Restore text selection in VPE when a Mylyn task is activated
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9741?page=com.atlassian.jira.plugin... ]
Alexey Kazakov updated JBIDE-9741:
----------------------------------
Component/s: (was: jsp/jsf/xml/html source editing)
> Restore text selection in VPE when a Mylyn task is activated
> ------------------------------------------------------------
>
> Key: JBIDE-9741
> URL: https://issues.jboss.org/browse/JBIDE-9741
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Affects Versions: 3.3.0.M3
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Labels: new_and_noteworthy
> Fix For: 4.0.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> *Actual behavior*
> Now when a Mylyn task is activated, the text cursor in VPE is set to the beginning of file regardless of the previous selection.
> *Desired behavior*
> Text cursor and text selection in VPE should be restored.
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-3236) SeamGen - provide ability to customize generated class/page names and paths
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3236?page=com.atlassian.jira.plugin... ]
Alexey Kazakov updated JBIDE-3236:
----------------------------------
Fix Version/s: LATER
(was: 4.0.x)
> SeamGen - provide ability to customize generated class/page names and paths
> ---------------------------------------------------------------------------
>
> Key: JBIDE-3236
> URL: https://issues.jboss.org/browse/JBIDE-3236
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate, seam2
> Reporter: Maksim Kaszynski
> Assignee: Koen Aers
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: LATER
>
>
> When using "Seam Generate Entities" ability in JBDS, it puts all generated pages and .page.xml files into view folder, and names them "FooList", "FooView", "FooEdit". This may be ok when there's up to 10 entities in the application, but when there's more, view folder becomes a bloody mess.
> It would be nice if there was possibliity to customize seam-gen output pattern, for example, "view/{class-name}/list.xhtml", so for Foo enity it would be "view/foo/list.xhtml", "view/foo/view.xhtml", "view/foo/edit.xhtml".
> Of course, it is possible to change view folder before launching "Generate Entities" for every entity, but it is not nice to do it 100 times when generating entities for hundred tables.
> When using console seam-gen, it is possible to co change that naming template in ant script, but JBDS has it all hard-coded.
> I propose to have some dialog for customizing output patterns.
--
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
11 years, 11 months