[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Perlappinst-devel] Re: App::Info
From: |
David Wheeler |
Subject: |
Re: [Perlappinst-devel] Re: App::Info |
Date: |
Tue, 04 Jun 2002 14:29:35 -0700 |
User-agent: |
Microsoft-Entourage/10.0.0.1331 |
On 6/4/02 1:28 PM, "David Wheeler" <address@hidden> claimed:
> Well, it makes sense to me to specialize parts of the API -- to break it up
> into specialized objects. I was just focusing on one part of what an
> installer needs to do -- try to find some relevant defaults by hunting
> around the file system. Another piece of the API can handle prompts and that
> sort of thing, but I hadn't got that far yet.
>
> A thin shell is okay -- I think that smaller, specialized parts that work
> well together (in a fully OO fashion) is a desirable design goal.
Actually on reflection, I think what makes sense is to have a number of
flags on an object to determine its behavior. Right now, I'm issuing
warnings when data can't be found or collected. I need to add a flag that
will turn those into exceptions, or silence them altogether. It's just one
more step to have the flag (or a related flag) have a setting of prompt.
Actually, there should be multiple levels of prompt -- sometimes just to
find the one important file (e.g., pg_config for PostgreSQL), and sometimes
to confirm *every* attribute.
I'll think about how to implement this.
David
--
David Wheeler AIM: dwTheory
address@hidden ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: address@hidden