Stevia: Human-readable auto-layout in code

Post by sachadso » Tue, Mar 08, 2016, 1:40 PM UTC

schwarrrtz wrote: post #40

Someone wrote: post #10

Earlier quoted context omitted.

They do, but search and replace, diffing, and copy-paste of multiple elements and their constraints likely (I haven't used Xcode's editor much, certainly not recently) do not work as well as their equivalent in text. And of course, some people find markdown more user-friendly than a visual GUI for more or less the same reasons, so it should not be that surprising to find some people experiment with this. And of cours…

you can copy elements in interface builder, iirc. you can't copy their constraints, which makes sense because the copied instances necessarily have different constraints. otherwise the copies would just stack on top of each other. in my personal opinion, IB is great for layout of one view or screen, especially with the new IBDesignable and IBInspectable features. doing app navigation in a storyboard is a terrible ide…

Post by sachadso » Tue, Mar 08, 2016, 1:43 PM UTC

ufo wrote: post #19

Is that operator-overloading abuse or something else?

Post by cellularmitosis » Tue, Mar 08, 2016, 2:57 PM UTC

kitsunesoba wrote: post #36

austinl wrote: post #17

Since people are discussing Auto Layout alternatives, I'd recommend AsyncDisplayKit ( http://asyncdisplaykit.org/ ) – although it's a bit more advanced. Layout mimics CSS and Flexbox. It was originally built by Facebook and very actively maintained. You also get a number of other advantages, like moving UI operations off of the main thread (which is often a pain point in iOS apps shooting for 60fps).

AsyncDisplayKit is cool stuff, but I really wish it were possible to yank its layout and “doesn’t do layout on the main thread” parts and apply them to vanilla UIKit. It’s frustrating to run into the inevitable unsupported use cases, bugs, etc with alternative UI systems. UIKit has its quirks but it’s mature enough that coming up with a use case that it can’t serve in on way or another is difficult. It’ll be years be…

Post by cellularmitosis » Tue, Mar 08, 2016, 3:12 PM UTC

schwarrrtz wrote: post #40

Someone wrote: post #10

Earlier quoted context omitted.

They do, but search and replace, diffing, and copy-paste of multiple elements and their constraints likely (I haven't used Xcode's editor much, certainly not recently) do not work as well as their equivalent in text. And of course, some people find markdown more user-friendly than a visual GUI for more or less the same reasons, so it should not be that surprising to find some people experiment with this. And of cours…

you can copy elements in interface builder, iirc. you can't copy their constraints, which makes sense because the copied instances necessarily have different constraints. otherwise the copies would just stack on top of each other. in my personal opinion, IB is great for layout of one view or screen, especially with the new IBDesignable and IBInspectable features. doing app navigation in a storyboard is a terrible ide…

Post by pbhjpbhj » Tue, Mar 08, 2016, 4:56 PM UTC

mpd wrote: post #20

glenda wrote: post #18

Earlier quoted context omitted.

I don't think this is actually an issue. You can always add context to searches -- rather than searching for just "stevia" you can search for "stevia iOS layout"

I mentioned it in my response to the other reply, but I've found that the average programmer's Google-fu is actually quite poor, and they would not do that subsequent narrowed search.