|
From: John T. <tr...@cs...> - 2009-07-07 17:00:52
|
Hi, In order to improve the flexibility of my models, I like to make use of interfaces to abstract from different possible implementations. Thus, I define agents & contexts with interfaces + implementing classes. The problem is that this approach doesn't fit very well with Repast Symphony since the model score and the scenario entries require to specify the concrete classes used. If I want to change the implementation of a context or an agent, I've almost nothing to do in my code, but then I've to update all the repast files that was referencing the previous implementation ... Moreover I've noticed that the scheduling annotation are processed only if they are defined in a class which is used in model.score file. If there is a schedule annotation in a super class, this one is not taken into account. It would be nice to be able to reference interfaces / super classes in the score file and in the scenario files, and so to be able to load easily different implementations at run-time. Do you think this is feasible? To achieve this at the moment, I suppose I've to build the scenario with java programming (but loosing the nice graphical interface ...). Is there any documentation or code examples you can recommend me to have a look at how to build a scenario in java ? Thanks, John |