Work more closely with Node Gallery team

Node Gallery looks good. =)
http://drupal.org/project/node_gallery

I hadn't seen it. If Node Gallery is a better, more support module than mine, then it might be a better route. Certainly for now the developer seems to have more time for maintenance than I do!

The advantage of CCK Gallery is it is very, VERY simple. I haven't tried to install Node Gallery so I don't know how it works...

After installing Node Gallery, I'd say definitely keep working on CCK Gallery as the CCK support makes your module very useful. You can use it with Views/CCK at the field level - enough said.

Node Gallery has plans to integrate with Views, but until that happens, I think your module is worth development. In fact I'd say that it's the right approach in the long term: rather than integrate everything into one module (and write your own views handlers), using CCK gallery, you can leave the uploads to another module, the Views to Views, the fields to CCK. Let them do what they do best. CCK gallery just glues these together.

The main thing CCK Gallery lacks at present is that it doesn't have good image reordering or cover selection capability, which are bases I think it should cover. I recommend installing Node Gallery and checking these aspects because it might be worth replicating these features in CCK gallery.

Cheers & thanks for this module

Thanks for your input.

It's interesting you say this about CCK support, as I'm in discussion in Groups about using a similar approach to building "wall" functionality. I think the CCK/Views combination as a basis for modules is a great way to go, since both will be core and offer the opportunity to give people so much flexibility with the way they configure the module.

Unfortunately the guys there are in favour of working on Guestbook (which I *really* don't like) or doing everything with comments, so it seems I won't get much help there.

Good to know some people are on the same page as me, wanting to work with nodes, CCK and Views and not comments/bespoke db schemas/custom code.

Kevin here... maintainer of Node Gallery.

Basically, the Node Gallery module was completely abandoned by the original author 2 weeks after rolling it out. Around late February of this year, I had a few personal sites and client sites that needed a solid gallery. Using lightbox / gallery2 / acidfree / nodereferences is a very poor option for most people out there. For me, the choices came down to this module (cck), PROG gallery and Node Gallery. PROG gallery seemed very solid but I felt the UI was difficult to use and it was buggy (The module is no longer being developed). I liked this module (CCK Gallery) but felt the limitations. First, it relied on CCK (which is a drawback, at least with d6, as you currently cannot install it in its current form). Second, you could only setup one "relationship." While this is simpler for new administrators, it is limiting because you cannot setup multiple gallery types (for example, with Node Gallery, I can make two different gallery content types, one that can only be edited/created by administrators and another that ALL authenticated users can add/upload too). However, the biggest drawback in my eyes was the lack of Batch API support--the bottom line was I did not want to manually create every node individually and assign which gallery it was supposed to appear in). In reality, it is nice you can select multiple galleries (Node Gallery is nowhere near ready to support that), but the Batch API was key for me. Don't get me wrong, I'm not hating on your module as I did believe it was a strong contender, it just wasn't right for me.

Anyways, Node Gallery was extremely buggy and was missing a lot of features that I wanted (Views, Lightbox2 etc) but I decided it was the best start for a great gallery module and proposed to become a co-maintainer for it. File CCK FileField and ImageField are solid modules, I see the strength of using upload.module until d7. I believe what is best for everyone is that the many gallery module maintainers come together to work on united module that will become *the* Drupal gallery module. Hell, maybe we can even get into Core for d8!

I don't plan on leaving the Node Gallery method of multiple relationships / batch API, but I am *very* open to suggestions as to what direction it should head. I'm even more open to suggestions if people are willing to contribute back code.

Here is the current roadmap as I see it: Prior to the beta I will commit 1) Views2 support 2) an alternative theme / improved theme api support and 3) closing out the buglist. I suspect the Beta will be released by June 1st. Hopefully a final release will be deployed in July.

Hi Kevin - thanks for jumping in! =)

I agree, we should all pull together! I'm also happy for Node Gallery to be the lead project, as it has a better name. My module is extremely simple, so it's not like it's a huge loss if some of it isn't carried forward. I need to fix the ImageField issue (sorry guys, I'm SO stacked right now) so it at least works in its basic form again - and it needs to exist until Node Gallery can achieve some of things people are saying CCK Gallery does better, but ultimately more work has gone in to Node Gallery to date, so it makes sense to support that project.

My main problem right now is time. I don't have time to TRY Node Gallery and see how it works. I need to sort out the showcase section of my own site and I could use it for that, but it's the TIME.... =(

I'll park this and ping you when I am next on the CCK Gallery project. Was going to say let's hook up on IRC, but Druplicon said:

(11:36:07 AM) gregharvey: Druplicon: seen kmonty
(11:36:08 AM) Druplicon: kmonty was last seen in #drupal-support 41 weeks 10 hours ago saying 'If not, Garland does a liquid layout, as does Zen'.

So I guess you're not a regular. ;-)

Alternative options are always welcome...

currently none of the galley modules are complete or bug free.

for node gallery, I am totally disappointed as it breaks continuity of upgrading from 1.x to 2.x, it is discouraging thing from using module.

Jury is still out on this. Node Gallery guys helped me out with an imagecache preset installation bug, so we are talking. Overwhelming feedback from users of *this* module (CCK Gallery) is that they prefer it and don't want to see a merge.

That said, support both products for Drupal 7 seems a bit daft. As such, I've created this issue to continue the debate:
#684706: Collaboration with CCK Gallery for Drupal 7?