What's the best way to "know" about available code without explicitly
(require)ing or (use)ing it from other code?
Would it be better to put all component *.clj files in a given
directory, and then recursively load all the files in that directory?
Or to have a separate registry file that you need to add components to
before they would be available?
Thoughts? Keep in mind that a long-term goal is to make it easy for
users to share components, without copying source files around....
Absolutely... I didn't meant that the files shouldn't be transferred
around, they should. But it shouldn't be the onus of the user to know
about *.clj files, I don't think. But maybe I'm wrong... Thoughts?
On Apr 23, 11:43 am, Serge Wroclawski <emac...@gmail.com> wrote: