One quick-and-dirty way to add "simple" (I guess you mean non-dynamic?) screens
to the system is by provide a special directory into which users place HTML
files. The way I have it set up, the base navigation module notices files in
these directories and adds them to the navbar. The filenames are passed to a
GenericScreen module that then displays them.
For example, given the file <template_home>/screens/generic/TuesdayMeeting.html:
- The navigation shaves off the ".html" and inserts spaces before non-initial
capital letters, yielding the text "Tuesday Meeting".
- The navigation generates the URL
"http://foo.com/servlet/Turbine/screen/GenericScreen/name/TuesdayMeeting".
- The GenericScreen appends the ".html" extension and looks for the template
<template_home>/screens/generic/TuesdayMeeting.html.
Probably not the best way, but I got it working quickly and I haven't had any
problems with it yet. The only restriction I gave the client is that these
files must contain only a single HTML table, i.e. no <html>, <head>, or <body>
tags.
-- Travis
Frank Conradie wrote:
>
> BRILLIANT! Leon and I have been discussing Python scripting in much the same
> way - our clients often require a way to add "simple" screens to their
> system - without recompiling Java etc. We will probably explore this a bit
> later - after the Torque stuff is where we want it.
>
> Frank
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
