Andy Baker

Curious about the status of this. I'm struggling to get HoverUI working at all in VR and if there's going to be some progress on VRTK integration then I might...

I might be missing something but what's the issue here? If you're using Flat theme and not overriding base_site.html: no problem If you're using Flat theme and you are overriding...

I've got myself a touch confused here. Is this correct?: "The only reason flat requires base_site.html is to add a class to the body tag" (as requested in #26 )...

I wonder if flexbox is a potential solution? We could combine that with the 'classes' parameter to fieldsets: ``` fieldsets = ( ("Something", { 'fields': (('property', 'type'), ('from_date', 'to_date')), 'classes':...

> But it breaks the grid: Is it really a grid once you have a few tuple rows? It just looks like a mess on most of my changeforms. If...

I'm making a bit of progress: 1. Remove the fixed width from inputs (your grid should control this) 2. Use padding instead of margin for .field-box so we can use...

Flexbox might make some of this a bit easier to handle - i.e. we would probably remove the need to mess around with margins and box-sizing.

I went the route of an explicit opt-in: ``` (" Status", { 'fields': (('foo', bar'),), 'classes': ('has-cols', 'cols-4',), }), ``` This seems to work. I'm still testing but let me...

Add this rule to get dividers: ``` fieldset.aligned.has-cols .form-row .field-box ~ .field-box { border-left: 1px dotted #CCC; margin-left: 6px; padding-left: 6px; } ```

Would a compomise be to have a "depth" option that switched between say 0-3m, 0-6m and 0-12m? (can't remember the max LIDAR depth but you get my point)