This document contains my list for what I would like to see done ASAP. It uses CSS/jQuery to provide sane numbering for embedded lists and won't be consistent on feed aggregators so for the list you need to read the original. I copied this to http://groups.drupal.org/node/116044 for easier editing. Disclaimer: this is just my list and not all items are agreed upon. I am not a core maintainer this is just a list of things that IMO needs to be done ASAP and I would love to see people working on them and obviously I will work on them too. We desperately need frontend folks to chime in -- I am more familiar with backend issues. As said in the previous post, get a few, important, quick, doable fixes now, think major at Chicago, code some foundations at Chicago, work until London, finish together in London.
- Change hook_field_op to an array of callbacks in hook_field_type_info (which is now hook_field_info). These dont define fields but field types.
- Tear block module apart into block (providing API), block_ui (providing UI) and block_custom (providing custom blocks). We want drastic block changes in D8 and we are on more firmer footing once this is in.
- Queue.
- Make every queue identity itself via an info hook and a queue running screen with a batch API indicator.
- Use queue API for node and comment, user, node multiple deletes
- Missing EntityFieldUpdateQuery
- Remove hook_node_info, node_invoke etc -- I do not see what can't be done with hook_field_extra_fields as necessary.
- Profile module, die, die
- At least get Make dashboard a fake theme in. We need to discuss the fate of dashboard, that's one item for Chicago!
- Change the hook separator from '_' to '_hook_'. Better do it ASAP.
- Get rid of form_set_error
- Menu system needs to be torn apart. Separate out menu links from hook_menu and Big task cleanup: Remove type and tasks from hook_menu().
Commenting on this Story is closed.
The code will be just so ugly with "_hook_" - why is "__" not sufficient?
Also, queuing deletes? Better at least be able to add a "deleted" flag field to each entity to insure that deleted items are hidden from listing?
If you don't mind explaining a bit more? And who benefits too? Devs/builders/users?
1. Change hook_field_op to an array of callbacks in hook_field_type_info (which is now hook_field_info). These dont define fields but field types.
I opened http://drupal.org/node/1032850
yched