On Jun 6, 1:01 am, "Mike Orr" <[EMAIL PROTECTED]> wrote:
> I thought a bit about this, but it really is a framework.  A
> toolkit/library is something you call.  A framework is something that
> calls you.  Given that it's the outer part of web applications that is

Yeah I thought the same after posting that. I think the issue that's
causing my ambiguity is there is so much discussion of customizability
and flexibility that it's almost easy to miss the fact that there is
(sort of) a default set of packages.

Probably cause I'm thinking in comparison to others like django and
rails which are complete kits out of the box (core/tmpl/db).  I
suppose Pylons is maybe more like Struts in being a central codebase
and general approach (framework?) but not being tied or shipped with
any db lib (though it does come with a template kit... I guess it's
halfway between the two camps?)

I'm certainly not saying this should change in any way, but I suspect
others may be a bit confused about this issue... or not?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to