Streamline field UI workflow

In the 'manage field' form (last screenshot), it seems a bit unnessecary to have a different form for adjusting the widget type.
Maybe it's better to provide a select list here ( instead of a link to a separate form ), so you can change the widget type immediately on the 'manage fields' form?

Then you're down to 2 settings forms, and I think having 2 different forms wouldn't hurt. With cck I often had to look twice while discerning between node-type specific settings and field specific settings. Offering 2 different forms would certainly help separating these two.
For now, only the field-settings form has a separate form. If you want to change the node-type settings you have to visit 'that long form' ( /admin/structure/node-type/page/fields/fields_new_field ). But you can edit the field specific settings there too, and that's , as webchick mentions, confusing. I think removing the field specific part there is the most obvious solution.

So when creating a new field the workflow is like this:

manage fields > add new field > field specific settings > node-type specific settings > manage fields

changing settings:

manage fields > field/node-type specific settings > manage fields

Indeed, clicking 'save field settings' doesn't take you to the same page. However, I do find these flows quite intuitive.
The first workflow (creating a new field) guides the user through the process of creating a field. If clicking 'save field settings' kept you on the same page this wouldn't be possible.

In short my suggestions:

• integrate the widget form into the manage fields form
• keep field and node-type specific as much separated as possible
• remove the general field settings from the /fields/fields_new_field form

Some other remarks concerning the manage fields form:

(1) I think it isn't very clear what the 'Field' column does.
It should be clear that clicking "boolean" takes you to a form where you can change
the general settings. Idem for 'edit'.

(2) the field settings form gives me the following helptext:

These settings apply to the new_field field everywhere it is used. These settings impact the way that data is stored in the database and cannot be changed once data has been created.

Ok, I added some data ( content? ), and indeed I can't change it (I get a warning). But when I go to that long form, there doesn't seem to a problem?

(3) the field-settings form doesn't give me the option to store multiple values? ( I think it should )

that's it for now

My very first patch, yeeha! :-)

This patch doesn't address all the issues I discussed in my previous post.

In short I separated the field-settings form and the instance (node-type specific ) form.
I als added a select list for the widget type on the manage fields form. See the attached screenshot for the result.
( Not very surprising though )

Tell me what you think!

This is no longer critical. Actually, is this is a hidden duplicate of other issues in the queue?