on 4/10/00 8:11 PM, Dave Bryson <[EMAIL PROTECTED]> wrote:
> But if the links you mention above are dynamic, won't their values most
> likely be driven by some kinda logic that should be handled in a screen.
> For example:
> if ( something )
> {
> //use these URIs and this information
> }
> else
> {
> //use these URIs
> }
>
> But, I do kinda see what your saying. So I think the decision boils down to
> whether
> we add more complexity to the page author or leave it to the programmer who
> is probably already smart on DynamicURIs.
No. I'm not talking about show/hiding URL's I'm just talking about
maintaining state between pages that may not have anything in them that is
really dynamic. For example, your Scheduler Help page. What if there was a
few help pages that all needed to link to each other? Would you want to
create a .java file to match each of those pages or would you just want to
type them out, link to them and forget about it?
> I'm just trying to keep the WM script a no-brainer for page authors. I'm sure
> we could customize (add tags) to WebMacro to do the things you are talking
> about.
>
> If we do decide to add tags to handle such things as :
> $dynamic.setScreen("edit.wm").addPathInfo("jobid", $job.getId() )
> Then I think WebMacro becomes more then just a Service in Turbine (it becomes
> bound to Turbine) and we should look at how to make a customized
> version of it that's optimized for use in Turbine (that may not be such a bad
> thing).
Actually, lets be careful of that. I can't speak more about *why* quite yet
but will be able to in a couple of days hopefully.
-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]
