Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Isn't typeof a static operator (i.e. resolved in compile time)? I think I would need to use GetType() in this case (which is not a problem) because the type passed to the UI is not known during compile time. Either way, it's a very good point to use types instead of enums. Commented Nov 9, 2015 at 9:33
  • @9a3eedi Right. Commented Nov 9, 2015 at 9:54
  • After thinking about it for a while, the Visitor pattern along with the rest of your answer sounds like the way to go, with one problem: how can I make sure that the UI executes only one of the choices that the Core has given it? I think I can work that out though. Commented Nov 9, 2015 at 16:18
  • 1
    @9a3eedi Well. UI doesn't need to execute anything. It can just pass it back to the Core Logic where it will be executed. Commented Nov 9, 2015 at 16:26
  • The "execute" function will still be exposed though. But I figured that I can still make it so that the UI has no way of providing the parameters it needs to execute it :) You're right. And maybe I'm obsessing about this too much.. Commented Nov 9, 2015 at 18:21