next up previous
Next: Requirements Up: EvoX - Evolution in Previous: Other uses of

Cop-outs and to-do's

Because I need to use EvoX for my research, I threw the interface together rather quickly. This means it's not as robust, beautiful or sophisticated as it might be, although it's actually pretty good (try it and see what you think). In any case the interface will improve at a fast pace.

Primary changes will be as follows (these are in no apparent order right now):

  1. Create specific widget types for the hierarchial views of the contents of objects and simulations. These may be based upon the `TkTreeTable' widgets supplied with TkNews 2.0b6. (Update: I've now implemented some of these as [incr tcl] widgets. They're really quite good now.)

  2. Incorporate more sophisticated drag'n'drop support.

  3. Use [incr tcl] --- primarily because I'm much more used to programming in the OO way, so my code is much better and easier for me to understand (and you too I hope!). The basic improvements it gives are a much better tcl namespace arrangement, classes and inheritance. I will no doubt be using [incr tk] as well, when it appears. Perhaps the widgets mentioned above will be implemented in [incr tcl/tk] rather than C. (update: I'm now using [incr tcl] for nearly everything)

  4. Give variables a tag as to whether they're read only. This will always be capable of being over-ridden (except for variables accessed or calculated via functions for which the class provides no `write' method) by setting some flag in the EvoX environment, but will mean that inadvertent changes of important flags are avoided. Perhaps there should be a number of flags (always read only, read only during a simulation, ...).

  5. More analysis tools



Vince Darley
Wed Apr 24 12:50:09 MDT 1996