From: <os...@us...> - 2013-11-16 16:18:16
|
Revision: 9511 http://sourceforge.net/p/oorexx/code-0/9511 Author: osims Date: 2013-11-16 16:18:13 +0000 (Sat, 16 Nov 2013) Log Message: ----------- Minor typo fixed. Modified Paths: -------------- docs/trunk/oodguide/en-US/Chapter07.xml Modified: docs/trunk/oodguide/en-US/Chapter07.xml =================================================================== --- docs/trunk/oodguide/en-US/Chapter07.xml 2013-11-15 13:59:15 UTC (rev 9510) +++ docs/trunk/oodguide/en-US/Chapter07.xml 2013-11-16 16:18:13 UTC (rev 9511) @@ -185,7 +185,7 @@ <computeroutput>ViewMgr</computeroutput>.</para> <para>When a user double-clicks on an item in say the Customer List dialog, the confident expectation is that a Customer dialog that shows the data associated with the list item will - be displayed. Now consider what has to happen to make that product dialog appear:</para> + be displayed. Now consider what has to happen to make that Customer dialog appear:</para> <orderedlist> <listitem> <para>Create the appropriate data component, which...</para> @@ -783,11 +783,11 @@ statements added for MVF use are commented with <computeroutput>MVF</computeroutput>; modified statements are commented <computeroutput>v01-00-->MVF</computeroutput>; and unchanged statements are commented <computeroutput>v01-00</computeroutput>. - <footnote><para>Actually, Wow is somewhat schizophrenic, in that it can be launched either as a + (Actually, Wow is somewhat schizophrenic, in that it can be launched either as a singleton or as anonymous - that is, with an instance name of "The" or "A". If "The", then only one instance is allowed. If "A", then multiple instances can be - created.</para></footnote> - As mentioned above, this whole approach of having component names define the type + created.)</para> + <para>As mentioned above, this whole approach of having component names define the type of component is not particularly scalable. A better approach - certainly for production-strength apps - is to provide a configuration file that names the classes and states what type they are. Such a file might look something like this, and would remove the |