* Jon Stevens [[EMAIL PROTECTED]], August 09, 2001 11:54 AM
>
> on 8/9/01 6:50 AM, "Finn Smith" <[EMAIL PROTECTED]> wrote:
>
> > A question for those who have a good grasp of the current state of
> > Pull tools and Intake in the Turbinen project:
> >
> > I've taken a look at the Scarab code, the documentation for the Pull
> > tool service, and the Intake tool service. It seems the use of the
> > Intake tool with actions and a request scope Pull tool (a la Scarab)
> > is a clean way to implement the MVC model.
> > ...
> > If Intake in 2.1 has too many problems, does anyone know of a clean
> > way to implement the MVC model, using the Pull tool, *without* using
> > the Intake tool?
>
> Pull != Intake
>
> Intake is simply an implementation of a Pull Tool.
>
> The Pull Service itself should be pretty stable in 2.1. I don't know
> of any real issues with it. It is pretty simple.
I guess I should have been more clear in my original post. I was
specifically talking about the combination of a user defined Pull tool
and the Intake tool in Scarab. It has a nice process wherein if a template
tries to access a class made accessible via the tool, e.g.
#set ( $issue = $scarabR.Issue )
then the ScarabRequestTool uses the Intake tool to access the Issue.
This struck me as a clean way of doing things as it allows templates to
avoid being associated with specific Screen classes, but still lets
specific Issues, etc. to be requested via forms. Your advice leads me to
believe that I do not want to use the Intake tool. So I am wondering if
anyone has recommendations about how to use a request scoped Pull tool
to provide similar functionality e.g. (using Scarab terms) having a
RequestIssue.vm template where a user could select an Issue followed by
a ViewIssue.vm template to view the result.
That is: how, using request scope, would the Pull tool learn about what
was requested in the previous template such that it could provide the
correct Issue object to the current template?
Thanks,
-F
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
