[Seaside-dev] crazy thought

[Dale Henrichs]

Julian Fitzell wrote:
> On Wed, Jul 14, 2010 at 12:25 AM, Dale Henrichs <dhenrich at vmware.com> wrote:
>> Julian Fitzell wrote:
>>> I dunno... I'm reluctant to expose that information by default just to
>>> allow for a case of someone who (a) has a minimal install and (b)
>>> doesn't know what is in it.
>> That's one of the reasons that I figured it was a crazy thought.
>>
>> On the other hand, there's an awful lot of code that gets loaded and it is
>> asking a fair amount for folks to know everything that gets loaded
>> especially when things are still in flux.
>>
>> I ran into the issue and assumed that I might be pretty close to the first
>> person to run into that problem and assumed that I won't be the last...
> 
> Well, I do think Dispatchers should list their contents by default
> when no child is specified in the URL and no default has been
> provided. This guarantees you would see something when you go to / at
> least. It's only the 404 that I'm not so sure about.
> 
>>> The OB tools provide a way to browse the handlers as do the web tools.
>>> Maybe we just need a slightly better API on WAAdmin to expose that
>>> information. I think it's reasonable to expect you to have *some* set
>>> of tools installed if you want a convenient way to work with the
>>> install.
>> OB tools for production would fill the bill ... and they could be added to
>> the Base group (and even opened by default) ...
> 
> I think we load Tools in base so I don't have a problem with including
> OB-Tools in theory (on platforms that have OB obviously), but I'm not
> sure about pulling in OB if the image doesn't already have it?

That's the rub isn't it ... If the dispatcher listed their contents, 
then that would scratch my itch.

Then the decision about bringing in OB would be up to the developer (as 
it is now)...


Dale