[ANN] chic-text 0.2.0 - Helpful functions for formatting console output
chic-text http://www.ryanmcg.com/chic-text/ is a library of functions that formats strings for console output. It allows content to be specified in columns (sequence of strings) or functions of a collection (one function per column, one item in the collection per row). It even defines a summary-fn for integration http://www.ryanmcg.com/chic-text/#clojure.tools.cli-integration with clojure.tools.cli https://github.com/clojure/tools.cli. I am using this in incise http://www.ryanmcg.com/incise/. This library was spun off of that project, so yeah, it is small and simple, but I figured others could benefit from it. I'd be happy for any feedback/contribution. Thanks! - Main - http://www.ryanmcg.com/chic-text/ - API - http://www.ryanmcg.com/chic-text/api/ - Source - https://github.com/RyanMcG/chic-text -- 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] Dunaj project, an alternative core API for Clojure
Thank you. Based on your suggestion I've added disqus commenting there. On Saturday, March 7, 2015 at 8:38:14 AM UTC+1, Bozhidar Batsov wrote: You might want to add some commenting capabilities to those articles. They'll be more valuable in the context of discussions IMO. On 6 March 2015 at 18:49, Jozef Wagner jozef@gmail.com javascript: wrote: Experiment #1 *Deconstructing Core API* While Clojure provides its functionalities in multiple namespaces (e.g. clojure.string, clojure.zip), the majority of it is defined in a single namespace called clojure.core. The first Dunaj experiment explores the idea of having multiple small namespaces where functions, macros and other public vars are grouped by their purpose. It investigates whether such separation is possible at all and whether it can be practical and useful. The goals of the first Dunaj experiment are as follows: - Devise a new user centric core API comprising multiple namespaces, leaving bootstrapping and low level vars in the clojure.core. - Define a concept of API presets that control which functions, macros and vars gets referred by default. - Let user choose which API preset he/she wants to use in his/hers namespace, using classic clojure.core as a default. The upside of this approach is that backwards compatibility is maintained and users can freely intermix multiple APIs in their projects. Functionalities can be more logically separated by their purpose. List of automatically referred vars are no longer driven by the namespace in which they were defined, but this list is handled by separate API presets that can be extended and customized. You can read more about this experiment at http://www.dunaj.org -- Jozef On Thu, Mar 5, 2015 at 10:33 PM, Jozef Wagner jozef@gmail.com javascript: wrote: I'm happy to announce a project called Dunaj [1], which provides an alternative core API for Clojure. Its main aim is to experimentally test major additions to the language. Dunaj /ˈdunaɪ/ is a set of core language experiments aimed to improve Clojure language and its core API. It deals with language features that require changes across different parts of Clojure and which cannot be evaluated in isolation. Dunaj aims to bring Clojure even more towards simplicity, consistency and performance. It is intended to be used by regular Clojure developers, either for application or library development. Dunaj was created to test 10 experiments that bring significant changes to the Clojure language. As there is a substantial number of additions and changes, I want to try a bit unconventional approach here. Before I'll release the actual library, I will introduce Dunaj's experiments in a series of individual posts. Every part states the motivation behind the experiment, introduces changes and additions to the language and demonstrates its intended use. If you do not want to miss any of this, you may want to register for a mailing list at [1] or follow @dunajproject at Twitter. -- Jozef Wagner [1] http://www.dunaj.org/ -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clo...@googlegroups.com javascript: Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+u...@googlegroups.com javascript: 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+u...@googlegroups.com javascript:. 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.
Re: State of Simulation Testing Survey - 2015
Hey again, I just wanted to let everyone know that I've published the results of the 2015 Simulation Testing survey. You can find them here: http://www.rkn.io/2015/03/07/state-of-sim-testing-results/ -Ryan On Tuesday, February 3, 2015 at 8:40:14 PM UTC-6, Ryan Neufeld wrote: Hey folks! As you probably know, there's always lots of new and exciting developments in Clojure-land. One, more recent technique that has me really excited has been *Simulation Testing*. I've used Simulant to implement simulation tests on a few projects this last year with great success, and I'm really curious to hear about if/how others are using the technique. To that end, I've put together a survey on sim-testing–*The State of Simulation Testing*–that I hope can become an annual fixture both inside and outside of the Clojure community. Once the ballots have closed on February 20th, I'll tally and report upon the results on my blog. If you've considered, implemented or even out-right rejected simulation testing, I'm curious to hear more from you: http://bit.ly/state-of-sim-testing-2015 Thanks for your time, Ryan Neufeld -- 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.
Has anyone seen this error with weasel/piggieback?
Can't change/establish root binding of: *cljs-repl-options* with set when evaluating (piggieback/cljs-repl :repl-env (weasel/repl-env :ip 0.0.0.0 :port 9001)) -- 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] Dunaj project, an alternative core API for Clojure
While the first experiment took long to implement, it was fairly easy to understand and I think we can move on to the second one. Second Dunaj experiment adds support for optional type signatures that can be used to annotate functions, protocol methods, type fields and local bindings. These type signatures are then used to automatically generate host type hints. At run-time, type signatures are stored in vars' metadata, available for third party type checking, data validation and documentation tools. Goals of the second Dunaj experiment are as follows: - Provide developers with a means to document type signatures for functions, protocol methods, let-like bindings and deftype fields. - Automatically generate type hints from provided type signatures, including primitive ones. - Open up type signatures for custom extensions and use in third party data validation and type checking tools. Dunaj aims to decomplect type declarations from type checking tools. It provides conventions and syntax extensions for defining type signatures, while leaving their exact interpretation to other libraries. Existing protocols, types and host classes can all be used as type declarations. By generating type hints automatically, users do not have to write types twice (first time as a type signature and second time as a type hint). Specifying type signatures does not produce any run-time overhead, as all processing is done at a macro expansion time. As I don't want to write long emails here, you can read more about this experiment at http://www.dunaj.org . Best, Jozef On Thursday, March 5, 2015 at 10:33:53 PM UTC+1, Jozef Wagner wrote: I'm happy to announce a project called Dunaj [1], which provides an alternative core API for Clojure. Its main aim is to experimentally test major additions to the language. Dunaj /ˈdunaɪ/ is a set of core language experiments aimed to improve Clojure language and its core API. It deals with language features that require changes across different parts of Clojure and which cannot be evaluated in isolation. Dunaj aims to bring Clojure even more towards simplicity, consistency and performance. It is intended to be used by regular Clojure developers, either for application or library development. Dunaj was created to test 10 experiments that bring significant changes to the Clojure language. As there is a substantial number of additions and changes, I want to try a bit unconventional approach here. Before I'll release the actual library, I will introduce Dunaj's experiments in a series of individual posts. Every part states the motivation behind the experiment, introduces changes and additions to the language and demonstrates its intended use. If you do not want to miss any of this, you may want to register for a mailing list at [1] or follow @dunajproject at Twitter. -- Jozef Wagner [1] http://www.dunaj.org/ -- 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 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 mine 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 Generating fresh Chestnut project. README.md contains instructions to get you started. $ -- 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 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.clinit(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.clinit(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.clinit(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_through_help_QMARK_.invoke(main.clj:78) at leiningen.core.main$task_args.invoke(main.clj:81) at leiningen.core.main$resolve_and_apply.invoke(main.clj:318) at leiningen.core.main$_main$fn__6160.invoke(main.clj:392) at leiningen.core.main$_main.doInvoke(main.clj:385) at clojure.lang.RestFn.invoke(RestFn.java:436) at clojure.lang.Var.invoke(Var.java:388) at clojure.lang.AFn.applyToHelper(AFn.java:160) at clojure.lang.Var.applyTo(Var.java:700) at clojure.core$apply.invoke(core.clj:624) at clojure.main$main_opt.invoke(main.clj:315) at clojure.main$main.doInvoke(main.clj:420) at clojure.lang.RestFn.invoke(RestFn.java:482) at
Re: [OT?] Best DB/architecture for n-gram corpus?
On 7 March 2015 at 00:25, Sam Raker sam.ra...@gmail.com wrote:
I'm trying to create an n-gram[1] corpus out of song lyrics. I'm breaking
individual songs into lines, which are then split into words, so you end up
with something like
{0 {0 go 1 tell 2 aunt 3 rhodie} 1 {0 the 1 old 2 grey 3
goose 4 is 5 dead}...}
Why split into lines? In this example, rhodie the is just as valid a
bigram as tell aunt. It would be more natural to split at a sentence
boundary.
(Yes, maps with integer keys is kind of dumb; I thought about using vectors,
but this is all going into MongoDB temporarily, and I'd rather just deal
with maps instead of messing with Mongo's somewhat lacking array-handling
stuff.)
The idea, ultimately, is to build a front-end that would allow users to,
e.g., search for all songs that contain the (sub)string aunt rhodie, or
see how many times The Rolling Stones use the word woman vs how many times
the Beatles do, etc. The inspiration comes largely from projects like
COCA[2].
I'm wondering if any of you have opinions about which database to use (Mongo
is most likely just a stopgap), and how best to architect it. I'm most
familiar with MySQL and Mongo, but I'd rather not be limited by just those
two if there's a better option out there.
First up, I think you'll likely want to trade space for speed, and the
simplest way to do this is to store every n-gram you're interested in.
This means deciding up-front the maximum size of the n-gram you're
interested in. You could fairly easily model this in any relational
database as:
tracks
id (serial, primary key)
name (text)
n_grams
id (serial, primary key)
n (integer)
n_gram (text)
track_n_gram
---
track (references tracks.id)
n_gram (references n_grams.id)
num_occurrences (integer)
With that schema, you should be able to answer all of the queries you
posed with some simple SQL.
Of course, this being the Clojure mailing list you should also
consider Datomic, and I think the above could be mapped to a Datomic
schema without too much effort.
Ray.
--
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: [OT?] Best DB/architecture for n-gram corpus?
A lot of guys would use Lucene. Lucene calls n-grams of words shingles. [1] As for architecture, here is a suggestion to use Lucene to find keys to records in your real database. [2] [1] https://lucidworks.com/blog/whats-a-shingle-in-lucene-parlance/ [2] https://groups.google.com/d/msg/datomic/8yrCYxcQq34/GIomGaarX5QJ -- 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
Vote for clojure.java.io/pushback-reader http://dev.clojure.org/jira/browse/CLJ-1611 ? That enhancement suggestion contains links to some previous discussions on the subject. On Friday, March 6, 2015 at 10:18:03 PM UTC-5, 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: Diagnosing a cljsbuild error
Could it be because of the :runner keyword you have in the vector? On Sat, Mar 7, 2015 at 2:20 PM Jonathon McKitrick jmckitr...@gmail.com wrote: Any thoughts as to why `lein cljsbuild test` would generate an error like this? Invalid :test-command, contains non-string value: [phantomjs :runner resources/es5-shim.js resources/public/js/test.js] -- 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.
Re: Has anyone seen this error with weasel/piggieback?
I have but ended up giving up on it and moving to using figwheel's REPL. You might want to reply to the topic I started over on clojure-tools: https://groups.google.com/forum/#!topic/clojure-tools/8C93CstHqpU. :A. On Sat, Mar 7, 2015 at 12:17 PM Jonathon McKitrick jmckitr...@gmail.com wrote: Can't change/establish root binding of: *cljs-repl-options* with set when evaluating (piggieback/cljs-repl :repl-env (weasel/repl-env :ip 0.0.0.0 :port 9001)) -- 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.
[ANN] clecs 2.0.0
clecs is an entity component system library. Repo is here: https://github.com/muhuk/clecs API documentation is here: http://clecs.muhuk.com/2.0.x/api/ Changelog is here: http://clecs.muhuk.com/2.0.x/user_guide/#_changelog This version comes with some major changes which will hopefully make working with clecs easier. -- Kind Regards, Atamert Ölçgen -+- --+ +++ www.muhuk.com -- 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.
Diagnosing a figwheel error
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.
Diagnosing a cljsbuild error
Any thoughts as to why `lein cljsbuild test` would generate an error like this? Invalid :test-command, contains non-string value: [phantomjs :runner resources/es5-shim.js resources/public/js/test.js] -- 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 cljsbuild error
Might want to diff the two project.clj files and see what you come up with. On Sat, Mar 7, 2015 at 3:22 PM Jonathon McKitrick jmckitr...@gmail.com wrote: I'm sure that's related, but the tests don't run without it. I went back to a working project.clj and started over, and it works now, but I'm trying to understand the cause of the error to begin with. On Saturday, March 7, 2015 at 4:13:56 PM UTC-5, Akiva Schoen wrote: Could it be because of the :runner keyword you have in the vector? On Sat, Mar 7, 2015 at 2:20 PM Jonathon McKitrick jmcki...@gmail.com wrote: Any thoughts as to why `lein cljsbuild test` would generate an error like this? Invalid :test-command, contains non-string value: [phantomjs :runner resources/es5-shim.js resources/public/js/test.js] -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clo...@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+u...@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+u...@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. -- 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 cljsbuild error
I'm sure that's related, but the tests don't run without it. I went back to a working project.clj and started over, and it works now, but I'm trying to understand the cause of the error to begin with. On Saturday, March 7, 2015 at 4:13:56 PM UTC-5, Akiva Schoen wrote: Could it be because of the :runner keyword you have in the vector? On Sat, Mar 7, 2015 at 2:20 PM Jonathon McKitrick jmcki...@gmail.com javascript: wrote: Any thoughts as to why `lein cljsbuild test` would generate an error like this? Invalid :test-command, contains non-string value: [phantomjs :runner resources/es5-shim.js resources/public/js/test.js] -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clo...@googlegroups.com javascript: Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+u...@googlegroups.com javascript: 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+u...@googlegroups.com javascript:. 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.
Re: Diagnosing a figwheel error
Unless I'm misunderstanding, this sounds like a routing issue. If you're going directly through Figwheel without a Ring server, you'll need something like Secretary to do the routing. Otherwise, you can configure Figwheel to interact with the Ring server's port and simply not use 3449 at all. This is how I go about things. On Sat, Mar 7, 2015 at 4:47 PM Jonathon McKitrick jmckitr...@gmail.com 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. -- 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
Sounds like you are fighting with project.clj. You'd be better off going with a template like chestnut as a learning tool. On Saturday, March 7, 2015 at 5:47:19 PM UTC-5, 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.
