Sorry for a bad explanation!
That I am trying to say is that i would be great with a way to do different
things with calls for different files.
In an another way:
With Turbine today you can call the Turbine servlet with parameters for screen
and other things like f.ex a file. This as a base is enough to do ...whatever.
But what I would like is to call the Turbine servlet with a parameter for a
file (docname=) and
that Turbine then is calling the handler (page) for this files filetype. The
handler on its side
can look for a parameter like f.ex fileaction= or docaction= and do something
that
match or the default if there is no parameter.
If no file is specified in the call for Turbine then the default screen (or
its layout)
is executed.
If a screen parameter is defined then that screen (or its layout) is executed
without regard to possible file parameters.
Now, you may see some possibilities.
Here is one:
If I ask Turbine for a xml file ( .../servlet/Turbine/docname/somefile.xml)
then i want Turbine to fire up XMLPage and let XMLPage to fire up
XMLScreenLoader and return a XMLScreen. The XMLScreen has
a getDocument method that returns a XMLScreenDocument.
The XMLScreenDocument is the actual xmldocument and has a
getLayout and/or a getLayoutDoc.
In this way you can build up a webpage like Turbine builds up a
webpage. Transformation with xsl is possible for the hole webpage
or for each module (screens and navigations). There is lots of
ways!!! F.ex Navigations can be xsp files.
Here is hints for an another possibillity (?):
.sh file and jni
regards
Killi
Jon Stevens wrote:
> on 7/26/2000 5:11 AM, "Roall Lein-Killi" <[EMAIL PROTECTED]> wrote:
>
> > Here is the case:
> >
> > - I wanna use several template systems:
> > (My own and WebMacro)
> > - As with WebMacro I need my own Page
> >
> > The solution (that I see):
> >
> > - Define a way to request a template
> > This may have been done with ...Turbine/template/index.wm...
> > But I would suggest docName= for the file and docClass= for the
> > location
> > because we then open up for future possibillities as
> > documenthandlers etc.. *
> > - Extend Turbine.java with the abillity to load a page dependent on
> > the
> > file extension.
> >
> > What do you guys think about this ?
> >
> > * especially if docAction also get defined. Then there is a cleen way
> > for the "extension page"
> > to load different screens dependent on the docAction (eks Edit, View,
> > Delete, Rename or default),
> > but then we also need a virtual filesystem with user permission.
>
> You are not making a huge amount of sense, but everything that you want to
> do can be done by simply building your own WebMacroSite* modules and using
> those. You don't even need to "extend Turbine.java".
>
> -jon
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
