Hi, I've been using intake for the last 6 months or so and well I'm not a great fan of it. For me in theory its a good idea but in practice its overly complex for what should be a relatively simple problem. Within the app I work on it has become quite diffcult. When the pages become complex and more pages are needed, and there happens to be an error, debugging and finding that error I find is more difficult than it need necessarily be.
Personally I prefer RegExp handlers to parse form information and return error messages or not as the case maybe. I think it avoids the forms themselves becoming unecessarily cluttered and of of course to avoid the action classes themselves becoming unmanageable monoliths, extract code to do the parsing into another class. My chosen RegExp handler is Oro, Regards James -----Original Message----- From: Jeff Barrett [mailto:[EMAIL PROTECTED]] Sent: 22 May 2002 03:04 To: Turbine Users List Subject: are there alternatives to Intake? I'm building an application with turbine that doesn't use Torque. I'm gathering from traffic on this list that if I'm not using Torque, I can't use Intake. So are there alternatives? +jeff -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
