[JBoss JIRA] (JBIDE-11259) BrowserSim: broken layout on Linux
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11259?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-11259:
-------------------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> BrowserSim: broken layout on Linux
> ----------------------------------
>
> Key: JBIDE-11259
> URL: https://issues.jboss.org/browse/JBIDE-11259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Fix For: 4.4.x
>
> Attachments: BrowserSim_BrokenRender.png, screenshot-1.png
>
>
> *Steps to reproduce:*
> # Run BrowserSim on Linux (I used Ubuntu Linux 11.10 x86_64)
> # Check 'Use Skins' if it is not checked.
> # Select 'Samsung Galaxy Tab 10.1' skin
> # Click 'Turn Left' several times.
> *Actual result:*
> From time to time the layout of the window is broken:
> !screenshot-1.png|thumbnail!
> *Update:*
> Video created by [~rhopp]: http://youtu.be/HKN7hnLQOz8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-9248) Add JSP 2.0 Tag Files support (<jsp:doBody> should be displayed correctly)
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9248?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-9248:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Add JSP 2.0 Tag Files support (<jsp:doBody> should be displayed correctly)
> --------------------------------------------------------------------------
>
> Key: JBIDE-9248
> URL: https://issues.jboss.org/browse/JBIDE-9248
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-templates
> Affects Versions: 3.3.0.M1
> Reporter: Maxim Areshkau
> Assignee: Konstantin Marmalyukov
> Fix For: LATER
>
> Attachments: greeting.jsp, greeting.png, jspDoBody.zip, response.png, response.tag
>
>
> Currently custom JSP tags from *.tag files are not properly displayed in VPE.
> As well as <jsp:doBody> tag from within such tags.
> The requirements are:
> 1) Add to VPE the ability to recognize JSP 2.0 custom tags files (*.[tag|tagx])
> 2) VPE should CORRECTLY display the content of the JSP 2.0 Tag Files.
> 3) The content(children) of the custom tag should be plased into its template from *.[tag|tagx] files to the place where <jsp:doBody> is specified.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[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)
10 years, 3 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)
10 years, 3 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)
10 years, 3 months