If Flexinode components could be shown as fields, this tool whould complement the flexinode-module and make Drupal a powerful RAD-tool for web applications.

I think a refactoring that let the view-module fetch the code for each module taxonomy, flexinode etc from certain module would make the module easier to extend and maintain.

Comments

robertdouglass’s picture

This work has already been started and is called the CCK (Content Construction Kit). Join the effort - 2006 is the year of CCK!

robertdouglass’s picture

Ahhh.... re-read your post. You probably already know about CCK. Still... you might consider trying to integrate Views and CCK instead of Views and Flexinode. Most of us are looking forward to being able to replace Flexinode with something better.

scroogie’s picture

Well, but looking at the pace of advance in CCK, it seems to be valuable to have Views integrated with flexinode first.

robertdouglass’s picture

Judging from the historical pace, yes. But two things to consider: 1) CCK needed the forms API in order to move forward, so that roadblock has been cleared. 2) John VanDyk is on a funded sabbatical in 2006 and one of his (and Matt Westgate's) primary goals for that time is to finish CCK. So the pace in the future will be somewhat of a different story. Besides, CCK works, now. It's just missing some of the features that it will eventually have.

merlinofchaos’s picture

Flexinode integration is on the queue for the 4.7 version. I don't know that it'll be done with the 4.6 version, however, as the 4.6 API was not completed.

Likewise, CCK integration as well, which definitely will not be done with 4.6.

Any module can be made to work with Views in 4.7 by using the API to tell Views what tables and fields are available.

forresto’s picture

How is this coming along? I'm interested in changing the default flexinode layout.

merlinofchaos’s picture

I did CCK integration, but flexinode integration is difficult and I am unlikely to do it myself.

If some enterprising soul wants to give it a shot, more power to them; I, however, don't consider it a priority. Instead I am going to hope that CCK is ready to be a flexinode replacement soon enough that this won't matter a lot.

For what it's worth, you can still do flexinode layout stuff reasonably well. Look at http://drupal.org/node/52032 -- dgtlmoon did some neat stuff using views, flexinode and smarty.

Bèr Kessels’s picture

Version: 4.6.x-1.x-dev » 6.x-2.x-dev
Status: Active » Closed (duplicate)

Moving this to http://drupal.org/node/54129. I registered an issue over at flexinode to work on this.