You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Christofer Dutz <ch...@c-ware.de> on 2022/10/24 14:06:48 UTC
[DISCUSS] Change the UI framework for the GUI application
Hi all,
today we noticed that JavaXF is GPL 2.0 (With classpath exception) licensed.
As we don’t want to jump through all the hoops needed to release this in an Apache project, we are planning on switching the UI framework we are basing everything on.
Any suggestions?
We also might consider building a Web-based application instead … personally I’m open to all.
However, I would really like feedback that’s not based on having heard something is cool but having first-hand experience with it. And even better if you’re willing to help execute the migration.
Chris
Re: [DISCUSS] Change the UI framework for the GUI application
Posted by Ben Hutcheson <be...@gmail.com>.
Hi Dominik,
That would certainly be interesting.
I started to briefly look into GraphQL for the OPC-UA server. I'll have a
bit more of a look this week and we can build upon it afterwards.
Ben
On Tue, Oct 25, 2022 at 12:54 PM Dominik Riemer <ri...@fzi.de> wrote:
> Hi,
>
> in case we choose Angular as the random front end, I'd also be willing to
> help whenever I find some time! It could also be interesting to configure
> the Web UI for microfrontend integration, e.g., to integrate the GUI into
> StreamPipes 😉
>
> Dominik
>
>
> -----Original Message-----
> From: Ben Hutcheson <be...@gmail.com>
> Sent: Tuesday, October 25, 2022 8:45 PM
> To: dev@plc4x.apache.org
> Subject: Re: [DISCUSS] Change the UI framework for the GUI application
>
> I think I'm going to hijack Lukas' comment about using electron from a
> previous post.
>
> I'm interested in building a GUI for the OPC-UA server with GraphQL and
> [insert some random front end] and having a common api would be really cool.
>
> Plus there seems to be a lot more selection when you get out of the Java
> community.
>
> On Mon, Oct 24, 2022 at 9:42 AM Łukasz Dywicki <lu...@code-house.org>
> wrote:
>
> > It's pity that javafx has this trouble. We are compiling our code
> > against java standard library which is *the* same license. Yet, we do
> > not distribute standard library, but we would need to distribute
> > javafx binaries and construct executable form in a proper way. I do
> > not insist on staying with javafx but I think it is easiest for
> > developer experience, given quick win Chris had there. Why not letting
> > ASF LEGAL sorting this stuff for us, given that ISIS, Netbeans, Sis
> > and others still use it?
> >
> > I used swing and swt with jface a long time ago. Swing was a bit of
> > pain due to limited set of widgets, swt was pain due to native library
> > handling. Some parts of jface are emulated, if platform does not have
> > corresponding widget ie. tree table.
> > I guess we won't have a perfect match any more. We can't do qt,
> > wxwidgets have custom license too, text ui might be too hard for end
> > users. With regard to netbeans it gives us some infrastructure, but it
> > is essentially a swing with all its shine and shadows. :/
> >
> > I looked for swt sources to see how active its development is, and it
> > seems to be maintained:
> > https://git.eclipse.org/r/plugins/gitiles/platform/eclipse.platform.sw
> > t/ yet eclipse project page indicates "archived" status. [1] (its
> > probably merged with other project) Its binaries should be possible to
> > fetch via maven repositories. I also found another animal called XWT
> > which is a declarative UI approach similar to fxml:
> > https://wiki.eclipse.org/XWT_Documentation, however this one is based
> > on P2 so it does not usable maven poms.
> > As far I recall Eclipse folks were debating how to approach P2-maven
> > repository ecosystem integration for years already, so I do not expect
> > any quick resolution here.
> >
> > Best,
> > Łukasz
> >
> > [1]
> > https://projects.eclipse.org/projects/eclipse.platform.swt/developer
> >
> > On 24.10.2022 17:03, Cesar Garcia wrote:
> > > Hello,
> > >
> > > Netbeans, all in one place.
> > >
> > > 1. Easy integration of libraries,
> > > 2. Graphical interface based on the venerable and stable Swing.
> > > 3. Graphing tools already available.
> > >
> > > and much more.
> > >
> > > Against, the learning curve.
> > >
> > > I'm already over it
> > >
> > > best regards,
> > >
> > > El lun, 24 oct 2022 a las 10:07, Christofer Dutz (<
> > christofer.dutz@c-ware.de>)
> > > escribió:
> > >
> > >> Hi all,
> > >>
> > >> today we noticed that JavaXF is GPL 2.0 (With classpath exception)
> > >> licensed.
> > >>
> > >> As we don’t want to jump through all the hoops needed to release
> > >> this in an Apache project, we are planning on switching the UI
> > >> framework we are basing everything on.
> > >>
> > >> Any suggestions?
> > >>
> > >> We also might consider building a Web-based application instead …
> > >> personally I’m open to all.
> > >>
> > >> However, I would really like feedback that’s not based on having
> > >> heard something is cool but having first-hand experience with it.
> > >> And even
> > better
> > >> if you’re willing to help execute the migration.
> > >>
> > >> Chris
> > >>
> > >
> > >
> >
>
RE: [DISCUSS] Change the UI framework for the GUI application
Posted by Dominik Riemer <ri...@fzi.de>.
Hi,
in case we choose Angular as the random front end, I'd also be willing to help whenever I find some time! It could also be interesting to configure the Web UI for microfrontend integration, e.g., to integrate the GUI into StreamPipes 😉
Dominik
-----Original Message-----
From: Ben Hutcheson <be...@gmail.com>
Sent: Tuesday, October 25, 2022 8:45 PM
To: dev@plc4x.apache.org
Subject: Re: [DISCUSS] Change the UI framework for the GUI application
I think I'm going to hijack Lukas' comment about using electron from a previous post.
I'm interested in building a GUI for the OPC-UA server with GraphQL and [insert some random front end] and having a common api would be really cool.
Plus there seems to be a lot more selection when you get out of the Java community.
On Mon, Oct 24, 2022 at 9:42 AM Łukasz Dywicki <lu...@code-house.org> wrote:
> It's pity that javafx has this trouble. We are compiling our code
> against java standard library which is *the* same license. Yet, we do
> not distribute standard library, but we would need to distribute
> javafx binaries and construct executable form in a proper way. I do
> not insist on staying with javafx but I think it is easiest for
> developer experience, given quick win Chris had there. Why not letting
> ASF LEGAL sorting this stuff for us, given that ISIS, Netbeans, Sis
> and others still use it?
>
> I used swing and swt with jface a long time ago. Swing was a bit of
> pain due to limited set of widgets, swt was pain due to native library
> handling. Some parts of jface are emulated, if platform does not have
> corresponding widget ie. tree table.
> I guess we won't have a perfect match any more. We can't do qt,
> wxwidgets have custom license too, text ui might be too hard for end
> users. With regard to netbeans it gives us some infrastructure, but it
> is essentially a swing with all its shine and shadows. :/
>
> I looked for swt sources to see how active its development is, and it
> seems to be maintained:
> https://git.eclipse.org/r/plugins/gitiles/platform/eclipse.platform.sw
> t/ yet eclipse project page indicates "archived" status. [1] (its
> probably merged with other project) Its binaries should be possible to
> fetch via maven repositories. I also found another animal called XWT
> which is a declarative UI approach similar to fxml:
> https://wiki.eclipse.org/XWT_Documentation, however this one is based
> on P2 so it does not usable maven poms.
> As far I recall Eclipse folks were debating how to approach P2-maven
> repository ecosystem integration for years already, so I do not expect
> any quick resolution here.
>
> Best,
> Łukasz
>
> [1]
> https://projects.eclipse.org/projects/eclipse.platform.swt/developer
>
> On 24.10.2022 17:03, Cesar Garcia wrote:
> > Hello,
> >
> > Netbeans, all in one place.
> >
> > 1. Easy integration of libraries,
> > 2. Graphical interface based on the venerable and stable Swing.
> > 3. Graphing tools already available.
> >
> > and much more.
> >
> > Against, the learning curve.
> >
> > I'm already over it
> >
> > best regards,
> >
> > El lun, 24 oct 2022 a las 10:07, Christofer Dutz (<
> christofer.dutz@c-ware.de>)
> > escribió:
> >
> >> Hi all,
> >>
> >> today we noticed that JavaXF is GPL 2.0 (With classpath exception)
> >> licensed.
> >>
> >> As we don’t want to jump through all the hoops needed to release
> >> this in an Apache project, we are planning on switching the UI
> >> framework we are basing everything on.
> >>
> >> Any suggestions?
> >>
> >> We also might consider building a Web-based application instead …
> >> personally I’m open to all.
> >>
> >> However, I would really like feedback that’s not based on having
> >> heard something is cool but having first-hand experience with it.
> >> And even
> better
> >> if you’re willing to help execute the migration.
> >>
> >> Chris
> >>
> >
> >
>
Re: [DISCUSS] Change the UI framework for the GUI application
Posted by Ben Hutcheson <be...@gmail.com>.
I think I'm going to hijack Lukas' comment about using electron from a
previous post.
I'm interested in building a GUI for the OPC-UA server with GraphQL and
[insert some random front end] and having a common api would be really cool.
Plus there seems to be a lot more selection when you get out of the Java
community.
On Mon, Oct 24, 2022 at 9:42 AM Łukasz Dywicki <lu...@code-house.org> wrote:
> It's pity that javafx has this trouble. We are compiling our code
> against java standard library which is *the* same license. Yet, we do
> not distribute standard library, but we would need to distribute javafx
> binaries and construct executable form in a proper way. I do not insist
> on staying with javafx but I think it is easiest for developer
> experience, given quick win Chris had there. Why not letting ASF LEGAL
> sorting this stuff for us, given that ISIS, Netbeans, Sis and others
> still use it?
>
> I used swing and swt with jface a long time ago. Swing was a bit of pain
> due to limited set of widgets, swt was pain due to native library
> handling. Some parts of jface are emulated, if platform does not have
> corresponding widget ie. tree table.
> I guess we won't have a perfect match any more. We can't do qt,
> wxwidgets have custom license too, text ui might be too hard for end
> users. With regard to netbeans it gives us some infrastructure, but it
> is essentially a swing with all its shine and shadows. :/
>
> I looked for swt sources to see how active its development is, and it
> seems to be maintained:
> https://git.eclipse.org/r/plugins/gitiles/platform/eclipse.platform.swt/
> yet eclipse project page indicates "archived" status. [1] (its probably
> merged with other project)
> Its binaries should be possible to fetch via maven repositories. I also
> found another animal called XWT which is a declarative UI approach
> similar to fxml: https://wiki.eclipse.org/XWT_Documentation, however
> this one is based on P2 so it does not usable maven poms.
> As far I recall Eclipse folks were debating how to approach P2-maven
> repository ecosystem integration for years already, so I do not expect
> any quick resolution here.
>
> Best,
> Łukasz
>
> [1] https://projects.eclipse.org/projects/eclipse.platform.swt/developer
>
> On 24.10.2022 17:03, Cesar Garcia wrote:
> > Hello,
> >
> > Netbeans, all in one place.
> >
> > 1. Easy integration of libraries,
> > 2. Graphical interface based on the venerable and stable Swing.
> > 3. Graphing tools already available.
> >
> > and much more.
> >
> > Against, the learning curve.
> >
> > I'm already over it
> >
> > best regards,
> >
> > El lun, 24 oct 2022 a las 10:07, Christofer Dutz (<
> christofer.dutz@c-ware.de>)
> > escribió:
> >
> >> Hi all,
> >>
> >> today we noticed that JavaXF is GPL 2.0 (With classpath exception)
> >> licensed.
> >>
> >> As we don’t want to jump through all the hoops needed to release this in
> >> an Apache project, we are planning on switching the UI framework we are
> >> basing everything on.
> >>
> >> Any suggestions?
> >>
> >> We also might consider building a Web-based application instead …
> >> personally I’m open to all.
> >>
> >> However, I would really like feedback that’s not based on having heard
> >> something is cool but having first-hand experience with it. And even
> better
> >> if you’re willing to help execute the migration.
> >>
> >> Chris
> >>
> >
> >
>
Re: [DISCUSS] Change the UI framework for the GUI application
Posted by Łukasz Dywicki <lu...@code-house.org>.
It's pity that javafx has this trouble. We are compiling our code
against java standard library which is *the* same license. Yet, we do
not distribute standard library, but we would need to distribute javafx
binaries and construct executable form in a proper way. I do not insist
on staying with javafx but I think it is easiest for developer
experience, given quick win Chris had there. Why not letting ASF LEGAL
sorting this stuff for us, given that ISIS, Netbeans, Sis and others
still use it?
I used swing and swt with jface a long time ago. Swing was a bit of pain
due to limited set of widgets, swt was pain due to native library
handling. Some parts of jface are emulated, if platform does not have
corresponding widget ie. tree table.
I guess we won't have a perfect match any more. We can't do qt,
wxwidgets have custom license too, text ui might be too hard for end
users. With regard to netbeans it gives us some infrastructure, but it
is essentially a swing with all its shine and shadows. :/
I looked for swt sources to see how active its development is, and it
seems to be maintained:
https://git.eclipse.org/r/plugins/gitiles/platform/eclipse.platform.swt/
yet eclipse project page indicates "archived" status. [1] (its probably
merged with other project)
Its binaries should be possible to fetch via maven repositories. I also
found another animal called XWT which is a declarative UI approach
similar to fxml: https://wiki.eclipse.org/XWT_Documentation, however
this one is based on P2 so it does not usable maven poms.
As far I recall Eclipse folks were debating how to approach P2-maven
repository ecosystem integration for years already, so I do not expect
any quick resolution here.
Best,
Łukasz
[1] https://projects.eclipse.org/projects/eclipse.platform.swt/developer
On 24.10.2022 17:03, Cesar Garcia wrote:
> Hello,
>
> Netbeans, all in one place.
>
> 1. Easy integration of libraries,
> 2. Graphical interface based on the venerable and stable Swing.
> 3. Graphing tools already available.
>
> and much more.
>
> Against, the learning curve.
>
> I'm already over it
>
> best regards,
>
> El lun, 24 oct 2022 a las 10:07, Christofer Dutz (<ch...@c-ware.de>)
> escribió:
>
>> Hi all,
>>
>> today we noticed that JavaXF is GPL 2.0 (With classpath exception)
>> licensed.
>>
>> As we don’t want to jump through all the hoops needed to release this in
>> an Apache project, we are planning on switching the UI framework we are
>> basing everything on.
>>
>> Any suggestions?
>>
>> We also might consider building a Web-based application instead …
>> personally I’m open to all.
>>
>> However, I would really like feedback that’s not based on having heard
>> something is cool but having first-hand experience with it. And even better
>> if you’re willing to help execute the migration.
>>
>> Chris
>>
>
>
Re: [DISCUSS] Change the UI framework for the GUI application
Posted by Cesar Garcia <ce...@ceos.com.ve>.
Hello,
Netbeans, all in one place.
1. Easy integration of libraries,
2. Graphical interface based on the venerable and stable Swing.
3. Graphing tools already available.
and much more.
Against, the learning curve.
I'm already over it
best regards,
El lun, 24 oct 2022 a las 10:07, Christofer Dutz (<ch...@c-ware.de>)
escribió:
> Hi all,
>
> today we noticed that JavaXF is GPL 2.0 (With classpath exception)
> licensed.
>
> As we don’t want to jump through all the hoops needed to release this in
> an Apache project, we are planning on switching the UI framework we are
> basing everything on.
>
> Any suggestions?
>
> We also might consider building a Web-based application instead …
> personally I’m open to all.
>
> However, I would really like feedback that’s not based on having heard
> something is cool but having first-hand experience with it. And even better
> if you’re willing to help execute the migration.
>
> Chris
>
--
*CEOS Automatización, C.A.*
*GALPON SERVICIO INDUSTRIALES Y NAVALES FA, C.A.,*
*PISO 1, OFICINA 2, AV. RAUL LEONI, SECTOR GUAMACHITO,*
*FRENTE A LA ASOCIACION DE GANADEROS,BARCELONA,EDO. ANZOATEGUI*
*Ing. César García*
*Cel: +58 414-760.98.95*
*Hotline Técnica SIEMENS: 0800 1005080*
*Email: support.aan.automation@siemens.com
<su...@siemens.com>*