 |
|||||||||
|
|||||||||
|
|
---------------
---------------
There is a new Acropolis sample available from the Acropolis team. It is definitely worth checking out. It includes a set of very thorough tutorial documents in the download.
Documents with Download:
You get a readme document an overview document and the following word documents:
Step 1a - Building the Expense Application Shell
Step 1b - Building the Line Item Part and View
Step 2a - Building the EditPart, ApprovalPart, and HomePagePart
Step 2b - Building the RootPart
Step 2c - Building the ExpenseExplorer Control
Step 2d - Adding State-Aware Navigation
Step 3a - Changing the View of an Acropolis Part
Step 3b - Adding Authentication
Below is an image of the layout of the application (taken from overview document).
Below are 2 screenshots of the application running logged in as manager.
Click here for larger picture.
Click here for larger picture.
Here is an overview description of the application (also taken form the overview document)
The Code Name "Acropolis" Expense sample represents a typical line-of-business requirement: providing a user interface to business data stored in a company database. This general requirement typically involves specific requirements that change over time. Potential changes include:
• Changes to user-interface requirements or technology.
• Changes to business-logic requirements such as validation or support for transactions.
• Changes to a database schema.
• The addition of features such as authentication, offline support, or theme support.
This tutorial focuses on common "Acropolis" tasks such as creating parts and their user interfaces, creating parts composed of other parts, and creating applications that combine new and existing parts and services. To demonstrate these tasks, this tutorial will guide you through the creation of various pieces of the "Acropolis" Expense sample. This tutorial will also demonstrate a few ways to improve an application: by replacing the user interface for a part and by adding an authentication service.
The Expense sample is complex enough to represent a real-world application for "Acropolis", but simple enough to demonstrate common "Acropolis" features and scenarios without too much distraction from the particulars of business logic. The complete Expense sample is too large to completely create within this tutorial, but typical "Acropolis" usage will more often involve the combination of new and existing functionality, making this tutorial more reflective of reality.
Get it here.
