Home > News > Announcements > CCK Development for XOOPS Cube

CCK Development for XOOPS Cube

gigamaster submitted 2009/11/7 21:15, published 2009/11/7 21:15 | 35937 views
Tags: ,

Hi all,

Quite a while since our last post, and that's with good reason. Past few weeks, we prepared what you could call the 'launch of the XCCK development'. Or in other words: we took the time to prepare the development of the Xoops Cube CCK, to sit back think about it, write down the wanted features and prepare for development. And today we can finally present you with what we're actually trying to build, as did we set up a project on sourceforge, organised a tracker, wiki, forum, homepage

For now we have about 4 developers in the team (Nuno Luciano, prof. Hidetoshi, Eikasai and Dirk Derom), but as you might expect, we're eager to get more developers on the project, so this post is not only to inform but also to attract anyone who wants to contribute in whatever way he/she wants to, be it design, coding, documenting

Btw, you can read this post in two ways: short version is to skip all that follows in this post and go straight to the feature list and project overview to get an idea on how we're currently organised (=project overview) and what we're trying to develop (feature list). Or you can read through this post (the following content can also be found on our homepage) and then go to the feature list and project overview.

For those who like some more info:

What are we trying to achieve?

  • Build a CCK for both power-users and end-users
  • Easily create both static as dynamic fields
  • Build powerful import and export features
  • Be open source

Goals of the CCK

The Xoops Cube CCK is not only about

  • Adding custom Fields (back-end)
  • Allow for rigid input control
  • Adding custom views (front-end)
  • ...

...but also about

  • Managing the data flow
  • Powerful permissions settings
  • ...

Potential usage of the CCK

The application of the planned CCK vary significantly, so do check the the feature list (aka 'wish list') to get a grasp of the potential usage. However, how about these examples:

  • Reviewed magazine where posts have to go through an 'automated' review process before they are submitted with e.g. a minimum of 5 moderators approvals before being published
  • Server/client databases where one is able to import/export data to a local install without any data loss and no DB breaks
  • Peer reviewed scientific journal ('automated' review process') or in other words and open source/knowledge journal
  • ...

The Xoops CCK differs from other CCK's since it allows to not only create custom fields and thus expand the upload process, but also to control what is entered in the form (control of values pulling data from custom value definitions, remote DB's...) and obviously present the entered data at will.

However, it does not stop there since this CCK aims to control the data flow: when is data entered, does it have to go through a review process, does it have to be approved and by whom...

Flexible yet user friendly and powerful...

Various CMS do have (some kind of) CCK, this project differs from those CCK's mostly by the (integration of) various features and yet remain user friendly. Or in other words: the goal is to build a CCK where users with arious levels of expertise can build and use the CCK to build complex forms/views/content.

Further Reading

For a detailed description of our feature list (aka 'wish list') check this wiki page.

Hope you guys are as enthusiastic as we are and look forward working with the community to get this thing up and running. If you would like to contact us, you can reply to this post, send Dirk a pm or email (dirk . derom at gmail . com) or post on the forum.

Comments (0)

Newest first | Oldest first | Nested view | RSS feed

Trackbacks (0)

Newest first | Oldest first | RSS feed

Welcome | News | Overview | Documentation | Forum | Tutorialstop
Brasilian | French | German | Greek | Japanese | Korean | Russian | T-Chinese
Powered by XOOPS Cube 2001-2011 The XOOPS Cube Project