Actor Framework Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

(MVVM ARCHITECTURE) in Actor Framework - UI handling

Hi all!

 

I am trying to find the most efficient way to have my UI generate events on the Main (Program Controller Actor) and I can do this via messaging (where they invoke a do.vi which generates a user even to which the helper loop in the main actor is subscribed)

Now, what I was thinking to do, is having other actors subscribed to the same user event in the main actor (those actors are not children of this actor).  What I had done is pass the Main Actor Object by composition to each Nested Actor and having a data accessor to the references of each User Event.

Is there a better way?

 

Thanks for the help in advance.

0 Kudos
Message 1 of 5
(6,232 Views)

I thought a lot about porting MVC or MVVM to labview, and came to the conclusion that it's wrong, because you basically "fight against the system".

 

So first of all, the main idea of MVC or MVVM is just to be a framework to build on and to use.

 

"Framework" = data/objects/code/documentation/example/tutorial ALREADY DONE.

 

There is simply no MVC or MVVM done in Labview so you would have to REINVENT the wheel, and it's a too complex task.

If you examine solutions made for .NET by 3rd parties (like DevExpress), and you go throught their tutorials, you will quickly realize it.

 

MVVM / MVC are very complex.

 

Labview is already an abstraction over Win32 (you have a "front panel + block diagram" by design), so you would build up another abstration on top of this, and ON TOP of that you would build your own program.... That's a huuuuge complex software.

Totally not worth imho.

 

So at the end of the day, I would just stick with "classic LabView concepts", like state machines, queues, parallel loops, and/or actor framework.

 

 

0 Kudos
Message 2 of 5
(6,185 Views)

That's the first time I've heard the phrase "Classic LabVIEW Concepts" applied to Actor Framework.   We've come a long way...

Sam Taggart
CLA, CPI, CTD, LabVIEW Champion
DQMH Trusted Advisor
Read about my thoughts on Software Development at sasworkshops.com/blog
GCentral
Message 3 of 5
(6,176 Views)

Because everyone use MVVM and separation of concerns so to say...Smiley Very Happy

 

The experts here will just tell you "make an actor that handles UI"

 

that's it. BUT this is not MVVM.

 

Message 4 of 5
(6,147 Views)

I believe this is what you want.

https://bitbucket.org/composedsystems/mva-framework/src/master/

Sam Taggart
CLA, CPI, CTD, LabVIEW Champion
DQMH Trusted Advisor
Read about my thoughts on Software Development at sasworkshops.com/blog
GCentral
Message 5 of 5
(5,254 Views)