> > The sample app doesn't use intake, which does server side
> > validation. This is a little tricky to use at the moment, but with a bit
> > of effort you can make it work. Check the mailing list, a number
> > of intake issues have been covered in the last couple of weeks.
> > Be careful with the docs - the intake ones contain a number of
> > inaccuracies, many of which can be worked out by looking at
> > the intake.dtd included with the tdk.
>
> Well, I was hoping Intake did do that, otherwise I will write my own
> probably similar to Scarab to allow me to easily pull objects.
>
> > In short, you don't need intake or OMTool to do what you are
> > after and the example application that is included with the tdk
> > clearly shows you how to do it.
>
> Again, hoping that Intake could do it for me =).
torque has done most of the work for you already. A screen class
is often just a thin veneer around one of the torque generated
methods that you use to put the data you are after into the context.
A pull tool is a more flexible way of achieving the same result.
Scarab is probably the best thing to copy so you are on the right
path.
As I said, intake is about validation, not data retrieval.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
