Hello
I know I have poked around this question in the past, but I wanted to see if there’s any thinking in this direction –
From my understanding the NetLogo Shapes Editor uses a simplified SVG format.
The Inkscape software outputs a “Plain SVG” which might be a good starting point for converson to NetLogo Shapes. For example, here is a snippet from that output, where the drawing is on a 300x300 field, and we have a filled rectangle and a non-filled star shape:
<rect
style="fill:#ff0000;stroke:#131313;stroke-width:0.564999"
id="rect1"
width="139.69067"
height="106.97034"
x="33.978813"
y="33.978809" />
<path
style="fill:none;stroke:#131313;stroke-width:0.564999"
id="path1"
d="m 64.182204,181.22033 5.373276,44.87738 40.01511,21.01529 -41.020491,18.97816 -7.621378,44.55071 -30.725332,-33.14823 -44.725378,6.51857 22.0311882,-39.4649 -20.0204252,-40.52201 44.341355,8.75758 z"
transform="translate(135.91525,-44.04661)" />
It seems like instructions such as these maybe could be programmatically converted to Rectangle, Polygon (and Circle, Line, etc) commands that NetLogo uses.
If so, then perhaps (a) Inkscape could be an authoring tool for shapes, and (b) this SVG format might be more widely known so that people might request generative AI tools to output designs there, allowing a workflow for less savvy Inkscape users.
Is there anything afoot in this direction? (Or more generally, toward making shapes more easy to create? I think I recall that there was some Turtle Universe talk toward NetLogo shapes at one point.)
Best,
-Corey
Corey Brady
Associate Dean, Research and Outreach
Associate Professor, Mathematics Education and the Learning Sciences
Department of Teaching and Learning
Simmons School of Education and Human Development
Giving NetLogo expanded options for shapes is definitely
something that has come up many, many times, over the years.
We've accumulated a bunch of issues on this topic on GitHub,
including this one,
this one,
and this
one. I think the idea is generally appealing to us, but has
historically not been given priority, in part because it would
require a substantial change to the NetLogo file format, and the
old '.nlogo' format was very rigid. In NetLogo 7, we're
introducing a new, extensible file format, which will make these
sorts of changes a lot less agonizing for us and our users.
I've targeted
the main ticket for this officially for NetLogo 8.0 (which
might be a way's off). This functionality won't go into NetLogo
7.0, nor probably even a 7.1, but I could see it ending up in a
7.2 or 7.3 or similar release, some months down the line. I think
our team is generally convinced of the value of it, but, for the
very near term, we just have other, higher priorities.
First comes NetLogo 7.0. Then, NetLogo 7.0: Special Edition.
Then, NetLogo 7.1: Director's Cut. And so on. You know how it
goes.
Jason
--
You received this message because you are subscribed to the Google Groups "netlogo-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netlogo-deve...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/netlogo-devel/9885FB7B-930F-4DA0-95E5-FEF1CF03E6A5%40smu.edu.