Feedback on functionality in 1st patch

Yay, now we can actually create new vocabularies, classes and properties :-)

Here are a bunch of comments on the way the four forms for the four entity types currently work.

On creating entities via “Add content”

1. In the "Add content" screen, "Vocabulary", "Property" and "Class" should be hidden. You can only create them through a "Vocabulary Workspace".

Here's how we did that in D6:

/**
 * Implementation of hook_menu_link_alter().
 */
function neologism_menu_link_alter(&$item, $menu) {
  // Hide the Class and Property content types from the Create Content menu
  switch ($item['link_path']) {
    case 'node/add/neo-class':
    case 'node/add/neo-property':
      $item['hidden'] = 1;
      break;  
  }
}

2. Now that we can see the data model we designed in an actual site, it turns out that the name "Project" is a bit confusing from a user perspective. It would be better to call it "Vocabulary Workspace". Sorry, my bad for not thinking this through properly earlier.

About the Workspace and Vocabulary forms

3. Since a Workspace only ever has exactly one Main Vocabulary, there is no real point in having two separate forms for these entities, and when creating one, it should automatically create the other.

(Later on when we get to external vocabularies, we will be able to add further external vocabularies to a workspace, but you can't change anything inside these external vocabularies and therefore don't need an edit form for them either. Just a form for adding/removing them.)

So, basically when we create a workspace, we want the fields for creating the main vocabulary to show up in the form. Then when saving the new workspace, it should automatically create the node for the main vocabulary as well.

The easiest way of getting the additional form fields might be to call drupal_get_form in order to generate the vocabulary form, and copy the relevant fields over to the workspace form.

4. When adding the vocabulary form fields to the workspace form, don't add a form field for the vocabulary title, and instead just automatically take the value of the workspace title when saving the vocabulary. These two titles will always be the same.

5. Authors list should be initialized with the user who is creating the workspace.

6. Project layout field should be hidden. It's XML for the layout of the diagram, and users should never see it

7. The main vocabulary for a workspace should be created automatically when you create the workspace. The "Main Vocabulary" form field should therefore never be visible in the Workspace form.

8. The form field for Namespace URI: The "Default" option for me shows "http://default/void#", it should be "http://neologism7.local/void#" (I'm running this on a host called neologism7.local)

About creating classes and properties

9. Adding a new class or property should be a "local action" on the workspace. So, when you look at the workspace node, and are logged in, you get an additional link "create class" and "create property". The local actions can be defined in hook_menu, see here for the D6 version:
http://code.google.com/p/neologism/source/browse/branches/drupal-6/neolo...
(the .../add-class and .../add-property bits are the interesting ones)
These menu items call neologism_add_term, which then just invokes the appropriate edit form:
http://code.google.com/p/neologism/source/browse/branches/drupal-6/neolo...

10. In the class/property edit form, the related vocabulary field should be hidden. When a class/property is first created, the related vocabulary should be pre-set to the main vocabulary of the workspace. In D6 this is done in neologism_add_term