Heya maintainers.
As you might or might not know, imagefield for Drupal 6 is far from ready still. You might go on and further improve stuff, and you could also copy lots and lots of code from filefield where I worked hard on getting upload issues, permission issues, CCK issues, AHAH issues and lots more worked out. The current state is like, get one CCK patch finished and filefield is basically production ready. Imagefield still has a long way to go until it gets to this point.
So my point is like, please have a look at current filefield combined with this new buddy and consider if it wouldn't possibly be less remaining work for an imagefield(-like) solution to join forces and steer against the file module proliferation rather sooner than later. Like, to drop imagefield 6.x completely, port the few additional features to filefield/filefield_image, and provide an upgrade path from imagefield 5.x-2.x.
How about that? Of course, if you stick with imagefield then I'll be just fine with that too. Your take!
Comments
Comment #1
windstray commentedwow! Common, it's really good step.
I don't know who will be first in this competion, but i need this ability many monthes ago and for now too, and it's VERY good news.
D6 really needs this ability to put an images via cck. for me and not only for me it's primary factor to choose D5 against D6. And it's really bad. :((
Please think about future and be the best.
Comment #2
anuradha-1 commentedWow again! How come I was looking for exactly this today! Thank you very much!
Comment #3
jpetso commentedJust to make this clear: I posted this not as an announcement or advertisement (the Planet is better for such things, and you'll find it there) but as a call for cooperation. Please don't clutter this issue if you don't have input on how cooperation and future directions could, should or will take place. Thanks.
Comment #4
niklp commentedI concur that increased integration can only be a good thing, although this does put dependency back on the agenda as a potential issue. Not really sure what the damage is though.
The bottom line is, this needs doing real soon, whichever way it goes - after Views 2 and CCK hit RC, image handling is the next most lagging area of contrib modules for D6.
Comment #5
jpetso commentedGiven the size of the image support module (somewhat at the lower end of LOC count values), it would be no problem for me personally to include it in filefield itself. If dopry (in his role as the other, original filefield maintainer) agrees to that then we could still have files and images in a single place. As for carrying over maintainers, this should definitely be no problem as dopry (in his role as one of the imagefield maintainers) is already maintainer for filefield, and granting co-maintainership status to quicksketch should also be a good thing :)
As for "this needs doing real soon", that's not my problem. I'll do what I can when I feel like it, or when my company pays me to do so. If someone needs image handling "real soon" then those people should get involved with development or by sponsoring developers.
Comment #6
Moonshine commentedI like the idea, but at minimum, Filefield "images" would need support for max resolution restrictions, default images, and imagecache to be a starting replacement for Imagefield in D6. Given that, other modules (Inline, Imagefield gallery, etc) could adapt pretty quickly/easily IMO. ( Personally I really think it needs Imagecache previews for node forms also, but that's another issue :) )
I would imagine this would also solve the issue of duplicate code which must be pretty heavy in these two modules. (FWIW, currently Imagefield HEAD 6.x and Filefield 6.x beta both define field_file_load() so they can't be installed together.)
I'm about 3 weeks away from needing to have a working D6 cck image field solution to build with (even if it's beta). So at the end of next week, I'd be *happy* to start work on patches to help make this happen. It would just be nice if there was a clear direction of which project will be actively moving forward so that time isn't wasted. :)
Comment #7
flickerfly commentedsub
Comment #8
alanburke commentedsub
Comment #9
sebos69 commentedsubscribing... I am also puzzled about what to use for our Drupal 6 site. Is there a possibility to easily switch from imagefield to filefield image ?
Comment #10
mrgoltra commented+1
Comment #11
jpetso commentedIf someone writes a migration path, sure. But that hasn't been the case still, and I don't know of anyone who plans to do so. Of course it's just moving three database columns per field into three other ones - with one of them dropped ("custom title") and one of them new ("List", which is always true in existing imagefields). Still, unless someone works on that, there is no easy way to migrate.
Comment #12
sebos69 commentedwell, that's a beginning :)
will tease my SQL guru about that...
Comment #13
jpetso commentedPlus, could we please leave this as an "I'd like to have feedback from the maintainers" issue? So far, every cat and his dog are subscribing to this issue or expressing their approval - which I'm thankful for, but it doesn't fit the purpose anyways.
What I was hoping for specifically is to get to know how dopry and quicksketch feel about how to move on with this. Please keep away from asking generic questions about filefield_image, or do so in the filefield_image issue queue.
Comment #14
drewish commentedpersonally i think the right place for this conversation to take place would be in the filefield module as a feature request/task. if we get a workable patch that's a feature complete replacement then we look at an upgrade path in this queue. talk is silver and code is gold and all that.
Comment #15
jpetso commentedagreed, let's take this off-site for fear of a low signal-to-noise ratio that doesn't help anyone involved. not sure how to make filefield issues out of this though, feel free to open up some of those....
Comment #16
zmove commentedVery interesting post, I tried filefield and filefield image and it work just fine. The features are pratically the same than the latest imagefield for D (token integration, imagecache integration, ...)
There are some missing stuff there like tickbox, lightbox and shadowbox, but I hope it will be resolved soon.
What about joining your forces into one single project, instead of developping 2 way to do the same thing ? ATM jpetso seems a lot more reactive than dopry about that, so maybe jpetso a main maintainer and dopry as co-maintainer ? don't know...
Comment #17
encho commentedHmmm... And just when I updated my site to use filefield image... Well, back to imagefield then.
Comment #18
kriskd commentedI see filefield image is no longer a supported project and imagefield for D6 still doesn't appear to be usable. I installed imagefield and I got the field label but not the field itself for uploading an image. Any suggestions?
Disregard the above... Sorry... imagefield is working fine for me. Thanks for your hard work!
Comment #19
bojanz commentedMaybe try: http://drupal.org/project/image_upload
Made it because I was in a hurry, imagefield 6.x was not usable yet, so I made this as a temp solution.
P.S. Sorry for this shameless plug ;)