Closed (won't fix)
Project:
IMCE
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Oct 2006 at 09:42 UTC
Updated:
19 May 2011 at 21:11 UTC
It would be nice to have some integration with the imagecache module. That way you wouldn't need to worry about doing any image manipulation coding as it would all be handled by imagecache. You could have a dropdown that allows you to select the 'rules domain' before you click on the image text and the url would be written accordingly.
Only minimal changes would be needed to the interface and it would make this module the bees knees.
Thanks
Adam
Comments
Comment #1
edrex commentedI'd also like to see some coordination of effort here.
Lack of clarity regarding the proper way to handle images is one of the most common problems for new Drupal users, due primarily to the proliferation of incompatible (and often shortlived) systems. IMCE is an excellent frontend, but If Drupal's image handling is to become strong, it is important that we all get behind just one image handling backend and work on that.
Imagecache is the backend for imagefield, which is becoming popular with the CCK crowd, so it isn't likely to go away anytime soon. Also, dopry has taken care to provide two seperate modules in an effort to prevent future fragmentation.
I haven't thoroughly tested either, so don't take me too seriously.
Comment #2
emackn commentedAny progress towards this for Durpal 5?
Comment #3
tflmike commentedI would love to figure out something for this to... I just recently found out that IMCE has an API available for this sort of thing, but I wouldn't know how to start with it. The API is at: http://ufku.com/drupal/imce/api
Does anyone have any thoughts on how we could add imagecache presets into IMCE using this API?
Cheers!
Comment #4
momper commented+1
momper
Comment #5
Tony Sharpe commentedsubscribe
Comment #6
encho commentedSubcsribe
Comment #7
Skirr commentedAnd it is needed in D6 too.
Comment #8
obrigado commentedSubscribing
Imagecache already works with IMCE + BUEditor, is there a way to adapt their solution?
Here's the code:
http://ufku.com/drupal/bueditor/contributions/imagecache
Comment #9
hunt3r commentedAny movement on this? Seems like a win to me. I'm not familiar with the IMCE bridge, but the BUI implementation is good enough. Any body have any success with TinyMCE?
Comment #10
gausarts commentedSubscribing. Thanks
Comment #11
agence web coheractio commentedSubscribing
Comment #12
cyberwolf commentedSubscribing.
Comment #13
nancydruIf the HTML tag could be customized/replaced, then perhaps the Inline module could do most of the work for this.
Comment #14
Helmut Neubauer commentedSubscribing.
Comment #15
emptyvoid commentedNote the 6.x-2.0 branch has an feature to create default image thumbs per profile, perhaps a sub-module could be written to use image cache rules dynamically instead of GD file operations that create thumbs on disk?
The crop sub-module is a great module to reference: http://drupal.org/project/imce_crop
Comment #16
nancydruLet me restate my need: I want a different image size between teaser view and full node view. None of the solutions mentioned above that produce a hard-coded image size are going to work for me. That's why I mentioned the Inline module. If IMCE could instead produce a link in that module's format, then it would accomplish my needs.
I guess I'll have a look at how IMCE_Crop gets hold of the image and see if I can create a similar module to insert an Inline link in its place.
Comment #17
Melissamcewen commentedSubscribing
Comment #18
pamster commentedSubscribing.
Comment #19
off commentedSubscribe
Comment #20
arlinsandbulte commentedCheck this module out:
http://drupal.org/project/filefield_sources
But, it only supports file browsing through IMCE (no uploading, deleting, or other file operations).
See this issue for more on that: #877452: Enable uploading and deletion through IMCE
Comment #21
momper commentedComment #22
spgd01 commentedSubscribe
Comment #23
ufku commentedClosing 6.x-1.x issues as this branch is no more supported.
OTH, this can be handled at editor side as suggested in #8