puzzler wrote: > I decided it would be a bad idea to include rhizome > directly in instaparse's dependencies. Nevertheless, it > made sense to enable the "visualize" function *provided* > rhizome was already in the user's dependencies.
I prefer to avoid these kinds of load-time tricks, as they break easily when anything else is involved in loading code, e.g. an IDE or app server. Fortunately, Rhizome is driven by data. If you can provide functions that return the data structures that Rhizome expects, then Instaparse users can easily invoke Rhizome themselves to get the visualizations. If this is not possible, I would suggest providing the visualization tools as a separate library release which depends on both Instaparse and Rhizome. This might make sense anyway, if they are intended only as a development-time tool. -S -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" 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/groups/opt_out.
