Comments on: iContent http://nick.iss.im/2010/01/20/icontent/ (( nick . iss . im )) Mon, 01 Mar 2010 17:36:04 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: nick http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6429 nick Fri, 22 Jan 2010 13:45:56 +0000 http://nick.iss.im/?p=362#comment-6429 Awesome barraponto! You got the point! Indeed this is part of ISS! Awesome barraponto! You got the point! Indeed this is part of ISS!

]]> By: barraponto http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6427 barraponto Fri, 22 Jan 2010 09:34:52 +0000 http://nick.iss.im/?p=362#comment-6427 @dalin integrating the "icontent" with rdf you can actually sort it the way we are all used to in drupal. but you can also have some fun with SPARQL and sort fields on a lot of different ways. and having it integrated on a SQL-database means it can run just as fast as we are used to. @nick sure thing. now thinking about the ISS framework you've been developing for quite some time, i hope these ideas can fit together. i see icontent and iss as killer features for a blogger, since it means posts fields can be extended on the fly, rdf-support can help sort it out, the theme-layer can support some fields (we can actually have tables of rdf-support for themes) and feed readers can choose what to display (or not) to the end user (the reader). @dalin integrating the “icontent” with rdf you can actually sort it the way we are all used to in drupal. but you can also have some fun with SPARQL and sort fields on a lot of different ways. and having it integrated on a SQL-database means it can run just as fast as we are used to.

@nick sure thing. now thinking about the ISS framework you’ve been developing for quite some time, i hope these ideas can fit together. i see icontent and iss as killer features for a blogger, since it means posts fields can be extended on the fly, rdf-support can help sort it out, the theme-layer can support some fields (we can actually have tables of rdf-support for themes) and feed readers can choose what to display (or not) to the end user (the reader).

]]> By: nick http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6412 nick Thu, 21 Jan 2010 13:59:59 +0000 http://nick.iss.im/?p=362#comment-6412 @barraponto: Excellent comment! I hope to further discuss this with you at DrupalCon Brazil! @dalin: You can still sort/filter by author, date and title. The main benefit is having this flexibility. @victorkane: The key idea is empowering the average user with this flexibility (while still keeping it simple). Fields in core is an important step towards this goal. @barraponto: Excellent comment! I hope to further discuss this with you at DrupalCon Brazil!

@dalin: You can still sort/filter by author, date and title. The main benefit is having this flexibility.

@victorkane: The key idea is empowering the average user with this flexibility (while still keeping it simple). Fields in core is an important step towards this goal.

]]> By: victorkane http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6411 victorkane Thu, 21 Jan 2010 13:11:34 +0000 http://nick.iss.im/?p=362#comment-6411 Two things: 1. What about relationships between content types, that's a most important thing for Drupal based website applications; for example a newspaper with editions and articles which point to those editions. 2. This functionality is available in Drupal 6, at least as you are presenting it, not just Drupal 7. Victor Kane http://awebfactory.com.ar http://projectflowandtracker.com Two things:

1. What about relationships between content types, that’s a most important thing for Drupal based website applications; for example a newspaper with editions and articles which point to those editions.

2. This functionality is available in Drupal 6, at least as you are presenting it, not just Drupal 7.

Victor Kane
http://awebfactory.com.ar
http://projectflowandtracker.com

]]> By: dalin http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6407 dalin Thu, 21 Jan 2010 05:49:34 +0000 http://nick.iss.im/?p=362#comment-6407 But I don't see what the benefit is. You then have a bunch of unrelated content all under the same heading with no way to sort/filter/ it. The content is now delineated so you can tell where 'field' data starts and ends, but I don't see how that is useful either. But I don’t see what the benefit is. You then have a bunch of unrelated content all under the same heading with no way to sort/filter/ it. The content is now delineated so you can tell where ‘field’ data starts and ends, but I don’t see how that is useful either.

]]> By: barraponto http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6406 barraponto Thu, 21 Jan 2010 03:13:23 +0000 http://nick.iss.im/?p=362#comment-6406 in order to avoid confusion and loads of content types we hardly have any use for, we could link this idea to the rdf semantic model. once the dynamic typing of the content is set, expected fields would naturally show up. new fields could be added, and depending on the website editor/manager some of the fields could be required. this would help users creating new content, since choosing a content type usually restricts the user and adds a lot of confusion. would like to help getting this idea implemented. in order to avoid confusion and loads of content types we hardly have any use for, we could link this idea to the rdf semantic model. once the dynamic typing of the content is set, expected fields would naturally show up. new fields could be added, and depending on the website editor/manager some of the fields could be required.
this would help users creating new content, since choosing a content type usually restricts the user and adds a lot of confusion.
would like to help getting this idea implemented.

]]> By: roger http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6402 roger Wed, 20 Jan 2010 22:36:08 +0000 http://nick.iss.im/?p=362#comment-6402 This also called typo3 where you can add different types of content in any order to a page. This also called typo3 where you can add different types of content in any order to a page.

]]> By: Jeff Geerling http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6401 Jeff Geerling Wed, 20 Jan 2010 22:11:53 +0000 http://nick.iss.im/?p=362#comment-6401 It would be best, imo, if there were a way for the administrator to set up a bunch of more-or-less generic fields, and then on the node addition page, a pop up menu would appear if the user wanted to add a 'video' (using video field or emfield), a podcast file (using filefield/ffpc), or an image (using imagefield). That way the admin would still be able to control the fields, but the user would have a little less clutter/more freedom. Wordpress' fields are convenient for simple metadata, but they aren't all that flexible (even if you are good with PHP). It would be best, imo, if there were a way for the administrator to set up a bunch of more-or-less generic fields, and then on the node addition page, a pop up menu would appear if the user wanted to add a ‘video’ (using video field or emfield), a podcast file (using filefield/ffpc), or an image (using imagefield).

That way the admin would still be able to control the fields, but the user would have a little less clutter/more freedom.

Wordpress’ fields are convenient for simple metadata, but they aren’t all that flexible (even if you are good with PHP).

]]> By: nick http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6398 nick Wed, 20 Jan 2010 16:39:24 +0000 http://nick.iss.im/?p=362#comment-6398 Very nice observation Damien! You are completely right: http://codex.wordpress.org/Using_Custom_Fields But I believe Drupals' Fields are in a whole new level when compared with Wordpress' Fields. Very nice observation Damien! You are completely right:

http://codex.wordpress.org/Using_Custom_Fields

But I believe Drupals’ Fields are in a whole new level when compared with Wordpress’ Fields.

]]> By: Damien McKenna http://nick.iss.im/2010/01/20/icontent/comment-page-1/#comment-6397 Damien McKenna Wed, 20 Jan 2010 16:28:25 +0000 http://nick.iss.im/?p=362#comment-6397 I believe that is called "Wordpress" that has had custom per-post fields for years. I believe that is called “Wordpress” that has had custom per-post fields for years.

]]>