[
https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin...
]
Mikhail Kalkov commented on JBIDE-2720:
---------------------------------------
If I had to switch today, I'd prototype in Evolus Pencil (a standalone wireframing
tool based on XulRunner) followed by manual translation into HTML&JS. In longer run, I
would move to a wireframing tool that supports direct HTML export. I'm sure there must
be such (likely proprietary and paid) tools out there, but haven't bothered to look
for them so far. After all, it's not something I'm doing all day long. My workflow
looks like this: got to create a UI -> prototype one quickly -> get feedback ->
code it in html -> get feedback -> polish it. VPE and BrowserSim provide a shortcut
because they make it possible to prototype directly in HTML.
Thanks for explaining the browser engine dilemma. As for 64-bit Windows support, you have
probably discussed this already, but is it possible to ask Intel to fix their library or
workaround the issue through some kind of [DLL
injection|http://en.wikipedia.org/wiki/DLL_Injection]? I also recall that on my previous
job we had similar issues with Citrix XenApp server, which [replaced some MS dlls with
their own
variants|http://support.citrix.com/article/CTX107824]. So, theoretically there
may be other applications apart from Intel OpenCL SDK which may lead to crashes. I have
neither Citrix XenApp nor Intel OpenCL SDK installed so cannot confirm this.
[~nickboldt], thanks for the new repo, I've updated and it seems to work! Would you
update the FAQ entry too?
https://community.jboss.org/wiki/JBosstoolsVisualEditorFAQ
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.2.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, 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.3.1#6329)