Rewrite of RepTag
| Project: | Rep[lacement]Tags |
| Version: | HEAD |
| Component: | Code / API |
| Category: | task |
| Priority: | normal |
| Assigned: | profix898 |
| Status: | active |
Jump to:
For now this is just a placeholder, and probably an announcement, for details and discussion on a rewrite of the Rep[lacement]Tags module.
Reptag was drafted in autumn 2005 and a first version was implemented shortly after (Feb 2006). However, in the last 3 years Drupal has evolved and now makes up an even more dynamic framework. We have CCK (and 'Fields in Core' for Drupal 7), Views, Panels and the competiting Token module. For that reason I started to rethink the internal design of the module about 2 months ago. The major design goals are (in no particular order) to make RepTag ...
- smaller and faster
- easier to interface/integrate (with cck, views, rules)
- compatible with Token (aka "move token.tags.inc into reptag core")
Due to heavy workload in my dayjob the redesign already takes much longer than I expected. However, I hope to commit a first version to CVS (6--2 branch) in May.
#1
Today is 7 May 2009 (in Australia), I hope your wonderful hoped rewrite of this super hopeful module has taken place.
If I may place a major wish on your rewrite wishlist, I would like to be able to view all tags in the edit form without a pager, so that I can see all existing tags and definitions in one place ! Also, it would be nice to be able to generate a list/view of all occurrences (usages) of a given reptag. Keep up the $good$ work on $this$ great module.
#2
This is great news, as I've said before this is a great, well-thought-out module that fills a real need.
My first wishlist item would be #462062: Reptag should be able to process non-node text easily