Directory in a block

This was requested before, but it was unclear what was wanted.

So:

1) the exact content of the block should be defined: what do you expect to see there?

2) I am currently busy, but if a patch comes along, I'll review it thoroughly.

I was poised to do I think such with Directory. I will go ahead and download the dev version of the package rather than the release version and start hacking on that version. Is that indeed the version I should be working with, or is there "something newer" elsewhere?

My intent is to get the block to represent the directory structure only, not display links to specific nodes. Best leave that to the center column, in my opinion.

Anyway, we will see what comes of my hacking attempt.

Development is done at the top of the DRUPAL-5 branch. The best would be for you to use a checkout from cvs: http://drupal.org/handbook/cvs.
But since the latest released version is in sync with the top of that branch, you can also start hacking with the released package.
To create a patch, using a cvs checkout would still be better: http://drupal.org/patch/create
Beware of the patch format and the coding standards http://drupal.org/coding-standards.

For the block content, I can imagine a block appearing on a node view, with a link back to the directory entry for each term assigned to that node. That would be the most useful block, I believe.

Could you be so kind as to take a crack at this one instead of me? The tagged teaser line is bewildering enough to me... making a Directory block seems far harder.

Attached is a screen capture of the output of taxonomy_menu.

We like the twisties... several shown open.
We suggest that only categories appear, not individual nodes... that is best left for the center column.

Basically we would like to arrive at taxonomy_menu's block with Directory's middle column. taxonomy_menu's middle column does not suit what we have envisioned at all. (So I was thinking to look inside taxonomy_menu and see how they made the block... copy/paste... etc...)

Very good! You give me another reason why I won't work on any feature before the following is resolved http://drupal.org/node/144743#comment-275314 (do I sound like a broken record?).

If taxonomy_menu does it well, then we don't need to replicate it.
Instead, directory.module should work in cooperation with core taxonomy.module and contrib taxonomy_menu.module.

That's what I want to avoid: duplication of work, of functionality, and of bug reports, etc.

What's your web site address? It sounds interesting, judging by the screenshot... Have a look at http://www.reuniting.info/ . Some of the science there might be relevant (forgive the theming, though: we are working on a new, much better one).

If taxonomy_menu does it well, then we don't need to replicate it.

Apart from taxonomy_menu having a block and Directory not, there is little of interest in taxonomy_menu. So, a vote to implement block functionality in Directory. ;-)

As for waiting until http://drupal.org/node/144743 is answered... why? We are happy with Directory, would like to see a block implemented. We have not dug into taxonomy deep enough to answer "Do we have need for xyz feature?"

The website we are working on for a client is at present VERY early in the migration from old to Drupal. "Hello, World!"

Come to find out, Directory seems much closer to doing what we want it to do. We were looking at the menuing, and discovered entries there from Directory we had not noticed, and turned them on. Basically the same as taxonomy_menu has!

The only thing lacking is the logic that taxonomy_menu has to show children nodes, etc... As-is, Directory does support menu entries, just for the root levels though. (Screen capture attached to this support request, #5.)

The rest we did on our own... creating a new menu, moving the taxonomy_menu entries to that menu from the default location, etc... I did not know those details previously.

Req: We would appreciate some assistance in comparing the code in taxonomy_menu to see if we can teach Directory the trick pictured previously on this feature request. TIA!

Please don't hijack this issue.