These forums seem so new, and you're trying to do a lot of different things, it might be best if there were separate discussion areas for APIs/GUI etc. Like in the dependency injection thread, if you're talking about DI but different people might be talking about different scopes, then it's not as productive as if we're all sure we're talking about the same thing.
So one question is, what is "Core-ESL", what does it aim to do? Where in this diagram from planning.pdf does it fit (the diagram of APIs was called "Behavior Layer", but there is no such labeled layer in the High level design)? How much clean separation between the APIs and various implementations will you try to maintain? The core classes you've created so far look to me like a good way to test and begin to implement an API, but they're a pretty rigid API in the sense that you can't re-use them to create all kinds of different simulations. It's ok if you limit yourself to banks, firms, households, etc, but what if people want to add in a layer that simulates the behaviour of different supply curves of different types of goods over time, or personal beliefs regarding religion and their effect on the economy, e.g. North Carolina's transgender issue? (Maybe that's all way outside of inital scope, just trying to find a better definition of Core-ESL.)
6
These forums seem so new, and you're trying to do a lot of different things, it might be best if there were separate discussion areas for APIs/GUI etc. Like in the dependency injection thread, if you're talking about DI but different people might be talking about different scopes, then it's not as productive as if we're all sure we're talking about the same thing.
So one question is, what is "Core-ESL", what does it aim to do? Where in this diagram from planning.pdf does it fit (the diagram of APIs was called "Behavior Layer", but there is no such labeled layer in the High level design)? How much clean separation between the APIs and various implementations will you try to maintain? The core classes you've created so far look to me like a good way to test and begin to implement an API, but they're a pretty rigid API in the sense that you can't re-use them to create all kinds of different simulations. It's ok if you limit yourself to banks, firms, households, etc, but what if people want to add in a layer that simulates the behaviour of different supply curves of different types of goods over time, or personal beliefs regarding religion and their effect on the economy, e.g. North Carolina's transgender issue? (Maybe that's all way outside of inital scope, just trying to find a better definition of Core-ESL.)