|
From: Mark R. D. <mdi...@la...> - 2003-08-12 14:40:59
|
I'm curious what others think about RePast in relation providing support
for features such as Java3D and Geotools. I think we start to really
reach an unrealistic limit in terms of packaging all this functionality
directly into RePast as one monlithic project. It also becomes
questionable as to whether RePast gets added to GeoTools (or any other
Platform) or the other way around during this extension process.
Maybe it would be wise to begin a goal of defining a "plugability" layer
for RePast such that the "core" features of RePast can be isolated from
the "extensions". This way one can either use the "bare-bones" of
RePast in thier project without having to drag along all the features
they may not actually be interested in, or they can provide an extension
to RePast itself if it is acting as the framework.
Mostly, these extensions tend to be isolated in the area of rendering.
But they do also involve mapping between various datastructures in both
RePAst and the Framework of question. It would be logical to consider in
the future that plugging RePAst into "X" platform will involve providing
"Graphical" and "Nongraphical" bindings to and from that framework.
RePast Platform X
1.) Implementatation of RePast space, graph or topology interfaces in
external API's for execution from within RePast.
RePast Interfaces <-- Platform X Data Structures
2.) Mapping model data structures to an external rendering engine.
RePast Model Data Structures --> Platform X Rendering Engine
3.) Exposing model controls and properties to external platform.
RePast Model Properties/Controls <-- Platform X
As we are starting to do to more of this "extension" these days. It
would be wise to begin such discussions while the interest is there.
This can happen at a couple of levels both internally to RePast with its
own displays/controls and external to RePast in relation to GeoTools and
other platforms that we are interested in "interfacing" with RePast.
-Mark
|