Closed TheBizzle closed 10 years ago
Sorry, we didn't notice the pull request until this week! Not sure why we didn't get a notification. But anyways, this is awesome. We're hoping to get back to the NetLogo data persistence and import/export work soon. So we'll take a look and let you know how it goes. Thanks so much! And thanks also for writing up the IntelliJ documentation.
I enjoyed reading your list.
Cool, I look forward to hearing about progress made with this!
Hey, sorry it took me so long to submit this. Working with applets is depressing....
master
branch is really what you'll want to do, but maybe it is. Essentially, some changes are going to still need to be made on your end after merging this, in order to get out the behavior that you want.imageStr
that I'm pulling out of NetLogo innetlogo.js
. It's a Base64-encoded PNG. (Not sure if you guys are aware of this or not, but, in modern browsers, you don't actually have to do any decoding, yourselves, in order to display a Base64-encoded image: http://css-tricks.com/data-uris/). You may even want to remove the generation of that image string fromnetlogo.js
and force steps that want to generate images to do so, themselves.NetLogoLite5.jar.bak
file that was sitting around, because, well... it was in version control, so it didn't actually need to stick around. (i.e. If you need that back-up of the.jar
, just get the old copy from version control.)NetLogoLite5.jar
with aNetLogoLite-5.0.x-zzzzzzz.jar
whose name contains the SHA hash for the NetLogo commit that is being used. People who, in the future, attempt to debug broken NetLogo applets might thank me for the versioning of this.jar
.jar
mentioned in (3) includes some important fixes for being able to use the Web Image extension sanely. It doesn't strip out two chunks of the Scala library needed by the Web Image extension (commit) and it allows you to look up extension URLs in applets from a property that you can pass into the applet (commit). These changes exist on the NetLogo5.0.x-appletland
branch—the branch that any future NetLogo.jar
s you guys use for applets ought to come from (which I'm telling you in case you, for some reason, need a new.jar
in the future and I mysteriously die before then). This is cordoned off onto its own branch because we, at Northwestern, are making minimal efforts to support applets—hadn't I sworn to myself that I'd never deal with applets again before I undertook all this?—and because I decided that I didn't have time to write Java code for this that was actually good, so I just threw something together for it. At the height of my writing it, I even decided to mock and insult myself a bit, but... maybe that was unfair, as Java is the problem, not me!.netlogo.js
file a lot to get rid of some very crufty stuff. There was an awful lot of unnecessary polling, juggling of globals, needlessly getting handles on objects, and unnecessary functions laying around. So... I trashed most of that. Also, did you know that I hate mutable state?this.nlCmdReport("data-export:make-model-data")
—first, because the model is massive and scary, and, second, because I'm not sure how to do so meaningfully with that model. It looks like the data being exported is already processed data, so I'm not sure how to import it back in while still being meaningful to the activity. I would suggest that, if Concord wants that data getting back into the model, someone from Concord should write the NetLogo code (or NetLogo extension) to handle that.