[Not distributed to the Planet]

Drupal calls views_page($view, $display_id)
views_page() calls views_get_view($view);
views_page() calls $view->set_display($display_id) -- this loads the display handler
views_page() calls $view->execute_display()
view::execute_display() passes through to views_plugin_page::execute_display()
views_plugin_page::execute_display() calls $view->build() which builds the query for the view.

Doing forms with Views is tricky, because ordinarily a form really likes to own the whole page. But they don't have to. We don't have to use drupal_get_form, and I don't think we have to even use the drupal builder function.

Instead, what we need to do is use drupal_prepare_form and drupal_process_form and do a little song & dance to make sure that everything that's supposed to happen in drupal_get_form actually happens.

In Drupal 6, FAPI 3 is finally getting to the point where it's powerful enough to do some of the things that it's been a real bear to do with it. For one, in Drupal 6 it now has image buttons, and using form alter you can now directly replace a regular submit button with an image button pretty easily. And submit buttons have their own submit and validate functions attached, so it's now very easy to have different buttons operate completely independently. This is a major improvement.

Today I released Nodequeue 2.0 RC2. There's at least 1 outstanding issue that I know of, but otherwise I think this is working fairly well. It does, however, need some documentation before I can call this a final release. And possibly some more bugtesting. But this is probably ok for general use.

Are there any volunteers to help me document this module? Particularly the API for writing plugins, but it needs some user documentation as well, just to describe what subqueues are, how they're used etc.