- From: Jonathan Snook <jonathan.snook@gmail.com>
- Date: Wed, 18 Mar 2009 13:25:14 -0400
- To: www-style@w3.org
On 16-Mar-09, at 4:01 PM, Bert Bos wrote: > + accidentally overlapping slots is impossible I don't think we can ever stop people from making mistakes and being able to overlap slots is, to me, a handy feature. > + what is the height and width of slots (your syntax allows multiple > conflicting widths and heights, even impossible ones) This is the case with tables, as well, which is something I tried to mimic as I felt it'd be easier for people to grasp (at least for those who've done table-based layouts) and easier for implementors (since this logic is already in place for tables). > + self-documenting: the "ASCII art" serves as a diagram of the > intended layout (some people do not like this, not sure why) The biggest dilemma with this is just spaces vs tabs and trying to maintain "ASCII art". (Somehow I see bloggers dedicating whole articles just on best practices for this.) My reason for putting together Matrix Layout was not because I felt it was a better implementation that solved all problems but because it was a simple implementation based heavily on existing concepts that would make it easier for implementors to build sooner rather than later. Dave Hyatt's recommendation of extending the Grid Module has made increasing sense to me and I have no major complaints with that solution, either. -js
Received on Wednesday, 18 March 2009 17:25:52 UTC