I totally disagree that "we all use #ids" :) When it comes to styling or semantic markup, ids have no advantage to well-choosen classes. It is rather problematic because there are some bad things about ids:
* They mess up CSS specificity because there are way too strong * They have to be unique which may lead to invalid html markup in the long run * ... So I think we shouldn't mess up the clean and concise syntax of phptal only to support something I wouldn't agree with at all. My two cents worth... Per Am 19.08.11 12:22 schrieb "aaatoja" unter <aaat...@o2.pl>: When creating typical web page we all use #ids, and something like: layout.html> metal:define-macro="html" metal:define-slot="content" index.html> metal:use-macro="../layout.html/html metal:fill-slot="content" And most probably content will be <div id="content">. So maybe just to make our work easier PHPTAL should also fill directly element with defined ids? layout.html> metal:define-macro="html" <div id="content">some text</div> index.html> metal:use-macro="../layout.html/html <div id="content">this will replace "some text" in master template</div> What do You think? _______________________________________________ PHPTAL mailing list PHPTAL@lists.motion-twin.com http://lists.motion-twin.com/mailman/listinfo/phptal -- webfactory GmbH Per Bernhardt, Anwendungsentwickler Lessingstraße 60 53113 Bonn Germany Fon +49 228 9114455 Fax +49 228 9114499 www.webfactory.de p...@webfactory.de Geschäftsführer: Sebastian Kugler, Matthias Pigulla Handelsregister: HRB 8673, Amtsgericht Bonn
_______________________________________________ PHPTAL mailing list PHPTAL@lists.motion-twin.com http://lists.motion-twin.com/mailman/listinfo/phptal
