General discussion

I wrote up a quick walkthrough of the groupapi module I have been working on. Comments are welcome, this is still under heavy development, but will almost certainly only serve as a potential model for how group and access management will work in future versions of Drupal as some problems arise in implementation.

I have an idea that I want to discuss about modules and the modules interfaces.

Currently, the modules are each in one file and are put into a "modules" directory. My problem is that it's a really big pain to work on a big script when it's only one file. Problems with improper initializations, data information hiding, and task distribution break down very quickly.

It would be great if someone could work on creating a comparaison review between drupal and xaraya. It seems that both shared the same design philosophy but that xaraya seems more flexible to the non-developer.

I'm interested in using drupal as a CMS for a Canadian website. As such, I need to be able to provide two versions of most nodes: an english version, and a french version (ie, one is a simple translation of the other). It would be ideal if this was implemented at a level below the modules, so that mods wouldn't have to be language aware.

Does anyone have an idea how to (cleanly) implement this feature?

Just a thought, but...

All content in Drupal is represented by nodes. Stories, static pages, forum topics, uploaded files, submitted links - all are nodes in general. These nodes vary from each other only in properties. But one type of content in Drupal, as far as i can see now, is not treated as node. It's user. Basically it's the same old content (information of the account), but with one unique property - the ability to create other types of nodes.

So i'm leading to the idea of expanding taxonomy on users!