On Mar 21, 2011, at 12:29 PM, Mike Orr wrote: > I like the word blueprint better than skeleton, actually. I would have > suggested it but you had already taken the name. I don't think we can > use your implementation classes directly, because they make a several > fundamental changes compared to PasteDeploy/PasteScript that I don't > think Pyramid is ready to commit to at this point. Such as using > alacarte, being another namespaced package, adding several > dependencies, etc. I've heard your packages are also Python 3-only? I > think what we'll probably do is make a new implementation of Paste* > but keep the features and API mostly the same, at least that's what a > few developers are working on. Would you mind if we use the term > "blueprint" in this "paster create" replacement?
flask is introducing "blueprints" for yet another meaning: http://lucumr.pocoo.org/2011/3/18/flask-at-pycon/ "So with the next Flask release we will ship a new concept for modules called “Blueprints”. Essentially what these blueprints will do is capturing construction information. You can then attach these blueprints to applications (even multiple times if you like). They can either extend the application itself or are registered with their own name." So using the term blueprint means we'll have our 'blueprint', flask's 'blueprint', and the css framework 'blueprint'. Let me rephrase, is there any real reason not to use an already widely acknowledged term in the web world that is *known* to mean exactly what we're already referring to? Anyways, a better question is, are people really baffled by the concept of paster templates for template languages? Is that a real problem? I'm just not sure.... I've been doing Pylons for a long time, and we generally do say 'paster templates' and no one thus far has ever gotten confused afaik. But hey, its a fun bike-shed, eh? :) Cheers, Ben -- 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.
