On Fri, Apr 17, 2020 at 10:23 AM Fernando Sancho <fsanchocaparr...@gmail.com> wrote:
> 1) Remap some editor keys, because they don't work on non-English laptops > (or give the user the option to decide how to map them). For example, on > Spanish laptops it is impossible to modify the zoom of the application > using the keyboard. > existing tickets in this area: https://github.com/NetLogo/NetLogo/issues/950 https://github.com/NetLogo/NetLogo/issues/1606 > 3) Create GUI versions of models without code access or interface > modification. A distributable interface that can call .nlogo files that > removes all the editor part and that works in the background with > NetLogo.jar would suffice . Even, perhaps you could think about the > possibility of including the intermediate compilation that the tool makes > prior to execution, and give options if this closed and distributable > version has access to the Command Center , agent inspection windows, etc ... > Note that this capability actually exists in current NetLogo: https://github.com/NetLogo/NetLogo/wiki/Controlling-API#example-embedding It just hasn't been packaged in a way that allows non-Java/Scala-programmers to use it. But, I second Ken's suggestion to consider using NetLogo Web for this. > 11) Fully manipulate the interface by code (as some extension does). > You're probably thinking of https://github.com/NetLogo/Goo-Extension — perhaps someone will revive it 1) Function (apply f [x1 ... xn]) = (f x1 ... xn). In order to have a much > more faithful approach to the functional paradigm, where a good role is > already being done. > This may actually exist as `__apply` and `__apply-result`? not sure, but see https://github.com/NetLogo/NetLogo/issues/539 and https://github.com/NetLogo/NetLogo/pull/1139 > Instructions like "link a b" should work receiving a and b as turtles, not > their who IDs > `link a b` is analogous to `turtle a`, which takes a `who`. The turtle-based version exists, it's called `link-from`: `[link-with b] of a`. I doubt that changing this around is possible at this late stage in NetLogo's development > 6) Add map, filter, foreach for structures like: table, string. In > general, if a structure can be worked in a functional way, it should have > all the functions apparatus to deal with it. Although sometimes the need to > define iterators for foreach might arise, it could work with the natural > iterator. > some past discussion in this area: * https://github.com/NetLogo/NetLogo/issues/1204 * https://github.com/NetLogo/NetLogo/issues/594 (disclaimer: I'm no longer involved with designing or implementing NetLogo) Seth -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/netlogo-devel/CAOoO2viKsZUzt1C8AO8SqvwLJJec%2BVAFirKLx8LjUxcmmp22nw%40mail.gmail.com.
