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: 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