New module makes custom menus from taxonomy - experienced coder wish to pick this up?
Sorry for the long title, but wanted to get the key facts in there. I've also posted in the module development forum, which seems more appropriate, but the module needs a little time from an experienced coder, up to speed on Drupal 6.x, so I'm leaving a message here, too. I've made a new module. It creates creates custom menus from the taxonomy. It stands out from the other solutions (unless I've missed something), like this, - It's a bigger module (two modules) than other cuter solutions (Tax'o'menu, TinyTax, Taxonomy-strider, Taxonomy-context, Site-menu, Menu-tree...) - It's far more generalised. In short, you can index any part of your taxonomy. The menus it produces update on the fly. They look like the navigation menu or the book menu, because they use the same Drupal systems. There are more details on my recent forum post. If the Dutch play total football, this is total Drupal (bit of hype). When researching, I found repeated requests in forums and lists for such a module, but nobody has made one, which leads to the question, shouldn't I post my work? Answer, no. I only started on Drupal a few months ago. I only started coding in PHP just before the 6.x upgrade, so this module has lived through that. What I have works very well for me. But if the community would like it, the module needs someone experienced to look it over and tidy it up. Anyone want to help? Or point me in some useful directions where I can get help? It's exciting coding, as it uses many of the new features in Drupal 6.x. You don't even have to do the tricky stuff, as the general approach is now worked - the module is up and running as a proof of concept. All you have to do is mail me back, and we can take it from there. Robert
robert crowther wrote:
All you have to do is mail me back, and we can take it from there. This is what Drupal's CVS contrib repository is for! :)
Seriously. Upload it to contrib, make a project and just have a development release, in the project description tell people about it and that you consider it alpha or beta quality. Say you're looking for a co-maintainer. If people want to use it and find bugs, you'll get bug reports. If you're lucky you'll also get patches. You may even get someone interested enough to help maintain it. But just posting to the dev list like this (is everybody that writes modules even subscribed to this list?) has more of an air of "I can't be bothered to maintain this, can someone do it for me?". At worst it'll sit in contrib and nothing will happen, at best you may get patches that teach you better php coding :) -- Adrian Simmons (aka adrinux) <http://perlucida.com> e-mail <mailto:adrinux@perlucida.com>
Hello Adrian, It's taken me a few days to reply, apologies. First up, thank you for taking the time to mail back explaining what I should do. No need for people to do that, but lists and forums would be better for the effort. See, I didn't think it was releasable, so I didn't follow any links on Drupal contributions. I don't even have that much culture. I've never used a content versioning system, let alone know where to find the Drupal one. So I may take this route up. Any project has a curve of learning plotted against achievement. I have learned about not one but two Drupal menu systems, taught myself PHP, and written the modules. In a few weeks. This is the obvious place for me to stop. But given that there is an evident low level interest in such a module, I wondered if it should go out work somewhere. I was aware of "I can't be bothered to maintain this, can someone do it for me?" Hope the above explains. I'm also aware of the strangeness of posting to the dev list. But the module reads like a core module in places. It needs that quality of input to make it solid. Yes, maybe I wouldn't subscribe to a dev list normally, but I would always trawl the dev list archives on any project. Wouldn't anybody? I like to know what can be known before I set my compass. Thanks again for the information, Robert On Tue, 2008-08-12 at 09:11 +0100, Adrian Simmons wrote:
robert crowther wrote:
All you have to do is mail me back, and we can take it from there. This is what Drupal's CVS contrib repository is for! :)
Seriously. Upload it to contrib, make a project and just have a development release, in the project description tell people about it and that you consider it alpha or beta quality. Say you're looking for a co-maintainer.
If people want to use it and find bugs, you'll get bug reports. If you're lucky you'll also get patches. You may even get someone interested enough to help maintain it.
But just posting to the dev list like this (is everybody that writes modules even subscribed to this list?) has more of an air of "I can't be bothered to maintain this, can someone do it for me?".
At worst it'll sit in contrib and nothing will happen, at best you may get patches that teach you better php coding :)
Hi Robert, There's a Taxonomy code sprint coming up in Chicago next month- http://sprint.eol.org/ The organizers have their own agenda, but it might make sense to get it released before then when a lot of taxonomy stuff is going to be kicked around. You could do that simply by posting a link to the files at the taxonomy group, http://groups.drupal.org/taxonomy best, benjamin Agaric Design Collective Open Source Free Software Web Development http://agaricdesign.com/ On Thu, Aug 21, 2008 at 5:29 PM, robert crowther <r.crowther@zen.co.uk> wrote:
Hello Adrian,
It's taken me a few days to reply, apologies.
First up, thank you for taking the time to mail back explaining what I should do. No need for people to do that, but lists and forums would be better for the effort.
See, I didn't think it was releasable, so I didn't follow any links on Drupal contributions. I don't even have that much culture. I've never used a content versioning system, let alone know where to find the Drupal one. So I may take this route up.
Any project has a curve of learning plotted against achievement. I have learned about not one but two Drupal menu systems, taught myself PHP, and written the modules. In a few weeks. This is the obvious place for me to stop. But given that there is an evident low level interest in such a module, I wondered if it should go out work somewhere.
I was aware of "I can't be bothered to maintain this, can someone do it for me?" Hope the above explains.
I'm also aware of the strangeness of posting to the dev list. But the module reads like a core module in places. It needs that quality of input to make it solid.
Yes, maybe I wouldn't subscribe to a dev list normally, but I would always trawl the dev list archives on any project. Wouldn't anybody? I like to know what can be known before I set my compass.
Thanks again for the information,
Robert
On Tue, 2008-08-12 at 09:11 +0100, Adrian Simmons wrote:
robert crowther wrote:
All you have to do is mail me back, and we can take it from there. This is what Drupal's CVS contrib repository is for! :)
Seriously. Upload it to contrib, make a project and just have a development release, in the project description tell people about it and that you consider it alpha or beta quality. Say you're looking for a co-maintainer.
If people want to use it and find bugs, you'll get bug reports. If you're lucky you'll also get patches. You may even get someone interested enough to help maintain it.
But just posting to the dev list like this (is everybody that writes modules even subscribed to this list?) has more of an air of "I can't be bothered to maintain this, can someone do it for me?".
At worst it'll sit in contrib and nothing will happen, at best you may get patches that teach you better php coding :)
participants (3)
-
Adrian Simmons -
Benjamin Melançon -
robert crowther