Views

This module takes a user's time budget as well as a list of tasks (issues/cases/bugs/...) with a specified time need, and uses this data in order to calculate estimated target dates for these tasks. Optionally, target dates are then also calculated for milestones that depend on these tasks.

In order to retrieve the required data, project forecast uses various data sources: the Time Budget module for determining how much time a user plans to invest, and Views/CCK in order to retrieve the list of tasks for each user as well as some other information. For a basic working forecast, you need the following set of views and CCK fields:

• A view of tasks that need to be done or have already been completed.
• One or more filters for the above view that make an "open tasks" view out of the general "tasks" view. For correct calculations, the tasks in that view need to be sorted in the order in which they're expected to be completed.
• A "Number" or "Duration" CCK field in the task content type that specifies how much time is still required for the given task.
• A "User reference" field in the task content type that specifies which user is assigned the given task.
• And a "Node reference" field in the task content type that links to the project which contains the task. Required because the Time budget module allocates the time per project, and estimates are in consequence calculated independently per project.

If you're a coder, you can add value providers for the "hours", "nid" and/or "uid" value types in order to use e.g. the Project module's tables instead of a CCK nodereference. That's not supported out of the box though, maybe it'll be included one day.

Apart from the admin settings, this module does not directly provide a visible UI - instead, it provides Views fields that you can use in your own views, as addition to a list of tasks or milestones.

Adds Views2 support to the Ad module for Drupal 6.x and Views 2.

A streamlined interface for building Views. Administrators make a few simple choices (What kind of content should be listed? Do I want to sort by date, or by title? etc.) and a view is generated on-the-fly. Because the Views API is used, the resulting views can be modified using the full Views UI module.

In addition, every content type gets a simple checkbox on its configuration screen: "Make a listing page for this content." When it's checked, the module... makes a custom listing page, complete with RSS feed, filtered to just that content type.

Flag is a flexible flagging system that is completely customizable by the administrator. Using this module, the site administrator can provide any number of flags for nodes, comments, users, and any other type of entity. Some possibilities include bookmarks, marking important, friends, or flag as offensive. With extensive views integration, you can create custom lists of popular content or keep tabs on important content.

Flags may be per-user, meaning that each user can mark an item individually, or global, meaning that the item is either marked or it is not marked, and any user who changes that changes it for everyone.

In this way, additional flags (similar to published and sticky) can be put on nodes, or other items, and dealt with by the system however the administration likes.

Allows you to create a feed for a view, much like Views RSS, except you can specify any custom markup you want (XML, JSON, whatever) instead of just RSS. The module works by providing a view argument and was largely copied from views_rss and modified.

WARNING: This module is intended to allow the quick creation of simple custom feeds backed by views. There are 2 main problems with this module:

Description

Select translation implements a Views filter to select which translation of a node should be displayed in a list of nodes.

Several modes are available to select a translation:

• Use the current interface language; if not available use the original node language.
• Use the current interface language; if not available use the default site language; if not available use the original node language.
• Specify a list of languages, and use the most appropriate language.
  
  Some special values are recognized in the languages list:
  • "current" will be replaced with the current interface language;
  • "default" will be replaced with the default site language;
  • "original" will be replaced with the original node language.

PLEASE NOTE: Development is currently on hold due to lack of time :(

About

Config to Code module for Drupal 5 makes it easy to deploy new views and panels and to version-control changes to existing ones with a source code repository like subversion. It makes it quick and easy to move configured views and panels in the database to code, then safely delete the configured views from the database and finally, expose the views and panels in code back to their respective modules. It is extensible for other types of configurations that can be stored both in database and code.

Defines a field type View reference which creates a relationship to a Views display and allows the view to be displayed as the content of the field.

This module is modelled on Node reference and usage is similar.

Allow the use of a mini panel as the style for the display of a view.