Module development and code questions

I would like to use an advanced where I can choose multiple fields to narrow down my search. I found the Trip Search module but there doesn't seem to be an available version download. Has anyone else tried to do something like this?

I've added a module to contrib that handles link management:

Navlinks Module

So far it just adds links to the navigation menu for nodes, but I'd like to have it manage all links generated by the _links() hook (although that will probably require some modification of the core).

You can add links to the Navigation menu, during link creation (an improvement on other taxo based methods)... and links can be associated to any path not already taken by another menu() call.

Is there some module I can use to point my front page to besides anything related to the node module? I would like to keep my blog private but static pages, stories, and such are related to the content which uses the node module.

I really just want to create an opening page with text without having to open my content to anonymous users.

I am previously an xoops user and used news for the journals and a module such as easyweb for a startpage.

Any suggestions?

Hi,

I'm wondering if it's possible for Drupal to utilize ONE module that displays DIFFERENT forms (depending on the URI).

Here's my implementation situation.

I want to create a "Fiction" (like a novel). A "Fiction" contains "Chapters", which are basically sub-nodes of a "Fiction" (very similar to the pages of a book). A user creates a "Fiction" that has fields such as "Genre", "Rating" (set up through taxonomy) and "Story Summary" (the node content).

When a user who owns the fiction is viewing a Fiction Node, they are permitted to add "Chapters". A "Chapter" inherits the "Genre" and "Rating" from the root Fiction node. The user is the allowed to write a "Chapter Body" (the node content).

One reason I did not use the existing book module is because the UI for the book isn't clear for my target audience. If they created a book with a genre, then it would be annoying if they had to specify the genre every time they posted a chapter.

My problem is that I want to call this customized form and can not create it. I create a link that points to "fiction/addchapter/38" (to edit fiction with node 38). I use my callback for viewing fiction (fiction_page) as follows:

if (arg(1) == "addchapter") {
	print fiction_chapter_form(arg(2));
	break;
}

The function

fiction_chapter_form

defines the logic for displaying form elements. The problem is that it does not display the standard Drupal form elements that are shown if you call something like "fiction_form" or "node_form".

I have written up a set of requirements for a "Document Submission" module at [http://yetta.net/~arcana/fiction_drupal_module/requirements.php]. It's similar to the book module, except that there's no permission for other users to edit it, I want to build a "file upload" field for it (I should add that to the book module too), and I want to auto-generate chapters.

I am designing software for managing fiction (or more generally, documents). An example of what I am attempting to build would be the script at Fanfiction.net (http://www.fanfiction.net) or the eFiction script provided by Orodruin (http://orodruin.sourceforge.net). I wrote down a set of requirements that I am looking for in composing this module, located at http://yetta.net/~arcana/fiction_drupal_module/requirements.php.

The navigation provided with the "Book" module would fit into my requirements perfectly. However, there are some limitations with that module - it doesn't allow restricted editing access, for example.

Why is this a problem? If I want to use the "Book" navigation tree in a module in Drupal right now, I would have to either code-clone the Book navigation tree, or import book.module and call the book_ functions for navigation. Code cloning is obviously not a good idea, because if the book module gets a nice facelift, then I want my module to get that facelift as well. Importing book.module would work, but it's risky as far as programming goes because I am exposing entirely that module to my own.

Is there a way to inherit characteristics from other modules without making it all kludgy and ugly?