Module development and code questions

Hi,

I'm doing some code for a client. It's not drupal specific, it's dedicated code for a client website. However, in the future it may make sense to "wrap" the class in a drupal module if nothing like it comes along (or I don't find anything close to what it does).

However, the code I'm writing uses a database (obviously). What's the best way to make this "drupal compat" for the future?

All I can think of at the moment is something like :-

i'm writing an advanced user profile module and i'd like for users to be able to specify in a field on their profile a custom name for the url in the same way that myspace do.

e.g. if my site was called domain.com and a user wanted his profile to be called "lookatme" whats the best way of aliasing his profile e.g. /profile/123 (where uid = 123) to domain.com/lookatme ?

I want to create a custom page layout where users will be able to update different sections of the page without changing the layout and design on the page - i've got a basic html page set up on my site that shows the layout i want to use:

www.interragate.info/countries/iran/

(I want the map and picture at the top of the content to only be editable by the administrator but the rest by the users)

Hey all

This is a stupid problem and one I've come across in the past (which I solved I believe, I just can't remember how!) - here's an example:

hi,

sorry that i post again but i have one more problem.
I created a module with some node types.
When i isert one of that types the User must print out a form.
I planned to use a popup that contains the form and can be printed out by window.print().
The problem is not the popup itself The problem is the code that pops up the popup.
It looks like this:

In the taxonomy_switch module, there is a functionality which allows you to change the classification of a node without loading the whole node content into the web page (whence a major gain in response time and performance if you have large nodes as I do). In 4.6 I used a very useful function call to "taxonomy_node_form" which returned a string containing the form elements appropriate to the node, and preset to the existing categorisation values. This was extremely simple and straightforward - but now it seems to have disappeared.