<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
I have provided a bit more information and bumped the version to
v0.0.2.<br>
<br>
Instructions for how to use Chronos with rebar is now given.<br>
<br>
Cheers,<br>
Torben<br>
<br>
On 25/2/12 20:37 , Torben Hoffmann wrote:
<blockquote cite="mid:4F49388E.5010201@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<br>
On 25/2/12 13:28 , Kirill Zaborsky wrote:
<blockquote
cite="mid:CAGMng39BwGMRBvBhj9-U_7BGCBwOJCMAMUzZnfJTT9VGekRjXg@mail.gmail.com"
type="cite">I think it can be seen in <a moz-do-not-send="true"
href="https://github.com/lehoff/chronos/commit/b9612ea73090f8037b47dc9b77045b3344df05cd">https://github.com/lehoff/chronos/commit/b9612ea73090f8037b47dc9b77045b3344df05cd</a>
<div>BTW I do not understand why rebar support was removed (I
think it's not a problem to have a branch with rebar support
for people who use it).</div>
</blockquote>
Chronos wil build with rebar as it is right now - I tested that.
Given the lack of a rebar.config file it will not grab gproc, but
there is a reason for this.<br>
<br>
I took out the rebar.config since I doubt I will ever have a
specific version need for gproc, so instead of imposing a specific
version or just run with the latest I wanted to make it clear that
the user has to try things out and handle potential conflicting
needs for gproc. <br>
<br>
I had all the good intentions of clearly explaining this, but as
you all know the road to hell is paved with good intentions...<br>
<br>
I will provide a pseudo .rel file and an INSTALL file so that it
becomes clear to people how to use Chronos.<br>
<br>
Cheers,<br>
Torben<br>
<br>
<blockquote
cite="mid:CAGMng39BwGMRBvBhj9-U_7BGCBwOJCMAMUzZnfJTT9VGekRjXg@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>Kind regards,</div>
<div>Kirill Zaborsky<br>
<br>
<div class="gmail_quote">2012/2/25 Zabrane Mickael <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:zabrane3@gmail.com">zabrane3@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Hi Torben,
<div><br>
</div>
<div>It seems that <b>chronos</b> depends on <b>gproc</b>.
Right?</div>
<div><br>
</div>
<div>Which version of <b>gproc</b> are you using as
there are plenty of forks on github?</div>
<div><a moz-do-not-send="true"
href="https://github.com/uwiger/gproc/network"
target="_blank">https://github.com/uwiger/gproc/network</a></div>
<div><br>
</div>
<div>Nice work ...</div>
<div><br>
</div>
<div>N.B: IMHO, you should adapt the doc accordingly</div>
<div><br>
</div>
<div>
<div>
<div>Regards,</div>
<div>Zabrane</div>
<div><br>
</div>
</div>
<div>
<div>On Feb 24, 2012, at 9:00 AM, Torben Hoffmann
wrote:</div>
<br>
<blockquote type="cite">
<div>To whom it may concern.<br>
<br>
I have released Chronos-0.0.1 at <a
moz-do-not-send="true"
href="https://github.com/lehoff/chronos"
target="_blank">https://github.com/lehoff/chronos</a><br>
<br>
Chronos is a small timer utility that can help
deal with timers without too much bookkeeping
and suggest a design of components that makes it
easy to test the functionality of timers without
having to wait for them to expire.<br>
<br>
There is also a short overview of the existing
timer solutions since you might have a problem
that is better solved with something else than
Chronos.<br>
<br>
Chronos comes with a QuickCheck test suite and
an example of how to abstract time from your
tests.<br>
<br>
Feedback is most welcome!<br>
<br>
Cheers,<br>
Torben<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
<a moz-do-not-send="true"
href="http://www.linkedin.com/in/torbenhoffmann"
target="_blank">http://www.linkedin.com/in/torbenhoffmann</a><br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a moz-do-not-send="true"
href="mailto:erlang-questions@erlang.org"
target="_blank">erlang-questions@erlang.org</a><br>
<a moz-do-not-send="true"
href="http://erlang.org/mailman/listinfo/erlang-questions"
target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</font></span></div>
</blockquote>
</div>
<br>
<div><span
style="text-indent:0px;letter-spacing:normal;font-variant:normal;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"></span></div>
</div>
</div>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a moz-do-not-send="true"
href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a moz-do-not-send="true"
href="http://erlang.org/mailman/listinfo/erlang-questions"
target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.linkedin.com/in/torbenhoffmann">http://www.linkedin.com/in/torbenhoffmann</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/torbenhoffmann">http://www.linkedin.com/in/torbenhoffmann</a></pre>
</body>
</html>