Module development and code questions

Intro

I'm relatively new to Drupal, so may be these ideas were discussed previously, if so please post a link here. I've got these ideas while reading Drupal docs, module development guide and handbooks on other application servers with component architecture.
While developing complicated modules with many components one can meet a problem of controlling interaction between them, especially with modules developed by other people. Here developers have to know deeply how to invoke foreign module's methods, which functions, parameters and responses they have to use. But in this case if modules "know" to much about each other they become very tied to each other. And developer have to pay much attention to this compatibility and not to break in in further versions. So much awareness leads to loosing flexibility from modular structure.

Interfaces are not panacea

I think direct calling function from foreign modules are evil for the further development process. Module functions should not be called directly except several interface methods which have fixed well-documented parameters and responce. Other methods should be private.
Like Drupal core invokes hooks from different modules. And these hook methods could be said as interface methods of the module for interoperaton with core. That's a great idea, but I think it is less suitable for working between modules. Because inter-modules operations are much more different and interfaces are to be more flexible to support calls which tends to be more complacted. How to keep compatibility in this case? Is it vicious circle?

I wonder if anybody can offer pointers about how to move all the links for a node into a block? So, each node's full page view displays a block taking you to the links for that node.

Thanks!

in addition to posting comments, can the user （perhaps and the author) rate a node/article?
and further, the rated nodes/articles can be sorted by ratings/stars?

I'm working on another much larger module and one of the pieces I needed was a site help feature for users specific to roles. Instead of folding it into my module, I decided it would be better implementented as it's own module.

The intention of Site Help is to create a simple, site help content infrastructure suitable for site users in understanding how to use aspects of the site.

I've only recently been approved for a CVS account, and still need to learn how to use CVS. I'm also quite busy putting the finishing touches on my other module, which is my first priority. But I thought I would post this code here for anyone who may want to look at it and try it out. It has only been tested a little by me. If anyone has a CVS account and wants to create a project around this, I would be more than happy for you to do that. If you would like me to be co-maintainer, I would be happy about that too. If no one takes up that offer, I will eventually create a project around it myself (assuming comment and suggestions warrant it), but it will probably take me a few weeks to get around to that.

Would really like to hear comments and suggestions.

Here is the needed SQL (mySQL only, sorry postgres folks, I am not very familiar with postgres).

CREATE TABLE `site_help` (
`nid` INT( 10 ) UNSIGNED DEFAULT '0' NOT NULL ,
`site_help_type` VARCHAR( 100 ) NOT NULL ,
`site_help_roles` VARCHAR( 255 ) NOT NULL ,
PRIMARY KEY ( `nid` ) 
) TYPE = MYISAM ;

Here is the module
<?php
/**
* Implementation of hook_node_name()
*/
function site_help_node_name($node) {
return t('site help');
}

/**
* Implementation of hook_help()
*/
function site_help_help($section) {
switch ($section) {
case 'admin/modules#description':
// This description is shown in the listing at admin/modules.
return t('Allows creation of a simple site help content infrastructure suitable for site users.');
case 'node/add#site_help':
// This description shows up when users click "create content."
return t('site help is content intended to help users understand how to use aspects of this site.');

case 'admin/help#site_help':
$output = '

The intention of Site Help is to create a simple, site help content infrastructure suitable ';
$output .= 'for site users in understanding how to use aspects of the site.

Hi,

Using Ecommerce module, Is it possible to create products that assign users to an existing role (authenticated, publisher, etc.) ?

Paypal_subscription module provides this functionality.

All comments greatly appreciated.

Thanks, Darly

Found a blog_archivemodule that seems to be exactly what I want. When I upload it and try to activate the block I get this message

Fatal error: Call to undefined function: node_access_join_sql() in /modules/blogarchive/blog_archive.module on line 88

Any developer here that can say what's the problem?