[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 commented on JBIDE-16332:
---------------------------------------
*Native WebKit*
SWT Webkit integration
|| || Java7 32bit || Java7 64bit || Java8 32bit || Java8 64bit ||
|| Windows 32bit | | N/A | | N/A |
|| Windows 64bit | | | | |
|| OS X 32bit | N/A | N/A | N/A | N/A |
|| OS X 64bit | *X* | | *X* | |
|| Linux 32bit ** | | N/A | | N/A |
|| Linux 64bit ** | | | | |
\* Both GTK 2 and GTK 3 supported
Advantages:
* Stable WebKit version for visual editor and browsersim
* Some features for VPE can be implemented in WebKit as it was done for xulrunner
* Windows 64 bit support through WebKit Cairo port
* GTK2 and GTK3 support
Disadvantages:
* We have to build it under all supported platforms
* Forked codebase maintenance
Performance:
* The same as for SWT browser
> 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, 5 months
[JBoss JIRA] (JBIDE-6315) Shrinkwrap output visualization
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6315?page=com.atlassian.jira.plugin... ]
Aslak Knutsen commented on JBIDE-6315:
--------------------------------------
I believe the Arquillian Cruiser view covers this
> Shrinkwrap output visualization
> -------------------------------
>
> Key: JBIDE-6315
> URL: https://issues.jboss.org/browse/JBIDE-6315
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: testing-tools
> Reporter: Pete Muir
> Assignee: Max Rydahl Andersen
> Labels: shrinkwrap
> Fix For: 3.3.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When writing packaging descriptions (e.g. via Shrinkwrap or traditionally via Ant/Maven), you often want to view what the generated artifact looks like so you can check where a particular file is placed.
> Provide a visualization of the current Shrinkwrap, this should view just like the package explorer in eclipse (consistency!) and update in realtime as someone alters their shrinkwrap declaration. Having a filter would be useful as well.
--
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, 5 months
[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16290:
-----------------------------------
Description:
This ticket is meant to list the bugs related to GTK3 affecting JBDS:
* JBIDE-16280 VPE/XulRunner crashes workbench
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=425692 (Import Existing Maven Project)
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581
* Central tests uses SWT_GTK3=0 in its pom.
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123
Some more minor ones:
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=417601
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=421834
We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA.
On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future.
was:
This ticket is meant to list the bugs related to GTK3 affecting JBDS:
* JBIDE-16280 VPE/XulRunner crashes workbench
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=425692 (Import Existing Maven Project)
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581
* Central tests uses SWT_GTK3=0 in its pom.
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123
We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA.
On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future.
> Fixing SWT issues in Luna
> -------------------------
>
> Key: JBIDE-16290
> URL: https://issues.jboss.org/browse/JBIDE-16290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Alpha2
>
> Attachments: Java - Eclipse _001.png, luna-crashing-on-outcomplete.ogv
>
>
> This ticket is meant to list the bugs related to GTK3 affecting JBDS:
> * JBIDE-16280 VPE/XulRunner crashes workbench
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=425692 (Import Existing Maven Project)
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581
> * Central tests uses SWT_GTK3=0 in its pom.
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123
> Some more minor ones:
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=417601
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421834
> We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA.
> On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future.
--
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, 5 months
[JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2874?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2874:
----------------------------------
[~ldimaggio] What do you think about supporting this scenario?
> Support updating JBDS via BYOE (update site) w/o having to update product too
> -----------------------------------------------------------------------------
>
> Key: JBDS-2874
> URL: https://issues.jboss.org/browse/JBDS-2874
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png
>
>
> I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both.
> Do we want this?
--
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, 5 months
[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2635:
----------------------------------
According to the docs [1], dropins is fully supported too, so we could simply unpack the product, then dump the update site within the izpack archive into ~/jbdevstudio-install-folder/studio/dropins/jbds/eclipse/\{plugins,features}/ and everything under there would be found w/o having to do a UI-based p2 install.
[1] http://help.eclipse.org/kepler/topic/org.eclipse.platform.doc.isv/referen...
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {code}
--
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, 5 months