Hi Seth, As always, thanks a lot for your mail...
> 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 > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FNetLogo%2FNetLogo%2Fwiki%2FControlling-API%23example-embedding&sa=D&sntz=1&usg=AFQjCNGbBusCRDX8uZADz7JDzFGvE6XZEw> > I didn't know that there exists an API only for the interface... that's great!, thanks. > > >> 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 > Yes, I am waiting for that for a long time ;)... I know, maybe I must get into Scala some day... > 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 > You are correct, they exist!!! (since 2016??), does someone know if there is a place where we can find the unofficial features? I use to look at https://github.com/NetLogo/NetLogo/wiki/Unofficial-features, but it seems to be outdate... Maybe it is my fault because I must see in some other place. > `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 > Thanks, I suppose that a lot of "wishes" must be hard to get (and they are only a personal wish, of course), overall when they are about changes that affect very common primitives. > 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 > Great discussions! .... I enjoy with the idea of adding sets as a general type. I know that maybe my view is different from a lot of NetLogo users... I am not thinking in kids as targets, but in how to use it more and more in a complete programming language for science experiments... and that is because I enjoy it, by using agents it helps to think in solving problems from a distributed point of view, although I know that there are other options out there... Thanks again for taking your time to read it. Fernando -- 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/1047b1a1-494a-4731-9cd9-02fdecbe37be%40googlegroups.com.
