Hello from Visual FoxPro 09.00.0000.5815 EXE Support Library for Windows.
The Time is: May 18, 2025 09:32pm.
Time | Request | Verb | IP Address |
---|---|---|---|
May 18, 2025 09:24pm | /testpage.pb | GET | 3.143.7.75 |
May 17, 2025 10:31pm | /testpage.pb | GET | 147.135.212.202 |
May 17, 2025 10:31pm | /HelloScript.pb | GET | 147.135.212.202 |
May 17, 2025 02:05pm | /testpage.pb | GET | 51.222.253.16 |
May 17, 2025 08:43am | /HelloScript.pb | GET | 51.222.253.16 |
May 17, 2025 07:03am | /testpage.pb | GET | 216.244.66.231 |
May 16, 2025 11:19am | /testpage.pb | GET | 24.109.180.10 |
May 16, 2025 12:22am | /testpage.pb | GET | 85.208.96.206 |
May 15, 2025 08:55pm | /HelloScript.pb | GET | 185.191.171.2 |
May 15, 2025 10:44am | /HelloScript.pb | GET | 185.246.188.74 |
This page is rendered using a Script page - HelloScript.pb - from disk that contains
FoxPro code embedded inside of < %= expression %>
expression tags. There's also
a HelloScript()
method inside of your process class that is fired to set up a
model of data that can be rendered. In this page a Message object for the info
box above, and the cursor for the request list are both created in the 'code behind'
controller method.
Using scripts you can:
< %= expression % >
< % code % >
< markdown></ markdown>
< %= RenderPartial() %>
You can write code inside of these scripts, and the scripts are automatically recompiled when you make changes.
This page is rendered using a script that references a _Layout page which provides most of the page chrome - the HTML header the toolbar and footer. This Content Page which references this Layout page is then rendered into the Layout producing the complete HTML output.
This MVC style mechanism allows you to create a master layout for your site, and render content pages into it. Content pages then only need to provide the page specific content without having to duplicate the page chrome. You can also create multiple _Layout pages to provide different layouts for different pages.
Note that you can also create completely self contained pages that include all HTML but generally using a Layout page is more productive as you don't have to duplicate the same common HTML into each page.
For more info see Mvc for Web Connection and Layout Pages, Content Pages, Partials and Sections in the Web Connection Documentation.
For building applications we highly recommend using the MVC based approach of using controller methods for setting up models that are then passed to a view for rendering. In Web Connection this translates to a process method that calls
Response.ExpandScript()
to render a view.
This block of text is rendered using Markdown that is embedded as a Markdown
Island into the script page using a < markdown></ markdown>
block. Markdown
embedded in this way is turned into HTML and embedded into the page.