User engagement

This module provides a new content type called dnd_character to allow users to store their player characters for Dungeons and Dragons. This is a Features package which contains the fields and content type needed to manage the character.

This module is not a character generator, and does not (currently) enforce many of the rules. It is merely a record-keeping utility at this point. Future plans are to impose SRD rules and provide a way to add house rules, but this isn't currently available.

This project also contains two additional modules: D&D Fields and D&D Character Sheet.

This is intended for use for D&D 3.x.

Description

Vote defines a new entity type (vote). Votes can be cast on ANY entity type that "your drupal" knows (even on "vote" itself).

Vote provides "functions" and "voting types":

A function basically provides a handler which defines how and where a function stores its result values. Each function can have its own db table to store the results in order to allow more complex functions to break the INTEGER barrier which the default result table uses for its results.

A voting type basically combines a group of functions. For example a voting type "percent" would combine the functions "average" and "count" while "points" would also use the "sum" function.

Voting types and functions both use a set of classes as handlers to provide custom option forms and advanced (and individual) functionality for each function / voting type. The functions handler -for example- makes it possible to store function result values in seperate db tables with different table structures.

A module to include a fivestar rating component within webform.

The code is stable and it mainly implements webform component hooks. Bugs and feature requests welcome.

Forms based on entities.

Status

The first Beta is released. We like to rethink the permissions before releasing stable. We also need to test more with features and ctools exports. Furthermore it is bug fixing! Fill that issue queue!

Description

Ever needed Webforms with complete Views integration?
Since Forms is build on the fieldable Entity layer, you get full support for Rules and Views out of the box.

When you are building long forms or expect a lot of submissions, the Webform module is probably a better choice. This Forms module is compared with Webform heavy, but more flexible.

The Forms module now comes with:

• Views support
• Rules support
• Features support
• Fields support
• A Field to attach a Form to another Entity (e.g. Nodes)

All Fields you use in nodes can be used in Forms as field, including images, files and dates.

Multi page Forms is supported with Field group or with skilip's sandbox project Page break field.

Use Forms with other Entities

This module adds functionality to reduce userpoint each time a user performs an extension of node expiry period.

The Yahoo Query Language (YQL) API Module only provides a mechanism for module developers to query the Yahoo's YQL databases. It is mainly intended as a launch point for developers to create plugin modules that harness the YQL API.

GitHub Repo is here https://github.com/sfstate/yql-drupal/tree/master/yql

To learn more about YQL check out: http://developer.yahoo.com/yql/
Also try out the YQL Console: http://developer.yahoo.com/yql/console/

A working example module is included with this package, yql_autotagging. In addition, a block is provided to test your YQL queries. The block itself contains an example query for textual extraction. The YQL autotagging module harnesses the power of the YQL API to provide term suggestions to the autotagging (http://drupal.org/project/autotagging) module. In this way, nodes can have taxonomy terms created automatically based on contextual analysis of their contents.

In order to use these modules, you will first need to enable them as usual. For instance, go to Site Building -> Modules and check the boxes for these two modules.