This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-11
Channels
- # aleph (3)
- # announcements (3)
- # aws (7)
- # babashka (121)
- # beginners (82)
- # calva (40)
- # chlorine-clover (37)
- # clj-kondo (68)
- # cljsrn (4)
- # clojure (43)
- # clojure-australia (1)
- # clojure-dev (6)
- # clojure-europe (15)
- # clojure-italy (2)
- # clojure-nl (1)
- # clojure-provo (3)
- # clojure-spec (23)
- # clojure-taiwan (1)
- # clojure-uk (21)
- # clojurescript (214)
- # code-reviews (1)
- # conjure (4)
- # core-async (10)
- # cursive (52)
- # datahike (5)
- # datascript (5)
- # datomic (62)
- # duct (1)
- # emacs (4)
- # fulcro (8)
- # graalvm (1)
- # helix (1)
- # honeysql (5)
- # integrant (1)
- # jackdaw (32)
- # jobs (3)
- # jobs-discuss (16)
- # juxt (1)
- # kaocha (3)
- # lsp (6)
- # malli (2)
- # meander (6)
- # nrepl (1)
- # off-topic (46)
- # other-languages (4)
- # pathom (7)
- # polylith (13)
- # re-frame (3)
- # releases (2)
- # shadow-cljs (56)
- # spacemacs (15)
- # tools-deps (3)
- # unrepl (1)
- # utah-clojurians (1)
If clojurians were to redesign html/css/js/ the browser experience... i wonder what that would look like.
a clojure-based browser đ
Yes. JavaScript is scheme with an object system borrowed from Self and a syntax borrowed from Java
Eichâs original scripting language was in fact Scheme but management told him not to be silly and to try again
On fosdem 2020 there was a talk about nyxt-browser (called next back then). a browser built in common lisp. (https://github.com/atlas-engineer/nyxt) The engine is pluggable (Blink / Webkit allowed), looked pretty interesting. Obivously just an UI though (not re-imagining html/js/css đ)
also; yes. I was at the 2020 talk; but since there was another talk too it seems đ
On the subject of css, I'd really like something new and better to come along. Then I won't be fighting with issues like this: Why is it moving! W.T.A.F
I bet it's some dynamic css causing it, loading then unloading. I don't think this is actually something that's just CSS's problem, similar issues can arise in any context.
looks like you got something changing the window height slightly to put the vertical scrollbar on right side.
It was working when I had stuff lower on the page. I had stuff I had to scroll down to see, I removed that. ANd now everything twitches
dunno without seeing the page, perhaps have an element that's resizing itself by 1px
ive pushed it to my git live page thing https://stuartstein777.github.io/ It twitches, but if you hit parse then play, it twitches even worse!
yeah not getting the issue on my mac, and i'm pretty sure if you resize your window just slightly to reduce the height it won't happen to you either. can check on my pc when i get back home
@qmstuart Even if moving the output box fixes it for you, the issue will still remain. Someone with a different screen size may hit it. It is perfectly fine if you are the only one using it though.
Does anyone have any links/resources for what an ideal, clojure based layout library might look like? (no relation to html/css required)
https://gss.github.io/guides/ccss Not Clojure based, but IMO constraint solvers are the only approach that matches both the essential complexity of rendering layouts and the accidental complexity inherited from CSS.
backwards compatibility with CSS is non-goal
I recently read Grid Systems in graphic design by Joseph MĂźller-Brockmann which was really interesting. It's the kind of approach I would be interested in, but it only covers static print. It doesn't really cover dynamic UI (it's from 1981)
So interestingly enough, Appleâs UI frameworks have used constraint-based systems for a long time and devs hate it. Theyâre now moving away from it with SwiftUI. I was all gung-ho on ccss and gss before I played around with the Apple version a little and I kind of get it: when the tool you have is CSS you often run into problems that feel like theyâd be easier to solve with a constraint-based system, but when the tool you have is a constraint-based system, you just want the overconstrainted/underconstrained errors to go away
Does that include designer sentiment? I think one issue that could use more work is being more thoughtful about the hand off between designers and programmers. It's hard to tell if the issue with constraints is the tooling, workflow issues between programmers and designers, or some combination of other factors.
Just browsing the layout options in SwiftUI, it seems like it's mostly VStacks and HStacks which is reasonable from a programmer perspective, but it kind of already assumes that the paddings, frames, etc. have already been worked out by a designer. It doesn't seem to try to encode or build on top of any design system. The intended workflow seems different compared to the Interface builder approach where you could theoretically have a designer fully layout the UI and the programmer just hooks up actions.
I havenât worked in iOS so I canât speak much to how itâd work in practice, but my sense is that interface builder is targeted at newbie devs/small teams moreso than designers. Having used it, it does take a fair amount of technical expertise to use effectively. Another interesting data point: from what Iâve heard, one of the first things experienced iOS devs do when âproductionalizingâ an app is ditch Interface Builder in favor of the plain code. Thereâs even a bunch of libraries for writing constraints in code more easily. So I get the sense that in general, IF and possibly also constraints donât scale well? That matches my intuition too: in SwiftUI, interactions are âlocalâ, in that a component canât base its layout on a component that doesnât have the same parent. With constraints, any component can reach across the interface and base its layout on anything else, which could yield more entangled/complected results
"Grid Systems in graphic design by Joseph MĂźller-Brockmann" sounds awesome
https://gss.github.io/guides/ccss Not Clojure based, but IMO constraint solvers are the only approach that matches both the essential complexity of rendering layouts and the accidental complexity inherited from CSS.
I guess ideal isn't the right adjective, but any ideas for a cohesive, thoughtful approach. I think iOS is based on the https://constraints.cs.washington.edu/cassowary/. SwiftUI has some interesting ideas.
CSS is apparently a descendant from "let's make a magazine on the screen" and has things like "float" and "clear" because it assumes a "flow" to the "page"
not exactly Clojure, but https://package.elm-lang.org/packages/mdgriffith/elm-ui/latest/ looked interesting when I checked it long time ago
this talk is really interesting so far, https://www.youtube.com/watch?v=Ie-gqwSHQr0. thanks for the pointer!
seems interesting. Is there any sort of background on why things are the way they are? Like a rationale or first principles approach? I've been slowly reading through different design systems which is the closest analog I can find.
As an example, I think "Grid Systems in graphic design" by Joseph MĂźller-Brockmann is the type of thing I'm looking for, but for computer UIs rather than print
I don't know anything off hand but flexbox seems to be something that a lot of time and effort went into. I'm sure there's resources out there that goes into the background and rationale of its design
Looking at the https://annairish.github.io/historicizing/history, it seems like it was derived from Mozilla's XUL. I didn't realize flexbox originated in 2008. This is the closest resource I could find to anything that might resemble a problem statement or rationale: http://mb.eschew.org/2 The design examples are pretty great, http://mb.eschew.org/figures/figure2.7.jpg
flex-box is kinda old and kinda new and also when do i use it? đ?
@U3ES97LAC every time, if possible. Flex is quite amazing to be honest :)
Hmm I'll have to put some time into learning what the heck it is.