Actor Framework Discussions
Newbie questions about AF
Hi everyone,
thank you very much for your comments. You are absolutely right that part of my frustration stemmed from the fact that I created logical layers but didn't put thought into the exact function they were supposed to fulfill.
I think zero coupling is the way to go and would make it very powerful.
I'll keep you posted with what I come up with.
thanks a lot again
BR Mathis
Have you considered making the UI a compound thing that is distributed amoung the various actors and assembled into a whole via subpanels? I generally have each component** have it's own dedicated subUI that is shown when needed in a subpanel or separate window. Then, most detailed information doesn't have to go very far. This is also a technique that works well with plugin components, since the higher-level actors don't need to know as much about their subactors.
**Note: I use a different actor-like framework than the AF.
Thank you very much for all the helpful comments. As already mentioned before I hadn't really thought throught through the structure of the software. I organised the software in fucntional groups without figuring out what each layer is actually doing. This is obviously kind of a suicide in any kind of OOP as a class/actor needs to have a defined purpose (and that shouldn't be just to create overhead by relaying messages).
My current approach has a structure which is a lot flatter (as I can't figure out what the process layer should be doing to the data before it gets displayed .. so clearly that layer is obsolete).
I think the idea to display sub panels is a great idea. I think XTabs would be a neat way of doing that. Do you have an elegant way of broadcasting the vi references of each actor to the GUI?
@Dr Powell: I've seen your post about your AF which uses 30k+ actors without performance issues. Impressive feat! Is that available to the public?
