on 4/10/00 6:28 PM, Dave Bryson <[EMAIL PROTECTED]> wrote:
> Not every. For example, I can pull two (and more) WM pages together in one
> Screen. I do this now to add JavaScript to the head of the document.
Right, but that isn't what I'm talking about...
> I'm totally confused then about the role we want WM to play in Turbine. I
> thought
> the idea was to ALWAYS call WM pages from an associated Turbine Screen (MVC).
> The motivation
> for using WM comes from having some dynamic content you want to put in the
> page.
> In
> our case I thought the dynamic content would be generated/pulled together in
> the
> Screen and pushed to the WM page. If you start jumping around between WM pages
> outside
> of Turbine isn't this going to make access control and session stuff a real
> pain
> in the ass?
I can imagine a case where some WM screens don't have any dynamic content on
them except for the links. So, having a .java file for each of the WM
screens would be a real pain in the rear. I would like to case for that.
When I think about MVC, I think about building the logic for the page
outside of the page (ie: in Java). I don't think about also having to build
all the links in the java code!
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
