Chris,
that is exactly my line of thought as well.
On Tue, Mar 6, 2018 at 4:43 PM, Christofer Dutz
wrote:
> Hi Niclas,
>
> as far as I understood Polygene especially after your examples. I would be
> hesitant to use this per default in PLC4Xs core. It does seem to add quite
> a lot of complexity
Hi Niclas,
as far as I understood Polygene especially after your examples. I would be
hesitant to use this per default in PLC4Xs core. It does seem to add quite a
lot of complexity which I personally would like to avoid. I don't want to
confuse potential users. Especially the ones peeking into
Polygene is highly opinionated, for better and worse. Minimally, Polygene
requires to start a runtime, and that everything needed is declared
explicitly upfront at boot time. The minimal start code is something like;
public static void main( String[] args )
throws Exception
{
app = new Si
Hi Niclas,
after recovering from that nasty Flu, that is plaguing Germany at the moment, I
am working on catching up on what I missed.
I tried to follow, but some things I felt to worn out to work my head around.
Could you elaborate a little on Ploygene? How would this allow extending our
req
Being the Overlord of Magic that can be done in Java, I have some comments
to make on this idea.
1. In principle what you suggest can already be done quite easily in Apache
Polygene, by creating a "generic mixin" that overrides the generic
PropertyMixin. Polygene is probably way more powerful than
Hi Dale,
The direction thing was inspired by the way the Beckhoff ADS protocol was
designed.
There they sometimes Send Data alongside read requests and sometimes have
strange "return what's in there and then overwrite with this" type of requests.
The Beckhoff support guy mentioned that they are
Doesn’t the user need access to the response code for each annotated item?
I’m unclear on why a Direction is needed/desired. Is it just for
“documentation" of what is possible for an item at that address? Maybe it
would be checked when the annotated class is used in a Read vs Write request to
Hi,
in the past I have been thinking how we can make the batch reads as simple as
possible.
I would like to introduce an idea I had:
What if we started supporting annotated POJO classes? (The following names are
just ideas …)
A POJO class could be annotated with some “@PlcEntity” annotation.
