- From: Alex Mogilevsky <alexmog@microsoft.com>
- Date: Wed, 26 May 2010 09:00:08 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>, Sylvain Galineau <sylvaing@microsoft.com>
- CC: www-style list <www-style@w3.org>
> -----Original Message----- > From: www-style-request@w3.org [mailto:www-style-request@w3.org] On > Behalf Of Tab Atkins Jr. > Sent: Tuesday, May 25, 2010 6:13 PM > > There are both global (language design) and local (use-case) reasons for that. > I've explored both of these at least partially in my previous emails, > ... Actually exactly from language design point of view I much prefer separate keywords for direction and orientation. Good design makes common cases simple and complex cases possible. There is nothing simpler than horizontal/vertical and normal/reverse, and it will pay off greatly in authors immediately understanding and appreciating the usability. If you end up with having to use an extra three properties in an exotic use case that is just fine, as long as you can... The point that properties that may apply elsewhere should have naming that is applicable elsewhere is good. It then needs specific understanding where that elsewhere will be, or it will just be overengineering (or overdesign).
Received on Wednesday, 26 May 2010 09:00:46 UTC