[jbosstools-dev] Do we still need Xulrunner in Devstudio?

[Alexey Kazakov]

Adding jbosstools-dev

Yes, Ilya is correct. We tried to remove VPE and Xulrunner but got 
immediate feedback from users that it's an important feature. Does 
having VPE/Xulrunner in devstudio causes any problem? If so please speak 
up. Otherwise we are planing to continue to include VPE and Xulrunner in 
JBossTools/devstudio.

Thanks.


On 09/28/2016 09:22 AM, Ilya Buziuk wrote:
> CC: Max Andersen & Alexey Kazakov
>
> On Wed, Sep 28, 2016 at 6:19 PM, Ilya Buziuk <ibuziuk at redhat.com 
> <mailto:ibuziuk at redhat.com>> wrote:
>
>     Actually, we planned to remove xulrunner and deprecate VPE some
>     time ago and leave only VPV as a WYSIWYG html editor. However, as
>     soon as we gave a shout out about this on tools.jboss.org
>     <http://tools.jboss.org> the first comment was:
>
>         Nice. The reason I used JBoss Tools was the Visual Editor for
>         JSF, especially for the Visual parts, which was not perfect
>         but was good enough to have it. Will you have alternatives for
>         that ? [1]
>
>
>     It was decided that we need to slow down with this process. I can
>     not say if it is a high time for doing this assuming that some
>     people actually use it. Furthermore, some people treat it as a
>     killer feature for JSF that only one IDE is providing. So, we need
>     to think twice before doing it.
>
>      [1]
>     http://tools.jboss.org/blog/2015-04-02-devstudio-8.1.0.GA-for-luna.html
>     <http://tools.jboss.org/blog/2015-04-02-devstudio-8.1.0.GA-for-luna.html>
>
>     On Wed, Sep 28, 2016 at 5:40 PM, Nick Boldt <nboldt at redhat.com
>     <mailto:nboldt at redhat.com>> wrote:
>
>         On the Eclipse team call today, the question of why we need
>         Xulrunner
>         was brought up again.
>
>         As I understand it, the only reason we still include Xulrunner
>         is for
>         the Visual Page Editor. But Alex pointed out today that
>         Xulrunner only
>         works on GTK2, which means a user has to explicity disable GTK3 in
>         order for Xulrunner to be used, as these days GTK3 is the
>         default OOTB
>         implementation on the platforms we support (Fedora 24/25, RHEL7,
>         etc.).
>
>         So... is it time to remove Xulrunner from the Devstudio
>         dependencies,
>         if most people are not even seeing it used?
>
>         Alex suggested it might be useful to set up a call to discuss
>         this in
>         more depth. Is there a good time tomorrow or Friday you guys would
>         like to meet to discuss this, if it can't be resolved
>         asynchronously
>         via email?
>
>         Whatever we decide here, we should make sure we announce this
>         on the
>         jbosstools-dev@ list.
>
>         --
>         Nick Boldt :: JBoss by Red Hat
>         Productization Lead :: JBoss Tools & Dev Studio
>         http://nick.divbyzero.com
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160928/ac05d799/attachment-0001.html