TECH NOTES

Starting with Acropolis
Click title for source at CodeProject.com…

This article explores the benefits of Acropolis, focusing on its ability to switch between page design and code, allowing faster development

Introduction
In Acropolis, a development process (such as creating a window from and writing code against it’s buttons’ event) can be divided into two parts. With Acropolis, there are two important concepts: Part and View. View means only the design of the form, whereas Part means code against the view. So, your form design is totally separated from code and the two types of development can be continued simultaneously. That is, while a developer is writing code, a designer may design the form. Later, Part and View can be bound together. So, the development will be faster and the component will be loosely coupled and changes can be made easily.

To connect these two items (i.e. Part and View), connection points are used. For example, to execute a code in Part against a button click in View, you use connection points. To bind methods, you’ll use ComponentCommand and to bind properties, you’ll use ComponentProperty. The overview of the discussion can be found in Figure 1. However, as you explore through this example, you’ll know about this.
(more…)