[JBoss JIRA] Resolved: (JBIDE-1494) TextFormating tag should have default behaviour, now it is used as copy everywhere
by Maxim Areshkau (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-1494?page=all ]
Maxim Areshkau resolved JBIDE-1494.
-----------------------------------
Resolution: Done
Assignee: Andrei Scherbovich (was: Maxim Areshkau)
For vpe:textFormatting was added attribute use-default-formats.
So to specify using default formats, you more shouldn't copy-paste formats, just only set use-default-formats="yes".
Default formats can be configurated in file org.jboss.tools.vpe/resources/textFormatting.xml.
If some format specified in default and textFormatting tempalte definition, it will be used from template section.
> TextFormating tag should have default behaviour, now it is used as copy everywhere
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-1494
> URL: http://jira.jboss.com/jira/browse/JBIDE-1494
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: Cleanup
> Affects Versions: 2.0.0.GA
> Reporter: Denis Golovin
> Assigned To: Andrei Scherbovich
> Priority: Minor
> Fix For: 2.1
>
>
> It should be renamed to vpe:textFormatting
> Now there ar ea lot of blocks like posted below:
> <vpe:textFormating>
> <vpe:format type="BlockFormat" addChildren="deny" />
> <vpe:format type="UnderlineFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="BoldFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="ItalicFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="FontNameFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="FontSizeFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="BackgroundColorFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="ForegroundColorFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> </vpe:textFormating>
> It should have default behavior that is defined by inserting just <vpe:textFormatting> tag inside template. If some behavior should be redefined use vpe:format tag for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Updated: (JBIDE-1494) TextFormating tag should have default behaviour, now it is used as copy everywhere
by Maxim Areshkau (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-1494?page=all ]
Maxim Areshkau updated JBIDE-1494:
----------------------------------
Affects: [Documentation (Ref Guide, User Guide, etc.)]
> TextFormating tag should have default behaviour, now it is used as copy everywhere
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-1494
> URL: http://jira.jboss.com/jira/browse/JBIDE-1494
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: Cleanup
> Affects Versions: 2.0.0.GA
> Reporter: Denis Golovin
> Assigned To: Maxim Areshkau
> Priority: Minor
> Fix For: 2.1
>
>
> It should be renamed to vpe:textFormatting
> Now there ar ea lot of blocks like posted below:
> <vpe:textFormating>
> <vpe:format type="BlockFormat" addChildren="deny" />
> <vpe:format type="UnderlineFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="BoldFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="ItalicFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="FontNameFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="FontSizeFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="BackgroundColorFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="ForegroundColorFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> </vpe:textFormating>
> It should have default behavior that is defined by inserting just <vpe:textFormatting> tag inside template. If some behavior should be redefined use vpe:format tag for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Created: (JBIDE-1953) Exceptions appeares if user DnD <rich:toolBar> component into sourse editor.
by Andrei Scherbovich (JIRA)
Exceptions appeares if user DnD <rich:toolBar> component into sourse editor.
----------------------------------------------------------------------------
Key: JBIDE-1953
URL: http://jira.jboss.com/jira/browse/JBIDE-1953
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.1
Reporter: Andrei Scherbovich
Assigned To: Maxim Areshkau
Exceptions appeares if user DnD <rich:toolBar> component into sourse editor from JBoss Tools Pallete.
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.LinkedList.entry(LinkedList.java:368)
at java.util.LinkedList.remove(LinkedList.java:360)
at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesToolBarTemplate$SourceToolBarItems.init(RichFacesToolBarTemplate.java:451)
at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesToolBarTemplate$SourceToolBarItems.<init>(RichFacesToolBarTemplate.java:426)
at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesToolBarTemplate.create(RichFacesToolBarTemplate.java:63)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:395)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:241)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:539)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:453)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:241)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateElement(VpeVisualDomBuilder.java:854)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:786)
at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:462)
at org.jboss.tools.vpe.editor.VpeController.notifyChanged(VpeController.java:381)
at org.eclipse.wst.sse.core.internal.provisional.AbstractNotifier.notify(AbstractNotifier.java:201)
at org.eclipse.wst.xml.core.internal.document.XMLModelNotifierImpl.notifyStructureChanged(XMLModelNotifierImpl.java:392)
at org.eclipse.wst.xml.core.internal.document.XMLModelNotifierImpl.endChanging(XMLModelNotifierImpl.java:180)
at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.changedModel(DOMModelImpl.java:163)
at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel$DocumentToModelNotifier.nodesReplaced(AbstractStructuredModel.java:152)
at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:602)
at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1201)
at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1970)
at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2394)
at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1)
at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:98)
at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:42)
at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:109)
at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2390)
at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2353)
at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditorInternal(PaletteInsertHelper.java:212)
at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:131)
at org.jboss.tools.common.model.ui.editors.dnd.FileDropCommand.run(FileDropCommand.java:55)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1779)
at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:111)
at org.jboss.tools.common.model.ui.editors.dnd.PaletteDropCommand.execute(PaletteDropCommand.java:111)
at org.jboss.tools.common.model.ui.editors.dnd.DropWizard.performFinish(DropWizard.java:80)
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:616)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:90)
at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$2.run(JSPTextEditor.java:703)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Created: (JBIDE-1823) Event Handling Error after focusing on <rich:simpleTogglePanel> in Visual part od Editor
by Anton Klimkovich (JIRA)
Event Handling Error after focusing on <rich:simpleTogglePanel> in Visual part od Editor
----------------------------------------------------------------------------------------
Key: JBIDE-1823
URL: http://jira.jboss.com/jira/browse/JBIDE-1823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.1
Environment: JBossTools-200802260013-nightly-ALL
Reporter: Anton Klimkovich
Attachments: 111.txt
EXECUTE: Create JSF with Facelets kickstart project
EXECUTE: Open inputname.xhtml
EXECUTE: Insert <rich:simpleTogglePanel> :
<rich:simpleTogglePanel>
#{msg.prompt}
<input jsfc="h:inputText" required="true" id="name" value="#{person.name}" />
<input type="submit" jsfc="h:commandButton" id="submit" action="greeting" value="Say Hello" />
</rich:simpleTogglePanel>
ASSERT: simpleTogglePanel will be displayed in Visual part of Editor
EXECUTE: Set cursor to #{msg.prompt} on Source tab
EXECUTE: Click on simpleTogglePanel in Visual part of Editor
FAILURE : java.lang.ClassCastException: org.jboss.tools.vpe.editor.mapping.VpeNodeMapping
Log attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Commented: (JBIDE-621) Traditional Chinese Input Failed in Visual Page Editor
by Maxim Areshkau (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-621?page=comments#action_12405420 ]
Maxim Areshkau commented on JBIDE-621:
--------------------------------------
When we will be modifying content we will be notified about it in event handlers, and we can get information about old value and new value.Also we can in event handlers prevent it's from processing by xulruner, if we won't modify some elements or change selection.
> Traditional Chinese Input Failed in Visual Page Editor
> ------------------------------------------------------
>
> Key: JBIDE-621
> URL: http://jira.jboss.com/jira/browse/JBIDE-621
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor
> Affects Versions: ExadelStudioPro4
> Environment: Eclipse 3.2.2+Exadel Studio Pro 4.0.4+Tomcat 5.5+Windows XP Home(US English)
> Reporter: KT Lo
> Assigned To: Maxim Areshkau
> Fix For: LATER
>
> Attachments: Chinese.png, editing.zip, screenshot-1.jpg, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg
>
>
> Step 1: Called Up Traditional Chinese Phonetic Input Method (Check ScreenShot:"Step1)
> Step2: Intended Chinese Character typed but not showed and in the VIsual Page Editor ( (Check ScreenShot:"Step2)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months