darevay
Dave Ray
seesaw.core is 3500 lines of which probably 2500 are docstrings. I wonder if they could be externalized somehow... #clojure
cemerick
Chas Emerick
@darevay Put your docs in another file you load at the *end* of seesaw.core, w/ a bunch of `(alter-meta! #'f assoc :doc "docs")` exprs
@darevay Put your docs in another file you load at the *end* of seesaw.core, w/ a bunch of `(alter-meta! #'f assoc :doc "docs")` exprs
IORayne
Anthony Grimes
@cemerick @darevay I hate both of your guts for even thinking about doing this.
@cemerick @darevay I hate both of your guts for even thinking about doing this.
darevay
Dave Ray
@IORayne @cemerick is this some kind of reverse psych or actual gut hating. Either's fine with me ;)
@IORayne @cemerick is this some kind of reverse psych or actual gut hating. Either's fine with me ;)
darevay
Dave Ray
@IORayne @cemerick Chas, sounds like we should come up with a name and set up a repo ASAP. I'm writing the ML announcement now. :)
@IORayne @cemerick Chas, sounds like we should come up with a name and set up a repo ASAP. I'm writing the ML announcement now. :)
cemerick
Chas Emerick
@darevay Oh! @IORayne is miffed b/c Marginalia doesn't load namespaces it's generating docs for. What was the rationale for that? /cc @fogus
@darevay Oh! @IORayne is miffed b/c Marginalia doesn't load namespaces it's generating docs for. What was the rationale for that? /cc @fogus
cemerick
Chas Emerick
@fogus Heh, sure. I'm just wondering if avoiding loading was intentional, i.e. in case someone has a (launch-missiles) top-level.
@fogus Heh, sure. I'm just wondering if avoiding loading was intentional, i.e. in case someone has a (launch-missiles) top-level.
cemerick
Chas Emerick
@darevay Maybe using: (defmacro docs-for [varname docstring] `(alter-meta! (var ~varname) assoc :doc ~docstring)) ;; :-) #Clojure
@darevay Maybe using: (defmacro docs-for [varname docstring] `(alter-meta! (var ~varname) assoc :doc ~docstring)) ;; :-) #Clojure
darevay
Dave Ray
@cemerick I like it. I was thinking a map of docs in a resource file then a macro that reads it and alters meta...
@cemerick I like it. I was thinking a map of docs in a resource file then a macro that reads it and alters meta...
darevay
Dave Ray
@cemerick ... so (load-docs) loads "resources/*ns*.docs" or something and does alter-meta! for all key/value pairs in the file ...
@cemerick ... so (load-docs) loads "resources/*ns*.docs" or something and does alter-meta! for all key/value pairs in the file ...
darevay
Dave Ray
@cemerick ... and if the resource file is missing, it does nothing so you could ship a minified jar if that's important. need more time. :)
@cemerick ... and if the resource file is missing, it does nothing so you could ship a minified jar if that's important. need more time. :)
cemerick
Chas Emerick
@darevay IMO, I'd wait for (or write!) a proper generalized Clojure minifier/tree-shaker instead of inventing local minification options.
@darevay IMO, I'd wait for (or write!) a proper generalized Clojure minifier/tree-shaker instead of inventing local minification options.
darevay
Dave Ray
@cemerick I'm actually more interested in reducing the file size for *editing* at the mo'. Or maybe I should optimize vimclojure :)
@cemerick I'm actually more interested in reducing the file size for *editing* at the mo'. Or maybe I should optimize vimclojure :)
kotarak
Meikel Brandmeyer
@darevay This is also a wide spread approach. :] I'm a master of it myself.
@darevay This is also a wide spread approach. :] I'm a master of it myself.
cemerick
Chas Emerick
@darevay Really, the editor can't keep up? Ouch. ccw had similar issues until @cgrand's parsley saved the day. bit.ly/urSYwv
@darevay Really, the editor can't keep up? Ouch. ccw had similar issues until @cgrand's parsley saved the day. bit.ly/urSYwv