Justin,<div><br></div><div>Just a follow-up: thanks for this suggestion. I re-factored my implementation to use post custom meta rather than Page Templates, and it's actually *much* simpler now.</div><div><br></div><div>
I skimmed through your theme-layouts.php implementation, and it seems that I'm using a rather similar method.</div><div><br></div><div>One question: are nonces not handled globally on post.php? I notice you've added nonce handling to your metabox markup and sanitization functions.</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Tue, Aug 9, 2011 at 12:36 PM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com">justin@justintadlock.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<u></u>
<div text="#000000" bgcolor="#ffffff">
Don't use page templates. Use post meta.<br>
<br>
Suppose the default layout was "content|sidebar". Further suppose
you have an "Archives" page template. Now, what happens if a user
wants a "sidebar|content|sidebar" layout but also wants to use the
"Archives" page template? If layouts are controlled by template,
they can't use both. If layouts are controlled by meta, the two can
be used together.<br>
<br>
This doesn't cross any boundaries to me. Does the data deal
specifically with presentation/display? Yes. Therefore, it is
theme territory. <br>
<br>
I don't see this as being any different than using page templates in
terms of appropriateness. Themes can include custom page templates,
which are also saved as post meta.<br>
<br>
Anyway, I've been working on a standard for theme developers who
want to incorporate this functionality into their themes if you're
interested in checking it out.<br>
<a href="http://svn.locallylost.com/themes/hybrid-core/trunk/extensions/theme-layouts.php" target="_blank">http://svn.locallylost.com/themes/hybrid-core/trunk/extensions/theme-layouts.php</a><div><div></div><div class="h5">
<br>
<br>
On 8/8/2011 12:27 PM, Chip Bennett wrote:
</div></div><blockquote type="cite"><div><div></div><div class="h5">Good afternoon reviewers and developers!
<div><br>
</div>
<div>I want to get your input/opinions on something. The next
version of Oenology will incorporate layout options:</div>
<div><br>
</div>
<div> - Static Page default layout, via Theme Option</div>
<div> - Per-Page layouts, via Page Templates</div>
<div> - Single Blog Post default layout, via Theme Option</div>
<div> - Blog Posts Index layout, via Theme Option</div>
<div><br>
</div>
<div>I am considering adding post meta to allow for per-post
layout selection. It is simple enough to implement; however,
here's my question: would this cross the content/presentation
line? Or expressed differently: would it be inappropriate to add
Theme-specific custom post meta in this manner, given that such
metadata would be mostly useless to the user after switching
Themes?</div>
<div><br>
</div>
<div>I'm leaning toward the opinion that it would be appropriate,
but I am concerned about the scalability of Themes filling up
the post meta table with data that are only useful when using a
given Theme.</div>
<div><br>
</div>
<div>Thoughts?</div>
<div><br>
</div>
<div>Thanks in advance,</div>
<div><br>
</div>
<div>Chip</div>
</div></div><pre><fieldset></fieldset>
_______________________________________________
theme-reviewers mailing list
<div class="im"><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</div></pre>
</blockquote>
</div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>