Lycos - 28 January 2010 04:19 PM
Are these features ready out of the box ? (if so - man thats awesome) Or is there any tuttorial you can link me to.
Yes, they come with User:
http://www.solspace.com/docs/detail/user_register/#select_member_groups
Lycos - 28 January 2010 04:19 PM
What i meant was - let me give you an example .In case of the “Global member_custom fields” for example the {Aol_im} tag is global no matter where you paste it. Meaning let it be forum or wiki or whereveer you put - {Aol_im} will appear without problem. (if you add any value that is). But normal custom fields do not go over member module thus cant be seen by the rest of the site. Lets assume i add a custom field named {the title} - can i use this tag wherever it appears?
You mean, when you create new custom member fields, will they be available in other areas of your site? 
Yes, many module tags will support them, and if not you can use the User:Stats loop to display that data. And in case this isn’t clear, User does not have it’s OWN set of member fields. It just uses/shares the regular EE standard and custom member fields. 
Lycos - 28 January 2010 04:19 PM
And In the case of membergroup based custom fields - Lets say i mage groups in the idea of hieracy of power. The users first become novice and has only profile fields allowed for them to edit. Later on they become teachers (lets say this is the title of the next level of member) and they are allowed for avatar and signature etc. As higher they get- more fields are allowed for them.
Yes, as I mentioned before, you’ll need to use conditionals based on the user’s member group to display/hide certain fields from showing 
Lycos - 28 January 2010 04:19 PM
And last but not least - these talks about profile would make me thinkthat whether if we can maybe divide the EDİT PAGE to many sections fitting our expectation rather than one page. Like in page one you got avatars - in page two you got profile fields etc.
Yes, absolutely! The User:Edit tag can totally do that. 
Lycos - 28 January 2010 04:19 PM
I tried to read the docs again but still kinda clueless with whats going on. I think adding little images to show what this module does (or yet better - a demo) would be wonderfull. After all its nearly a 100 bucks of investment.
Fair enough… however, it’s sort of difficult to display a demo of User when it’s almost purely template based. But if need be, you can have a look here on the Solspace site… we use User here for our Register form, Forgot Username/Password form, Profile pages, Edit/Update Profile pages, etc: http://www.solspace.com/members/
Lycos - 28 January 2010 04:19 PM
Also I know its out of topic but - whats the difference between Diggie - favorites and Rating. Arent they (in the matter of “idea”) doing the same thing under different names? I mean - in the core ;its whether we like a post or not. If we like it - do we rate it ? Or fave it or Dig it?. Its very confusing.
Also rating has review box (from the pic i see on its page) . Is this added instead of Comments? If not whats the difference between comments and reviews.?
Rating allows you to have users submit form-based ratings/reviews for weblog entries. You can also create several custom rating fields that would allow you to have multiple types of rating fields or written review fields, etc. It’s more of a traditional Rating/Review method. Many people have used this as a replacement to Comments because Rating is like Comments but lets you do a lot more. 
Favorites allows your users to save/bookmark weblog entries and visit them at a later time by seeing a list of all weblog entries they’ve saved. Favorites also allows you to rank a list of entries by most Favorited/bookmarked, etc. It does more, but that’s it’s primary purpose.
Diggie works similar to Favorites, but it allows your users to vote on weblog entries, which could be a simple +1 / -1 like Digg.com, or it can go as far as having a set of custom values (+3, +2, -5, etc). Users can also vote multiple times, cumulative or non-cumulative, based on your settings. So it’s possible to display entries that have a “sum” values of “+258” or even “-73”, etc. We also have a filter in place that allows you to stop displaying entries that have a lower value than “X” (whatever you specify), etc.
While each may overlap a little, or seem similar, they each perform different tasks and use different methods.