q.tagger

[andy]

me again...

Going to be having a go with q.tagger soon, im looking at maybe
subclassing it to produce something along the lines of the demo here:

http://devthought.com/wp-content/projects/mootools/textboxlist/Demo/

as im looking to have a tag list that is user generated showing the
tags in the box with the remove buttons and allowing people to add
them by simply typing in a word followed by comma, the comma (or
whatever char is chosen) would fire the event to turn it into a tag
and add it to the list - firing an event so the user could pop some
ajax in there or ping a q.informer etc, so slightly different to
current way of thinking where user selects from tags.


do you think its best if i subclass q.tagger - or create a new
superclass to do it...

Im thinking subclass would be best as it could be a useful addition
once done if you wanted it...


andy

[wonderingwout]

I see what you mean, but we took another approach with Q.Tagger.
People type tags in the textarea / text input, not in the actual
taglist.

Once your page with thags is saved the tags added by the user will
appear in the list.
Looks a little less fancy but it works very effective.

We use it a lot in combination with the acts_as_taggable_on gem for
Rails:
http://rubygems.org/gems/acts-as-taggable-on

If you want that kind of functionality, go ahead and subclass :-)
We're more convinced of the current way it works.