[Dev] Re: Initial Mail Settings

[Donn Denman]

John,

On Aug 29, 2004, at 12:18 PM, John Anderson wrote:

> Personally I don't like adding lots of crufty environment variable 
> code that is hard to remove from the final product and make the code 
> ugly.
>
> I had done this in the past by just editing the default item in the 
> XML and remembering not to check it in -- In 
> parcels/osaf/mail/parcel.xml.
>
> This issue keeps coming up in other situations, however, and another 
> approach would be to add debugging code that looks for a prebuild 
> repository, named say __repositoryTemplate__ which is copied to 
> __repository__ when __repository__ doesn't exist. That way you could 
> make all your settings, copy the repository to the template and each 
> time you run you'd get a copy of the template when you blew away your 
> repository. Obviously, when the schema changes, you have to redo your 
> settings.
I think this is a great idea.  Humm.... I wonder if it generalizes into 
repository layers that you can rebuild separately...

- Donn

>
> John
>
> Donn Denman wrote:
>
>> Now that I'm doing a lot of mail testing, I really want a new feature 
>> - one that sets up my default IMAP and SMTP settings even though I'm 
>> running with a fresh repository.  Is there some way we can get and 
>> use default data, like getenv()?  Then we could just set up our 
>> accounts with environment variables, and we'd be ready to test mail.  
>> Or we could each check in a bunch of prebuilt account settings and a 
>> test menu to activate one.
>>
>> - Donn
>>