Marco van de Voort wrote:
On Wed, Aug 22, 2007 at 10:18:07PM +1000, David Lyon wrote:
Interpreted what exactly? Template system which has a limited
interpretation, the program itself, javascript, what?
I'm just speaking from my experience with delphi-webscript2.
It appeared very effective at calling functions embedded in function
snippets.
Practically this might involve small .pas file for every page object
that could form the section with parameters and return a result.
This would imply having say a header.pas, footer.pas, side-bar.pas,
body.pas. For whatever templates are needed. Obviously the names would
be flexible.
Then you need a object list (stringlist) containing all the names of the
templates that are used to build the page. This is quite a dynamic list,
and would need to change with navigation through the application logic.
When the the form processor runs through the object list (stringlist)
runs the functions, appends the results of the functions into the web
page and possibly sends as it goes.
But delete a (string) item, and it dissapears from the web page on the
browser on next page send.
That's the basic mechanism for controlling what objects get published.
Combined with a session object, which you can easily add member
variables to, that will give you a sense of navigation. The session
object has a timer, and will eventually time out like sessions we see on
sites.
Not forgetting, the target for all of this is to be able to build a web app
in a way that is reasonably familiar to old timers (attempting to preserve
legacy code) and have it run on modern platforms. Be that in a web browser
or whatever.
What is "it" ? If it is existing pascal code, most likely it won't run in
an interpreter in the first place without changing.
Yes it might need slight changing. But that is going to be easier than a
complete rewrite to python or a redesign to some other language like php.
David
