I know that this is not the right way to do things, that I should create an issue for each request, but I want to guage reactions on the full list before splitting it out:
- Move configuration / Add configuration to the ImageField's setting page itself
This just seems logical to me, as this is where I instinctively look for all ImageField related settings.
- AHAH based CCK-esque configuration form
Instead of having two textfields for text based configuration, having a 'type' dropdown, 'key' field and 'name' field with an 'Add another' field utilizing AHAH would make for a greatly more usable interface.
- Add more field types
Making use of the improved configuration form (above), you could easily add more field types, such as select-lists, radio buttons, and more.
I'm also happy to be heavily involved in the coding of these changes, as the end result will benefit WYSIWYG ImageField in a big way.
Cheers,
Deciphered.
Comments
Comment #1
alan d. commentedSounds very cool, but I can not help with this at the moment (I'm currently spending 90% of my time in the Baja deserts on a motorbike!)
"Move configuration / Add configuration to the ImageField's setting page itself"
It would be possible using the current configuration for moving everything to ImageField settings page. Sharing of these additional fields between types would need to stay.
Maybe:
Add existing [ ---- \/] or New field [ type \/] [ name ] [ key ]
"Add more field types"
There would need to be a bit of code refactoring, I was having a bit of a brain freeze when coding it and ended up with two field naming conventions for the textareas and checkboxes. Other than that, it should be fairly easy to integrate multiple field types (and simplify the rest of the module at the same time).
In case you want to fly with this, I've granted you CVS access.
Good luck
Alan
Comment #2
alan d. commentedMaybe better validation functions could also be considered but nothing springs to mind.
Cross-posting #857830: Date field with calendar?, #347070: Ability to make alt and title text required for each image
Comment #3
crea commentedSubs
Comment #4
alan d. commentedThere are no more plans for developing this on Drupal 6.x and the module is obsolete on Drupal 7.x. As such I'm closing the existing non-bug related issues. Reopen of you want to take over and develop this further.
Comment #5
alan d. commented