Has the use of named sections been considered for the NetLogo file format?
Indeed, it has been. With the recent work on Tortoise (the
browser-based version of NetLogo), there has been murmuring about us
switching to a nicer file format. The old format essentially must
always be supported in some way, but we're hopeful that, in the future,
NetLogo model files can be JSON or some other standard serialization
format. JSON isn't exactly the pinnacle of human-readability, but it's
better than what we currently have, and it's natively supported by browsers.
Separately, for human readability it would be nice if widgets were
specified as collections of key value pairs.
Totally agreed.
On 07/31/2014 01:04 PM, Alan Isaac wrote:
Has the use of named sections been considered for the NetLogo file format?
This would be easier for humans to read (and would not require the
presence of empty sections).
E.g., the section divider markers could remain unchanged but allow a
name to follow on the same line,
with the being those given at
https://github.com/NetLogo/NetLogo/wiki/Model-file-format
(Side note: currently that page calls the second section both Widgets
and Interface).
Separately, for human readability it would be nice if widgets were
specified as collections of key value pairs.
Until then, thanks for the documentation at
https://github.com/NetLogo/NetLogo/wiki/Widget-Format
fwiw,
Alan Isaac
--
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-devel+unsubscr...@googlegroups.com
<mailto:netlogo-devel+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
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-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
