[JBoss JIRA] (JBIDE-16332) VisualEditor: Use JavaFX WebView to render JSP/XHTML/HTML pages at design time
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16332?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-16332 at 1/16/14 6:28 PM:
----------------------------------------------------------------
*Oracle Java FX WebKit*
Webkit compiled from fork located [here|https://oss.oracle.com/projects/webkit-java-mods]. javafxwebkit.dll is included in 32bit and 64bit version of JDK and located in jre/bin folder.
Html 5 rating is close to 500 according http://html5test.com/.
|| || Java7 32bit || Java7 64bit || Java8 32bit || Java8 64bit ||
|| Windows 32bit | | *X* | | *X* |
|| Windows 64bit | | | | |
|| OS X 32bit | *X* | *X* | *X* | *X* |
|| OS X 64bit | *X* | | *X* | |
|| Linux 32bit *| | *X* | | *X* |
|| Linux 64bit *| | | | |
\* No GTK3 support for linux
Advantages:
* Support for Windows 64bit
* Support for Mac OS X 64bit
* provides API to access to DOM model
Disadvantages:
* Under Eclipse for Linux swt-javafx uses glass.so which is linked with GTK 2 only. To let it work eclipse should be started with SWT_GTK3=0 to trigger usage GTK 2.
* Not included in Open JDK 7
* Is not public API
Performance:
* Slower under Linux
was (Author: dgolovin):
*Oracle Java FX WebKit*
Webkit compiled from fork located [here|https://oss.oracle.com/projects/webkit-java-mods].
Html 5 rating is close to 500 according http://html5test.com/.
|| || Java7 32bit || Java7 64bit || Java8 32bit || Java8 64bit ||
|| Windows 32bit | | *X* | | *X* |
|| Windows 64bit | | ? | | ? |
|| OS X 32bit | *X* | *X* | *X* | *X* |
|| OS X 64bit | *X* | | *X* | |
|| Linux 32bit *| | *X* | | *X* |
|| Linux 64bit *| | | | |
\* No GTK3 support for linux
Advantages:
*
*
Disadvantages:
*
*
Performance:
> VisualEditor: Use JavaFX WebView to render JSP/XHTML/HTML pages at design time
> ------------------------------------------------------------------------------
>
> Key: JBIDE-16332
> URL: https://issues.jboss.org/browse/JBIDE-16332
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.x
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
> Questions to answer:
> 1) compatibility when both osgi hooks in place our and e(fx)clipse
> 2) is it working with gtk3
> 3) check how to add osgi hooks parameters into user's eclipse when installing from update site (p2 tochpoints should help)
> 4) how javafx load webkit and how it collides with eclipse loaded web kit
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBDS-340) Intro/Welcome screen cleanup
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-340?page=com.atlassian.jira.plugin.s... ]
Snjezana Peco commented on JBDS-340:
------------------------------------
In my opinion, it is Out of Date.
> Intro/Welcome screen cleanup
> ----------------------------
>
> Key: JBDS-340
> URL: https://issues.jboss.org/browse/JBDS-340
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: LATER
>
>
> SWT did some changes to allow xulrunner to be configured at startup - we should make sure we do what is needede there.
> If that happens we should be able to remove our big code duplication and just use the normal welcome screen mechanism
> and hopefully create a JBDS branded version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-14448) Build doesn't detect cycle dependencies between JBossTools modules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14448?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-14448.
------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.2.x)
Resolution: Duplicate Issue
Closing as dupe of JBIDE-16309
> Build doesn't detect cycle dependencies between JBossTools modules
> ------------------------------------------------------------------
>
> Key: JBIDE-14448
> URL: https://issues.jboss.org/browse/JBIDE-14448
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.0.Beta1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.0.Alpha2
>
>
> Currently every component references nightly composite update site during the build to get dependencies. That leads to possibility to introduce cycle dependencies between components that is not detected by build.
> Here is example of PR introduced a cycle between JST and VPE. Build works because JST have access to VPE BrowserSim through nightly composite update site.
> The solution would be to reference specific nightly update sites for modules that are dependencies for current one.
> In this case JST should have reference only to base composite nightly update site. That would solve cycle dependency detection problem and speed up the build because it would not require to download and analyse all metadata from jbosstools nightly composite update site.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-14448) Build doesn't detect cycle dependencies between JBossTools modules
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14448?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-14448:
---------------------------------------
I agree JBIDE-16309 solves the problem
> Build doesn't detect cycle dependencies between JBossTools modules
> ------------------------------------------------------------------
>
> Key: JBIDE-14448
> URL: https://issues.jboss.org/browse/JBIDE-14448
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.0.Beta1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.x
>
>
> Currently every component references nightly composite update site during the build to get dependencies. That leads to possibility to introduce cycle dependencies between components that is not detected by build.
> Here is example of PR introduced a cycle between JST and VPE. Build works because JST have access to VPE BrowserSim through nightly composite update site.
> The solution would be to reference specific nightly update sites for modules that are dependencies for current one.
> In this case JST should have reference only to base composite nightly update site. That would solve cycle dependency detection problem and speed up the build because it would not require to download and analyse all metadata from jbosstools nightly composite update site.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-428) Add new features to Feemarker Plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-428?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBIDE-428.
----------------------------
Fix Version/s: 3.2.3.Final
(was: LATER)
Resolution: Out of Date
Freemarker is sort of getting to end of life in JBoss Tools, so not sure what to do w/ this patch, especially since in 2009 we were on Eclipse 3.x and using SVN, whereas now we're on 4.x and using github.
So closing Out of Date. Does anyone want to update this patch to work w/ the new github repo?
> Add new features to Feemarker Plugin
> ------------------------------------
>
> Key: JBIDE-428
> URL: https://issues.jboss.org/browse/JBIDE-428
> Project: Tools (JBoss Tools)
> Issue Type: Patch
> Components: freemarker
> Reporter: ZERR Angelo
> Assignee: Joe Hudson
> Fix For: 3.2.3.Final
>
> Attachments: FreemarkerIDE.zip, org.jboss.ide.eclipse.freemarker.patch, patch.txt
>
>
> I have updated Freemarker Plugin to :
> 1) have template completion capability : (ex : type list in your ftl template, and CRTL+SPACE => <#list ....><#list> will be generate.
> You can customize your template with menu Window/Preferences/Freemarker Editor/Templates
> 2) add XML context capabilty. You can choose XML file and have completion with element and attribute of your XML.
> 3) add String context. I beleive it will be better to have Java Type context (Boolea, String,...)
> 3) add Preview Tab to see the result of the merge of your template and your model. It works ONLY with XML context. It's not available dor Class context.
> To use Preview Tab with Class, I believe it will good to have a class wich return getter of your Class.
> Ex : if you have class MyForm, user will have to add getMyForm in the context class for the preview.
> MyForm getMyForm() {
> MyForm form = new MyForm
> form.setId("MyId")
> return form;
> }
> If user have the ftl template ${myForm.id}, when you click to th epreview tab, you will have MyId displayed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBDS-340) Intro/Welcome screen cleanup
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-340?page=com.atlassian.jira.plugin.s... ]
Nick Boldt commented on JBDS-340:
---------------------------------
[~maxandersen] [~snjeza] is this something to fix in JBDS 8? Or something to close as WONTFIX / Out of Date?
> Intro/Welcome screen cleanup
> ----------------------------
>
> Key: JBDS-340
> URL: https://issues.jboss.org/browse/JBDS-340
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: LATER
>
>
> SWT did some changes to allow xulrunner to be configured at startup - we should make sure we do what is needede there.
> If that happens we should be able to remove our big code duplication and just use the normal welcome screen mechanism
> and hopefully create a JBDS branded version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months