On 2/1/07, <b class="gmail_sendername">Karoly Negyesi</b> <<a href="mailto:karoly@negyesi.net">karoly@negyesi.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> That's why I was asking. :) I think CCK makes a lot of sense for<br>> profile fields in the long run. Will CCK be in D6 core though?<br><br>No. There is not enough time. Examples: the installer took years to finish and form API was eight months of damned hard work. The new menu system will be about four-five months -- do not forget that I had a skeleton in Brussels (and it was more than proof-of-concept shortly after) and I started on the real thing well before the freeze and still I will be happy if everything will be together before the end of March.
<br><br>Based on the change data API would require, if you starting coding Adrian's data API _right now_ with a speed that would put the split-finger operators of GiTS to shame then you might make Drupal 7. Otherwise even Drupal 7 is out of question.
<br><br>Regards,<br><br>NK<br></blockquote></div><br>What Karoly is saying is something I observed: every long thread recently has alluded<br>to the "CCK in core" wish that many of us would like to see. An example is the user
<br>profile thread by Rowan, and the replies in it just today, and many others before it.<br clear="all"><br>Karoly is quoting past precedence on how long it takes things to mature and make it<br>into core, and is of the opinion that cck in core will not be ready for D6.
<br><br>Anyone willing to take up the challenge and prove him wrong?<br>-- <br><a href="http://2bits.com">2bits.com</a><br><a href="http://2bits.com">http://2bits.com</a><br>Drupal development, customization and consulting.