Sweet module, and I'll just float an idea - make the template selector a CCK field. The only reason is so that the module can leverage Conditional Fields since additional fields may or may not be desired depending on a selected template. If you're on board at all with this idea I can probably help with some patching.

Comments

WebNewCastle’s picture

WebNewCastle CreditAttribution: WebNewCastle commented

Hi Manatwo,

This is very interesting. I'm a bit tied up at the moment, but I would like to chat / look into this with you so more soon.

dabblela’s picture

dabblela CreditAttribution: dabblela commented

Ditto on the tied up thing, I had developed a very rudimentary CCK solution for a site I was working on and had wondered if there was something more "polished." It might not be worth the trouble converting until #648934: Plugin system for compatibility with non-core CCK modules is resolved or at least has a direction, be a shame to do all that work and then have to re-write.

WebNewCastle’s picture

WebNewCastle CreditAttribution: WebNewCastle commented

Hmm, that is interesting. I was reading through that thread and another linked from it, then I went back to the main project page. At first, I thought maybe this wouldn't necessarily be an issue. But since the discussion is about non-core CCK in general, I don't know.

Just to make sure I'm not making false assumptions, you're envisioning the node template selection as the controlling field, right?

dabblela’s picture

dabblela CreditAttribution: dabblela commented

Most definitely, and I think CF supports radios so #666492: Hack with vertical tab support and using radios with images instead of select box is still in play.

WebNewCastle’s picture

WebNewCastle CreditAttribution: WebNewCastle commented

What do you think ... is it worth giving this a shot this month or do you think it's better to wait?

dabblela’s picture

dabblela CreditAttribution: dabblela commented

I say let's go for it, at the very least there's a lot of groundwork for CCK modules that I would think wouldn't have much effect on conditional fields - I'm not sure exactly, I think the part we have to worry about with regards to conditional fields is the part that defines the widget.

How do you want to handle development from here, is #666492: Hack with vertical tab support and using radios with images instead of select box included in a cvs release that we can patch against?

WebNewCastle’s picture

WebNewCastle CreditAttribution: WebNewCastle commented

Hi, sorry for the delay. Will you give me just a few more days to respond more fully? I'm pretty open on process. The vertical tab support is in the current version too, and I also added support for re-ordering on the node form.

The other main thing that I've still been trying to think through further is overall direction. What I really wanted to see is a module that provides this same functionality for more than just the node template including pages, blocks, views, etc. But that means some overlap with other modules, although it differs in usability to some others. But I haven't quite had time to think through what would be best or if just keeping this separate and continuing development is best, etc.