Creating the ProjectLast Updated: 10/18/2005 | |
| Sections above here: Home » Development » Page Mode » IntraWeb Pages | |
|
Sections below here: Topics in this section: |
IWP pages need either a WebBroker or WebSnap application as host. The first step is to create a new Web Server application (WebBroker or WebSnap). Once you have a WebModule, you need to drop 2 components from the IWControl palette onto the form. The first one, like all PageMode applications with IW is the IWModuleController. The second one is either a TIWPageController or a TIWPageController32 depending on whether you are creating a 4.0 or a 3.2 project. You can even combine both types of applications in one project by dropping one of each components onto the WebModule. The IWModule controler is just the "magic glue" between Borland's WebBroker/WebSnap architecture and IntraWeb, and has no properties or events at all. The TIWPageController has just one event and 2 important properties. This component maps the current request to the corresponding IWP page, parses the contents, generates the form and returns the result to the browser. TIWTemplateProcessor and TIWPageProducer components are not required for IWP applications. These are both inherent to the component and are transparently used. The TagType property indicates what type of tag you will be using in your IWP pages. By default this is the ttIntraWeb tag, which is expects control names in braces: . You can also set this to Borland style tags; <#ControlName>. The OnUnknownTag event gets fired when the .iwp file contains an unknown control . By default these unknown controls are ignored. The other relevant property is the ApplicationURL which specifies the virtual URL path to your application. So for example, if your script directory in your web server is /scripts and your project is called project1.dll, then ApplicationURL has to be set to /scripts/project1.dll/ (note the prefixing and suffixing of the / character). That is all you need to do with these properties. The next step is to save the project and optionally set the output path to that of your physical scripts directory location. Once this is done, we can move on to configuring the server to work with IWP and then continue with the design of our pages. |
(C) 2002-2009 - Atozed Software Ltd. | |