On Tue, Apr 9, 2019 at 3:55 PM Matthew Flatt <mfl...@cs.utah.edu> wrote:
> > Are you running into problems where you really need GUI functionality > to create the image? Or it is just a library is bundled with GUI > functionality --- like `plot`, and maybe the `plot/no-gui` analog is > missing? Or is it more a question of keeping track of which libraries > imply a GUI and which do not? > In this case, there's probably a number of things going on. 1. Me not knowing when to use plot vs. pict. 2. Me having used plot in a library of my own, and then wanting to use something from that library in my documentation. At that point, perhaps my library should be organized so that I can separately include the parts that require plot and the parts that don't. 3. I want to use the plot-generating parts of my library to write docs, but can't use them directly (on OSX, but it would work elsewhere?)... which, is some combination of #1 and #2. The summation of 1, 2, and 3 might sum to a result that says I haven't taken the time to understand the connections between these libraries, and that I have assembled my own code in sloppy ways. It was, however, a surprise for me when I ran into it. Cheers, Matt -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
