Re: GSoC 2015 - Better Clojure/Android integration project discussion
Hello, Thanks for your interest. On Sun Mar 8 17:17 2015, Devang Shah wrote: > This message is intended for suggester Daniel Solano Gómez, to initiate the > discussion on the project mentioned in the subject line. Please feel free > to jump in if you feel/wish to answer the questions or clarify points. > > I am interested in developing a plugin for the Clojure which will work in > conjunction to the Android plugin. As I understand the project idea, > > TODO: > 1. Develop functionality into the lein-droid (as an independent plugin) to > support Gradle build system. > 2. The new functionality has to be compatible with the current Android > plugin in lein-droid. > 3. Develop a "superset" and independent plugin to support build system and > integration of Clojure and Android. > 4. Since the new plugin will be integrated into the lein-driod, also modify > lein-droid to support the new plugin. I think these are the right steps, as a whole, but I think I would tackle them in the following order: 1. Develop a Clojure plug-in for the Gradle-based Android build system 2. Examine lein-droid's features and see which can or should be handled by the Android build system 3. Rewrite bits of lein-droid to use the new build system Aside from the work on developing the Gradle plug-in, the key bits is figuring out exactly what lein-droid does and how that maps onto what the new Android build system does. Additionally, would it be possible to generate a build.gradle file from the project.clj? > Questions (Project specific): > 5. Can you elaborate "Unfortunately, because the Android plugin replaces > the Java plugin, the current Clojure plugin doesn't work for Android." What > do you mean "replaces the Java plugin"? Gradle comes with a plug-in to compile Java. Clojuresque, the Clojure plug-in for Gradle depends on this Java plug-in. Unfortunately, the Android build system does away with the Java plug-in (the Android plug-in is in charge of compiling Java), so Clojuresque doesn't work there. This is why a new Clojure plug-in is needed. > Also, can someone highlight in brief some features (of Gradle plugin) that > we are planning to support? Any known features that are not supported by > the current build system? Ideally, you could just include the Clojure plug-in into an Android build.gradle, and it will handle all Clojure sources similarly to Android Java sources are handled (build types, etc.). It should also present all the necessary options to configure the plug-in, such as source directory locations, Clojure compiler options, etc. It would be good to review what Clojuresque supports. > Questions: (GSoC application specific): > 6. Where can I get the template for the application? > 7. What are all the things expected to be addressed in the application. Please refer to: http://dev.clojure.org/display/community/Student+application+guidelines Again, thank you for your interest. Please feel free to post to this e-mail list and the clojure-android list for more feedback on your idea. Sincerely, Daniel > > Thank you. > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > 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 clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
GSoC 2015 - Better Clojure/Android integration project discussion
This message is intended for suggester Daniel Solano Gómez, to initiate the discussion on the project mentioned in the subject line. Please feel free to jump in if you feel/wish to answer the questions or clarify points. I am interested in developing a plugin for the Clojure which will work in conjunction to the Android plugin. As I understand the project idea, TODO: 1. Develop functionality into the lein-droid (as an independent plugin) to support Gradle build system. 2. The new functionality has to be compatible with the current Android plugin in lein-droid. 3. Develop a "superset" and independent plugin to support build system and integration of Clojure and Android. 4. Since the new plugin will be integrated into the lein-driod, also modify lein-droid to support the new plugin. Questions (Project specific): 5. Can you elaborate "Unfortunately, because the Android plugin replaces the Java plugin, the current Clojure plugin doesn't work for Android." What do you mean "replaces the Java plugin"? Also, can someone highlight in brief some features (of Gradle plugin) that we are planning to support? Any known features that are not supported by the current build system? Questions: (GSoC application specific): 6. Where can I get the template for the application? 7. What are all the things expected to be addressed in the application. Thank you. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Pink 0.1.0, Score 0.2.0
Hi Mike, That's fantastic, thanks for sharing! It definitely looks useful. I've bookmarked the page and cloned the repo to study up on later. I'm not sure I'll be able to use the implementation directly as I'm not quite sure yet what direction I'll go with for implementing FFT's in Pink (I have a todo to explore getting Pink working in Clojurescript, which might affect what libraries I go with). imagez looks like it'd work very nicely for the pink-viz side though. Either way, I'll be sure to credit anything I use from your article and project. Thanks! steven On Sunday, March 8, 2015 at 6:40:40 PM UTC-4, Mikera wrote: > > Looks cool, thanks for sharing! > > Not sure how useful it is, but I wrote some code and a blog post a while > back about doing spectrograms in Clojure: > > https://clojurefun.wordpress.com/2013/12/22/spectrograms-with-overtone/ > > On Monday, 9 March 2015 02:36:27 UTC+8, Steven Yi wrote: >> >> Hi All, >> >> I'd like to announce the release of Pink 0.1.0 and Score 0.2.0: >> >> [kunstmusik/pink "0.1.0"] >> [kunstmusik/score "0.2.0"] >> >> Pink is an audio engine library, and Score is a library for >> higher-level music representations (e.g. notes, phrases, parts, >> scores). >> >> For more information, please see the projects' docs at: >> >> http://github.com/kunstmusik/pink >> http://github.com/kunstmusik/score >> >> and examples of using both at: >> >> http://github.com/kunstmusik/music-examples >> >> To note, this is the first stable version of Pink. I got into a bit >> of "let me add just one more feature..." but decided it was time >> enough to issue a release. Score's changes since 0.1.0 are primarily a >> better organization of files, as well as organizing music into >> measured and/or timed scores. See [1] for an example of measured >> score use. >> >> Next steps planned for Pink are some more unit generators (i.e. comb >> filter, convolution) and effects (i.e. reverbs). Next steps planned >> for Score are currently just adding Xenakis-style sieves. I've also >> been using plotting code enabled as a separate Leiningen profile in >> Pink, which I am planning to move to an additional library >> (tentatively called pink-viz). The plans for pink-viz are to collect >> useful functions for helping to write unit generators (i.e. >> oscilloscope, bode plot, FFT spectrogram). >> >> Thanks! >> steven >> >> [1] - >> https://github.com/kunstmusik/music-examples/blob/master/src/music_examples/track1.clj#L263 >> >> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: about macro exception : Unable to resolve classname: LinkedList, macro question and possible better approach
Sure, because you haven't quoted the symbol. If you write: > > (str *ns* ":" some-bus) > > ups!!, yes I forget quoted the symbol, thanks james!!... In Clojure, then Clojure will look for a variable called "some-bus". The > error you get is because it can't find such a variable. > > You want to either quote the symbol, or turn it into a string, e.g. > > (str *ns* ":" (quote ~bus-name)) > ; or > (str *ns* ":" ~(str bus-name)) > > - James > just now I'm gonna use the defbus macro, I preferred use a function instead for the other case based in your suggestion and works really well (I changed the async code for a more readable too :D)... -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Pink 0.1.0, Score 0.2.0
Looks cool, thanks for sharing! Not sure how useful it is, but I wrote some code and a blog post a while back about doing spectrograms in Clojure: https://clojurefun.wordpress.com/2013/12/22/spectrograms-with-overtone/ On Monday, 9 March 2015 02:36:27 UTC+8, Steven Yi wrote: > > Hi All, > > I'd like to announce the release of Pink 0.1.0 and Score 0.2.0: > > [kunstmusik/pink "0.1.0"] > [kunstmusik/score "0.2.0"] > > Pink is an audio engine library, and Score is a library for > higher-level music representations (e.g. notes, phrases, parts, > scores). > > For more information, please see the projects' docs at: > > http://github.com/kunstmusik/pink > http://github.com/kunstmusik/score > > and examples of using both at: > > http://github.com/kunstmusik/music-examples > > To note, this is the first stable version of Pink. I got into a bit > of "let me add just one more feature..." but decided it was time > enough to issue a release. Score's changes since 0.1.0 are primarily a > better organization of files, as well as organizing music into > measured and/or timed scores. See [1] for an example of measured > score use. > > Next steps planned for Pink are some more unit generators (i.e. comb > filter, convolution) and effects (i.e. reverbs). Next steps planned > for Score are currently just adding Xenakis-style sieves. I've also > been using plotting code enabled as a separate Leiningen profile in > Pink, which I am planning to move to an additional library > (tentatively called pink-viz). The plans for pink-viz are to collect > useful functions for helping to write unit generators (i.e. > oscilloscope, bode plot, FFT spectrogram). > > Thanks! > steven > > [1] - > https://github.com/kunstmusik/music-examples/blob/master/src/music_examples/track1.clj#L263 > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: about macro exception : Unable to resolve classname: LinkedList, macro question and possible better approach
On 8 March 2015 at 20:05, coco wrote: > >> I don't know what the rest of your function is supposed to be doing > > > you can check my second example > I'm afraid that doesn't explain you intend your function to do. You appear to be setting up some form of message passing system, but you don't explain to what purpose you're doing this, or why you're going about doing it in such an unusual fashion. The reason I ask is that there may be a far better way of solving your problem. > It only waits a specific value in the channel and do somehting...in this case > change an atom...I'm still curious about why I get that error when I declare > it likes macro but it works when it's a function > > It's probably because the return value from your macro was not valid Clojure code. I did this > > (defmacro defbus [bus-name args code] >`(eb/on-message (str *ns* ":" ~bus-name) (fn ~args ~code))) > > the macro-expansion looks ok but when I try use it..I get some-bus is not > defined..seems than it's trying evaluate the name..is it ok??..how can avoid > it??... > > Sure, because you haven't quoted the symbol. If you write: (str *ns* ":" some-bus) In Clojure, then Clojure will look for a variable called "some-bus". The error you get is because it can't find such a variable. You want to either quote the symbol, or turn it into a string, e.g. (str *ns* ":" (quote ~bus-name)) ; or (str *ns* ":" ~(str bus-name)) - James -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Chestnut 0.7.0
I ran into this same behavior, and then I realized it only happened if I run the "lein new" command if I'm *already in* a previously-created project created with "lein new chestnut". I'm guessing that something in the generated project.clj interferes some of the lein new behavior somehow. At any rate, running lein new in a directory without a project.clj file in it is working fine for me. Tim On Saturday, March 7, 2015 at 5:38:41 AM UTC-5, webber wrote: > > I tested the v 0.7.0 of chestnut and I encountered the following error. > The v 0.6.0 works fine. > > $ lein new chestnut test-app > Retrieving chestnut/lein-template/0.7.0/lein-template-0.7.0.pom from > clojars > Retrieving chestnut/lein-template/0.7.0/lein-template-0.7.0.jar from > clojars > Exception in thread "main" java.lang.ExceptionInInitializerError > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:270) > at clojure.lang.RT.loadClassForName(RT.java:2093) > at clojure.lang.RT.load(RT.java:430) > at clojure.lang.RT.load(RT.java:411) > at clojure.core$load$fn__5066.invoke(core.clj:5641) > at clojure.core$load.doInvoke(core.clj:5640) > at clojure.lang.RestFn.invoke(RestFn.java:408) > at clojure.core$load_one.invoke(core.clj:5446) > at clojure.core$load_lib$fn__5015.invoke(core.clj:5486) > at clojure.core$load_lib.doInvoke(core.clj:5485) > at clojure.lang.RestFn.applyTo(RestFn.java:142) > at clojure.core$apply.invoke(core.clj:626) > at clojure.core$load_libs.doInvoke(core.clj:5524) > at clojure.lang.RestFn.applyTo(RestFn.java:137) > at clojure.core$apply.invoke(core.clj:626) > at clojure.core$require.doInvoke(core.clj:5607) > at clojure.lang.RestFn.invoke(RestFn.java:421) > at stencil.core$loading__4958__auto__.invoke(core.clj:1) > at stencil.core__init.load(Unknown Source) > at stencil.core__init.(Unknown Source) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:270) > at clojure.lang.RT.loadClassForName(RT.java:2093) > at clojure.lang.RT.load(RT.java:430) > at clojure.lang.RT.load(RT.java:411) > at clojure.core$load$fn__5066.invoke(core.clj:5641) > at clojure.core$load.doInvoke(core.clj:5640) > at clojure.lang.RestFn.invoke(RestFn.java:408) > at clojure.core$load_one.invoke(core.clj:5446) > at clojure.core$load_lib$fn__5015.invoke(core.clj:5486) > at clojure.core$load_lib.doInvoke(core.clj:5485) > at clojure.lang.RestFn.applyTo(RestFn.java:142) > at clojure.core$apply.invoke(core.clj:626) > at clojure.core$load_libs.doInvoke(core.clj:5524) > at clojure.lang.RestFn.applyTo(RestFn.java:137) > at clojure.core$apply.invoke(core.clj:626) > at clojure.core$require.doInvoke(core.clj:5607) > at clojure.lang.RestFn.invoke(RestFn.java:512) > at leiningen.new.templates$loading__4958__auto__.invoke(templates.clj:11) > at leiningen.new.templates__init.load(Unknown Source) > at leiningen.new.templates__init.(Unknown Source) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:270) > at clojure.lang.RT.loadClassForName(RT.java:2093) > at clojure.lang.RT.load(RT.java:430) > at clojure.lang.RT.load(RT.java:411) > at clojure.core$load$fn__5066.invoke(core.clj:5641) > at clojure.core$load.doInvoke(core.clj:5640) > at clojure.lang.RestFn.invoke(RestFn.java:408) > at clojure.core$load_one.invoke(core.clj:5446) > at clojure.core$load_lib$fn__5015.invoke(core.clj:5486) > at clojure.core$load_lib.doInvoke(core.clj:5485) > at clojure.lang.RestFn.applyTo(RestFn.java:142) > at clojure.core$apply.invoke(core.clj:626) > at clojure.core$load_libs.doInvoke(core.clj:5524) > at clojure.lang.RestFn.applyTo(RestFn.java:137) > at clojure.core$apply.invoke(core.clj:626) > at clojure.core$require.doInvoke(core.clj:5607) > at clojure.lang.RestFn.invoke(RestFn.java:512) > at leiningen.new$loading__4958__auto__.invoke(new.clj:1) > at leiningen.new__init.load(Unknown Source) > at leiningen.new__init.(Unknown Source) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:270) > at clojure.lang.RT.loadClassForName(RT.java:2093) > at clojure.lang.RT.load(RT.java:430) > at clojure.lang.RT.load(RT.java:411) > at clojure.core$load$fn__5066.invoke(core.clj:5641) > at clojure.core$load.doInvoke(core.clj:5640) > at clojure.lang.RestFn.invoke(RestFn.java:408) > at clojure.core$load_one.invoke(core.clj:5446) > at clojure.core$load_lib$fn__5015.invoke(core.clj:5486) > at clojure.core$load_lib.doInvoke(core.clj:5485) > at clojure.lang.RestFn.applyTo(RestFn.java:142) > at clojure.core$apply.invoke(core.clj:626) > at clojure.core$load_libs.doInvoke(core.clj:5524) > at clojure.lang.RestFn.applyTo(RestFn.java:137) > at clojure.core$apply.invoke(core.clj:626) > at clojure.core$require.doInvoke(core.clj:5607) > at clojure.lang.RestFn.invoke(RestFn.java:408) > at leiningen.core.utils$require_resolve.invoke(utils.clj:80) > at leiningen.core.utils$require_resolve.invoke(utils.clj:83) > at leiningen.core.main$lookup_task_var.invoke(main.clj:68) > at leiningen.core.main$pass
Re: about macro exception : Unable to resolve classname: LinkedList, macro question and possible better approach
> > All your macro needs to do is to convert the first form into the second. > thanks james, that make sense for me... > I don't know what the rest of your function is supposed to be doing you can check my second example (def data (atom "")) (defmacro blahhh [] (go (let [ch (chan)] (do (loop [] (let [res (>" res) (reset! data res)) (recur) (do(doseq [word ["blah" "bang" "secret" "goal"]] (put! ch word)) It only waits a specific value in the channel and do somehting...in this case change an atom...I'm still curious about why I get that error when I declare it likes macro but it works when it's a function 3) I've this other code (defmacro defbus [bus-name args code] `(eb/on-message (str *ns* ":" ~bus-name) (fn ~args ~code))) basically I need convert from this (defbus some-bus [a] (eb/reply (str ">>" a))) to this (eb/on-message "some-namespace:some-bus" (fn [a](eb/reply (str ">>" a I did this (defmacro defbus [bus-name args code] `(eb/on-message (str *ns* ":" ~bus-name) (fn ~args ~code))) or (defmacro def-bus [bus-name args code] `(let [fun# (fn ~args ~code)] (eb/on-message (str *ns* ~bus-name) fun#))) the macro-expansion looks ok but when I try use it..I get some-bus is not defined..seems than it's trying evaluate the name..is it ok??..how can avoid it??... thanks again james -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[ANN] Pink 0.1.0, Score 0.2.0
Hi All, I'd like to announce the release of Pink 0.1.0 and Score 0.2.0: [kunstmusik/pink "0.1.0"] [kunstmusik/score "0.2.0"] Pink is an audio engine library, and Score is a library for higher-level music representations (e.g. notes, phrases, parts, scores). For more information, please see the projects' docs at: http://github.com/kunstmusik/pink http://github.com/kunstmusik/score and examples of using both at: http://github.com/kunstmusik/music-examples To note, this is the first stable version of Pink. I got into a bit of "let me add just one more feature..." but decided it was time enough to issue a release. Score's changes since 0.1.0 are primarily a better organization of files, as well as organizing music into measured and/or timed scores. See [1] for an example of measured score use. Next steps planned for Pink are some more unit generators (i.e. comb filter, convolution) and effects (i.e. reverbs). Next steps planned for Score are currently just adding Xenakis-style sieves. I've also been using plotting code enabled as a separate Leiningen profile in Pink, which I am planning to move to an additional library (tentatively called pink-viz). The plans for pink-viz are to collect useful functions for helping to write unit generators (i.e. oscilloscope, bode plot, FFT spectrogram). Thanks! steven [1] - https://github.com/kunstmusik/music-examples/blob/master/src/music_examples/track1.clj#L263 -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Better/more idiomatic way to read EDNs than using java.io.PushbackReader
I've done something like: (clojure.edn/read-string (slurp (clojure.java.io/resource edn-file))) This of course assumes the file resides in `/resources`. On Friday, March 6, 2015 at 8:18:03 PM UTC-7, Sam Raker wrote: > > I'm experimenting a little with EDN files. I've currently got this > function: > > (defn from-edn [edn-file] (with-open [r (clojure.java.io/reader edn-file)] > (edn/read (java.io.PushbackReader. r > > Having to explicitly reach into the Java API to read a clojure-only format > seems wrong. What should I be doing instead? > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Who's using Clojure?
On 06/03/2015 10:46, Fergal Byrne wrote: Clojure is winning one dev at a time. There are almost no cases of teams switching back to Java or Scala once they've worked with Clojure for a while. The same cannot be said for Groovy or Scala, which are being abandoned in good numbers. What's your source evidence for these assertions? gvim -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Diagnosing a figwheel error
Can you post your project.clj and your folder structure? You might have your `:http-server-root` pointing to the wrong place. To see a working configuration try `lein new fighweel your-project-name` and you'll get a template with figwheel ready to go. On Saturday, March 7, 2015 at 11:47:19 PM UTC+1, Jonathon McKitrick wrote: > > I decided to ditch piggieback/weasel and try figwheel, and though it > starts without errors, I get 'Page not found' when visiting localhost:3449. > > What's the best way to track down the cause? > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
