Clojurians
#cljsrn
<
2015-12-14
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

anisoptera02:12:51

xpost: has anyone gotten a list view working in om next on ios?

mfikes03:12:00

@anisoptera: I had it working with Om a long time ago. I suppose Om Next is probably very similar. Here is the video I recorded: https://youtu.be/Dt2zNemLCCk

anisoptera03:12:23

sweet, thanks for this

dvcrn07:12:50

mwah. is there any way I can debug why my app is crashing before it even loads?

dvcrn07:12:55

like can I somehow retrieve the stack trace?

dvcrn07:12:09

xcodes error messages are pretty useless

dvcrn08:12:42

deleted close to all my changes and still crashes. I think I need to just rm -rf and start over :confused:

dvcrn08:12:36

we need to implement a pokemon exception handler or something like that on a root level that just returns the stack trace

dvcrn09:12:27

man, writing a om next query parser is still a mind bender on the serverside. I think I'm switching to reagent

artemyarulin09:12:15

@dvcrn: native EX_BAD_ACCESS or JS crash?

artemyarulin09:12:45

don’t know about server side parser implementation - but you can pretty much use Om-next with bunch of REST services and later on move to the one-point-query backend

dvcrn09:12:17

@artemyarulin: do you have some code how you implemented normal REST?

dvcrn09:12:42

wasted again hours on getting that one query thing working without success

dvcrn09:12:22

I don't know why I keep try it again. I must be a little masochistic inside :x

artemyarulin09:12:14

@dvcrn: Unfortunately I’m not aware about such examples. There is one https://github.com/omcljs/om/wiki/Remote-Synchronization-Tutorial which supports multiple different remotes, so kinda the thing you want

artemyarulin09:12:19

Better to ask it in #C06DT2YSY channel. I guess using REST backend with UI on Om-Next should be quite a common thing

anmonteiro11:12:18

FWIW, I'm communicating with a REST backend here: https://github.com/anmonteiro/deathrow

anmonteiro11:12:34

@artemyarulin: @dvcrn: ^^

anmonteiro11:12:02

that's both written in Om & Om Next

anmonteiro11:12:20

that is a small project I'm constantly re-doing to learn how to use new stuff

anmonteiro11:12:36

currently switching to a better architecture in the "aemette" branch (https://github.com/anmonteiro/deathrow/tree/aemette)

anmonteiro11:12:59

(but only Om part done, stil haven't gotten around to commit the Om Next part)

artemyarulin11:12:35

@anmonteiro: Oh thanks, I’ll have a look

johannjohann20:12:35

anyone poke around with the navigator? am having an issue with transacting in om next causing the nav to rerender, losing its route state