[JBoss JIRA] (JBIDE-6501) Add possibility to change string value in the message bundle directly from the VPE.
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6501?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-6501:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Add possibility to change string value in the message bundle directly from the VPE.
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-6501
> URL: https://issues.jboss.org/browse/JBIDE-6501
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 3.2.x
> Reporter: Denis Maliarevich
> Assignee: Konstantin Marmalyukov
> Fix For: LATER
>
>
> Add possibility to change string value in the message bundle directly from the VPE.
> For instance, if there is a key value on a page like #{Message.Name} the user should be able to change the value of the key 'Name' directly from the VPE without opening a 'message.properties' file.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-4523) Visual Page Editor for JSF doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4523?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-4523:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Visual Page Editor for JSF doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-4523
> URL: https://issues.jboss.org/browse/JBIDE-4523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 3.1.0.M1
> Environment: Mac OSX 10.5.7, Eclipse 3.5 JEE Cocoa, JBoss Tools 3.1.0.M1
> Reporter: César Pérez
> Assignee: Konstantin Marmalyukov
> Labels: cocoa, new_and_noteworthy, osx, vpe
> Fix For: LATER
>
>
> The Visual Page Editor does not work under the final version of Eclipse 3.5 JEE Cocoa for Mac OSX and JBoss Tools 3.1.0.M1, the error is due to a missing cocoa version of XUL runner as you can see in the following stacktrace:
> org.jboss.tools.vpe.xulrunner.XulRunnerException: Bundle org.mozilla.xulrunner.cocoa.macosx is not found.
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.getXulRunnerPath(XulRunnerBrowser.java:219)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.initXulRunner(XulRunnerBrowser.java:114)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:85)
> at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.<init>(MozillaPreview.java:59)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:59)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:921)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:248)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart$2.widgetSelected(JSPMultiPageEditorPart.java:106)
> 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.Display.sendEvent(Display.java:3542)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3256)
> at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2045)
> at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:323)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3440)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
> 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:194)
> 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:368)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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:559)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-2720:
------------------------------------------
Fix Version/s: 4.4.x
(was: 4.2.x)
(was: 4.3.x)
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.4.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, screenshot-1.png, Unbenannt.PNG, Unbenannt.PNG, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-2519) Add support for CDATA tags
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2519?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-2519:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Add support for CDATA tags
> --------------------------
>
> Key: JBIDE-2519
> URL: https://issues.jboss.org/browse/JBIDE-2519
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-templates
> Affects Versions: 3.0.0.alpha
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Fix For: LATER
>
>
> Here is an example:
> <para>The source coding should be something like this now:</para>
> <programlisting role="XML"><![CDATA[<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
> <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
> <html>
> <head>
> <title></title>
> </head>
> <body>
> <f:view>
> <h:form id="greeting">
> <para>Please enter a name:</para>
> <h:inputText id="name" value="#{personBean.name}"/>
> <h:commandButton value=" Say Hello " action="greeting"/>
> </h:form>
> </f:view>
> </body>
> </html>
> ]]></programlisting>
> <para>The editor should look like this:</para>
> In this context CDATA blocks seems must be processed in relation with parent tag. Taking in consideration that now all tags that has no prefix considered as HTML it cannot be supported without VPE refactoring
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-8711) Visual Page Editor very often just shows Grey area where Visual Page Editor should be when clicking a search result
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8711?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-8711:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Visual Page Editor very often just shows Grey area where Visual Page Editor should be when clicking a search result
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-8711
> URL: https://issues.jboss.org/browse/JBIDE-8711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, visual-page-editor-core
> Affects Versions: 3.2.0.Final
> Environment: MacOS X Cocoa, Eclipse 3.7
> Reporter: Max Rydahl Andersen
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: LATER
>
> Attachments: Screen shot 2011-05-05 at 3.20.15 PM.png
>
>
> This is probably an OSX specific bug, but its very annoying.
> When having a match in the Searches view that matches a xhtml file then more often than not the UI for the visual page editor and sometimes the whole editor is just grey as if nothing is rendering.
> Switching back and forth between the tabs make it show up eventually.
> Makes the visual page editor very annoying to use when navigating code :(
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-16575:
-------------------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> Tests for BrowserSim
> --------------------
>
> Key: JBIDE-16575
> URL: https://issues.jboss.org/browse/JBIDE-16575
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.4.x
>
>
> We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX.
> It's probably imposible to have such tests without special Jenkins settings.
> So [~nickboldt]'s help is needed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months