This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # alda (12)
- # announcements (1)
- # beginners (5)
- # boot (241)
- # clara (2)
- # cljs-dev (7)
- # cljsrn (9)
- # clojure (54)
- # clojure-conj (7)
- # clojure-russia (12)
- # clojurescript (118)
- # cursive (11)
- # editors (3)
- # hoplon (58)
- # immutant (17)
- # off-topic (58)
- # om (1)
- # onyx (12)
- # re-frame (10)
- # reagent (8)
- # spacemacs (6)
Hi guys. It has been two years since I have touch Hoplon for the last time. Seems like Hoplon is back in my radar. Has the general performance improved?
@micha: i was also thinking about getting that curved monitor. i just saw it 3 weeks ago live and it was rather impressive. i found that problems with taller displays is that they r putting a strain on the neck when u r looking up and down, but looking left and right is less of an pain. for example a 27" 2k display vertically - while super convenient because u hardly ever have to scroll your source files vertically - is tiring to scan up n down.
@micha: re: flux-challange and cancelling (i assume xhr) requests.
we just had to do that again and we found that the
xhr.abort method "gets lost" along the way, because the
.done calls on the original xhr promise will return new promises, but just plain vanilla jq.Deferred ones, which dont have
the need for this arose from the fact that currently our backend have a huge variation in response time and sometimes earlier requests overwrite the response of a newer request once the earlier request finally returns.
the function created by
mkremote is already returning a promise, which indeed do have an
xhr attribute, it's just "not the right one"...
pretty much anything you’ve got sending more than one ajax request should only allow the most recent one sent to update its state, or be prepared to show a log of everything that’s coming back and be careful about the order of what was sent vs. returned
off the top of my head, i can’t really imagine anything where you’d want older ajax to override newer ones
what im also missing is the debuggability. the loading cell containing the vector of requests in flight is a great idea, but currently i can't inspect it to see what's in flight
hmm, other than debugging, is there a benefit to keeping track of canceled ajax?
you know, i’m going to just assume that whatever i did in the past isn’t directly applicable here :stuck_out_tongue:
in our case for example i would expect to see something like:
[get-config get-current-user] [get-current-user] [get-apps] 
though i would probably use a different loading cell for stuff which is only relevant for the logged-in states
@alandipert: @micha: https://gitter.im/red/red?at=5648d1516296df7f6efeba1a a little cross pollination :wink:
u need rebol2/view to run it (which needs 32bit compatibility libs under linux unfortunately)
just noticed the audio track on the video... sorry for that. i was sitting on the 7am lamma ferry :simple_smile: the kid next to me was sucking his nose...
Its a super simple editor BUT its part of the 1MB rebol/view exe so it's cross platform and u can count on it... U can also inspect and modify its source...
The thing is w rebol that u have to type a lot less so u dont need a super-duper editor for it... Which is not the case w lisps, though w lisp u dont need a generic editor. But in a lisp project u might still want to edit regular txt files...
Nenad's vision is to have a full collaborative ide with chat linked to the author of every lines of code within a 1MB single file exe