views

"Relationship" I understood as relationships between fields (nodes are many relationships, which are subject of more advanced process).

Wanted features:

1. Powerful and without limitation thanks to the most abstract (see: "everything is a field", compare this to: Global CCK fields, A controversial(?) point: store translations as nodes).
2. Build-in categorization features.
3. Build-in views features (listing fields, not necessary nodes).
4. Build-in menu features.
5. Support for Semantic Web/Microformats/similar.

Observations about current situation:

Hello views aficionados. If anyone has the time, could you review the module posted in

http://drupal.org/node/103171

It's a module (that I will recode as a patch to views itself, eventually) that provides views within forms. These views can be used to select nodes. It includes exposed filters and a pager, and it generally behaves exactly the same as any other view would.

The module even includes a test harness where you can click a few buttons and test the new form element with any view on your website.

This is not production code, but I wanted to alert people early. Please do review this module and let us know what you think. It's a lot of code, and may require some changes to the underlying views implementation, so the more people who try it, break it, and suggest changes the better. Also, you can use this to start testing with your own modules.

I'd like CCK to do tables :-)

One existing solution is the Matrix Field module: it provides a new field type where you can set up a matrix of textfields. The data type is string, and seems to be independent from the other CCK field types.

This doesn't meet my needs because I'd like to mix different CCK fields, for example a column of nodereference fields with a column of number fields.

I want to start compiling a views FAQ.

There are LOTS of frequently asked questions, and particularly in the areas of HOWTO. One of the problems I have, as a person, is that I need this data to be compiled before I can act on it. Therefore, I'm asking people to help me out a bit.

Please, comment here with common questions (and answers if you have them, but they are not as necessary). Give links if there's an intricate discussion involved.

With Views it's pretty easy to build a simple FAQ engine just with taxonomy, so that's going to be one of the first FAQs. The only additional piece that I think is needed is weighting, and I believe weight.module will do that without any fuss or muss.

I have a mostly-working Views Calendar module available at http://www.drupal.org/project/calendar. It's still a little buggy and the css needs tweaking but it is generally working. Create a view and select the Calendar display (instead of table or teaser). Add any date field to the view (CCK dates, event dates, node updated dates, whatever). Add three arguments, Calendar: Year, Calendar: Month, and Calendar: Day.

Navigate to the view where you will see a year of mini calendars. Click on a month name to see the month or a day name to see the day. Back and next navigation is provided for month and day views (not yet added to the year view). It comes with a default calendar that displays all nodes in a calendar by their last updated dates. If you like, select the Calendar view for the block, too to get a mini calendar in a block.

I believe the evil credentials of views and CCK are well established. I wanted to unveil a new module that combines the two into an unbelievably devilish system: viewfield.

Viewfield allows content type administrators to add view reference fields into CCK content types. When a user creates one of these nodes, he/she can select from a list of views to embed into the node. When the node is viewed, the view runs and is output as one of the node fields. (Of course this can be themed).

Earl Miles has integrated some very cool audio/playlist functionality into his Views Bonus pack. After trying it out on my test site (filtered on audio per user), and some helpful feedback, it's looking like there are all sorts of possibilities and applications.

Here are just a few of the things (I think) we can create:

• playlist for any sort of music related article (posted about that here)
• event and/or venue specific playlists - specific to those performing an event; upcoming/previous shows for a particular venue
• location based - bands coming to a certain area
• artist/album specific playlists
• genre-based playlists
• playlists for a specific year
• maybe even playlists based on organic groups or buddy lists?

In addition to music, wouldn't the same sort of dynamic functionality work for other node types such as podcasts or even video?

Hey together!

Is there any current development inprogress to integrate USER location-data in views?
The great location_views module does an excellent job regarding the integration of node-locations ... however, often you (well, at least i ;) need to integrate - and later proximity-search - the location of the user who posted the content.
Example: a Skill- or Equipmepment-Database build with CCK, location and views, where Skill- or Equipment-nodes are added by each user and listet/searched via a view. There you need to display and proximity-search for the user's location - not a node-specific location (since not a single skill or equipment has a - maybe changing! - location, but it's user).

Since part of the purpose of this group is to track views development, I thought I would share my solution for creating flexible date range arguments for the Date module.

Creating arguments for date fields is hard because there are so many possible ways people might want to use them. You may need to find a full date or a part of a date or you may want to look for a date + duration or maybe specify that the duration will start on the current date or some other date, etc. etc. In creating arguments for dates I have been finding that the list of arguments in views gets longer and longer, but no matter how many you create, someone will always come back and ask for another type of argument.

Just an FYI, I created a Views Bonus Pack module.

Any dev who wants commit access to add plugins, just ask me. The idea being that this is just a collection of Cool Stuff that people can grab.