Interface based messaging for Actors.

[PrimaryKey]

Please add to AF:

Interface based messaging. The need to create messages for all communication is a major decrease in productivity and speed of actor programming. It also decreases readability. It is a better with the BD Preview in Choose Implementation Dialog in LV19, but still.

[drjdpowell]

You need to flesh this one out.  What would "interface based messaging" look like?

[PrimaryKey]

An example project would contain many small and simple actors, each designed to only implement a single actor interface and messages to invoke it. Then concrete actors would actually implement those small interfaces and create the actors with required functionality. All messaging would be done in a small layer of communication interfaces, and application specific logic would be inside the app actors implementing interface actors.

Example: Logging Actor interface includes the generic LOG method, with a LOG message to invoke it. The generic LOG method is empty, but specifies an interface for specific TDMS_Actor.lvclass implementation. This is currently possible in LV, but only for a single inheritance of a single "interface". 

This would mean that the number of classes would shrink significantly in AF projects.

[AristosQueue (NI)]

Please see the beta of LV 2020 and let me know if this one is done or not. There's a shipping example here:

 examples\Object-Oriented Programming\Actors and Interfaces\Actors and Interfaces.lvproj

I find it very nice.

Go to http://ni.com/beta to join.

I think we have what you're asking for, but "This would mean that the number of classes would shrink significantly in AF projects." is not true, which makes me wonder if you're talking about something else.