Re: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Christofer Dutz
Just noticed this was the wrong thread ;-) Daffodil is now generally history but I didn't delete the protocol modules I haven't migrated yet as I wanted to translate the KNXNet/IP definitions I had created to the new format before deleting the dfdl schemas. Chris Am 26.06.19, 08:27 schrieb "C

Re: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Christofer Dutz
Also Done :-) At first I had moved the java template into the plc4j module, but noticed that we were thinking of making plc4py, plc4cpp and plc4net use their own build systems internally, so keeping the structure would be a challenge, so we'll simply add all templates to the plc4x root build-ut

Re: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Tim Mitsch
Sorry for late response, quite busy on a fair. But also +1 from me Best Tim Am 25.06.19, 10:08 schrieb "Christofer Dutz" : Oh wow ... that was a quick one ... I think I'll just do it right away. Thanks for the ultra-quick responses Chris Am 25.06.19

RE: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Strljic, Matthias Milan
+1 😊 Matthias Strljic, M.Sc. Universität Stuttgart Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) Seidenstraße 36 70174 Stuttgart GERMANY Tel: +49 711 685-84530 Fax: +49 711 685-74530 E-Mail: matthias.strl...@isw.uni-stuttgart.de Web: http://www.isw.un

[BUILD-STABLE]: Job 'PLC4X/PLC4X/develop [develop] [404]'

2019-06-25 Thread Apache Jenkins Server
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [404]': Is back to normal.

Re: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Christofer Dutz
Oh wow ... that was a quick one ... I think I'll just do it right away. Thanks for the ultra-quick responses Chris Am 25.06.19, 10:05 schrieb "Julian Feinauer" : Hi, I agree and I think its important to tag it as it really was an intersting step. Julian Am 25

Re: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Julian Feinauer
Hi, I agree and I think its important to tag it as it really was an intersting step. Julian Am 25.06.19, 09:57 schrieb "Markus Sommer" : +1 Freundliche Grüße Markus Sommer Geschäftsführer isb innovative software businesses GmbH Otto-Lilienthal-Strasse 2

AW: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Markus Sommer
+1 Freundliche Grüße Markus Sommer Geschäftsführer isb innovative software businesses GmbH Otto-Lilienthal-Strasse 2 D - 88046 Friedrichshafen Tel.:    +49 (0) 7541 3834-14 Mob:  +49 (0) 171 537 8437 Fax: +49 (0) 7541 3834-20 E-Mail: som...@isb-fn.de Web: www.isb-fn.de Geschäftsführer: Ma

AW: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Bjoern Hoeper
+1 cleaning up is always good Björn -Ursprüngliche Nachricht- Von: Christofer Dutz Gesendet: Dienstag, 25. Juni 2019 09:42 An: dev@plc4x.apache.org Betreff: [DISCUSS] Retire Daffodil and SCXML? Hi all, I would like to start to move the new code generation outside the sandbox. For this

Re: [DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Sebastian Rühl
+1 sure go for it Sebastian > Am 25.06.2019 um 09:42 schrieb Christofer Dutz : > > Hi all, > > I would like to start to move the new code generation outside the sandbox. > For this I would like to replace the existing code-generation modules. > > We currently have the dynamic driver modules, w

[DISCUSS] Retire Daffodil and SCXML?

2019-06-25 Thread Christofer Dutz
Hi all, I would like to start to move the new code generation outside the sandbox. For this I would like to replace the existing code-generation modules. We currently have the dynamic driver modules, which were a proof of concept and have proven to be technically interesting, but performance-wis

Re: [DISCUSS] [CodeGen] Move the core generator modules to a separate git repo

2019-06-25 Thread Christofer Dutz
Ok, so the split is done :-) Unfortunately I noticed the filter did filter out the commit history for the stuff, but only the part since I moved it to its final destination. But as I think I wrote all of that code anyway there's no problem with matching who wrote which line of code. And if som