Hello Luis and Jason! I came across this conversation while searching for resources on using Netlogo in wordpress, because I'm also trying to create a resource. Luis- did your project pan out? I would love to look over it t see what you did, and I'm running into similar issues as you did here.
Any help you can offer would be VERY appreciated! Thanks! Andy On Friday, September 16, 2016 at 3:17:56 PM UTC-5 Jason Bertsche wrote: > if there's a simple way to switch off the view in NLW from the code, we'd > love to know. > > > Unfortunately, no, there's no simple way to do that in NLW yet. > > > Also, if you can think of a more standard way of doing stacked bar charts > in NetLogo Desktop (ideally compatible with NLW), we'd love to hear about > it. I cannot think of a simpler way to implement them. > > > Ah, maybe I should have been clearer. I didn't mean to suggest that you > had implemented the "stacked columns" thing incorrectly. To my knowledge, > your implementation is the best that can be done in desktop NetLogo. > Rather, the idea was that desktop NetLogo makes you jump through hoops in > order to accomplish some things when plotting, and I've chosen a plotting > solution for NetLogo Web that should eventually allow us to easily provide > a more diverse range of plots, with far less hoop-jumping, but at the cost > of not reproducing all of NetLogo's hoop-jumping abilities. > > > We keep on seeing silly-looking inputs in the current netlogoweb.org, > though (for instance, in the same model that was causing the issues with > the wrapping color arguments). > > > Thanks for bringing this to my attention. The display problem was > properly fixed, but there was an issue where not everyone was receiving the > latest version of the page. That latter issue has now been resolved, and > you should no longer see tall Input widgets looking ridiculous. > > > On 09/12/2016 02:41 PM, Luis R. Izquierdo wrote: > > > Dear Jason, > > Thank you so much for your answers and work. We really appreciate it. I > comment on each of your points below: > > With #1 (`read-from-string` support), it's not hugely far off from being >> implemented, but it's also not hugely close. It's definitely something >> that's on my radar and that I have made a lot of progress on, but I would >> guess that it's *at least* one month away, probably a bit more than that. >> > > That's great, we can certainly wait. > > >> Regarding #2 (`no-display`), yeah, that one's a long ways off. `display` >> and its ilk are a huge pain to implement correctly in the browser. We want >> to implement them, but it's going to be a bit. With primitives like >> `display`, I find that the they can usually be worked around with the stuff >> in NLW that currently functions, but I'd need to see the model in order to >> say for sure, one way or another. >> > > We actually use no-display only to make the model run faster without > having to tell the user to turn off the switch in view control (we don't > use the view at all in many of our models). It's not big deal, but if > there's a simple way to switch off the view in NLW from the code, we'd love > to know. > > With #3 (the stacked bar charts), I don't plan to make your current code >> for that compatible with the plotting functionality in NetLogo Web. While >> having stacked bar charts is an undeniably useful thing, your version of >> them in NetLogo is achieved by doing some very non-standard stuff in >> desktop NetLogo, which the plotting library we're using in NLW doesn't >> understand. However, that library *does* know how to handle *proper* >> stacked bar charts >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.highcharts.com_demo_column-2Dstacked-2Dpercent&d=CwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=sxGjFFyk2A6rYHwAdDtnqeTKj3cEcXDGDo_G9va2ruI&m=Ib4C0J04Tq9WmBv4zUZgEPsJsODfM3WSL7cct3guGIE&s=nXqY1KC9Oyl6X04skXvKbYC_Y7q_gspqjHmpozKTw_4&e=>, >> >> so we could talk at some point about how we modify your web-based models to >> tap into the proper functionality instead. >> > > That would be awesome (or if you want to point us to an example -so we > don't waste your time-, that's also perfect). Also, if you can think of a > more standard way of doing stacked bar charts in NetLogo Desktop (ideally > compatible with NLW), we'd love to hear about it. I cannot think of a > simpler way to implement them. > > >> Regarding the bug reported in #5, that was because `extract-rgb`, >> `extract-hsb`, `scale-color`, and `shade-of?` weren't wrapping their color >> arguments to keep them within [0, 140), so it broke when it got color >> number that was `145`. >> > > Thank you so much!! > > >> That and #4 (the silly-looking Inputs) are both now fixed on >> netlogoweb.org >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__netlogoweb.org&d=CwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=sxGjFFyk2A6rYHwAdDtnqeTKj3cEcXDGDo_G9va2ruI&m=Ib4C0J04Tq9WmBv4zUZgEPsJsODfM3WSL7cct3guGIE&s=imypNR0s-E5yIqMQfR2KEY502T-VJYtobhu7lu6Xv5Y&e=> >> >> . >> > > We keep on seeing silly-looking inputs in the current netlogoweb.org, > though (for instance, in the same model that was causing the issues with > the wrapping color arguments). > > >> Thank you for bringing both of those issues to my attention. >> > > Thank YOU for your awesome work and the great help! > Luis > > > >> >> On 09/08/2016 09:41 AM, Luis R. Izquierdo wrote: >> >> Dear Jason, >> >> This post is about running the models inside wordpress, >> >>> 2. Regarding running NetLogo models: To have a NetLogo engine inside the >>> book, so everything works even if NetLogo changes too much for our code. >>> (And potentially be able to change the css of NetLogoWeb slightly, to make >>> running models fit better with the rest of the e-book, e.g. fig.1 at >>> http://ccl.northwestern.edu/2016/WeintropEtAlConstructionism2016-1.pdf) >>> >>> Okay, got it. Do you already know all of the models you want to use? I >>> primarily ask because I want to know if NetLogo Web can already do >>> everything you want to be able to do in your book, or if it makes sense to >>> hold off on this plugin until some feature or another is implemented. >>> >>> >> We have tried to run all the models we have implemented so far, and these >> are the issues we have encountered so far: >> >> 1. read-from-string is not supported in NetLogo Web so far. >> We need a way to allow the user to input lists (or, more generally, a >> list of lists). Currently we do this with an input box and >> “read-from-string”, but this reporter is not implemented in NetLogo Web yet. >> >> 2. no-display is not supported in NetLogo Web so far. (not big deal) >> >> 3. The display of (temporary) pens in bar mode which overlap each other >> is not dealt adequately in NetLogo Web yet (see pictures 1-*.png attached). >> >> 4. The appearance of input boxes is not dealt adequately in NetLogo Web >> yet (see "payoffs" input box in pictures 2-*.png attached). >> >> 5. We have one particular model (attached) which runs fine in Netlogo >> Desktop, but throws the following error in NetLogo web: >> >> "A type error has occurred in the simulation engine. More information >> about these sorts of errors can be found here >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__netlogoweb.org_info-23type-2Derrors&d=CwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=sxGjFFyk2A6rYHwAdDtnqeTKj3cEcXDGDo_G9va2ruI&m=aEqysEkm9CAtkWO8WkOX8pwKW83C6Ee84jK0Q4s0FC4&s=-jzWoTqCXHX-NjTBUc6N3qWt9m5mBUge2ltqMVPMMSs&e=> >> . >> Advanced users might find the generated error helpful, which is as >> follows: >> *ref is undefined*" >> >> Given this, I guess the best way to proceed is: >> 1. To post these issues in https://github.com/NetLogo/Galapagos/issues >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_NetLogo_Galapagos_issues&d=CwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=sxGjFFyk2A6rYHwAdDtnqeTKj3cEcXDGDo_G9va2ruI&m=Ib4C0J04Tq9WmBv4zUZgEPsJsODfM3WSL7cct3guGIE&s=T_JUd7jZ1cBSQFf7rafUZBYpJBP-FJglFpabiJy2rmo&e=> >> >> 2. To wait a little bit for these to be solved. >> >> Is that what we should do? >> Thank you so much for all your help! >> >> >> -- >> 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 [email protected]. >> For more options, visit https://groups.google.com/d/optout >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=CwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=sxGjFFyk2A6rYHwAdDtnqeTKj3cEcXDGDo_G9va2ruI&m=aEqysEkm9CAtkWO8WkOX8pwKW83C6Ee84jK0Q4s0FC4&s=3fCMuCxjWF46MTCxJdOEda3tBGcaBKkeU3kNshgTm0M&e=> >> . >> >> >> -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout > <https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=CwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=sxGjFFyk2A6rYHwAdDtnqeTKj3cEcXDGDo_G9va2ruI&m=Ib4C0J04Tq9WmBv4zUZgEPsJsODfM3WSL7cct3guGIE&s=NlaO4Kv46YNPwYGEIoG-L0M1UCk7G2yI3JErseiQHJE&e=> > . > > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netlogo-devel/819f343f-dceb-4a9d-a432-364949024f48n%40googlegroups.com.
