Site structure

Simple GMaps v2 implementation.
Alpha stage.
No additional tables in db, uses CCK to store all data.

Requirements: CCK

Only one marker per one gmap is possible.
This module was created for internal use, for our clients websites, when I was tired of fixing bugs/simplifying interface of GMaps related modules available. (Some of them are >200kb of PHP code, I was sure I don't need 95% of this code on our websites - they are already heavy because of cck/views, really).

I've made simplest_gmap public - may be someone will find it useful :)

If you need maximum of functionality, check out much more advanced
http://drupal.org/project/gmaps + http://drupal.org/project/location

Aims of simplest_gmap project:
- simplify interface to create marker for editor
- minimize peroformance overhead and code amount

Usage:
1) Enable module on Drupal admin
2) Insert your Google Maps API Key on admin/settings/simplest_gmap
3) Create CCK field for GMap. You'll see available settings on field creation page.
That's it!

This module was developed by Pixeljets team.

Donate via Paypal / Webmoney / Yandex.Money

This module was written against an older version of the GMap module, and a development version of the Geo module. If you would like to use this code, it will require some heavy lifting. If you are interested in taking over this project, let me know.

Gmap_geo provides a Google Map location picker widget for Geo point fields and a Google Maps-based output formatter for point, line, and polygon fields.

HOWEVER: Gmap_geo was written for an earlier iteration of the Geo module. It has not been updated to use recent Geo API changes. If you are interested in maintaining or helping to maintain this module, please contact bec.

Requirements:

• Geo
• GMap (version 6.x-1.1-RC1 or later)
• CCK

Gmap_geo adds functionality to Geo CCK fields, so to use its functionality you will edit a content type.

• When adding a "Geospatial data" CCK field to a node type, among the widget options you will now see "GMap picker" along with the default "Direct Text Entry" and "Latitude / Longitude".

Extends the Event module by providing a vCalendar file to download per node which will provide a vCalendar file to import into Calendar applications.

This extremely simple module allows you to easily open links to external sites or PDF documents in new tabs. It uses jQuery instead of target=_blank so the markup will still validate.

The interface module allows site administrators to modify the way entities look through a drag and drop interface. It uses plug-ins to present information in different styles, such as tabbed interfaces, complex page layouts, and the like.

The original D6 version of the module was concerned only with content entry forms. The D7 version is a complete rewrite and is concerned primarily with the presentation of entities, especially ones lacking a conventional layout in relation to typical content in a Drupal site. It will also support modifications to entry forms, just not yet.

Features include:

* Drag-and-Drop Authoring Tool

Form elements can be moved around on a page by simply clicking on them and dragging them where they belong.

* Plug Ins

Interface uses a number of plug ins to control the presentation of content. The D7 version ships with a tabbed interface plug-in for right now, with others coming soon.

* Multiple Interfaces per Content Type

Interface allows users to create different layouts for each display mode associated with a bundle.

* API

Interface provides ample hooks for templates and behaviors to perform actions without needing to modify the core interface module. Documentation for developers is provided within some of the behaviors included with this distribution.

We need to have one good module. Not a lot of half good.
#894680: Merge similar "node repeat" module

This module is intended as an add-on for the Date Repeat module, part of the Date package of modules. It grew out of the feature request discussion at http://drupal.org/node/298334. Subsequently, it was orphaned and adopted.

Date Repeat allows you to specify a wide range of repeating date sequences. However, each sequence is stored in a single node. This means that all dates in a sequence share characteristics such as the description and other non-date fields. You can specify monthly meetings, but cannot change an individual description to add an agenda when it becomes available. You can specify weekly games, but cannot specify the teams in a specific game when they become known. Because the date fields are not in separate nodes, they do not work with Views.