Re: clojurescript, sourcemaps, and debugging info

2014-05-18 Thread t x
On Sun, May 18, 2014 at 7:25 AM, Timothy Baldridge wrote: >>> foo.cljs >>> foo/whatever.cljs >>> bar.cljs >>> bar/stuff.cljs > > yes, do this, it also matches what most of the Clojure community does. > I'm convinced. Using this style now. > > On Sun, May 18, 2014 at 4:16 AM, Thomas Heller wro

Re: clojurescript, sourcemaps, and debugging info

2014-05-18 Thread Timothy Baldridge
>> foo.cljs >> foo/whatever.cljs >> bar.cljs >> bar/stuff.cljs yes, do this, it also matches what most of the Clojure community does. On Sun, May 18, 2014 at 4:16 AM, Thomas Heller wrote: > Don't think plugins can touch the devtools. > > I tend to organize my code that the public "interface" o

Re: clojurescript, sourcemaps, and debugging info

2014-05-18 Thread Thomas Heller
Don't think plugins can touch the devtools. I tend to organize my code that the public "interface" of foo reside in foo.cljs and the implementation details go into foo/something.cljs so in your case you'd get foo.cljs foo/whatever.cljs bar.cljs bar/stuff.cljs Maybe an alternative solution to y

Re: clojurescript, sourcemaps, and debugging info

2014-05-17 Thread t x
flat namespace is ugly. Someone please please tell me there is a better solution. :-) Is there no 10-line chrome-plugin which solves this? On Fri, May 16, 2014 at 7:35 AM, t x wrote: > Bah, I've reverted to a flat namespace, i.e. foo_internal.cljs, > foo_public.cljs, bar_internal.cljs, bar_public

Re: clojurescript, sourcemaps, and debugging info

2014-05-16 Thread t x
Bah, I've reverted to a flat namespace, i.e. foo_internal.cljs, foo_public.cljs, bar_internal.cljs, bar_public.cljs ... :-) On Fri, May 16, 2014 at 6:24 AM, Tim Visher wrote: > Seems worth a bug report/feature request to the Chrome Dev Tools team. > > On Thu, May 15, 2014 at 11:45 PM, t x wrote:

Re: clojurescript, sourcemaps, and debugging info

2014-05-16 Thread Tim Visher
Seems worth a bug report/feature request to the Chrome Dev Tools team. On Thu, May 15, 2014 at 11:45 PM, t x wrote: > Hi, > > * background: > > * I have clojurescript + lein cljsbuild auto working perfectly fine. > > * I have source maps working (when I click on a file in Chrome, it > jumps m

Re: clojurescript, sourcemaps, and debugging info

2014-05-16 Thread Thomas Heller
Its Chrome, no way around it AFAICT. FWIW you can mouseover the filename in the console and the title popup will show the entire URL to the file. On Friday, May 16, 2014 5:45:28 AM UTC+2, t x wrote: > > Hi, > > * background: > > * I have clojurescript + lein cljsbuild auto working perfectly f

clojurescript, sourcemaps, and debugging info

2014-05-15 Thread t x
Hi, * background: * I have clojurescript + lein cljsbuild auto working perfectly fine. * I have source maps working (when I click on a file in Chrome, it jumps me to the corresponding *.cljs file) * problem I am facing: * I like to name my modules: foo/public.cljs foo/other-stu