Rename project and namespace to 'Extended File Field'

+1

Do you want to just create a new project node, and then push all the commits from here into the new Git repo, rename the module and all the files in that new repo, and then mark this project obsolete/abandoned? Or do you have another plan in mind? Lemme know how you want to proceed.

Thanks!
-Derek

Sanity check. We really want these:

hook_file_field_enhancements_metadata_types()
hook_file_field_enhancements_items_alter()
hook_file_field_enhancements_output_alter()
mymodule_file_field_enhancements_cid_formatter()

?

Probably the best we're going to come up with, and we don't have unlimited time, but if we're going to go through the trouble to rename this, it'd be nice to only do it once. ;)

Cheers,
-Derek

I prefer fieldfield over ff.

Maybe:

filefield_advanced

?

What about the modifier in front to further isolate us from possible namespace collisions with core? E.g.

advanced_filefield
extended_filefield
enhanced_filefield

?

Based on further IRC discussion, I think we're converging on:

extended_file_field

Any final objections?

Thanks!
-Derek

https://drupal.org/sandbox/jthorson/1964794 now exists.

I'm going to work on pushing these commits into there and renaming the module later today. If I don't get to this before I have to leave for the evening I'll unassign myself again.

Once there's working code and we fix the project description, we can promote that to full, move all the issues out of this queue, and mark this project obsolete/abandoned.

Thanks,
-Derek

Pushed the commits:
https://drupal.org/node/1964794/commits

Now I'll work on renaming everything.

Mostly went fine. A few lingering doubts:

hook_extended_file_field_metadata_types()

Do we still want think of this as the "metadata types" hook? I guess that's okay, even though metadata is no longer in the name of this module. It's still ultimately what the hook is about.

mymodule_extended_file_metadata_cid_formatter()

Is that a reasonable example name for this callback? Didn't seem like "mymodule_extended_file_field_metadata_cid_formatter()" was necessary, but it'd technically be more consistent that way.

There are a few Field API hooks that start with the word "field", so our module ending in the word "field" results in function names like:

extended_file_field_field_formatter_info()
extended_file_field_field_formatter_settings_summary()

etc. Slightly unfortunate, but I think it's fine.

Otherwise, this all seems to be working again on my local test site. I split it up into two commits to hopefully make it easier to follow WTF happened. The first is a pure 'git mv' on the 4 filenames:

http://drupalcode.org/sandbox/jthorson/1964794.git/commit/bdbd42d

The second is the actual code/docs changes:

http://drupalcode.org/sandbox/jthorson/1964794.git/commit/7096390

Once we resolve the above questions and get the project node happy, we can promote, move issues, fix up the d.o BZR tree, etc.

Thanks!
-Derek

Split the first off into a separate issue: #1964926: Rename hooks from "metadata" to "columns"

Agreed on the 2nd:
http://drupalcode.org/sandbox/jthorson/1964794.git/commit/5f7213a

Put remaining tasks in the summary.

Yay, thanks!