dirac

Dirac v1.7.2 is out: https://github.com/binaryage/dirac/releases/tag/v1.7.2
Shuai Lin 2019-10-24T10:12:40.004800Z

anyone know what software are these nice ASCII graphs made of? https://github.com/binaryage/dirac/blob/master/docs/about-repls.md#the-lisp-machine

2019-10-24T16:06:57.005100Z

@linshuai2012 https://monodraw.helftone.com/

p-himik 2019-10-24T18:25:05.007800Z

Would it be possible to support custom formatting of values received over WebSockets? E.g. I'm using https://github.com/ptaoussanis/sente that can send e.g. EDN or transit via a WS connection. Transit is more or less tolerable when sent in its verbose form (not sure how DevTools understands that it's JSON). But its packed form is rather hard to read. EDN is readable but not browseable - it's just a string since the browser has no idea how to work with it.

2019-10-24T18:28:32.008200Z

@p-himik this? https://github.com/binaryage/dirac/issues/37

p-himik 2019-10-24T19:05:19.010700Z

Ah, I was looking for WebSockets so didn't find it. Yeah, more or less the same. Although I'm not sure if supporting WebSockets could be handled with the same code as for regular requests since there's no content-type attached to messages. Also, the "Transit EDN" phrase confuses me a bit since tansit and EDN are different formats.

2019-10-24T19:06:08.011Z

by “transit EDN” I meant the packed form

p-himik 2019-10-24T19:09:08.013100Z

I see. I'm definitely interested in that, plus regular EDN. 🙂 On a separate note - I started looking at how it would be possible to implement it in Firefox since its dev tools appear to have matured more or less to the comparable level to Chrome's DevTools. But no, they still haven't implemented the ability to create custom formatters. 😞

2019-10-24T19:15:33.013400Z

They have a bug thread somewhere about it

2019-10-24T19:16:19.013600Z

still open: https://bugzilla.mozilla.org/show_bug.cgi?id=1262914

2019-10-24T19:25:53.014500Z

just briefly looked at the devtools sources, web socket data frames and normal network request previews are handled differently

2019-10-24T19:26:44.015400Z

web socket frame can be either text or binary and devtools creates corresponding view for it (in case of text type, it creates JSON view), no detection of mime type or anything like that

2019-10-24T19:27:27.016200Z

in network requests it tries to look at response headers or request headers and then interpret the mime type

2019-10-24T19:29:49.017400Z

actually if JSON view cannot be provided, it falls back to Common.resourceTypes.WebSocket type, whatever it is

2019-10-24T19:35:44.018500Z

we would have to implement a new SourceFrame.ResourceSourceFrame type and detect packed transit there