On Mon, Mar 21, 2011 at 2:05 PM, Ben Bangert <b...@groovie.org> wrote: > On Mar 21, 2011, at 1:48 PM, Mike Orr wrote: > >> "Template" has been a problem for years. Even if people can figure it >> out, it's cumbersome to write in documentation and tutorials where you >> have to explain that a template (skeleton) is not a template (file) >> although some of its files are templates. And the phrase "application >> template" is long and cumbersome when you have to repeat it many >> times. > > Ah, good point. I guess I'm too used to explaining things in person. ;) > > So any reason it *shouldnt* be called 'scaffolding' given its already a well > known name that people already associate with this exact thing? I mean, I can > see how 'blueprint' can technically be a more accurate term, but existing > re-use of the name and lack of anyone already associating it with this seems > like a point against it.
'Skeleton' is a long-established term in Unix where it refers to the files initially copied to a newly-created home directory. That's an exact analogue of what we're doing. "Scaffold" or "Scaffolding" would be OK too, although I'd prefer the shorter "Scaffold". "Scaffolding" connotes the ad-hoc process of constructing it individually for each building, while "Scaffold" sounds like a product that remains the same over many uses, which is how an app template works. There's also that word "Fixture" that some people call a class that acts as a framework for unittests. -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
