Andreas Hartmann wrote:
Jörn Nettingsmeier wrote:
Andreas Hartmann wrote:
At the moment, usecases are designed to occupy the whole page.
All elements outside the "main" usecase GUI (usually a form) are
included (like the site tree in the site area etc.). I don't think
that this will be easy to change, because usecases are invoked
by the core sitemaps before entering any publication-specific
sitemaps.

hmmm. that seems to be true for the "traditional" usecases. however, there is an alternate usage pattern as described on solprovider's page: http://solprovider.com/lenya/multiple i'm not sure if this sort of thing should be encouraged in 1.4, but it does work (i've been using it for a while), although it bypasses almost all of the usecase framework...

I took a quick look at it, but it really seems to be quite different
to the current usecase framework.

yeah, as i said, it is bypassing most of it, except for the usecase sitemap. no flowscript, and it's not registered in cocoon.xconf, since it does not involve java classes and jxtemplates.

<...>
I think so too, which would lead to option (c).

c) tie usecases to documents, i.e. a document calls a usecase
   and displays its output (that would be a kind of
   "usecase resource type")

would work for simple stuff, but where does the flow control go?

Everything would be like it is now. The flow control is still
handled by the usecase framework. The only difference is that
the usecase flow is not called before the publication is handled,
but when the document is accessed.

i see.

sure, but sounds like a can of worms, and definitely post 1.4 stuff.

Hmm, I don't think so - IMO it is quite straightforward.
Basically I wouldn't object to defer it, but if it solves
the search screen issue I'd be glad to introduce it asap.

well, i don't really understand how intrusive it will be. if you can do it and it does not break anything other than the already-broken search results, i'm all for it.



--
"Open source takes the bullshit out of software."
        - Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to