[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What about tommorrow?

From: DAve Goodrich
Subject: Re: What about tommorrow?
Date: Thu, 19 Jul 2001 11:00:28 -0700

on 7/19/01 9:08 AM, Helliwell, Matthew at address@hidden wrote:

> -----Original Message-----
> From: DAve Goodrich [mailto:address@hidden
> Sent: 19 July 2001 16:51
>> This means applications will be built from not just ASCII text, but also
>> *.swf, *.dcr, *.gif, *.jpg, *.png, *.xls, *.doc, *.pdf, *.mov, *.avi,
> *.cct,
>> *.dll files. A large, very large, portion of these applications are not
>> built on machines with access to sed, bash, make, (Mac and Windows).
> Not wishing to be too pedantic, but bash etc are available on Windows
But does your general web developer on Windows understand them? Will your
sysadmin install and maintain and train on them? My windows admin's (I only
admin the Unix servers) generally don't install anything that doesn't come
with a cellophane wrapper and a MS stock number.

>> Automated building of a product from separate storage/respositories is not
>> possible or even desirable.
> I don't understand this, what do you mean?

One solution that has been discussed is to keep all files not meeting
certain criteria, as yet to be fully defined on this list (what is a
'source' file?) in another storage space or binary compatible repository.
Upon checkout these non-source or "anti-source" files would be merged into
the target directory. See the "build system" portions of the past

I for one don't think you will get many people to subscribe to this
methodology. It may prove difficult to visualize and understand to Mac and
Windows "anti-source" developers, certainly few Flash and Photoshop
designers I have worked with would be willing to use such a system.
My 2 cents worth, I pass the potato now...


Dave Goodrich
Director of Interface Development
Reality Based Learning Company
9521 NE Willows Road, Suite 100
Redmond, WA 98052 
Toll Free 1-877-869-6603 ext. 237
Fax (425) 558-5655 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]