where to put CSS and JS files

David Miller justdave at syndicomm.com
Wed Oct 30 20:20:19 UTC 2002

On 10/30/02 10:42 AM -0800, Myk Melez wrote:

> Dave, here are the three extant alternatives.  All of them are good
> enough (TM).  Pick one and let's move on

> css/ and js/ - short, obvious, and css/ already exists; less flexible
> than the other alternatives because it specifies the type of files it
> will contain (although all examples of the problem this causes are
> hypothetical).

And we can always add more directories later for other types if we want to
stay consistent.  I'm pretty sure when the "Makefile" thing lands (if it
ever does) our entire directory structure is going to get changed around

> style/ and logic/ - logically consistent, but leaves css/ empty, and
> people think "logic" is bad because marketingesque.
> style/ and scripts/ - the popular choice, but leaves css/ empty and
> logically inconsistent.

I don't like scripts, because guess what a CGI is? :-)  I'm not sure logic
works for me either.  Personally I'd just go with css/ and js/ since
they're specific to what we're using.  If someone adds VBScript files
later, they can always add a vbs/ directory or something.

>> It's a hassle yes.  But it's not impossible.  It will not only be
>> confusing to users but show poor judgement on the developer who leaves
>> a needless empty directory without removing it.  It's not like we cvs
>> remove directories every day....  surely we can do it just once...
> Technical note: not really.  There's no such thing as "cvs remove
> directory", there's only "manually delete directory from CVS repository,
> causing chaos in local working copies".  We don't want to go there.

We've done this exactly once that I know of in the past, to remove some
directories that were created on accident.  Anyone who had a cvs checkout
updated within the three weeks those directories existed had to manually
remove them from their CVS/Entries files in order to get cvs update to not
error out.
Dave Miller      Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/             http://www.bugzilla.org/

More information about the developers mailing list