filters

Edit: There is now an offical project page on d.o. The module is nearly ready for a beta release, so the more people that test it, the better.

I have created a filter module for 6.x that in it's current state will allow posts containing:

[item]1234[/item]

-or-

[item]Earthwarden[/item] (for example)

to be converted to WoW DB links. The javascript for mouseover popups is embedded, and results are cached for performance.

Drupal is formatting the user input by applying a set of customized filters before the content is send to visitor’s browser. In other words the user input is stored untouched in the database (except the SQL injection filtering) and then the filter module is performing code cleanup and formatting at the HTML output. In fact the input formats are... output formats :)

This patch to the Formtweaker module, modifies views filters, so they render as checkboxes and radio buttons, instead of select boxes and drop down menus.

Currently there is no way for a user to choose between rendering a filter as checkboxes/radio buttons, or as the default select menus.

How is it done?
How do I add this condition (as a checkbox in the exposed filter section I guess) to the views ui?

Hello mappers,

I have a proposal that I think will make the gmap module stronger, but I wanted to solicit other opinions before I start writing the patch.

I recently was working on two additional gmap functionalities for a client: the first was the ability to load KML files located at an offsite URL as overlays, and the other was a "click to add nodes" functionality so that users could add images by simply clicking on their locations on a gmap.

In both cases I started trying to build my functionality as add modules to gmap. This quickly broke down as I discovered the macro processing was hard coded and not easy to work with. Additionally, I attempted to modify the gmap module itself, but again working with the macro processing was such a headache that I abandoned that idea as well. Finally, I developed these tools as stand alone JavaScript additions, with not UI in Drupal. Not an optimal situation, but I had to get these features out in a reasonable time frame.

I've been thinking about my experience since then, and I have come to the following conclusion: the gmap macro hinders development of the gmap module and prevents additional module development. Therefore, it should be discontinued in favor of a simpler, UI and data model driven alternative, similar to Views.