Hi Mike - sure. I have a significant deadline approaching so I won't
get to it for the next few days, but yep.
On 30 March 2015 at 02:54, Mike Thompson m.l.thompson...@gmail.com wrote:
On Sunday, March 29, 2015 at 11:38:44 PM UTC+11, Colin Yates wrote:
Hi all, I have read the docs but might
I created this reagent component:
(defn duallist []
[:div.row
[:div.col-md-7
[:select {:multiple multiple
:size 10
:name duallistbox_demo
:class demo
:style {:display none}}
[:option {:value option1} Option 1]
[:option
I have a reagent component :
(defn duallist2 []
[:div.row
[:div.col-md-7
[:select {:multiple multiple
:size 10
:name duallistbox_demo
:class demo
:style {:display none}}
[:option {:value option1} Option 1]
[:option
To start the conversation,
http://unredacted.redalemeden.com/2015/initial-thoughts-about-react-native/
(via HN, #1 link right now)
I've been thinking hard if I should keep my hopes up in React Native based
on the potential for a ClojureScript version, but after reading this
article (plus some
Personally I see some of the cons as pros.
Some examples:
* JavaScript means we can use clojurescript, and also means live updating of
applications that have been approved in the App Store.
* Component based file structure: I'm not sure what this means within the
context of react native, but
With respect to it being ready for prime time within a year or two:
The Facebook Ads app is evidently written using React Native.
There is a tremendous amount of interest in it (for example, the #reactnative
IRC channel is very active). Facebook appears to be very responsive―my guess is
that a
Hi Lucas
I totally agree with you on the components comment.
Hi Mike:
I'm watching your Ambly REPL project and Nolen's experiment with JSX (
https://github.com/swannodette/jsx-fun)
The part of the article that highlights my concern is:
Unless you want to subclass an unhealthy amount of UIKit
I know about chestnut, but this is a learning exercise for me to be more
familiar with the development environment.
I have been trying to setup a workflow like the one in chestnut from scratch,
but I have hit a roadblock when I try to add Om in my setup.
Before I have required Om, I could
To be fair, xyz isn't *that* private. I.e. you can still get at the
function via a namespaced var #'xyz and execute it if you want (#'xyz).
On Mon, Mar 30, 2015 at 10:23 AM, Marc Fawzi marc.fa...@gmail.com wrote:
Does the :private limitation below mean that defn- xyz and def ^:private
xyz
Does the :private limitation below mean that defn- xyz and def ^:private
xyz won't make xyz inaccessible from outside the namespace? Any reason this
would be difficult to implement for cljs? just curious.
def notes
def produces ordinary JS variables
:private metadata is not yet enforced by the
right but you couldn't do it accidentally
On Mon, Mar 30, 2015 at 8:34 AM, Brandon Adams emi...@gmail.com wrote:
To be fair, xyz isn't *that* private. I.e. you can still get at the
function via a namespaced var #'xyz and execute it if you want (#'xyz).
On Mon, Mar 30, 2015 at 10:23 AM, Marc
The various means of attaching ^:private metadata has always been for
supporting documentation - both human machine (i.e. autodoc) - not
encapsulation.
No there are no plans to actually encapsulate anything.
David
On Mon, Mar 30, 2015 at 11:37 AM, Marc Fawzi marc.fa...@gmail.com wrote:
right
Ok if the CLJS compiler doesn't throw an error when it sees ^:private then I
suppose that's much better than naming stuff using underscores ___xyz___
although the latter has the advantage of being easy to spot (when used in a
different namespace)
How about warning during compilation that a
Another option if you don't want to go the Swift route is RoboVM, which is
actually a very impressive project. It would be great to see a React-style
UI diff library for it. Apparently you can use Clojure with it, however I'm
not sure it really plays to Clojure's strengths - everything must be
I really like the idea of a var/fn being declared pirate. :) Some typos are
just perfect.
Jamie
On Mar 30, 2015, at 12:52 PM, Marc Fawzi marc.fa...@gmail.com wrote:
Ok if the CLJS compiler doesn't throw an error when it sees ^:private then I
suppose that's much better than naming stuff
;)
t's just metadata, right? It could be anything in including
^:_Do_Not_Use_Me___ but I guess what ClojureScript needs is a tool like
JSHint something that ca be configured to warn when say something
declared with ^:private is used from another namespace
Is there such a tool already?
Issue #1:
Running my test suite under 0.3.2 passes.
Running it under 0.3.3 fails with this message:
TypeError: 'null' is not an object (evaluating 'a.appendChild')
and can be tracked down to this function used for testing React components:
(defn add-test-div [name]
(let [doc js/document
Generally the React elements mirror dom objects rather than html tags and
attributes.
For example, :multiple and :selected are booleans, not strings.
Also, the select element has a value property you can set directly instead of
messing with :selected.
18 matches
Mail list logo
