I have separated the code for reactive atoms, cursors and expressions from
freactive (https://github.com/aaronc/freactive) into a separate
freactive.core library: https://github.com/aaronc/freactive.core.
The code for these data structures has evolved significantly since I
released freactive, howe
Finally, an official release of fx-clj, my Clojure library for JavaFX:
https://github.com/aaronc/fx-clj.
I've been using it for quite a number of months now and most of the core
functionality is pretty stable.
This library works with my freactive.core (
https://github.com/aaronc/freactive.core) r
freactive (pronounced "f reactive" for functional reactive) is a new high
performance, pure Clojurescript, declarative DOM library:
https://github.com/aaronc/freactive
It has a syntax very similar to that of Reagent and was in fact inspired by
Reagent, Om, and others.
I came up with it when I was
> Do I correctly understand, that freactive does not care about tag names, and
> I can use any ones (potentially injecting polymer or smth like pieces)?
>
Yes! It tries to work with pure DOM nodes wherever possible. In freactive,
Clojurescript vectors are virtual DOM - so the "hiccup" vectors
On Monday, November 17, 2014 9:19:29 AM UTC-5, Max Gonzih wrote:
> Wow! Amazing! I see some ClojureCLR code in this repository, but from brief
> look it's not clear why is it there. Are you also experimenting on CLR
> support?
>
Yes, I'm not sure if it's in a working state right now, but I was
On Monday, November 17, 2014 12:02:32 PM UTC-5, Diogo Almeida wrote:
> This is really cool (especially if what Ruslan said is the case). What would
> the best practice be for stateful effects? Do you have any plans of adding
> the equivalent of React's lifecycle methods?
So I plan to write more
On Monday, November 17, 2014 2:32:18 PM UTC-5, Shaun LeBron wrote:
> How does it perform its dom-diffing?
So, it does not actually do diffing. It is very close to being able to, but if
this is added it will be sort of an extra optimization as opposed to a "core"
algorithm.
Instead of diffing, c
On Monday, November 17, 2014 2:27:17 PM UTC-5, Ruslan Prokopchuk wrote:
> I've played a little bit with freactive today, and investigated this idea
> with using polymer components — it works! I'm unsure of right usage of rx,
> especially on conditional rendering — (rx (if @state ... does
> autor
Hi Niels,
It is true that this comparison is a bit stacked because basically
freactive only modifies the needed attributes without needing to diff the
whole structure. I'm not sure if I understand totally your other questions
- maybe you could clarify a little.
Regarding diffing - in terms of rer
Fresco isn't bad. I think it's better than "freactive" at least. Seems to
be relatively popular for a name, but no big projects:
https://github.com/search?o=desc&p=1&q=fresco&s=stars&type=Repositories&utf8=✓
On Sun, Nov 23, 2014 at 3:05 AM, Olli Piepponen wrote:
> If you are open to name suggest
;re known as highly reactive elements.
> Precipitate: both a noun and a verb, the solid that falls out of a solution,
> or to bring about such a reaction.
>
>
> Other chemical-ish names considered
> Enantiopure - Containing compounds of only a single chirality
> Fullerene - Bucky
On Monday, November 24, 2014 3:49:22 PM UTC-5, Andrew Rosa wrote:
> Aaron,
>
> Still need to study the more detailed docs, but from what I read from UI-SPEC
> the only thing I get confused about was the event/lifecycle.
Okay - that's something that would be platform-specific. It's still being
So, you've made a good observation about the spec - it doesn't proscribe
any convention for dealing with sequences of items. The reason for this is
pretty much that the DOM is the only modern UI framework that I've worked
with that doesn't include something like an "items view". So, I understand
th
?
> Should this be done in a different way?
>
> Best Regards,
> Sven
>
> Am Montag, 17. November 2014 03:20:29 UTC+1 schrieb Aaron Craelius:
> > freactive (pronounced "f reactive" for functional reactive) is a new
> high performance, pure Clojurescript, declarative
I've just posted gists about the items-view and observable collections proposed
for freactive.
In case anyone is interested in discussing please comment on the gists
themselves.
observable collections: https://gist.github.com/aaronc/0654151190b9145dd473
items-view: https://gist.github.com/aaron
o wrap
> forms in (rx ...) all the time.
>
> - What is the rationale behind the second argument "callback" (to one of
> :on-hide or :on-show)? I noticed that sometimes it is passed and sometimes
> it isn't and that I have to call it when it is passed...
>
&g
Hi Rainer, glad you're checking this out. This code (as I believe I
mentioned above) requires a special build of the ClojureCLR compiler (see
this github branch https://github.com/aaronc/clojure-clr - I just merged it
with the clojure-clr master). I'm going to try to make some effort today
to see
On Fri, Mar 1, 2013 at 6:48 PM, Rainer Schuster wrote:
> 2. I assume, you created your a nuget and added it to a local repo. I
> don't have one and don't know what version you are using.
> 3. I deleted the Clojure and Nuget.Core dependency. Using Stable
> Nuget.Core Version 2.2.0 but thats not an
My Clojure.dll shouldn't break ngen. I ilmerge'd it from AOT compiled
assemblies - it doesn't use embedded assemblies which would break ngen.
For me ngen seems to work fine. Open up the Clojure.dll from nuget in
Ilspy or DotPeek to see how it's done. Btw, I just posted a new build on
nuget toda
Not yet. I'll have to take care of that.
On Mon, Mar 19, 2012 at 5:48 PM, David Nolen wrote:
> On Mon, Mar 19, 2012 at 1:36 PM, Aaron wrote:
>
>> I pushed the patch to my fork on github in this commit:
>> https://github.com/aaronc/clojurescript/commit/3193ed6e27061765782da32d36a63b0f7630f5e9
>
I tried it a while back and couldn't get it working, but I have since heard
that it was updated. I wouldn't be the one to ask though. In my case, I
prefer Emacs for editing lisp and it is much lighter on system resources
than Visual Studio.
On Thu, Sep 6, 2012 at 10:55 PM, Erlis Vidal wrote:
>
Ok, sounds good. I can do that. I have 2-3 pretty specific changes that I
can outline. I also have one bug fix (support for IntPtr and UIntPtr in
HostExpr). Should I maybe start a separate thread in this group describing
the proposed changes or should we do this via JIRA or github? I'm not
rea
22 matches
Mail list logo
