This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-21
Channels
- # admin-announcements (2)
- # beginners (22)
- # boot (223)
- # cider (161)
- # cljs-dev (19)
- # cljsrn (4)
- # clojure (186)
- # clojure-austin (6)
- # clojure-beijing (1)
- # clojure-boston (3)
- # clojure-china (1)
- # clojure-czech (1)
- # clojure-france (1)
- # clojure-greece (10)
- # clojure-russia (17)
- # clojure-uk (154)
- # clojurebridge (3)
- # clojurescript (82)
- # component (12)
- # cursive (12)
- # datomic (71)
- # dirac (3)
- # editors (2)
- # emacs (29)
- # flambo (31)
- # hoplon (21)
- # immutant (11)
- # instaparse (17)
- # jobs (2)
- # jobs-discuss (2)
- # jobs-rus (1)
- # lein-figwheel (12)
- # leiningen (2)
- # off-topic (44)
- # om (78)
- # onyx (38)
- # parinfer (1)
- # re-frame (34)
- # reagent (32)
- # spacemacs (56)
- # untangled (74)
- # vim (12)
- # yada (2)
hey all, just added an error handling recipe to the cookbook — let me know if you have any thoughts or questions
https://github.com/untangled-web/untangled-cookbook/tree/master/recipes/error-handling
also, the error stuff is only available in 0.4.7-SNAPSHOT, and your project must require om-alpha32
thank you!
@tony.kay: I've started the tutorial. Well done! Nice to use. It is also my first time with Cursive
So far so good
so far I found om-next mind-bending...
And I'm just at B_UI_Exercices
😉
going to sleep. I might watch your CLJ West talk in the bed. But that doesn't mean I expect it to be tiresome 😉
@cjmurphy: @currentoor Yeah, watch the CHANGELOG if you're using SNAPSHOT. I'm trying to make sure it stays up to date as we make changes. Trying to not break things, but it is a snapshot NOTE: There was a bug I fixed that exposed another bug: recursive queries won't work right now on SNAPSHOT
I'm interested in getting stuff added to the cookbook as quickly as possible. I'm trying to personally add a couple a week. If others were to all pick a single recipe a week it would get done super fast. Let me know if any of you have time/interest in doing a recipe and I'd be glad to help you get started and also understand what my plan is for the given recipe
Looks like @mahinshaw is going to do Sente/web sockets
@tony.kay: I'm interested in "Simple CRUD example - Wizard-like form filling" and "Modals".
@currentoor: modals is easy (and can be combined with the tabbed-interface-union-query stuff to make a single modal with mutliple UIs). The wizard forms can leverage the same kind of logic, but probably adds in some interesting things like validating a field and making a form act as more of a unit. @adambros is working on some form stuff, so there is probably some synergy there. So, if you wanted to skype about the modal bit I could get you started on that...and follow up later on the form stuff.
@tony.kay: we've already got a working modal. You're right it was pretty easy. I just wanted to make sure we were doing it correctly and possibly save someone the trouble.
the form stuff is definitely more nuanced
So, modal is mostly about CSS and an overlay to prevent further interaction, or are you blocking it internally?
nope that's about it
yeah...so you're not missing anything there. Either the app state causes the modal to go or not
cool, well I'm happy to help @adambros in any way that I can 😄
so, yeah. Forms is something lots of ppl are going to want, and I think we're going to make an untangled-components library to put things like that in
im currently knee deep in mark/sweep for ‘… & # for recursive limits but im hoping ill be done by today and move on to a validated form (input) component
@currentoor: so if you want to make the modal recipe, just send me a PR. There is a script new-recipe
...there are instructions in the readme. should be easy to get going. Let me know if you need help
I am currently working on allowing users to integrate websockets as a pluggable network component. In the process, I have to add ways to overload the default routes (i.e. “/api”). Currently we are using bidi
for defining routes. Is there any interest in making the route handler pluggable so that one could use an alternative (i.e. compojure
)?
It think that will be desirable. If it isn't too hard to do at the same time (and doesn't break the defaults) then it would be great
@tony.kay: As a caveat, we may need to either cut a release of server, or publish a snapshot build on clojars
@mahinshaw: do :extra-routes
or pre-hook
not suffice?
well so you can have :extra-routes handle /api itself
:extra-routes
does "suffice"...but making that concern pluggable will make ppl happy
we talking about, say using compojure instead?
Even more we want to allow more control if desired, and :extra-routes
doesn’t give that
okay ill leave you to it
"Looks like @mahinshaw is going to do Sente/web sockets" - tell me more
@kmandrup: I think to be more explanatory about the web socket integration - The goal is to make the networking stack pluggable with a component that uses websockets. I plan on adding an item to the untangled cookbook, that would demonstrate the usage of websockets.
Sweet I'm done with REST except for legacy API integrations and perhaps initial load
@mahinshaw: while you're looking at the network stack: I just found a bug
@mahinshaw @tony.kay at one point we were manually encoding exceptions and removing the stack traces, since that would be a security concern. not sure if we still want to do that
Another issue handling server errors: https://github.com/untangled-web/untangled-client/issues/6
i was having a very hard time figuring out how to do that
swapping the react key didn’t work, nor did force-root-rerender
didn’t have access to the reconciler
i think
oh wait
didn’t have access to the whole app atom
that’s what it was
Maybe this needs to be a design discussion. Because that needs to happen with regards to swapping out the network component in general
yeah, sooner rather than later too. we need it working asap over here
definitely willing to do that, and lend a hand with implementation
works for me