date:20240321

Re: AW: So when do we want to meet on Saturday?

2024-03-21 Thread Julian Feinauer

Why do all of you hate sleep? 樂

On 2024/03/18 09:51:50 Sebastian Rühl wrote:
> 11 sounds good
> 
> - Sebastian
> 
> On 2024/03/18 09:48:04 Christofer Dutz wrote:
> > Hi Lukasz,
> > 
> > Ok … I could have a look and be there some time round 11 AM …
> > 
> > My Toddy shirt is so faded, that you can’t even see it anymore :-(
> > 
> > And with bringing stuff … I’m a bit torn … I could load up my car with all 
> > the stuff I have (Except the big Factory).
> > But then there’s no beer for me at the hackathon.
> > 
> > But on the other side we actually only need a hand full of devices, right?
> > They should fit in a bag.
> > 
> > Chris
> > 
> > 
> > 
> > 
> > Von: Łukasz Dywicki 
> > Datum: Montag, 18. März 2024 um 10:30
> > An: dev@plc4x.apache.org 
> > Betreff: Re: So when do we want to meet on Saturday?
> > If I'm not asleep, I'll land at 09:45. I think it will take me about
> > hour and something to get into downtown.
> > 
> > My other question is - what shall we bring with us, beyond toddy shirts? ;-)
> > 
> > Cheers,
> > Łukasz
> > 
> > On 18.03.2024 09:04, Lukas Ott wrote:
> > > Hi all,
> > >
> > > according to my travel plans.
> > > My train arrives in Frankfurt Main Station at 14:00.
> > > Connection on Sat. 23.03.2024
> > > - from Oerestad st, departure 00:46 Gl. 2 with IC 1401
> > > - to Frankfurt(Main)Hbf, arrival 14:00 Gl. 6 with ICE 75
> > > Verbindung ansehen:
> > > https://www.bahn.de/buchung/start?vbid=c10e14c7-cd2b-4691-90f9-82e504366818
> > >
> > > So I can not join earlier.
> > >
> > > Lukas
> > >
> > >
> > > Am Mo., 18. März 2024 um 08:59 Uhr schrieb Christofer Dutz <
> > > christofer.d...@c-ware.de>:
> > >
> > >> Hi all,
> > >>
> > >> So, when do we want to meet on Saturday?
> > >>
> > >> I would propose something round 13:00 (could also do even earlier)
> > >>
> > >> Chris
> > >>
> > >>
> > >
> > 
>

Re: AW: [DISCUSS] What do we want to look into/talk about on the Meetup/Workshop?

2024-03-21 Thread Cesar Garcia

Hello,

I agree with Lukasz proposal to include OSGi in the discussion as the
runtime.

+1

Specifically, it would be interesting to evaluate the sections

103.- Device Access Specification.
141.- Device Abstraction layer Specification.

Kind regards,

El jue, 21 mar 2024 a las 14:33, Łukasz Dywicki ()
escribió:

> I can add one more:
>
> - Support for OSGi as a potential project runtime.
>
> It is a technology which is still popular for various applications
> running on the edge.
> @Cesar, I know you use it, pulling you into thread so you can also share
> your point in this regard.
>
> I do maintain a separate repository [1] with hand written karaf feature
> sets. I do so to avoid large duplication of dependencies between
> drivers, as generated feature sets are quite dumb.
> I did it initially to make 0.6 and 0.8 release work with openHAB, after
> seeing recent updates from 0.11 release I think we have most of stuff in
> place to make it work.
> One missing concept is a classloader propagation so whole thing would
> work without Aries Spifly in other down stream projects, i.e. openems.
>
> Cheers,
> Łukasz
>
> --
> [1] https://github.com/ConnectorIO/plc4x-extras/
>
> On 21.03.2024 14:39, Christofer Dutz wrote:
> > Possibly worth adding:
> > - Refactor the OPC-UA test-suite to run as Integration-Test in the build
> and to rely on a Milo server started in the pre-integration-test phase and
> which is stopped in the post-integration-test-phase.
> >
> > Von: Lukas Ott 
> > Datum: Montag, 18. März 2024 um 11:51
> > An: dev@plc4x.apache.org 
> > Betreff: Re: [DISCUSS] What do we want to look into/talk about on the
> Meetup/Workshop?
> > Mine are much simpler:
> > - Merge my pull request
> >  * https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes
> with
> > Sebastian.
> > - Go through PLC4PY with Ben and get things running on my side
> >* Add Pip Package to https://pypi.org/ including release integration
> etc.
> >* What is missing for PLC4Py to get out of the sandbox?
> >* Find little tasks where I can start and not overwhelmed as one
> of
> > the rare-non developers in that project.
> > - Look into what you (Chris) did with ReactJS on the UI branch and get
> that
> > running
> >
> > For the rest I am giving a +1 for your points.
> >
> > Lukas
> >
> > Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
> > christofer.d...@c-ware.de>:
> >
> >> Here some things I have on my mind:
> >>
> >>
> >>*   Road to 1.0.0 (What’s still missing?)
> >>*   Generating larger portions of the code (Mesasages &
> Request+Response)
> >>*   Missing features:
> >>   *   Optimizer Framework (Optimize requests, by rewriting them)
> >>   *   Subscription Emulation (General purpose component, that uses
> the
> >> READ api to simulare subscriptions)
> >>   *   New/Advanced Scraper (Rewrite of the Scraper, that allows
> things
> >> like “read, triggered by subscription”)
> >>*   How can we distribute the workload a bit better?
> >>*   How can we grow the community?
> >>
> >> 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.automat...@siemens.com
*

Re: UI Branch

2024-03-21 Thread Cesar Garcia

A few years ago I wrote about that concept,

If you visit the blog, But there are many details. The technologies have
changed, but in general the needs are the same,

http://glcj.blogspot.com/

I should restart the blog,

Best regards,




El jue, 21 mar 2024 a las 12:31,  escribió:

> I see...
>
> Are you sure you wanna go with gRPC or Apache Karaf as Backend? Can you
> elaborate on this? Why not websockets builtin in plc4x?
>
> Best regards
>
> -
> Coding Nexus LLC
> Björn Haverland
> 2880W Oakland Park Blvd
> Suite 225C
> Oakland Park
> 33311 Florida
>
> Tel: +1 954 607 2347
>
> bjo...@coding-nexus.com
> https://www.coding-nexus.com
>
>
> -Ursprüngliche Nachricht-
> Von: Cesar Garcia 
> Gesendet: Donnerstag, 21. März 2024 17:17
> An: dev@plc4x.apache.org
> Betreff: Re: UI Branch
>
> Hello,
>
> I took the flag raised by Chris regarding the UI, and we are evaluating
> the different technologies, the idea is to keep things as simple as
> possible (I think).
>
> For the frontend
>
> 1. qooxdoo.
> 2. Apache Echarts.
>
> For the backend
>
> 3. gRPC
> 4. Apache Karaf (Merlot).
>
> I'm going to try to make a demo for the work team on Saturday, against the
> clock, but I'll do my best.
>
> Kind regards,
>
> El jue, 21 mar 2024 a las 12:07,  escribió:
>
> > I’m splitting the topic, I read something about an UI Branch, where
> > can I find it? Is there a particular reason why ReactJS? What is it
> > supposed to be? A unified UI library for all supported plc?
> >
> > So many questions 
> >
> >
> >
> > I had an idea of using plc4j add a websocket API and use vueJS (I’m
> > using vue in several projects, have only little experience with React)
> > to export a simple UI library. This way a UI would be very portable
> > across many platforms.
> >
> > Is the ReactJS Branch a similar approach?
> >
> >
> >
> > Best regards
> >
> >
> >
> > Björn
> >
> >
> >
> >
> >
> > Gesendet von Outlook für Android 
> >
> >   _
> >
> > From: Christofer Dutz 
> > Sent: Thursday, March 21, 2024 1:39:11 PM
> > To: dev@plc4x.apache.org 
> > Subject: AW: [DISCUSS] What do we want to look into/talk about on the
> > Meetup/Workshop?
> >
> >
> >
> > Possibly worth adding:
> > - Refactor the OPC-UA test-suite to run as Integration-Test in the
> > build and to rely on a Milo server started in the pre-integration-test
> > phase and which is stopped in the post-integration-test-phase.
> >
> > Von: Lukas Ott 
> > Datum: Montag, 18. März 2024 um 11:51
> > An: dev@plc4x.apache.org 
> > Betreff: Re: [DISCUSS] What do we want to look into/talk about on the
> > Meetup/Workshop?
> > Mine are much simpler:
> > - Merge my pull request
> > *  
> > https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with
> > Sebastian.
> > - Go through PLC4PY with Ben and get things running on my side
> >   * Add Pip Package to   https://pypi.org/
> > including release integration etc.
> >   * What is missing for PLC4Py to get out of the sandbox?
> >   * Find little tasks where I can start and not overwhelmed as one
> > of the rare-non developers in that project.
> > - Look into what you (Chris) did with ReactJS on the UI branch and get
> > that running
> >
> > For the rest I am giving a +1 for your points.
> >
> > Lukas
> >
> > Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
> > christofer.d...@c-ware.de>:
> >
> > > Here some things I have on my mind:
> > >
> > >
> > >   *   Road to 1.0.0 (What’s still missing?)
> > >   *   Generating larger portions of the code (Mesasages &
> > Request+Response)
> > >   *   Missing features:
> > >  *   Optimizer Framework (Optimize requests, by rewriting them)
> > >  *   Subscription Emulation (General purpose component, that uses
> the
> > > READ api to simulare subscriptions)
> > >  *   New/Advanced Scraper (Rewrite of the Scraper, that allows
> things
> > > like “read, triggered by subscription”)
> > >   *   How can we distribute the workload a bit better?
> > >   *   How can we grow the community?
> > >
> > > 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.automat...@siemens.com
> *
>
>

-- 
*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.automat...@siemens.com
*

Re: AW: UI Branch

2024-03-21 Thread Björn Haverland

Ok, well all of this are a bit more bound to certain projects. But you are 
right it all depends on the goal one would chase. open HAB for example would be 
a good choice for HomeAutomation projects, but not that suitable for 
manufacturing appliances.
I just thought of maintaining the server part( websockets, available on python, 
c#, java, etc.) within the project, maybe implemented as a driver. That would 
give an user a powerful tool where he can extend his programm with an UI. With 
this option the frontend again is at users choice.

Gesendet von Outlook für Android

From: Łukasz Dywicki 
Sent: Thursday, March 21, 2024 5:08:24 PM
To: dev@plc4x.apache.org 
Subject: Re: AW: UI Branch

I can throw in one more option - openHAB on top of apache karaf. :)
Its more a question about what you are trying to build. There are
several approaches out there. openHAB is one, merlot is second, eclipse
kura is third, openMUC or amplia-iiot (oda) or openems is yet another
one. Real question is what kind application/system you wish to bring and
how it differs from others.

I could see also other architecture which would involve websockets, but
with clean structures defined via i.e. graphql schema. I've made some
experiments with later one combined with react, to see how hard it works
together.

Currently I have built amsads and s7 bindings on top of plc4j APIs:
https://docs.connectorio.com/connectorio-addons/3.0.x/index.html

Sources:
https://github.com/connectorio/connectorio-addons

Binaries:
https://repository.connectorio.cloud/#browse/browse:co7io-public-snapshots:org%2Fconnectorio%2Faddons

Cheers,
Łukasz

On 21.03.2024 17:30, bjo...@coding-nexus.com wrote:
> I see...
>
> Are you sure you wanna go with gRPC or Apache Karaf as Backend? Can you 
> elaborate on this? Why not websockets builtin in plc4x?
>
> Best regards
>
> -
> Coding Nexus LLC
> Björn Haverland
> 2880W Oakland Park Blvd
> Suite 225C
> Oakland Park
> 33311 Florida
>
> Tel: +1 954 607 2347
>
> bjo...@coding-nexus.com
> https://www.coding-nexus.com
>
>
> -Ursprüngliche Nachricht-
> Von: Cesar Garcia 
> Gesendet: Donnerstag, 21. März 2024 17:17
> An: dev@plc4x.apache.org
> Betreff: Re: UI Branch
>
> Hello,
>
> I took the flag raised by Chris regarding the UI, and we are evaluating the 
> different technologies, the idea is to keep things as simple as possible (I 
> think).
>
> For the frontend
>
> 1. qooxdoo.
> 2. Apache Echarts.
>
> For the backend
>
> 3. gRPC
> 4. Apache Karaf (Merlot).
>
> I'm going to try to make a demo for the work team on Saturday, against the 
> clock, but I'll do my best.
>
> Kind regards,
>
> El jue, 21 mar 2024 a las 12:07,  escribió:
>
>> I’m splitting the topic, I read something about an UI Branch, where
>> can I find it? Is there a particular reason why ReactJS? What is it
>> supposed to be? A unified UI library for all supported plc?
>>
>> So many questions 
>>
>>
>>
>> I had an idea of using plc4j add a websocket API and use vueJS (I’m
>> using vue in several projects, have only little experience with React)
>> to export a simple UI library. This way a UI would be very portable
>> across many platforms.
>>
>> Is the ReactJS Branch a similar approach?
>>
>>
>>
>> Best regards
>>
>>
>>
>> Björn
>>
>>
>>
>>
>>
>> Gesendet von Outlook für Android 
>>
>>_
>>
>> From: Christofer Dutz 
>> Sent: Thursday, March 21, 2024 1:39:11 PM
>> To: dev@plc4x.apache.org 
>> Subject: AW: [DISCUSS] What do we want to look into/talk about on the
>> Meetup/Workshop?
>>
>>
>>
>> Possibly worth adding:
>> - Refactor the OPC-UA test-suite to run as Integration-Test in the
>> build and to rely on a Milo server started in the pre-integration-test
>> phase and which is stopped in the post-integration-test-phase.
>>
>> Von: Lukas Ott 
>> Datum: Montag, 18. März 2024 um 11:51
>> An: dev@plc4x.apache.org 
>> Betreff: Re: [DISCUSS] What do we want to look into/talk about on the
>> Meetup/Workshop?
>> Mine are much simpler:
>> - Merge my pull request
>>  *  
>> https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with
>> Sebastian.
>> - Go through PLC4PY with Ben and get things running on my side
>>* Add Pip Package to   https://pypi.org/
>> including release integration etc.
>>* What is missing for PLC4Py to get out of the sandbox?
>>* Find little tasks where I can start and not overwhelmed as one
>> of the rare-non developers in that project.
>> - Look into what you (Chris) did with ReactJS on the UI branch and get
>> that running
>>
>> For the rest I am giving a +1 for your points.
>>
>> Lukas
>>
>> Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
>> christofer.d...@c-ware.de>:
>>
>>> Here some things I have on my mind:
>>>
>>>
>>>*   Road to 1.0.0 (What’s still missing?)
>>>*

Re: [DISCUSS] Fix or disable some flaky OPC-UA tests?

2024-03-21 Thread Łukasz Dywicki


Chris,
If you can, please drop links to failed agent executions into this 
thread or github discussion/issue. I'll look at them.
Currently we have a bunch of github actions executed within each build, 
it is quite hard for me to track every failure caused by opcua tests. If 
we will aggregate few in one place I'll look at cause and possible 
solutions.


Best,
Łukasz

On 18.03.2024 13:33, Christofer Dutz wrote:

Hi all,

having a look at the latest builds, it shows that some of the OPC-UA tests are 
continuing to be super-flaky … they fail in one build and in anoter others fail.

I would like to see our build on develop become stable and not a gamble.

So, if someone could have a look at these tests and why they have been failing, 
that would be great:


   *   ChunkFactoryTest
   *   OpcuaSubscriptionHandleTest


Otherwise, I’ll simply add a “skip” or “disable” to them in a week or so. I’ve 
invested such an enormous amount of time into trying to find issues in the 
OPC-UA testsuite over the last years, that I consider my fuel-tank for OPC-UA 
issues empty.

Chris

Re: AW: [DISCUSS] What do we want to look into/talk about on the Meetup/Workshop?

2024-03-21 Thread Łukasz Dywicki


I can add one more:

- Support for OSGi as a potential project runtime.

It is a technology which is still popular for various applications 
running on the edge.
@Cesar, I know you use it, pulling you into thread so you can also share 
your point in this regard.


I do maintain a separate repository [1] with hand written karaf feature 
sets. I do so to avoid large duplication of dependencies between 
drivers, as generated feature sets are quite dumb.
I did it initially to make 0.6 and 0.8 release work with openHAB, after 
seeing recent updates from 0.11 release I think we have most of stuff in 
place to make it work.
One missing concept is a classloader propagation so whole thing would 
work without Aries Spifly in other down stream projects, i.e. openems.


Cheers,
Łukasz

--
[1] https://github.com/ConnectorIO/plc4x-extras/

On 21.03.2024 14:39, Christofer Dutz wrote:

Possibly worth adding:
- Refactor the OPC-UA test-suite to run as Integration-Test in the build and to 
rely on a Milo server started in the pre-integration-test phase and which is 
stopped in the post-integration-test-phase.

Von: Lukas Ott 
Datum: Montag, 18. März 2024 um 11:51
An: dev@plc4x.apache.org 
Betreff: Re: [DISCUSS] What do we want to look into/talk about on the 
Meetup/Workshop?
Mine are much simpler:
- Merge my pull request
 * https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with
Sebastian.
- Go through PLC4PY with Ben and get things running on my side
   * Add Pip Package to https://pypi.org/ including release integration etc.
   * What is missing for PLC4Py to get out of the sandbox?
   * Find little tasks where I can start and not overwhelmed as one of
the rare-non developers in that project.
- Look into what you (Chris) did with ReactJS on the UI branch and get that
running

For the rest I am giving a +1 for your points.

Lukas

Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:


Here some things I have on my mind:


   *   Road to 1.0.0 (What’s still missing?)
   *   Generating larger portions of the code (Mesasages & Request+Response)
   *   Missing features:
  *   Optimizer Framework (Optimize requests, by rewriting them)
  *   Subscription Emulation (General purpose component, that uses the
READ api to simulare subscriptions)
  *   New/Advanced Scraper (Rewrite of the Scraper, that allows things
like “read, triggered by subscription”)
   *   How can we distribute the workload a bit better?
   *   How can we grow the community?

Chris

Re: AW: UI Branch

2024-03-21 Thread Łukasz Dywicki


I can throw in one more option - openHAB on top of apache karaf. :)
Its more a question about what you are trying to build. There are 
several approaches out there. openHAB is one, merlot is second, eclipse 
kura is third, openMUC or amplia-iiot (oda) or openems is yet another 
one. Real question is what kind application/system you wish to bring and 
how it differs from others.


I could see also other architecture which would involve websockets, but 
with clean structures defined via i.e. graphql schema. I've made some 
experiments with later one combined with react, to see how hard it works 
together.


Currently I have built amsads and s7 bindings on top of plc4j APIs:
https://docs.connectorio.com/connectorio-addons/3.0.x/index.html

Sources:
https://github.com/connectorio/connectorio-addons

Binaries:
https://repository.connectorio.cloud/#browse/browse:co7io-public-snapshots:org%2Fconnectorio%2Faddons

Cheers,
Łukasz

On 21.03.2024 17:30, bjo...@coding-nexus.com wrote:

I see...

Are you sure you wanna go with gRPC or Apache Karaf as Backend? Can you 
elaborate on this? Why not websockets builtin in plc4x?

Best regards

-
Coding Nexus LLC
Björn Haverland
2880W Oakland Park Blvd
Suite 225C
Oakland Park
33311 Florida
  
Tel: +1 954 607 2347
  
bjo...@coding-nexus.com

https://www.coding-nexus.com
  


-Ursprüngliche Nachricht-
Von: Cesar Garcia 
Gesendet: Donnerstag, 21. März 2024 17:17
An: dev@plc4x.apache.org
Betreff: Re: UI Branch

Hello,

I took the flag raised by Chris regarding the UI, and we are evaluating the 
different technologies, the idea is to keep things as simple as possible (I 
think).

For the frontend

1. qooxdoo.
2. Apache Echarts.

For the backend

3. gRPC
4. Apache Karaf (Merlot).

I'm going to try to make a demo for the work team on Saturday, against the 
clock, but I'll do my best.

Kind regards,

El jue, 21 mar 2024 a las 12:07,  escribió:


I’m splitting the topic, I read something about an UI Branch, where
can I find it? Is there a particular reason why ReactJS? What is it
supposed to be? A unified UI library for all supported plc?

So many questions 



I had an idea of using plc4j add a websocket API and use vueJS (I’m
using vue in several projects, have only little experience with React)
to export a simple UI library. This way a UI would be very portable
across many platforms.

Is the ReactJS Branch a similar approach?



Best regards



Björn





Gesendet von Outlook für Android 

   _

From: Christofer Dutz 
Sent: Thursday, March 21, 2024 1:39:11 PM
To: dev@plc4x.apache.org 
Subject: AW: [DISCUSS] What do we want to look into/talk about on the
Meetup/Workshop?



Possibly worth adding:
- Refactor the OPC-UA test-suite to run as Integration-Test in the
build and to rely on a Milo server started in the pre-integration-test
phase and which is stopped in the post-integration-test-phase.

Von: Lukas Ott 
Datum: Montag, 18. März 2024 um 11:51
An: dev@plc4x.apache.org 
Betreff: Re: [DISCUSS] What do we want to look into/talk about on the
Meetup/Workshop?
Mine are much simpler:
- Merge my pull request
 *  
https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with
Sebastian.
- Go through PLC4PY with Ben and get things running on my side
   * Add Pip Package to   https://pypi.org/
including release integration etc.
   * What is missing for PLC4Py to get out of the sandbox?
   * Find little tasks where I can start and not overwhelmed as one
of the rare-non developers in that project.
- Look into what you (Chris) did with ReactJS on the UI branch and get
that running

For the rest I am giving a +1 for your points.

Lukas

Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:


Here some things I have on my mind:


   *   Road to 1.0.0 (What’s still missing?)
   *   Generating larger portions of the code (Mesasages &

Request+Response)

   *   Missing features:
  *   Optimizer Framework (Optimize requests, by rewriting them)
  *   Subscription Emulation (General purpose component, that uses the
READ api to simulare subscriptions)
  *   New/Advanced Scraper (Rewrite of the Scraper, that allows things
like “read, triggered by subscription”)
   *   How can we distribute the workload a bit better?
   *   How can we grow the community?

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.automat...@siemens.com
*

AW: UI Branch

2024-03-21 Thread bjoern

I see... 

Are you sure you wanna go with gRPC or Apache Karaf as Backend? Can you 
elaborate on this? Why not websockets builtin in plc4x? 

Best regards

-
Coding Nexus LLC
Björn Haverland
2880W Oakland Park Blvd
Suite 225C
Oakland Park
33311 Florida
 
Tel: +1 954 607 2347
 
bjo...@coding-nexus.com
https://www.coding-nexus.com
 

-Ursprüngliche Nachricht-
Von: Cesar Garcia  
Gesendet: Donnerstag, 21. März 2024 17:17
An: dev@plc4x.apache.org
Betreff: Re: UI Branch

Hello,

I took the flag raised by Chris regarding the UI, and we are evaluating the 
different technologies, the idea is to keep things as simple as possible (I 
think).

For the frontend

1. qooxdoo.
2. Apache Echarts.

For the backend

3. gRPC
4. Apache Karaf (Merlot).

I'm going to try to make a demo for the work team on Saturday, against the 
clock, but I'll do my best.

Kind regards,

El jue, 21 mar 2024 a las 12:07,  escribió:

> I’m splitting the topic, I read something about an UI Branch, where 
> can I find it? Is there a particular reason why ReactJS? What is it 
> supposed to be? A unified UI library for all supported plc?
>
> So many questions 
>
>
>
> I had an idea of using plc4j add a websocket API and use vueJS (I’m 
> using vue in several projects, have only little experience with React) 
> to export a simple UI library. This way a UI would be very portable 
> across many platforms.
>
> Is the ReactJS Branch a similar approach?
>
>
>
> Best regards
>
>
>
> Björn
>
>
>
>
>
> Gesendet von Outlook für Android 
>
>   _
>
> From: Christofer Dutz 
> Sent: Thursday, March 21, 2024 1:39:11 PM
> To: dev@plc4x.apache.org 
> Subject: AW: [DISCUSS] What do we want to look into/talk about on the 
> Meetup/Workshop?
>
>
>
> Possibly worth adding:
> - Refactor the OPC-UA test-suite to run as Integration-Test in the 
> build and to rely on a Milo server started in the pre-integration-test 
> phase and which is stopped in the post-integration-test-phase.
>
> Von: Lukas Ott 
> Datum: Montag, 18. März 2024 um 11:51
> An: dev@plc4x.apache.org 
> Betreff: Re: [DISCUSS] What do we want to look into/talk about on the 
> Meetup/Workshop?
> Mine are much simpler:
> - Merge my pull request
> *  
> https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with 
> Sebastian.
> - Go through PLC4PY with Ben and get things running on my side
>   * Add Pip Package to   https://pypi.org/ 
> including release integration etc.
>   * What is missing for PLC4Py to get out of the sandbox?
>   * Find little tasks where I can start and not overwhelmed as one 
> of the rare-non developers in that project.
> - Look into what you (Chris) did with ReactJS on the UI branch and get 
> that running
>
> For the rest I am giving a +1 for your points.
>
> Lukas
>
> Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
> christofer.d...@c-ware.de>:
>
> > Here some things I have on my mind:
> >
> >
> >   *   Road to 1.0.0 (What’s still missing?)
> >   *   Generating larger portions of the code (Mesasages &
> Request+Response)
> >   *   Missing features:
> >  *   Optimizer Framework (Optimize requests, by rewriting them)
> >  *   Subscription Emulation (General purpose component, that uses the
> > READ api to simulare subscriptions)
> >  *   New/Advanced Scraper (Rewrite of the Scraper, that allows things
> > like “read, triggered by subscription”)
> >   *   How can we distribute the workload a bit better?
> >   *   How can we grow the community?
> >
> > 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.automat...@siemens.com
*

Re: UI Branch

2024-03-21 Thread Cesar Garcia

Hello,

I took the flag raised by Chris regarding the UI, and we are evaluating the
different technologies, the idea is to keep things as simple as possible (I
think).

For the frontend

1. qooxdoo.
2. Apache Echarts.

For the backend

3. gRPC
4. Apache Karaf (Merlot).

I'm going to try to make a demo for the work team on Saturday, against the
clock, but I'll do my best.

Kind regards,

El jue, 21 mar 2024 a las 12:07,  escribió:

> I’m splitting the topic, I read something about an UI Branch, where can I
> find it? Is there a particular reason why ReactJS? What is it supposed to
> be? A unified UI library for all supported plc?
>
> So many questions 
>
>
>
> I had an idea of using plc4j add a websocket API and use vueJS (I’m using
> vue in several projects, have only little experience with React) to export
> a simple UI library. This way a UI would be very portable across many
> platforms.
>
> Is the ReactJS Branch a similar approach?
>
>
>
> Best regards
>
>
>
> Björn
>
>
>
>
>
> Gesendet von Outlook für Android 
>
>   _
>
> From: Christofer Dutz 
> Sent: Thursday, March 21, 2024 1:39:11 PM
> To: dev@plc4x.apache.org 
> Subject: AW: [DISCUSS] What do we want to look into/talk about on the
> Meetup/Workshop?
>
>
>
> Possibly worth adding:
> - Refactor the OPC-UA test-suite to run as Integration-Test in the build
> and to rely on a Milo server started in the pre-integration-test phase and
> which is stopped in the post-integration-test-phase.
>
> Von: Lukas Ott 
> Datum: Montag, 18. März 2024 um 11:51
> An: dev@plc4x.apache.org 
> Betreff: Re: [DISCUSS] What do we want to look into/talk about on the
> Meetup/Workshop?
> Mine are much simpler:
> - Merge my pull request
> *  
> https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with
> Sebastian.
> - Go through PLC4PY with Ben and get things running on my side
>   * Add Pip Package to   https://pypi.org/ including
> release integration etc.
>   * What is missing for PLC4Py to get out of the sandbox?
>   * Find little tasks where I can start and not overwhelmed as one of
> the rare-non developers in that project.
> - Look into what you (Chris) did with ReactJS on the UI branch and get that
> running
>
> For the rest I am giving a +1 for your points.
>
> Lukas
>
> Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
> christofer.d...@c-ware.de>:
>
> > Here some things I have on my mind:
> >
> >
> >   *   Road to 1.0.0 (What’s still missing?)
> >   *   Generating larger portions of the code (Mesasages &
> Request+Response)
> >   *   Missing features:
> >  *   Optimizer Framework (Optimize requests, by rewriting them)
> >  *   Subscription Emulation (General purpose component, that uses the
> > READ api to simulare subscriptions)
> >  *   New/Advanced Scraper (Rewrite of the Scraper, that allows things
> > like “read, triggered by subscription”)
> >   *   How can we distribute the workload a bit better?
> >   *   How can we grow the community?
> >
> > 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.automat...@siemens.com
*

UI Branch

2024-03-21 Thread bjoern

I’m splitting the topic, I read something about an UI Branch, where can I find 
it? Is there a particular reason why ReactJS? What is it supposed to be? A 
unified UI library for all supported plc? 

So many questions 

 

I had an idea of using plc4j add a websocket API and use vueJS (I’m using vue 
in several projects, have only little experience with React) to export a simple 
UI library. This way a UI would be very portable across many platforms.

Is the ReactJS Branch a similar approach?

 

Best regards

 

Björn

 

 

Gesendet von Outlook für Android  

  _  

From: Christofer Dutz 
Sent: Thursday, March 21, 2024 1:39:11 PM
To: dev@plc4x.apache.org 
Subject: AW: [DISCUSS] What do we want to look into/talk about on the 
Meetup/Workshop? 

 

Possibly worth adding:
- Refactor the OPC-UA test-suite to run as Integration-Test in the build and to 
rely on a Milo server started in the pre-integration-test phase and which is 
stopped in the post-integration-test-phase.

Von: Lukas Ott 
Datum: Montag, 18. März 2024 um 11:51
An: dev@plc4x.apache.org 
Betreff: Re: [DISCUSS] What do we want to look into/talk about on the 
Meetup/Workshop?
Mine are much simpler:
- Merge my pull request
*   
https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with
Sebastian.
- Go through PLC4PY with Ben and get things running on my side
  * Add Pip Package to   https://pypi.org/ including release 
integration etc.
  * What is missing for PLC4Py to get out of the sandbox?
  * Find little tasks where I can start and not overwhelmed as one of
the rare-non developers in that project.
- Look into what you (Chris) did with ReactJS on the UI branch and get that
running

For the rest I am giving a +1 for your points.

Lukas

Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Here some things I have on my mind:
>
>
>   *   Road to 1.0.0 (What’s still missing?)
>   *   Generating larger portions of the code (Mesasages & Request+Response)
>   *   Missing features:
>  *   Optimizer Framework (Optimize requests, by rewriting them)
>  *   Subscription Emulation (General purpose component, that uses the
> READ api to simulare subscriptions)
>  *   New/Advanced Scraper (Rewrite of the Scraper, that allows things
> like “read, triggered by subscription”)
>   *   How can we distribute the workload a bit better?
>   *   How can we grow the community?
>
> Chris
>

AW: [DISCUSS] What do we want to look into/talk about on the Meetup/Workshop?

2024-03-21 Thread Christofer Dutz

Possibly worth adding:
- Refactor the OPC-UA test-suite to run as Integration-Test in the build and to 
rely on a Milo server started in the pre-integration-test phase and which is 
stopped in the post-integration-test-phase.

Von: Lukas Ott 
Datum: Montag, 18. März 2024 um 11:51
An: dev@plc4x.apache.org 
Betreff: Re: [DISCUSS] What do we want to look into/talk about on the 
Meetup/Workshop?
Mine are much simpler:
- Merge my pull request
* https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with
Sebastian.
- Go through PLC4PY with Ben and get things running on my side
  * Add Pip Package to https://pypi.org/ including release integration etc.
  * What is missing for PLC4Py to get out of the sandbox?
  * Find little tasks where I can start and not overwhelmed as one of
the rare-non developers in that project.
- Look into what you (Chris) did with ReactJS on the UI branch and get that
running

For the rest I am giving a +1 for your points.

Lukas

Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Here some things I have on my mind:
>
>
>   *   Road to 1.0.0 (What’s still missing?)
>   *   Generating larger portions of the code (Mesasages & Request+Response)
>   *   Missing features:
>  *   Optimizer Framework (Optimize requests, by rewriting them)
>  *   Subscription Emulation (General purpose component, that uses the
> READ api to simulare subscriptions)
>  *   New/Advanced Scraper (Rewrite of the Scraper, that allows things
> like “read, triggered by subscription”)
>   *   How can we distribute the workload a bit better?
>   *   How can we grow the community?
>
> Chris
>

Re: [PR] build(deps): bump com.google.protobuf:protobuf-java from 3.25.3 to 4.26.0

2024-03-21 Thread via GitHub



sruehl closed pull request #1454: build(deps): bump 
com.google.protobuf:protobuf-java from 3.25.3 to 4.26.0
URL: https://github.com/apache/plc4x/pull/1454


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@plc4x.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] build(deps): bump jackson.version from 2.16.1 to 2.17.0

2024-03-21 Thread via GitHub



sruehl closed pull request #1458: build(deps): bump jackson.version from 2.16.1 
to 2.17.0
URL: https://github.com/apache/plc4x/pull/1458


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@plc4x.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] build(deps): bump org.codehaus.plexus:plexus-compiler-eclipse from 2.13.0 to 2.15.0

2024-03-21 Thread via GitHub



sruehl closed pull request #1459: build(deps): bump 
org.codehaus.plexus:plexus-compiler-eclipse from 2.13.0 to 2.15.0
URL: https://github.com/apache/plc4x/pull/1459


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@plc4x.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: AW: So when do we want to meet on Saturday?

Re: AW: [DISCUSS] What do we want to look into/talk about on the Meetup/Workshop?

Re: UI Branch

Re: AW: UI Branch

Re: [DISCUSS] Fix or disable some flaky OPC-UA tests?

Re: AW: [DISCUSS] What do we want to look into/talk about on the Meetup/Workshop?

Re: AW: UI Branch

AW: UI Branch

Re: UI Branch

UI Branch

AW: [DISCUSS] What do we want to look into/talk about on the Meetup/Workshop?

Re: [PR] build(deps): bump com.google.protobuf:protobuf-java from 3.25.3 to 4.26.0

Re: [PR] build(deps): bump jackson.version from 2.16.1 to 2.17.0

Re: [PR] build(deps): bump org.codehaus.plexus:plexus-compiler-eclipse from 2.13.0 to 2.15.0

14 matches

Site Navigation

Mail list logo

Footer information