I'd love to see it go, but Larry's explanation matches what I've been told when it's been discussed before. It'd also be worth grepping Drupal 6 contrib to see which modules are using it and how.<br><br>
Nat<br><br><br><br><div class="gmail_quote">On Thu, May 21, 2009 at 2:57 PM, Larry Garfield <span dir="ltr"><<a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thursday 21 May 2009 7:54:03 am Arancaytar Ilyaran wrote:<br>
<br>
> Will hook_node_info() eventually die entirely, in favor of working on<br>
> nodes centrally handled by node.module? Should it?<br>
><br>
> Thanks for reading all the way, :)<br>
><br>
> -Aran<br>
<br>
</div>Potentially, but there are two key things that need to happen first:<br>
<br>
1) There are still things that can only be done by a custom-defined node in its<br>
own module. The most notable is hook_access(), which still must be defined by<br>
the declaring module if you want permissions that differ even ever so slightly<br>
from what node module defaults to. That needs to get ripped out and made<br>
pluggable per-type, and stackable. There has bee discussion on how to do this<br>
well back in Szeged, but unfortunately no one who was at that BoF has had the<br>
spare mental cycles to work on it. :-( (If you want to volunteer, let me know<br>
and I'll try to help.) I think there's a few others items that must be done<br>
by the declaring module still, but I can't recall them off the top of my head.<br>
<br>
2) Easy programmatic creation of new nodes. Some modules need to have custom<br>
behavior that comes with their nodes. Poll is a text-book example. For<br>
hook_node_info() to go away, it would need to be replaced by a *good*, *easy<br>
to use*, *flexible* way to declare a node type and additional behavior (eg,<br>
Fields) in a way that could be easily imported on module installation;<br>
patterns.module looks like it could be a step in that direction (I understand<br>
it's in the process of moving away from doing everything via drupal_execute(),<br>
which is good), but there are other efforts along similar lines.<br>
<br>
If you want to kill hook_node_info(), tackle one of those problems first. :-)<br>
<font color="#888888"><br>
--<br>
Larry Garfield<br>
<a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a><br>
</font></blockquote></div><br>