From d109f8356d1dd2c66f66d316ee46a51043731206 Mon Sep 17 00:00:00 2001 From: xue <> Date: Wed, 28 Dec 2005 14:05:40 +0000 Subject: --- demos/quickstart/protected/pages/Configurations/Templates1.page | 2 +- demos/quickstart/protected/pages/Fundamentals/Applications.page | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/demos/quickstart/protected/pages/Configurations/Templates1.page b/demos/quickstart/protected/pages/Configurations/Templates1.page index 5d387e14..d9b71d35 100644 --- a/demos/quickstart/protected/pages/Configurations/Templates1.page +++ b/demos/quickstart/protected/pages/Configurations/Templates1.page @@ -1,7 +1,7 @@

Templates: Part I

-Templates are used to specify the presentational layout of controls. A template can contain static text, components, or controls that contribute to the ultimate presentation of the associated control. By default, an instance of TTemplateControl or its subclass may automatically load a template from a file whose name is the same as the control class name. For page templates, the file name suffix must be .page; for other regular template controls, the suffix is .tpl. +Templates are used to specify the presentational layout of controls. A template can contain static text, components, or controls that contribute to the ultimate presentation of the associated control. By default, an instance of TTemplateControl or its subclass may automatically load and instantiate a template from a file whose name is the same as the control class name. For page templates, the file name suffix must be .page; for other regular template controls, the suffix is .tpl.

The template format is like HTML, with a few PRADO-specifc tags, including component tags, template control tags, comment tags, dynamic content tags, and dynamic property tags. .

diff --git a/demos/quickstart/protected/pages/Fundamentals/Applications.page b/demos/quickstart/protected/pages/Fundamentals/Applications.page index 8ea9a1f7..df1418fb 100644 --- a/demos/quickstart/protected/pages/Fundamentals/Applications.page +++ b/demos/quickstart/protected/pages/Fundamentals/Applications.page @@ -5,7 +5,7 @@ An application is an instance of TApplication or its derived class. It manages modules that provide different functionalities and are loaded when needed. It provides services to end-users. It is the central place to store various parameters used in an application. In a PRADO application, the application instance is the only object that is globally accessible via Prado::getApplication() function call.

-Applications are configured via application configurations. They are usually created entry scripts like the following, +Applications are configured via application configurations. They are usually created in entry scripts like the following, 

 require_once('/path/to/prado.php');
 $application = new TApplication;
-- 
cgit v1.2.3