Andreas Hartmann wrote:
> In fact, all modules should be
orthogonal to publications, unless they are specifically designed
to extend a certain publication.
that sounds good.
I had already implemented a generic search page as a resource type
which could be used in arbitrary publications. It was located in the
search module. What do you think about this approach?
IMO we should change this. I don't see a way to implement the
search results page as a usecase without requiring special
configurations / conventions, and I don't see a problem with
implementing it as a resource type which actually worked very well.
to me, a resource type sounds ok. however, i don't really like to have
loads of those "singleton" resource types that you use on just one page...
out of curiosity, can you explain what problems you are anticipating
when doing it as a usecase, and what those special confs and conventions
are?
--
"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]
