3 ms·

Not in the target demographic, but it certainly looks interesting. Over the years I grew used to CSS, and generally find it's good enough for my needs. I find

Not in the target demographic, but it certainly looks interesting. Over the years I grew used to CSS, and generally find it's good enough for my needs. I find it incredibly refreshing to see you guys openly point out use-cases where the tool might not be a good fit. Any plans to license the layout engine? If you decide to go down that path, I'd ask you to consider allowing free non-commercial usage. I probably wouldn't consider paying for a library unless I got to try it first, but if it's a good fit it can be well worth the cost. e.g. At my previous job we ended up buying a Highcharts license by my suggestion, since I'd had positive prior experiences and it was a good fit for our problem. Here's one complaint I have with some designers: they always design for the perfect scenario. They don't consider what should happen when a value is too long or short, as well as what should happen when dealing with an empty collection, or worse, a large one. Having a way to specify all those kinds of variations would be absolutely amazing.

RyLuke 9y ago
The demos and engine are free to use and modify for non-commercial use right now. The repo is here: https://github.com/lynaghk/subform-layout https://github.com/lynaghk/subform-layout The happy path issue is definitely one of the big pain points in the "designer throws mockups over the wall" workflow. Simulation of the production medium in the visual design tool can help a bit, but the real solution is to get designers working in the production medium. That's easier said than done, of course. (And ultimately more of an organizational/practice issue than a tooling one.)
lynaghk 9y ago
The runtime engine already free for non-commercial usage: https://github.com/lynaghk/subform-layout/blob/master/LICENSE https://github.com/lynaghk/subform-layout/blob/master/LICENS... Or am I misunderstanding your question? Re: designing for the perfect scenario, I'd say devs are guilty of that too --- I'm in Australia right now, and it's obvious when an app or site has only been tested on localhost =) Specifying dimensions in the "application state space" along which to vary is a tricky problem. It's not clear to me how much of that can work in a GUI tool vs. programming languages and stuff like Clojure.spec, property-based testing, concolic testing, etc.

RyLuke 9y ago

The demos and engine are free to use and modify for non-commercial use right now. The repo is here: https://github.com/lynaghk/subform-layout https://github.com/lynaghk/subform-layout The happy path issue is definitely one of the big pain points in the "designer throws mockups over the wall" workflow. Simulation of the production medium in the visual design tool can help a bit, but the real solution is to get designers working in the production medium. That's easier said than done, of course. (And ultimately more of an organizational/practice issue than a tooling one.)

lynaghk 9y ago

The runtime engine already free for non-commercial usage: https://github.com/lynaghk/subform-layout/blob/master/LICENSE https://github.com/lynaghk/subform-layout/blob/master/LICENS... Or am I misunderstanding your question? Re: designing for the perfect scenario, I'd say devs are guilty of that too --- I'm in Australia right now, and it's obvious when an app or site has only been tested on localhost =) Specifying dimensions in the "application state space" along which to vary is a tricky problem. It's not clear to me how much of that can work in a GUI tool vs. programming languages and stuff like Clojure.spec, property-based testing, concolic testing, etc.