Module development and code questions

I've created module which provides a wizard to assign a geographic location to your website and register it to geoURL.net.
It does also enable a block with a list of selected nearby websites around your page...

The wizard is implemented with the help of ajax, and might be a nice example if you like to implement something like that for yourself.

Ok, hopefully this is quick and I just missed something. I am building a click-edit Google map, and everything is alive and functions except for 1 element -- saving marker data. The difficulty (as I see it) is a choice between two ways of moving marker data.

Layout:
Map table -- has/stores map specific settings, center, zoom, etc
Marker table -- has/stores marker data and is keyed to a map entry based on $mapid
The ability to reuse markers without having to re-enter them is an unexpected benefit of this design.

Methods:
1. XMLRPC all the way. I click a point to create a marker, I edit that marker inline in the javascript, and I can save it directly vi XMLRPC. Piece of cake. Not much code, not much effort. The problem is going to be one of access. I can write XMLRPC code to dump all markers, or even in a worst case scenario, the problem of map or location based spam becomes a nightmare. The only token that I am aware I have access to would be document.cookies.PHPSESSID, but I don't know how that relates back to anything in Drupal that would let me authenticate and verify a content creator. The second problem with an XMLRPC only method is the fact that any new markers will/can get updated in a marker table before the map node has a nid assigned (or even exists for that matter)! The work around for that would be a staging table where orphans get deleted after a specified age limit, everything is keyed on PHPSESSID, and markers that belong to a map node that actually gets created get migrated to the live marker table when the submit occurs. Gut feeling tells me this is the method I should be trying to use, but I really don't have much of a starting point as far as Drupal and user verification are concerned.

Look more likely that I have thought up !
add in module flexinode an opportunity to place fields according to html a pattern and

add an opportunity of automatic scaling of pictures in a floor image

here new the module

here screenshot

Is there a way to create more than one forum? I run a student organization with multiple degrees represented and as we develope our site I was wondering if it was possible to create a couple more forums. I would prefer to have seperate forums instead of just containters. Or, could I focus containers on different pages? I'm still learning the drupal system and would like to avoid having more than one install. Any ideas? Thx guys!

I don't know if this is the right area for this post, but my problem is with a module.

I have created a custom module, which includes a custom block. I am unable to view the block from admin/block to enable and configure it. The code is as follows:

/** 
 * Implementation of hook_block(). 
 */ 
function case_calendar_block($op = 'list', $delta = 0) { 
  global $user;
  // The $op parameter determines what piece of information is being requested. 
  if ($op == 'list') { 
    // If $op is "list", we just need to return a list of block descriptions. This 
    // is used to provide a list of possible blocks to the administrator. 
    $blocks[0]['info'] = t('Calendar'); 
    return $blocks; 
  } 
  else if ($op == 'view') {
    if ($user->uid) {
      $block = array(); 
      // If $op is "view", then we need to generate the block for display purposes. 
      // The $delta parameter tells us which block is being requested. 
      switch ($delta) { 
        case 0: 
          // The subject is displayed at the top of the block. Note that it should 
          // be passed through t() for translation. 
          $block['subject'] = t('Calendar'); 
          // The content of the block is typically generated by calling a custom function. 
          $block['content'] = case_calendar_contents(1); 
          break; 
      } 
      return $block; 
	}
  } 
}

What's weird is that the code for this block is borrowed from another block that works perfectly.