MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

Pro and Cons of API vs Source Code purchase (Closed) (Mono Support )

Viewed 18521 time(s), 7 post(s) 6/28/2011 6:33:05 PMby KrisBethea
KrisBethea

KrisBethea

6/28/2011 6:33:06 PM
So, what is it I can or cannot do with the API that I can do with the Source Code?
I'm under the impression I can pretty much use API calls to create the same functionality as the demo site but design it to be more personalized simply by using the API.

Thoughts?

Thanks,
Kris
This content has not been rated yet. 
37 Reputation 4 Total posts
denis

denis

6/28/2011 8:44:05 PM
Hi Kris,
It depends on your requirements. Getting the functionality similar to the demo site can be only a matter of changing skin CSS and master pages. You can also achieve a lot by simply inheriting the base pages/Web parts and adding or changing the default functionality.
Typically, you will need the access to the source code if you want to make more complex custom applications.
This content has not been rated yet. 
7207 Reputation 956 Total posts
KrisBethea

KrisBethea

6/28/2011 9:06:11 PM
So basically, until I get in there and try to make it do what I want it to do, I won't know...

I am hoping to hear input from others' as well. At this point, I don't want to ask my client to purchase the source code, but I also don't want that to come back and bite me.

I saw some the sample Monox sites that are listed but I don't know if they are coded with or without access to the Source Code.

Like, can I control the Reputation points? Make it so that reputation is by popularity only? Is the api accessible to add or subtract points?

This content has not been rated yet. 
37 Reputation 4 Total posts
khorvat

khorvat

6/29/2011 10:17:20 AM
Hi,

reputation points can be controlled in a few ways, you modify the default MonoX reputation points programatically by setting one of the following properties

MonoSoftware.MonoX.ApplicationSettings.Reputation.UserProfile.NewAvatarScore = 20;
MonoSoftware.MonoX.ApplicationSettings.Reputation.Blog.NewPostScore = 30;
MonoSoftware.MonoX.ApplicationSettings.Reputation.SocialNetwork.NewNoteScore = 5;
MonoSoftware.MonoX.ApplicationSettings.Reputation.SocialNetwork.Discussion.NewTopicScore = 15;

please take a look at the MonoSoftware.MonoX.ApplicationSettings.Reputation API documentation to get the full list of available reputation properties.
Note: Reputation default values are read-only in MonoX version prior to 4.1.2757

Every MonoX module (Web Part) uses these default values to initialize his reputation points and you can modify reputation points by using the MonoX Web part properties UI or by setting properties programatically.

Here is an example of setting Reputation points on several modules

Programatically
userProfile.UserReputationNewAvatarScore = ApplicationSettings.Reputation.UserProfile.NewAvatarScore;
or
userProfile.UserReputationNewAvatarScore = 30;
 
blogModule.UserReputationNewPostScore = ApplicationSettings.Reputation.Blog.NewPostScore;
or
blogModule.UserReputationNewPostScore = 35;
 
etc.

Using the MonoX Web part properties UI (see attached screenshot)

For adding or subtracting reputation points in your custom modules you can use the MonoX data model which allows you to modify reputation points (e.g. you can programatically add, subtract, reset points).  

I hope this explains a bit more the MonoX Reputation points layer.

Regards
Rated 5.00, 1 vote(s). 
15993 Reputation 2214 Total posts
denis

denis

6/29/2011 10:36:15 AM
It is really difficult to give you a definitive answer regarding the source code purchase without more information on your requirements. Most of the sample sites were developed without access to the source code, and that approach usually works for standard content-based sites and social networks. The opposite would be true if you need to develop a complex custom Web application on top of MonoX, or want to see how our infrastructure works behind the scenes, or need to tightly integrate pieces of MonoX functionality into your application, or have a company policy that requires the source code of all products...
This content has not been rated yet. 
7207 Reputation 956 Total posts
KrisBethea

KrisBethea

6/29/2011 1:27:07 PM
oooh! khorvat!!!
thank you SOOO much!!!
That was ever so perfect information!!

You RAWK!! :)
Happy Hump Day!
Kris

This content has not been rated yet. 
37 Reputation 4 Total posts
KrisBethea

KrisBethea

6/29/2011 1:27:34 PM

Denis,
You as well have been extremely helpful! As typical of a project, we are in the beginning stages and the specific details often don't show up until you're knee deep in the coding!!

Thanks for your information and your insights!
*hugs*
Kris
This content has not been rated yet. 
37 Reputation 4 Total posts