Active
Project:
ImageAPI
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Apr 2009 at 14:56 UTC
Updated:
30 Apr 2010 at 22:13 UTC
Jump to comment: Most recent file
Comments
Comment #1
drewish commentedI agree that it's confusing but I don't think we really can. Core's image settings require .inc files and ImageAPI's require modules. So you could have the ImageMagick module installed but not a .inc toolkit. If you selected ImageMagick then ImageAPI would work correctly but core's image operations would not.
Comment #2
thepanz commented@drewish: I was talking about Menu entry/position, not system functionality! :)
What I mean is to place:
Image Toolkit -> admin/settings/image-toolkit (as 1st level Default Local Task)
ImageApi LIST -> admin/settings/image-toolkit/imageapi (2nd level Default Local Task)
ImageApi Settings -> admin/settings/image-toolkit/imageapi/settings (2nd level Local Task)
What do you think?
Comment #3
drewish commentedah, that makes more sense. i'm not sure how it would work in practice but if you would mind whipping up a quick patch i'd love to see what you're describing.
Comment #4
thepanz commented@drewish: ok :) I'll let you know! give me 24/48 hrs! :)
Comment #5
thepanz commentedHi, I can't provide a patch right now (CVS external access is disabled at my University).. I've made some screenshost with ImageAPI under ImageToolkit admin menu (with one and two toolkits installed)..
What do you think?
Note: if only one toolkit is installed, Configure will appear as title for configuring it;
else if two or more toolkits are present, a new tab for each config will appear..
Comment #6
drewish commentedhumm... i see what you're saying but i'm not sure that makes it much easier. people often don't see the tabs much less the secondary tabs.
Comment #7
thepanz commentedI think that Drupal admins (the real users of Image-API settings IMHO) are quite comfortable with primary/secondary tabs :)
In addition, you can add, after module install, a message like "ImageAPI successfully installed, visit _LINK_ for configuration"..
I think that moving ImageAPI into ImageToolkit menu can group the "imaging" functionality in one single place, so admins will not have another entry in /admin/settings and can easily configure ImageToolkit and ImageAPI with only one click in the tabs instead of go back to admin/settings and look for ImageAPI..
What do you think? Maybe other admins/users can give their opinion... :)
Cheers
Comment #8
thepanz commentedComment #9
drewish commentedThere's no patch.