On Feb 6, 2006, at 9:16 PM, Ian Bicking wrote:
>
> The inversion of control is the tricky part. In something like
> Cheetah, Kid, or ZPT the template (as represented solely by the
> file contents) gets control first, and then explicitly hands it off
> to whatever it is "inheriting" from (t
Ian Bicking wrote:
>> I would say that
>> the argument or arguments passed to find_template() need to be pretty
>> open ended, since you cant predict what kinds of things might be
>> meaningful to a template finder, such as in myghty's case, the resolver
>> wants to know if you are asking for t
On Feb 5, 2006, at 5:33 PM, Phillip J. Eby wrote:
> As Ben has previously pointed out, systems like Myghty are going to
> ignore
> your 'find_template()' because they do their own finding. So the
> spec will
> leak no matter what, until we get to the level of specification
> called for
> b
is a core functionality of myghty...very nested and recursive,
also keeps an internal stack frame going to track the whole thing.
Michael Bayer wrote:
> Phillip J. Eby wrote:
>> What I'd suggest is that this is actually an opportunity for Myghty to
>> put
>> its lookup
Phillip J. Eby wrote:
> What I'd suggest is that this is actually an opportunity for Myghty to put
> its lookup and caching on one side of the interface, and an actual
> template
> rendering facility on the other side. That is, treat Myghty as an
> embedd*er* rather than the embedd*ee*, so that th
is it possibly of value to just put some of these ideas into practice
first without shooting any of them down ? I find it very hard to
come up with broad-ranging specs, and then declare it as "thats the
way it will be", without having a decent community of folks trying
out the ideas and se
On Feb 1, 2006, at 12:59 PM, Phillip J. Eby wrote:
> At 1
>
> So asking for "foo" can resolve to "foo.gif" or "foo.jpeg" in the
> file system? If you have to say in the code which it is, that's
> not what I mean.
you can write a resolver that searches the filesystem for "foo.*" and
does s
On Feb 1, 2006, at 11:07 AM, Phillip J. Eby wrote:
>> spec is about (like what is template polymorphism exactly ?)
>
> Specifying only a template's *name* in code, not its type. In
> peak.web, if I refer to a resource or template named "foo", the
> system looks in the resource directory and
do either of these specs address the concept of componentized
templates ? that is, when you are referencing a template, compiling
its output, and delivering its textual output, in reality that
template would consist of possibly dozens of smaller sub-templates,
to form different parts of th
Clark C. Evans wrote:
>
> I'd stick with the notion of a "template_name" that is neither the
> template file nor the template body. Then you'd want a template factory
> method that takes the name and produces the template body (complied if
> necessary). This needs to be once indirect since a temp
hey all -
I have released Myghty 0.99a, which includes a variety of bugfixes, as
well as a new demo application which illustrates some new controller ideas
plus integration with an improved MyghtyJax toolkit and the upcoming
SQLAlchemy database library.
Myghty is a full Python port of HTML::Mason
On Aug 17, 2005, at 6:49 PM, Phillip J. Eby wrote:That really hasn't been my experience. Partly, this is because I tend to use RESTful approaches that put 99% of all statefulness in the browser. For example, if I have a multi-page form, I embed all the previous pages' data as hidden fields on the
my particular confusion, and this may very well be because i am not
digging in heartfully enough into the docs, is that the main example is
very much bonded to using Webware and Zope templates, and since I am
unfamiliar with those it is very difficult for me to see what parts of
the example
On Apr 17, 2005, at 1:18 PM, Brendan O'Connor wrote:
Let me put it this way: I've spent weeks and weeks researching many
many python frameworks, but never found one that seemed proven in
terms of adoption by a large number of high-traffic sites.
one could say the same thing about Rails.
And since
On Apr 15, 2005, at 8:54 PM, Brendan O'Connor wrote:
Amen. I don't mean to slam the work of any web framework developers,
but you can't overestimate how much it helps just-beginning web
developers to see a unified framework, or at least a good website that
directs them to one particular way to
my own project, Myghty, is modeled after Perl's HTML::Mason, which in
turn is a lot like PHP with regards to "just plug it in and start
writing pages". it does foster a more compentized design than PHP and
also integrates nicely into whatever MVC framework the developer
chooses. Myghty a
if you run multiple virtual hosts out of Apache, mod_python by default
creates new subinterpreters, via Py_NewInterpreter, for each virtual
host. this can also be set up per apache directive, an arbitrary name,
or within individual directories.
although how well Py_NewInterpreter separates
17 matches
Mail list logo
