Michael Wechner wrote:
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
using a doctype doesn't mean one needs a workflow
how come?
for instance a search engine screen or a dynamic listing ....
they should rather use a wf schema that only has one transition.
why a transition at all?
otherwise, you end up with hacks all over the codebase to handle the
'no wf' case,
what hacks?
and that is just wrong.
i propose we require a wf schema for all doctypes
what if you don't use a doctype and want to apply the Lenya menu
transformer?
+1
-1 This requirement is just imposing something which is in many cases
not necessary at all, e.g.
Search Engine Screen
Dynamic Listing
Aggregation of various content
....
I am afraid that my knowledge of doctypes/publets in 1.4 is too limited
for me to vote, but wouldn't the above examples be considered usecases
and not doctypes? (possibly usecases of the doctype publet?). Sorry for
another stupid question :).
--Doug
Let's not put a requirement which makes development very rigid.
Michi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
