IMO, you definitely have your priorities straight, and I would question
whether Om ever needs to add a lot of sugar. When building any non-trivial
app, you will most likely end up creating your own abstractions anyway.
On Jan 28, 2014 7:59 PM, David Nolen dnolen.li...@gmail.com wrote:
People
Yes! This is good stuff.
Over the weekend, I started working on using Om for a potential real world
project and I quickly encountered the need for higher order polymorphic
components. Then I started worrying that maybe I had missed some fundamental
concept of Om/React and was complecting.
On Mon, Jan 27, 2014 at 12:48 PM, Mike Haney txmikes...@gmail.com wrote:
I was initially surprised by the implementation in your tutorial using
multimethods instead of protocols, especially since you are only
dispatching on a single function. But as I thought about it more, I
realized this
Did you get this fixed Rudi?
If your project file requires om 0.2.3, then it was something with the
lein new command (which is now fixed).
I recommend manually changing the project file to require om 0.3.0 and then
don't forget to lein cljscript clean before recompiling (which I did).
On
A by the way this is how it looks using Sablano/Kioo would be nice in the
tutorial.
On Mon, Jan 27, 2014 at 12:10 PM, David Nolen dnolen.li...@gmail.comwrote:
On Mon, Jan 27, 2014 at 12:48 PM, Mike Haney txmikes...@gmail.com wrote:
I was initially surprised by the implementation in your
om/join is conceptually quite cool, but it actually needs some serious work
as alluded - currently you're likely to run into some nasty surprises if
you really try to use it. The tutorials aren't going to proceed until this
is addressed sometime this week.
David
On Mon, Jan 27, 2014 at 1:28 PM,
I'm a big fan of this new tutorial.
It hi-lights some of the benefits of cursors, and I actually realize how I
might use om/join suddenly :D
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to
Yip - that fixed it for me - the behaviour of the delete button is now working
as per your tutorial.
On Sunday, January 26, 2014 6:52:46 AM UTC+11, David Nolen wrote:
You need to use 0.3.0 and you need to run `lein cljsbuild clean` before
running `lein cljsbuild auto`.
On Sat, Jan 25,
David, there's a confusing sentence in the paragraph before the om.core/root
header:
Everything in the atom should be an associative data structure - either a
ClojureScript map or indexed sequential data structure such as a vector, list
and lazy sequences are not allowed.
On Jan 26, 2014, at
I'm not Jamie, but I had to read that a few times to realize list and
lazy sequences are not allowed is another sentence, not a
continuation of the list of things that are allowed.
On Mon, Jan 27, 2014 at 1:35 AM, David Nolen dnolen.li...@gmail.com wrote:
What is unclear?
On Sun, Jan 26, 2014
Ah good point, I've clarified the tutorial.
On Sun, Jan 26, 2014 at 8:40 PM, Ivan Kozik i...@ludios.org wrote:
I'm not Jamie, but I had to read that a few times to realize list and
lazy sequences are not allowed is another sentence, not a
continuation of the list of things that are allowed.
I was following along with this and hit an interesting bug
The contact list delete button actually works out of the gate in the first
example, (when its supposed to fail) and when I add the deref in the next step
I get
Uncaught Error: No protocol method IDeref.-deref defined for type
I just now tried `lien new mies-om foo` which created a project that uses
0.3.0.
On Sat, Jan 25, 2014 at 2:59 PM, David Pidcock eraz0rh...@gmail.com wrote:
Ahh whoops. Forgot the clean step.
The lein new project imported 0.2.3 for me. I assume that has been fixed
then?
--
Note that posts
This tutorial was exactly what I needed, and hope to see more in the tutorial
as hinted at at the end.
I think I'm having a Light Table issue though. There is quite a few places
where you mention to try evaluating the functions. However, I think something
is messed up with my LightTable
Nothing wrong here. Light Table shows the result from the browser, that's
the source of the function you just evaluated. It's a quirk of
ClojureScript that's existed for some time - we might show something else
in the future.
On Sat, Jan 25, 2014 at 10:17 PM, Joel j...@harpsoft.com wrote:
This
15 matches
Mail list logo
