[JBoss JIRA] (JBIDE-17199) HTML5 Palette: New Widget wizards are not modal
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17199?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17199.
-------------------------------
Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104
> 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: Daniel Azarov
> 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 was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-16687) provide access to palette entries via content assist
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16687?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16687.
-------------------------------
Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104
> provide access to palette entries via content assist
> ----------------------------------------------------
>
> Key: JBIDE-16687
> URL: https://issues.jboss.org/browse/JBIDE-16687
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta2
>
> Attachments: scrn.png
>
>
> Just had the idea while playing with drag'n'drop and JBIDE-16636.
> Why don't we have the elements in the palette available via content assist too ?
> Possibly as templates entries ?
> i.e. if I write "table|" and | is content assist it would provide a content assist that would allow to invoke the insert of any palette entries that matches table (assuming its valid at the location).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-15152) jQuery Mobile palette contains mix of jQuery Mobile and HTML5 items
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15152?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-15152.
-------------------------------
Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104
> jQuery Mobile palette contains mix of jQuery Mobile and HTML5 items
> -------------------------------------------------------------------
>
> Key: JBIDE-15152
> URL: https://issues.jboss.org/browse/JBIDE-15152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.CR1
> Reporter: Michelle Murray
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Beta2
>
> Attachments: html.png, jqm.png, MobileWeb_Palette.png
>
>
> 'jQuery Mobile' palette contains *mix* of jQuery Mobile and HTML5 items (screen capture attached). This could be confusing to users.
> To fix this, I suggest:
> A) changing the title of the palette to 'Mobile Web', to better reflect that it contains both jQuery Mobile and HTML5
> *OR*
> B) create two palettes - one for jQuery Mobile widgets and one for HTML5 widgets
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-16975) jQuery Mobile palette: add drop-down list identifier to version
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16975?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16975.
-------------------------------
Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104
> jQuery Mobile palette: add drop-down list identifier to version
> ---------------------------------------------------------------
>
> Key: JBIDE-16975
> URL: https://issues.jboss.org/browse/JBIDE-16975
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Daniel Azarov
> Labels: documentation
> Fix For: 4.2.0.Beta2
>
> Attachments: DropDownList.png
>
>
> The implementation for multiple jQuery Mobile palette versions is very clean. But I'm not sure users will intuitively know that they can click on the version number to see a list of available versions and change the version.
> Can a downwards arrowhead be added next to the version number to clarify this? Like in the OpenShift Application connection wizard where the connection field has a downwards arrowhead at the end of the value, or the new server wizard where the profile field has a downwards arrowhead at the end of the value. In both of these the downwards arrowhead immediately signifies to user to click here to see more options.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months