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 <cesar.gar...@ceos.com.ve> 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, <bjo...@coding-nexus.com> 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 <https://aka.ms/AAb9ysg> > > _____ > > From: Christofer Dutz <christofer.d...@c-ware.de> > Sent: Thursday, March 21, 2024 1:39:11 PM > To: dev@plc4x.apache.org <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 <ott.lukas...@gmail.com> > Datum: Montag, 18. März 2024 um 11:51 > An: dev@plc4x.apache.org <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> > 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/> 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 <support.aan.automat...@siemens.com>*
