On 2/11/06, Simon Belak <[EMAIL PROTECTED]> wrote:
>
> http://www.oreillynet.com/pub/wlg/9168?wlg=yes
>
> I am *not* posting this as a call to arms, but rather as means of
> gathering end-user input.
>
> My comments:
>
> 1,2: With full WSGI multi-app support from the bottom up we will retain
> praised simplicity while adding even more powerful application composition.

Yes. The TurboGears model is not to lump a bunch of applications in
one project. You make independent projects, build eggs out of them and
then wire them up into bigger projects.

> 3: It would be nice to support Django templates now they decoupled them
> somewhat.

I actually don't care about that one :)

> We really need to improve error reporting for Kid.

Definitely. Odds are very good that we'll make serious headway at the sprint.

> 4: WSGI + Ian's excellent middleware

Yep.

> 5: Some work into alternative mapping schemes would be good.
> How are we on Routes integration?

Lee has some stuff working that sounds good. There may be some more
config/multiapp work necessary for it. This is not going to land in
the first 0.9 release, but it's the kind of thing that we can try out
on a branch and build it up from there.

> 6: we are getting there with ToolBox

Not exactly. The Toolbox, in my opinion, is an excellent, unique
feature of TurboGears for helping a developer work on their project.
Django's admin system is designed to be deployed to end users (which
is how it varies from the Toolbox). That's where FastData is heading.
I'd like to see FastData, via widgets, become a very customizable way
to do CRUD on the cheap. It's not there yet, but it's a start.

Kevin

Reply via email to