durusmail: quixote-users: Why class 'Session' has no method get_user() ?
Why class 'Session' has no method get_user() ?
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
Why class 'Session' has no method get_user() ?
2005-03-17
Why class 'Session' has no method get_user() ?
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
Why class 'Session' has no method get_user() ?
Why class 'Session' has no method get_user() ?
Why class 'Session' has no method get_user() ?
2005-03-18
Why class 'Session' has no method get_user() ?
2005-03-18
Why class 'Session' has no method get_user() ?
2005-03-18
Why class 'Session' has no method get_user() ?
2005-03-18
Why class 'Session' has no method get_user() ?
"Template" components. Was: Why class 'Session' has no method get_user()?
2005-03-19
"Template" components. Was: Why class 'Session' has no method get_user()?
2005-03-19
Why class 'Session' has no method get_user() ?
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
Why class 'Session' has no method get_user() ?
Michele Simionato
2005-03-18
On Thu, 17 Mar 2005 19:48:39 -0800, Shalabh Chaturvedi
 wrote:
> (Wow interesting conversation on this list today!)

Agreed ;)

> mso@oz.net wrote:
> > It's easier to have
> > methods/functions just get the context objects they need directly from a
> > central registry, and that's one uniform way that works at any point in
> > the application.
>
> I completely agree.

+1. I am all for having the minimum amount of classes and inheritance
as possible (yes, I am another Zope refugee ;)

>  > Regarding persistence, are you talking about one of my earlier
>  > e-mails?  I
>  > would like to see Quixote come with "batteries included", yes.
>
> Note that a free set of Quixote batteries can be downloaded anytime from
> qlime.org ;) And while I'm shoving in plugs - cafepy.com now runs
> Quixote + QLime on the main site - (not that there's much content there).
>
> Seriously, though, I think newbies will be happier if a few more things
> work out of the box (a simple session persistence to picked file, for
> example). I'm -0 on including Dulcinea though. Some good utilities are
> already there (StaticFile etc.) and more could be picked up from the
> wiki or submissions. However do the core developers really have the
> resources to maintain all these other things? Hmm.. or should outside
> developers (that's us!) start a quixote-extras project on SF?

This is a most interesting observation ;)
Seriously, I was attracted by Quixote minimalism, so I agree with the
small core concept. OTOH, as Mike says, nearly all real Web applications
require persistence, user management, etc. so it would have sense
to have a standard default library providing that. It was fun and
instructive for me to implement a permission mechanism in Quixote.
Nevertheless, I think there should be an "official" permission mechanism.
Of course, in order to be useful the mechanism must be very simple,
so we can build on it ;) But at least we would have a set of common names
to override, a suggested way of doing things in a "Quixotesque" way, etc.

Concerning the idea of the quixote-extras project: I like the idea, but
we need to guarantee an overall consistency of the batteries. I mean,
not every contribution can go into it, the core Quixote developers
must coordinate the efforts. This mean they would have a lot of time
to spend just in discussions with the contributors: are they willing to
spend all that time?

Finally, about the Wiki. The Wiki is useful, but it is difficult to extract
information from it. And it is difficult to keep it updated. I am not
sure what can be done to improve that situation :-/

            Michele Simionato

reply