[Seaside-dev] WACurrentSession users

[Julian Fitzell]

On Tue, Jul 15, 2008 at 1:48 AM, Lukas Renggli <renggli at gmail.com> wrote:
>> Hm... only the one sender. WAHtmlStreamDocument is referenced directly
>>  in a few places. It looks like they could pretty much all use a
>>  preference if there was a use case for users changing it. Can anyone
>>  think of a good reason someone would want configurable document
>>  classes per-application or per-something-else?
>
> Maybe some document that does an on-the-fly validation according to a DTD?
>
>>  Other than SUDocument, the only other subclass currently is the
>>  often-asked-for-but-problematic-and-not-overly-useful
>>  WAPrettyPrintedDocument which there seems to be no way of using in
>>  2.9.
>
> WAPrettyPrintedDocument is used in the source-code rendering of the
> halos. It uses an instance of WAHtmlStreamDocument as delegate, but
> pretty-prints and syntax-highlights the generated XHTML to XHTML.
>
> Pretty-printing the XHTML itself is problematic indeed. This is not
> really possible without changing the visual appearance.
>
> Lukas

Ah ok, good to know it's being used. And yes, when I wrote the
original pretty printer I has to quickly unlearn the credo that
whitespace isn't relevant in XML. :)

So I can see a desire to have other subclasses of Document, but it
still doesn't answer my question which is: If you do have subclasses,
is it useful to be able to select the one you want in the
configuration or would you want it hard coded to a particular
component or handler or what-not? Is it beneficial to have a config
option for this or should everywhere in the code just use the
hardcoded document class they want?