Difference between revisions of "Talk:Workflow example"
From Organic Design wiki
(workflow images) |
|||
| Line 1: | Line 1: | ||
That old problem of not wanting the image to be clickable is showing up here - we need the image to just be in the background, but that's not easy to implement from a standard template, so it would have to be hard-wired. Rather than hard-wiring an image based on a parameter, I'll make part of the workflow frame have next/prev buttons so that it's obvious they can be changed and means the image can link like normal. | That old problem of not wanting the image to be clickable is showing up here - we need the image to just be in the background, but that's not easy to implement from a standard template, so it would have to be hard-wired. Rather than hard-wiring an image based on a parameter, I'll make part of the workflow frame have next/prev buttons so that it's obvious they can be changed and means the image can link like normal. | ||
| + | : This is looking real good already. The forward/Back buttons are a good idea, you definately want ot be able to step in either direction in the workflow, not just cycle forward throught the sequence. --[[User:Sven|Sven]] 23:59, 26 October 2007 (NZDT) | ||
Revision as of 10:59, 26 October 2007
That old problem of not wanting the image to be clickable is showing up here - we need the image to just be in the background, but that's not easy to implement from a standard template, so it would have to be hard-wired. Rather than hard-wiring an image based on a parameter, I'll make part of the workflow frame have next/prev buttons so that it's obvious they can be changed and means the image can link like normal.
- This is looking real good already. The forward/Back buttons are a good idea, you definately want ot be able to step in either direction in the workflow, not just cycle forward throught the sequence. --Sven 23:59, 26 October 2007 (NZDT)
