Also operate as taxonomy widget ONLY

In the description of the module on the main page, it is implied that storage of data picked up by these widgets is optionally stored in EITHER cck OR taxonomy:

"Additional it's possible to control, how the terms are saved to the node. Default, the terms are saved via the Taxonomy Module. This means, that the saved terms are available to the core taxonomy system and further contribution modules as the tagadelic can be used without any problems. Contrary it's possible, that the storage is done in CCK tables (which might be more efficient)."

However, in the field widget text, it says the opposite:

"Save values additionally to the core taxonomy system (into the 'term_node' table).
If this option is set, saving of terms is additionally handled by the taxonomy module. So saved terms from Content Taxonomy fields will appear as any other terms saved by the core taxonomy module. Set this option if you are using any other taxonomy application, like tagadelic. Otherwise terms are only saved in the cck tables and can only be accessed via the node or a view"

This is contradictory and very badly written. In any case, I think it is far more beneficial that the data would be stored in the taxonomy tables - otherwise, the admin could have set up the data as a CCK field instead and themed the field handler. The fact that this module acts on taxonomy and DOESN'T (or does it??) store the data in taxonomy tables by default is very confusing and should be reversed, IMO. If the vocab has been set up, the implication is obvious that it is there for a reason, so why reverse the logic in the first place??