If anyone wants to help with this, send me a message.

Cleanup:
- Easier maintenance. I want to be able to fix a bug or implement a new feature, without having to bend my mind.
- I would like to avoid shared variable scope whenever possible. That is, every variable should only be visible in a scope of no more than ~10 lines of code.
- I want a flat hierarchy of functions and "classes". Nesting only causes variable scope to grow.
- More and better comments, and especially better identifiers.

Option for more simple multicrud elements:
- to disable the "insert new item" functionality. This means, no empty row at the bottom.
- to disable the "delete item" functionality. This means, no delete checkbox column.

Paging, sorting (by column x) and filtering:
Ouch, this is really scary to think of.
- What happens if you change some values, and then click one of the page links, before you submit? Will this discard the changes?
- What if you submit, and the values created or updated appear on a different page?
- What about pagination and filters in combination with (hierarchical) tabledrag sort?

I think I could solve all those problems, if I had some time and a budget. Unfortunately, none of this is the case. If I have time left, I will rather spend it on other things.

Comments

donquixote’s picture

donquixote CreditAttribution: donquixote commented

Another thing I would like to have:
Different "types" of items in a multicrud element.

Example:
The CCK fields configuration form has CCK fields, field groups and non-CCK fields. Each have different widgets. And each can have a different "role" in the tabledrag. Groups act as parents, fields act as children (leaves).
The user should have the possibility to choose which type of object she wants to create. This can be by providing one empty row for each type, for instance.