Developer Guide
Introduction to Active Pages

    Active Pages are a cloud framework for rapid development that allows developers to build sophisticated custom user interfaces natively hosted within the Magentrix platform. Active Pages are extensions of ASP.NET framework, which allows developers to use their existing knowledge and utilize the advanced component library offered in a tag-based markup language.

    In Active Pages, each component corresponds to a fine-grained user interface element which is used consistently across the platform. This allows developers to build new applications that follow the same user-interface pattern as the rest of the platform and provide a higher adaptation rate for the end-users.


    Active Page and Development Framework

    The Active Pages markup consists of Active Page Components, HTML, Javascript, CSS and many other web-enabled code embedded inside the pages. New applications within the framework follow a MVC (Model - View - Controller) pattern, which allows developers to separate the logic from visual components and have full control over output in different devices.

    Active Pages can be associated with a Controller. Controllers are a special type of Active Class that can respond to HTTP requests and perform custom logic such as reading and writing records and working with files. If no Controller is specified for an Active Page, a default Controller called "AspxController" is used, which supports an "Index" action used to load the page. You can extend the AspxController's functionality by writing your own custom Controllers. In order to learn more about writting Custom Controllers, click here.

    Active Pages and Device Support

    Each Active Page can have up to three variations:
    1. Main
    2. Tablet
    3. Mobile
    The "Main" version is used for all devices by default and works in an adaptive/responsive fashion. Mobile and Tablet versions of the same page can alternatively be specified. All Magentrix Active Page components are designed in an adaptive fashion, meaning that, based on what device is accessing the system, the output is adapted to render the version of HTML most suitable for that device. However, in some cases you may prefer to create separate user-interface for each devices group such as mobile phones or tablets. Below follows the process of how a request is handled in your Active Page:
    1. Request is received by Magentrix Route Handler.
    2. Request is translated to the proper action on your Controller and your Controller's action is executed.
    3. Depending on your Controller's Action Response, the most suitable view is selected and passed to the Magentrix engine to be rendered into HTML.
      1. If the target device is a classical device (desktop, laptop, etc), the main view is used.
      2. If the target device is a tablet, and the tablet view exists, the tablet view is used.
      3. If the target device is a tablet and the tablet view does not exist, but the mobile view exists, the mobile view is used.
      4. If the target device is a tablet, but only the main view exists, then the main view is used.
      5. If the target device is mobile, and the mobile view exists, then the mobile view is used.
      6. If the target device is mobile, and the mobile view does not exist, then the main view used.
    This section consists of: