|
From: | Mike Solomon |
Subject: | Re: anyone notice speed of 2.17.95 on Windows ? |
Date: | Sun, 15 Dec 2013 09:57:20 +0200 |
On Dec 15, 2013, at 12:58 AM, Keith OHara <address@hidden> wrote: On Sat, 14 Dec 2013 00:49:43 -0800, Mike Solomon <address@hidden> wrote:On Dec 14, 2013, at 9:35 AM, David Kastrup <address@hidden> wrote:Most of the contortions seem focused about when or when not and how to I prefer the second name, with the corollary that pure heights and pure anythings are the largest implementation of a basic strategy all over the code base, which is:
This happens for slurs, beams, ties, and line breaking. In the case of line breaking, the elaboration of the options entails making estimates, which is why we calculate pure heights. -- This is indeed transparent, but given that a single object can return many pure heights based on the begin/end values being used or based on how far downstream we are, it’s not clear what this property would look like.
This seems not too far from what we’re doing now, but it adds a lot more properties.
This seems to get the same result we have now while adding a lot of extra properties. I like the idea of their being a single property that is honed in on with successive estimates until we get the perfect value. This is how I do a Sudoku - I pencil the guesses in the squares until I get the actual value and then erase all the estimates and write the good value. Something about using the container (the property) as a holder of the estimates and the final item itself feels sound design-wise. Cheers, MS |
[Prev in Thread] | Current Thread | [Next in Thread] |