Hello,
Playing with CCK and Janode in a moment, I have an idea, why not integrate Janode with CCK?

The module will still provide its own content type if needed, but a widget for CCK can be maintained concurrently (i.e. they use the same underlying code). This will solve many problems at once. Multiple values in a Janode won't be any problem because CCK already handles this. Changine the name of the content type is also trivial in CCK.

My suggestion is that Janode acts as a replacement for the standard CCK weburl widget that validates the URL.

Comments

AjK’s picture

AjK commented
Assigned: Unassigned » AjK

I've been "toying" with this idea for a while now. Haven't decided yet but it may be better to contribute to the weburl widget as opposed to integrate with CCK. I'm all for collaboration over duplication ;) Janode only came about as "my boss" wanted it's functionality "right now" and was stuggling with CCK. So, janode is meant to be simple for just that reason.

On a side note, the current cvs head version has more features than the drupal-4-7 released version, is stable and 4.7 compatible. So, if you are "playing" with janode, I'd suggest you use the cvs version to "play" with.

thanks for the feedback and best regards,
--AjK

AjK’s picture

AjK commented
Status: Active » Closed (fixed)

CCK has a type "link" so this is never going to happen.