On 2/13/02 6:12 AM, "Gabriel Sidler" <[EMAIL PROTECTED]> wrote:
> Ted, > Thanks, that's good input. If I understand you right you > are basically saying > > - Define your optimal view API, not worrying much about the > existing JSP view API How do you do this? We in Velocity can come up with a view API that is optimal for us. However, other systems may need a different API? I saw ted's post about the 'raw' API, but I am not convinced that wouldn't be tailored to a specific approach. For example, can you make it not require it having to be passed in a page request scope? With a clean low-level API, each view system can roll their own. Maybe the ContextHelper is your low-level API (but I suspect it will be passed around in a scope...) > - From the view API we'll derive a controller API. Ideally, this > controller API should be able to satify the needs of all view API. I have the same questions as above for this point... I guess we see what Gabriel proposes today, and what Nathan's response is as a familiar-with-Velocity new struts user. Geir -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting The question is : What is a Mahnamahna? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
