The Drupal developer community is working hard on the forms API. I've already did forum and menu. The new form code requires a different mindset... once you are into it, it's quite easy and extremely powerful.

I expect that the code will be frozen real soon now and then I can began preparing my EuroOSCON speech.

Also, I plan to write specs for a new taxonomy module and make a reverse bounty out of it.

... wishing happy birthday. That really says a lot about him and how much he cares about the folks working for Drupal. This really meant a lot to me. Thanks!

BTW. if you are expecting development news, I am working on taxonomy anything

Dries included the channel into temporary server text. I expected an increased flow of newcomers, and there were some surprises: some of them read the topic! Now really, what the world gets to?

Of course, trolls (so far only one) have also come along.

Also, a bit off topic, it seems that we got a great contributor through SoC, she is running under the nick webchick. Put together an API module guide on http://www.planetsoc.com/node/103, made the frowning Druplicon... besides doing her SoC code.

Up until now I stayed away from XML-RPC. Now I have tried this, this will result at least in better documentation. Thanks for John K. VanDyk for helping me out.

So, when I "turn one" on May 29 with Drupal, only aggregator will be uncharted territory for me...

Today I tested the e-commerce package. I had a custom node, and I found that it is very easy to upgrade it to be a product. It's not absolutely necessary 'cos anything can be a product but I wanted a seemless integration -- just a few fields added to my node edit form and that's it.

• changed all my _load, _form, _view, _insert, _update, _delete functions by adding a _ before the function name and calling these from hook_nodeapi. I changed the node type for existing nodes to product. I found one inconsistency: you need to use db_fetch_array instead of db_fetch_object in load. In _mymodule_form you need to delete body and related form_tips, you want to return your special things only.

It seems that split mode is working nicely -- this morning I benched some 40 percent speedup. I suspected something like this, 'cos the split script itself needs several seconds for one pass, and a significant amount of that time is spent tokenizing Drupal code.

We should modify the menu structure so it stores an "admin" flag for admin pages. This should be editable from the menu screen, 'cos for eg. it depends on site whether node/nid/edit is admin or not. To save a lot of typing, we could define that all children of an admin page is also an admin page.

When this is in place, we could do the admin theming as discussed in Antwerp: if the page is an admin page, the theme system would like into the directory of the current theme for an admin subdirectory and fetch the admin theme from there. It would be not be a necessity, we would provide some defau

I thinking a lot about the multi region patch, and the possibilities it will open.

For example, we could get rid of 'form pre' and 'form post' in nodeapi and have 'form' which calls the nodeapi modules in turn and those set up their blocks -- weighted. We will need to define weight ranges, like 0-1000 is the former 'form pre' and so on.