add new user role when profile is completed to xx %

Good idea, if anyone can make a go at writing such an action I will put it in the module.

The rules integration!

It adds a rules condition that compares (>=) the defined content type completeness value with a defined value ( if you negate it, then you have <)

I have tested it with a rule that when user log in and then shows a message in screen depending of the defined values, but it can be integrated with any action.

Thanks for the code, I will test it and add it to the dev version ASAP. Next to rely on rules, and before releasing a stable version, I also want to have support for the core triggers/actions, so we need to implement our own trigger.

You should define what kind of event could be fired by the content completed module.
I was thinking about that when writing the code. Some ideas:

- define into the module a trigger level that when reached then execute the rules trigger against this possible trigger (but I think that it is better that it should be defined by any rule)
- activate o deactivate fields to be included into a completed status (¿?)
- activate o deactivate a block (¿?)

Also the same for the actions:
- the only one that I thought about was to write the completed percent or next field available into a message

The rest of actions are triggered by the existing rule condition and are executed by other module rules,
also it is possible to chain events triggered by that condition in some moment (already defined as actions in other modules, log in, log out).

Patch for rules integration has been added to CVS. I made a modification so the user parameter is taken into account when computing the completion data.

For example, it should be possible to run completion checks for users combined with scheduled rule sets, so you could bug your users every day by mail to complete their profiles (I haven't tested it though).

Using core actions/triggers is indeed a bit more tricky. The completion check could be implemented as an action and triggered upon user login for example. Then the value of the action should on its turn generate another trigger on which another action can hook into (eg write an email if the percentage is > x%). As far as I know core actions/triggers do not pass arguments (hence why the rules module). Is that correct?