Wiki source code of Features

Hide line numbers
  1: {{include document="Shept.Header"/}}
  2: 
  3: {{velocity }}
  4: (% id="content" class="home" %)(((
  5: 
  6: {{section}}
  7: {{column}}
  8: 
  9: Shept picks up the tradition of [[4GL frameworks>>http://en.wikipedia.org/wiki/4GL]] which were commonly used for building Client-Server applications.
 10: It offers decent capabilities for data-handling in tables (data-grids). Beeing a thin layer on top and a close integration into todays popular web application building tools **Spring** and **Hibernate** it is as well a concept as a toolset and a framework.
 11: Check [[the facts>>Demo1.FactCheck]] on the [[online demo>>http://demo.shept.org/SheptDemo]].
 12: 
 13: {{info}}
 14: Shept doesn't reinvent the wheel. It's just a tiny layer on top of spring-mvc and leverages springs infrastructure in a ready-to-go fashion for complex forms.
 15: {{/info}}
 16: 
 17: =Data Grids=
 18: 
 19: * Filterable
 20: * Sortable
 21: * Pageable
 22: * Expandible
 23: * {{html}}<span style="background-color:#CECECE">Full In Cell editing support</span>{{/html}}
 24: * {{html wiki="true"}}<span style="background-color:#CECECE">Full [[CRUD>>http://en.wikipedia.org/wiki/Create,_read,_update_and_delete]] feature set</span>{{/html }}
 25: 
 26: {{/column}}
 27: 
 28: {{column}}
 29: (% class="sheptBox" %)(((
 30: [[image:Table2.png|| height=300px]]
 31: )))
 32: {{/column}}
 33: {{/section}}
 34: 
 35: {{section}}
 36: {{column}}
 37: =Layout composition=
 38: * build dynamic pages by composing segments
 39: * build simple segments with default templates
 40: * build complex forms effortlessly through composition
 41: 
 42: (% class="sheptBox" %)(((
 43: [[image:Table3.png|| height=450px]]
 44: )))
 45: 
 46: {{/column}}
 47: 
 48: {{column}}
 49: =Segment chaining and reuse=
 50: * Bind your segments to datasources
 51: * Navigate from segment to segment
 52: * Reuse your forms in different contexts
 53: * Extend your forms infinitely to the bottom of the page
 54: 
 55: (% class="sheptBox" %)(((
 56: [[image:Table4.png|| height=450px]]
 57: )))
 58: 
 59: {{/column}}
 60: {{/section}}
 61: 
 62: {{section}}
 63: {{column}}
 64: 
 65: 
 66: 
 67: 
 68: =Business objects lifecycle support=
 69: * ModelCreation
 70: * NewModelValidation
 71: * ModelDeletion
 72: {{/column}}
 73: 
 74: {{column}}
 75: (% class="sheptBox" %)(((
 76: [[image:Table5.png|| width=300px]]
 77: )))
 78: {{/column}}
 79: {{/section}}
 80: 
 81: {{section}}
 82: {{column}}
 83: (% class="sheptBox" %)(((
 84: [[image:Table6.png|| width=300px]]
 85: )))
 86: {{/column}}
 87: 
 88: {{column}}
 89: 
 90: 
 91: =Validation and Error Handling=
 92: * Validating data entries
 93: * Dealing with Concurrency
 94: {{/column}}
 95: 
 96: {{/section}}
 97: 
 98: {{section}}
 99: {{column}}
100: =Comprehensive DataSource Coverage=
101: * Example entity objects
102: * {{html}}<span style="background-color:#CECECE">Build-in support of your models generated relationships</span>{{/html}}
103: * Hibernate Criteria API
104: * Hibernate Query Language HQL
105: {{/column}}
106: 
107: {{column}}
108: =Efficient server resource usage=
109: In contrast to the many existing [[RIA frameworks>>http://en.wikipedia.org/wiki/Rich_Internet_application]] building a composite shept page requires just one request by default thus saving resources on your backbone infrastructure. Alongside todays modern browsers and their fast rendering engines users can't tell the difference anymore to RIA based apps.
110: {{/column}}
111: {{/section}}
112: 
113: )))
114: 
115: {{/velocity}}