image image Home   About   Downloads   Support   Links   Contact  
image

IntraWeb
» Blog & News
» General features
» Why IntraWeb?
» How does IW Work?
» Download a Trial Version
» Bugs List

Bundled Users
» Key Request
» Downloads
» Delphi 7 Users 
» Delphi 2005 Users
» BDS 2006 Users
» Delphi 2007 Users
» CDS 2009 Users

Technical info
» Why IntraWeb?
» Comparison with
   Other Web Tools

Resources
» Getting Started
» Documentation
» Articles
» Books
» Third Parties
» Tutorials
» Training

What others say
» Case Studies
» Companies using IW
» Demos
» Magazine Reviews
» User Quotes

Miscellaneous
» Just for Fun

Registered Users
» Bug System
» Login





Copyright
2002 - 2009
Atozed Computer
Software Ltd.

image
Buy Online   Download Support  FAQ Questions
Atozed Home  »  IntraWeb  »  Features

Model View Controller

IntraWeb uses the Model View Controller design paradigm. This design paradigm separates internal logic, user code, and presentation layer into separate pieces.

MVC Crash Course

If you are not familiar with MVC, here is a crash course:

  • Controller - Provides internal application direction and flow. Interprets external input and routes information to appropriate model code.
  • Model - User code. Normally this consists of many separate units that are connected to the controller.
  • View - Code or data that is used to provide the user interface.

Many detailed overviews of the MVC design paradigm can be found by searching for "MVC model view controller" in Google.

IntraWeb and MVC

IntraWeb provides all the functions of the controller layer transparently to the developer. The user code is written by the developer and resides in the model layer. The view layer is provided by a layout manager. In many cases no explicit layout manager is specified by the developer. In such cases it may appear that there is no separate view layer, however IntraWeb maintains the layer separately by creating an implicit default layout manager.




CodeGear - Where Developers Matter