Basics uses this phrase to define/describe Shapes:
…object that contains all the information…
Implies the ability to filter according to user type / role.
Exactly where can i see this magic in action / which learning curve twist do i bark up?
thx
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Check this article: Accesing and rendering shapes
It introduces the basic concepts behind shape rendering. You should also read about dynamic objects (appropriate MSDN links are inside this article)
I wrote an article about using shapes as helpers, which gives some insight on how does it all work: Using shapes as HTML helpers in Orchard.
[EDIT]: I also wrote an article today about shape customization. Hope that’ll give you more insight.