-
-
Notifications
You must be signed in to change notification settings - Fork 715
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from Day8/develop
Update my fork to day8 develop branch
- Loading branch information
Showing
8 changed files
with
142 additions
and
54 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,21 @@ | ||
## Namespaced Ids | ||
|
||
## What About Event Ids? | ||
As an app gets bigger, you'll tend to get clashes on ids - event-ids, or query-ids (subscriptions), etc. | ||
|
||
One panel will need to `dispatch` an `:edit` event and so will | ||
another, but the two panels will have different handlers. | ||
So how then to not have a clash? How then to distinguish between | ||
one `:edit` event and another? | ||
|
||
As an app gets bigger, you'll tend to get clashes on event ids. One panel will need to `dispatch` an `:edit` event and so will another, but the two panels will have different handlers. | ||
So how then to not have a clash? How then to distinguish between one edit event and another? | ||
Your goal should be to use event-ids which encode both the event | ||
itself (`:edit` ?) and the context (`:panel1` or `:panel2` ?). | ||
|
||
Your goal should be to use event-ids which encode both the event itself (`:edit` ?) and the context (`:panel1` or `:panel2` ?). | ||
Luckily, ClojureScript provides a nice easy solution: use keywords | ||
with a __synthetic namespace__. Perhaps something like `:panel1/edit` and `:panel2/edit`. | ||
|
||
Luckily, ClojureScript provides a nice easy solution: use keywords with a synthetic namespace. Perhaps something like `:panel1/edit` and `:panel2/edit`. | ||
You see, ClojureScript allows the namespace in a keyword to be a total | ||
fiction. I can have the keyword `:panel1/edit` even though | ||
`panel1.cljs` doesn't exist. | ||
|
||
You see ClojureScript allows the namespace in a keyword to be a fiction. I can have the keyword `:panel1/edit` even though `panel1.cljs` doesn't exist. | ||
|
||
Naturally, you'll take advantage of this by using keyword namespaces which are both unique and descriptive. | ||
Naturally, you'll take advantage of this by using keyword namespaces | ||
which are both unique and descriptive. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,34 @@ | ||
**re-frame logo** | ||
## The re-frame Logo | ||
|
||
Created by the mysterious @martinklepsch | ||
|
||
Some say he appears on high value stamps in Germany and that he once | ||
punched a horse to the ground. Others say that he loves recursion so much | ||
that in his wallet he keeps a photograph of his wallet. | ||
|
||
All we know for certain is that he wields [Sketch.app](https://www.sketchapp.com/) like | ||
Bruce Lee wielded nunchucks. | ||
|
||
## Genesis Theories | ||
|
||
While we wouldn't presume to fathom the cavernous depths of Martin's creativity, some have | ||
speculated the re-frame logo was created as a bifarious rainbow omage to Frank Lloyd Wright's Guggenheim. | ||
|
||
![](Guggenheim.jpg) | ||
|
||
<br><br> | ||
Others scoff and insist he smeared the cljs logo across re-frame's official | ||
architecture diagram to form a flowing poststructuralist rebuttal of the tyrannical | ||
"OO" adjacency. | ||
|
||
|
||
![](Genesis.png) | ||
|
||
You be the judge. | ||
Are we better off never knowing? Does art require an answer? | ||
|
||
### Instructions | ||
|
||
Use [Sketch.app](https://www.sketchapp.com/) to update the `re-frame-logo.sketch` file. | ||
|
||
Unfortunately the gradients are not exported properly so we can't provide an SVG here for now. | ||
Unfortunately the gradients are not exported properly so we can't provide an SVG here for now. |