пользователь Mike Thompson написал:
On Thursday, May 28, 2015 at 4:55:09 PM UTC+10, Ruslan Prokopchuk wrote:
(meta #'f)
Hmm. I think there's something fundamental I'm not grasping here. But I'm
struggling to ask the right question to get the ahhh moment.
Perhaps this: why, in my original
at 5:39:54 PM UTC+10, Ruslan Prokopchuk wrote:
Okay, thanks, that makes some sense. So, attaching metadata to the var
rather than the value the var is bound to. Got it.
But ... I then performed this experiment where I feel I am attaching metadata
to the value ...
(def fff ^{:a 1} (fn
Re: Javelin subscriptions.
Code to mimic subscriptions with cells and to use them as ratoms in Reagent
code is pretty straightforward:
Definition:
https://github.com/ul/ampere/blob/master/src/ampere/adapters/reagent.cljs#L5
Usage in Reagent view:
And that is why they should be compiled, not implemented directly in main
language of the project. I've made experimental yEd diagrams → CLJ(S) FSM
compiler and executor (https://github.com/ul/vfsm). Simple example of its usage
could be found here
Jamie, exactly, I took re-frame (it's awesome!) and replaced subscriptions
mechanism with Javelin cells. I like Javelin, it allows elegant and succinct
data coordination. See todomvc example in the amper and re-frame repos for
comparison.
Also I've replaced Reagent with Om because of my
With 3269 I have the following error:
java.lang.IllegalArgumentException:
/home/ul/Projects/project1/lib/transformflatgeom.js is not a relative path
at clojure.java.io$as_relative_path.invoke (io.clj:405)
config is:
:compiler {
:output-to resources/public/js/dev.js
:output-dir
you don't need
specify each library, `:libs [lib]` should suffice.
David
On Mon, May 11, 2015 at 1:10 AM, Ruslan Prokopchuk fer@gmail.com wrote:
With 3269 I have the following error:
java.lang.IllegalArgumentException:
/home/ul/Projects/project1/lib/transformflatgeom.js
One of solutions that I see now is to wrap `anchor` in div with :ref and get
width of that div. Also, pass parent owner (or channel as alternative) to Popup
component and give it responsibility to pass width to `popup` or ignore it.
This problem is interesting as a class of similar problems, so
I want to make Om Popup component based on Closure Popup [1], which takes two
results of `om/build` (let name it `anchor` and `popup`) and wraps them to add
popup functionality to `popup`, anchoring its position to `anchor`. But in my
component I need to get `anchor` and `popup` DOM elements to
Salute!
Prima facie, I have an interest to it, could you reach me by email
fer.ob...@gmail.com with details?
среда, 18 марта 2015 г., 1:03:51 UTC+3 пользователь Marc Fawzi написал:
I started is a list for that.
CC-ing
Begin forwarded message:
Hi All
(I'm not sure how people feel
Works in my Firefox 34.0 on Linux. Does page produce any errors in Console?
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
ClojureScript group.
To unsubscribe from this
I believe that lein-pdo [1] could help a little, but my workflow anyway
heavyweight, I'm also will be grateful for suggestions.
Example of using pdo:
:aliases {dev-up [with-profile dev
pdo
cljx auto,
суббота, 22 ноября 2014 г., 16:55:01 UTC+3 пользователь Ruslan Prokopchuk
написал:
I believe that lein-pdo [1] could help a little, but my workflow anyway
heavyweight, I'm also will be grateful for suggestions.
Example of using pdo:
:aliases {dev-up [with-profile dev
Does anybody have experience using Om GSS (gridstylesheets.org) together?
Especially in live environment like lein-figwheel.
Plain Om + GSS combination works fine (as I hope; I haven't investigated this
far because of struggling with problem described below), but when lein-figwheel
sends
And even more, you can define component systems for every endpoint (reusing
components between them!) using [com.palletops/leaven] (or port to CLJS
[com.stuartsierra/component] or [im.chit/hara.component] by yourself) and start
necessary one on each endpoint. As bonus, if some or all of
David, thanks for reply. I like idea of om.core/join and vote for it if one
will not complicate things. Because in my current project I have some global
app options which could be changed and are used in several places of component
hierarchy. I know, it is cheap to merge them to components'
What is conceptual difference between get-shared and join? Should shared data
be something like root-scope config, which is not meant to be changed during
root lifecycle? And will component be rendered on om.core/join'ed data change?
--
Note that posts from new members are moderated - please
Component is dropped by user near some position, in render this component sees
it and snaps itself to this position. Then component and position ids should be
reported to app global state. I've done it in render, but now I think about
putting message with ids into core.async channel and process
cljs.user= (map identity :x)
(: ' x)
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it,
19 matches
Mail list logo
