One of the areas that I forgot to cover was the access levels. The basics of access levels are so that each user is given an access level, which is a number like 1, 3, 5, etc. Then content can be given access levels also. If the user’s access level is greater or equal to the number assigned to the content, they are able to view it. Otherwise, access denied.

The tutorial yesterday was utilizing both the access levels and user roles. ProdigyView is made to support dual privilege system because I did not want to tie a developer to using one. For a simple projects, access levels easily get the job done. For a more complex access control, user roles would be the answer. Again these tools and the CMS should be used for quickly building proofs of concepts before designing an actual product.

Access Levels and User Roles: http://www.prodigyview.com/tutorials/slideshare/390/105

The posted today was on user’s relationships <3.

I mean a relationship as a way of relating two user together based on a common entity. As you read through the tutorial think of relationships not only as friends but users being able to have multiple kinds of relationships. For example, users can be friends, co-workers and also school mates.

When building a social site, those connections also be to distinguish was type of relationships are able to view certain content. Only share this picture with users who are family. In other words, you basically have a way of setting up a social setting similar to Google’s circle. Always remember to think outside the box when programming and the possibilities will be endless.

User Relationships: http://www.prodigyview.com/tutorials/slideshare/389/111

Version 1.5.3 is on its way. Changes and updates to this version will include:

• Mongo updates
  • GridFS implement
  • Sorting, Limits and offsets
  • Pagination
  • Integration into Helium
• Improved Image Rendering
  • Drop Shadows on images
  • Scaling Image
  • Text To Images
  • Watermarks
• Authorization
  • Hashing Password with Salt
  • Multiple field authorization

A lot of it has be completed but needs testing. So I am currently running it through various test, if anyone else up to test, shoot me an email.

The tutorial released today was on management of user roles. In short, create, update, delete and search for user roles. Also it goes over to assigning a user to a role.

User Roles - http://www.prodigyview.com/tutorials/slideshare/388/111

Finally, we are getting to some of the database tied parts of ProdigyView. I think enough of the other features have been talked about to make the upcoming parts of the framework more usable.

One of the ProdigyView coolest features is the built in cms(content management system). The purpose of the cms is to quicky build a prototype of the of a concept to show to decision makers and stakeholders. This could mean your boss, investors, etc. After a prototype has been approved, then you can go back and build the product in a way that is more fitting towards the environment.

The reason why I say use the CMS and its features as a prototype is because it has many features and fields that you do not need. An axample is the video content of the content management system. The video content has fields for ogv, wemb, mp4, ra, mov, avi, fla and others. You may not normally need all these fields and having all these fields can increase the size of your database. So quickly build a video site with the CMS to show as a prototype or proof of concept, then go back and do it the right way.

In some cases, you might want to build a site using the cms and all it’s features. If you choose to use the CMS as your system, remember to fine tune the database for scaling. An example could be indexing important fields that you use.

Today’s tutorial was on user management. This involves creating, updating, searching, and deleting users. It requires that you have installed ProdigyView with a database connection. 

User Management Basics: http://www.prodigyview.com/tutorials/slideshare/387/111

We will get into further tutorials about creating user relationships, user roles, and custom fields.