[JBoss JIRA] Created: (JBIDE-3054) CSS Class Wizard UI improvements
by Max Rydahl Andersen (JIRA)
CSS Class Wizard UI improvements
---------------------------------
Key: JBIDE-3054
URL: https://jira.jboss.org/jira/browse/JBIDE-3054
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 3.0.0.beta1
Reporter: Max Rydahl Andersen
Fix For: 3.0.0.cr1
The CSS class editor is really useful now but I found a couple of glitches/suggestions while testing it:
1) When using the wizard directly please initialize the File and style based on the current selection so users don't have to browse hundreds of projects/directories
2) If used from the VPE editor and I don't specify a css or class and press Ok I get an exception; shouldn't it either generate internal style CSS in this case or at least require the user to fill in file and style fields
3) Used from the vpe it should give a dropdown with the included .css files if possible, again to avoid unecessary manual browsing
4) On new styles (style attribute is empty) it would be good to remember the previous editied external css
5) The preview area is blank at first; I need to touch a field to see a preview..and couldn't we take the first 50 characters from the selected tag instead of just having the default string ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBIDE-3150) CSS Style Class Dialog possibilities
by Yura Zhishko (JIRA)
CSS Style Class Dialog possibilities
------------------------------------
Key: JBIDE-3150
URL: https://jira.jboss.org/jira/browse/JBIDE-3150
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 3.0.0.beta1
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
First test case:
1) Open/create CSS file
2) Add next content:
.myClass1, .myClass2 {
background-color: red;
}
3) Save changes
4) Choose any componenet on the page that support styleClass attribute.
5) Click button opposite styleClass attribute in Properties view
ASSERT: CSS Style Class Dialog should appear
6) Choose changed CSS file
7) Check Style class and choose line with classes from Step 2
8) Press Ok
RESULT: new styleClass attribute appears with next content: myClass1,.myClass2
POSSIBLE SOLUTION: style classes should follow one by one, throw white spaces
Second test case:
1) Choose any component with styleClass attribute
2) Set up the value of styleClass attribute in source code
3) Click button opposite styleClass attribute in Properties view
ASSERT: CSS Style Class Dialog appears but we haven't any preload into Style class field
4) POSSIBLE SOLUTION: the value of styleClass attribute should be displayed in the Style class field
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBIDE-3164) Need validation for CSS class dialog
by Yura Zhishko (JIRA)
Need validation for CSS class dialog
------------------------------------
Key: JBIDE-3164
URL: https://jira.jboss.org/jira/browse/JBIDE-3164
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.0.0.beta1
Reporter: Yura Zhishko
Assignee: Igor Zhukov
Test case:
1) Open CSS class dialog to create a new CSS class, do not check anything
2) Press Finish button
Exeption appears:
java.lang.NullPointerException
at org.jboss.tools.jst.jsp.outline.cssdialog.CSSClassDialog.saveChanges(CSSClassDialog.java:248)
at org.jboss.tools.jst.web.ui.wizards.css.NewCSSClassWizard$NewCSSClassWizardPage.saveChanges(NewCSSClassWizard.java:91)
at org.jboss.tools.jst.web.ui.wizards.css.NewCSSClassWizard.performFinish(NewCSSClassWizard.java:55)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:472)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:882)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:571)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:512)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:127)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1184)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1352)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3894)
at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:341)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3787)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:337)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4528)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2371)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBIDE-3204) rich:scrollableDataTable's bugs
by Yura Zhishko (JIRA)
rich:scrollableDataTable's bugs
-------------------------------
Key: JBIDE-3204
URL: https://jira.jboss.org/jira/browse/JBIDE-3204
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.0.0.cr1
Reporter: Yura Zhishko
Assignee: Yahor Radtsevich
1) <rich:subTable> shouldn't work inside <rich:scrollableDataTable>, but VPE renders it OK.
2) No one style or styleClass should be applyed for the footer and header of scrollableDataTable as default.
3) Template has to be modified itself. Here is a list of courses provides to this decision:
a) Vertical and horizontal scrolls should appear only if the values of height or/and width less than default size of column's fields (see screenshot-1) and, in this situation, I have to able to abserv the containing of the table with scrool's help, footers and headers of columns inside table must have fixed vertical positions (see screenshot-2).
b) The footer and header must be outside of the table (scrolls) (see screenshot-2)
4) columnClasses and rowClasses don't work at all (use attachment file)
5) If it possible, give support for selectedClass attribute
P. S. Some other problems exist in this component, but I think, there are problems of the richface itself...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months