[binarycloud-dev] Awwww man, facility, not policy!!!

[Justin F. <je...@ey...>]

Alex:

Shucks.

Here I sit down tonight to revise my modules to make them
run in the latest r2 with ubiquitous Makefiles.

Shucks.

I don't get to first base.  Immediately, with the new gizmo
as used in import() in the prepend, but also (evidently)
in the parsing of th $bc_page hash, of substituting "/" for a dot
(I suppose this is going to allow you to use the MS "\"
path separator), kills me.  Why?  Because I, in my world,
use:

	*.layout	for layout template files
	*.master	for master templates files
	*.mod		for modules

I am not going to justify myself (very much anyway),
I just think that, BY INSPECTION, I know the "content"
and/or the purpose of the file.  This is my policy.
It avoids problems and confusion.  Now, you are
forcing policy on me, you make me have _all_ my files
end with ".php", WHEN THERE IS NO REASON TO.  These
modules/layouts/templates are not in the DOCUMENT_ROOT
where httpd _has_ to have known filename extensions.
These files are down in the boiler room, conceptually,
they have nothing, per se, to require a certain
naming convention to operate properly.

You have sinned, my son.

Just to rub in a bit more salt, here is the conceptual
"site", the "Hello World" site, and you have, in this
package of files TWO files named example.php.  One
is a master, the other is a layout.  You don't have
to use much imagination to see the problems that
could unnecessarily occur, a tarball, for example.
Phooey.  Fiddlesticks.  Lordy.  Pox on ya.

At first, I thought this "dot" thing was kind of
interesting when I started looking around.  I wondered
if there was a refugee from the Xanadu project now
working on BC...

OK, I'll conform to your policy, for now, so I can
keep going.  But I won't shut up on this one.  This
is a real bitch, not gentle observation.

_jef
 
-- 
Justin Farnsworth
Eye Integrated Communications
321 South Evans - Suite 203
Greenville, NC 27858 | Tel: (252) 353-0722