- From: Greg Whitworth <gwhit@microsoft.com>
- Date: Wed, 3 Jun 2015 20:23:47 +0000
- To: François REMY <francois.remy.dev@outlook.com>, "'Ian Kilpatrick'" <ikilpatrick@chromium.org>
- CC: "public-houdini@w3.org" <public-houdini@w3.org>
> A note, though: I didn't see in the proposed desired properties the ability to rely on an existing layout mode. Maybe the > customized grid layout may (after some precomputations and adjustements) actually want to rely on the normal grid for > the last steps of the layout. I don't know how feasible this is. If this is not feasible, it's ok, we just need to think about it. This is a good suggestion; however, I would really like our first stab at this to focus solely on getting it up and running: 1. Access the fragment tree 2. Create a box 3. Do it's layout (and any of its children) 4. Add it to the necessary trees via the API when done 5. Call for paint invalidation on next avaialable frame via custom paint (although this is should not be a dependency) I would prefer to get just basic layout working before we try to get too much communication happening between native layouts and dependency by those from custom layouts. Additionally, it feels like we're trying (to some extent) to move more of this to the author, so we _may_ not want the author to depend on native since we're trying to give them more of the control. ~Greg
Received on Wednesday, 3 June 2015 20:24:16 UTC