From: Eric C. <ecr...@us...> - 2006-09-25 19:16:55
|
User: ecrutchfield Date: 06/09/25 12:16:52 Modified: andromda-aspdotnet/src/site/axdoc index.xml Log: minor wording changes Revision Changes Path 1.2 +5 -5 cartridges/andromda-aspdotnet/src/site/axdoc/index.xml Index: index.xml =================================================================== RCS file: /cvsroot/andromdaplugins/cartridges/andromda-aspdotnet/src/site/axdoc/index.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -w -r1.1 -r1.2 --- index.xml 17 Sep 2006 17:31:53 -0000 1.1 +++ index.xml 25 Sep 2006 19:16:52 -0000 1.2 @@ -27,13 +27,13 @@ </p> <p> The generated code should be consistent and in-line with the most common best-practices in web development. - It must also help the user adding the final pieces of code in order to finish the implementation. Except - for the business logic that will need to be implemented manually, the user should not need to have knowledge + The cartridge must make it easy for the user to add the final pieces of code in order to finish the implementation. + Except for the business logic that will need to be implemented manually, the user should not need to have knowledge of the rest of the generated application, although it can never hurt. </p> <p> Regeneration of code from UML should not overwrite manually written code. Classes can attain this - goal by using a construction such as inheritance. We use MasterPages and WebControls to isolage + goal by using a construction such as inheritance. We use Code-Behind classes, MasterPages, and WebControls to isolate those pieces of the ASPX page that need regeneration. </p> <p> @@ -183,7 +183,7 @@ </p> <h3>View</h3> <p> - In an ASP.NET application you will use ASPX pages to represent the view components. In the + In the ASP.NET application ASPX pages will be used to represent the view components. In the application's activity graphs views are tagged with the <![CDATA[<<FrontEndView>>]]> stereotype. </p> <h3>Controller</h3> @@ -193,7 +193,7 @@ by an action that will defer any business operation to the controller. Typically in an ASP.NET application this is handled by the code-behind class for a given page. To better support the regeneration capabilities that are a key component of AndroMDA, we create a seperate controller class for each use case. The code-behind - class still exists, though, as is used to insert manual implementations as required (more about this later). + class still exists, though, and is used to insert manual implementations as required (more about this later). </p> </section> |