Closed arthurhjorth closed 8 years ago
If we do #43, then you'll have a better way to get that information.
You know what would be cool? A reflection extension for NetLogo. That's where this stuff belongs. It wouldn't even take long to write. Maybe we should just break that functionality off into another extension?
Anyway, I'd really rather not have this stuff here. As I said, #43 completely removes the need, and even without it, having both models open is pretty easy.
I agree. I'll migrate all this stuff to a reflection extension.
We've gone back and forth on this a few times. I can't really figure out if I think it's a good idea or not, but I think I do:
We currently on the xwgui branch (called tpl-reporting) have three prims that help you make sense of your child models:
ls:_list-breeds
,ls:_globals
, andls:_model-procedures
. Disregarding their current names, should we include these?I'm thinking yes, because it's SUPER practical, when you are building LS models, to be able to quickly see your breeds and variables from the command line. Any objections?