@Naheem,<div><br></div><div>That doesn't answer the question. We can use a fields-in-core field to create a body field that automatically gets created when you create a new content-type. Sensible default settings have nothing to do with it. So I still ask, "Why are we using the legacy body field for new content types in D7?"</div>
<div><br></div><div>While we are talking sensible defaults... the default for a body field in a new content type should be to use the "Long text" handler and NOT the "Long text with summary." The use-cases for "Long text with summary" are far fewer than for "Long text." And it can take years for people to actually grok "long text with summary" anyway :). Now that we've got fields-in-core, we should be defaulting on a new content-type body field to "long text".</div>
<div><br></div><div>Shai<br><br><div class="gmail_quote">On Fri, Jan 15, 2010 at 10:50 AM, Naheem Zaffar <span dir="ltr"><<a href="mailto:naheemzaffar@gmail.com">naheemzaffar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote">2010/1/15 Shai Gluskin <span dir="ltr"><<a href="mailto:shai@content2zero.com" target="_blank">shai@content2zero.com</a>></span><div class="im"><br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div>But this is what I don't get: Why is the body field still there when you create a <i>new</i> content-type the body field is still there on the content-type edit screen.</div></blockquote></div><div><br>usability - most people will expect a content type to be useable after
creation.<br>
<br>
Customisation is great, but it should never be at the expense of good
defaults<font color="#888888"><div><br></div>
</font></div></div><br>
</blockquote></div><br></div>