Under active development

This module provides a counter that indicates the max. limit of characters in a certain text field. The soft limit means that the user will be warned if the content length of the field is exceeded, but he will still be able to save all data in the field.

It basically does two things:

* Lets the user configure any instance of a text field's widget, to have a specific soft limit. This is done in the usual field settings for entity types. This counter will always be shown on fields with a soft limit, no matter the settings mentioned below.

Makes all system entities available to the oEmbed provider.

Usage:
Install module and go to:
http://example.com/oembed/endpoint?url=http://example.com/user/123
to retrieve the oEmbed code for an entity with ID 123 and type user.

As a third URL argument, the desired view mode can be specified. This view
mode is passed on to any default or custom viewer functions.

Nodequeue Suggestions

This module allows the administrator to specify that a certain nodequeue
contains suggestions for another nodequeue.

To use this functionality, create two node queues, and specify that the second
queue has the first queue attached as a "suggestion queue", by checking the
box and choosing the second queue.

Nodes placed in the queue specified for suggestions, will now be treated as
suggestions for the main node queue.

This module solves the issue of referring to both external and internal content from within a node.

It creates a field type which may both refer to an external URL, if an http:// (or other allowed protocol) link is entered, or autocomplete on node titles, to refer to internal nodes by their node ID.

You can also specify a custom title or use the referenced node title or URL as default title.

This project will enable site authenticated user to send cloud message (via either Apple APN or Android GCM) to each other, kind of a replacement of short message to save cost. Two separate client (currently Apple and Android) will be provided for device registration and push receiving purpose.
The project is the placeholder for now. Cheers.

test

Hi,
As per the requirement I am responsible for developing the core Integration between the Drupal with diffrent technologies.
I contributed in developing generic API for Integration.

Drupal 6 does not search taxonomy terms, this is the solution for that.

The goal of this project is to provide a method for users to easily configure access settings to their own entities. The interface for configuring access will come from a shared access field attached to the entity.

A very small module enabling users to select a filesystem to upload to during upload.