jon * wrote:
>
>
> No, it would be bad because it would do two things:
>
> #1. designers would not be able to link to other WM pages directly.
> #2. for *every* wm page, there would *have* to be a .java file to match it.
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.
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?
--
Dave
[EMAIL PROTECTED]
your flame > /dev/null
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
