On 4/20/06, Igor Murashkin <[EMAIL PROTECTED]> wrote:
> Yeah, there's lots of ways to improve SQLObject :).

For those thinking about how SQLObject can be better, I'd recommend
taking a look at SQLAlchemy and stretching where things can go *from
there*. SQLAlchemy needs:

1) an SQLObject compatibility layer
2) a layer that is as easy as SQLObject for the easy stuff
(ActiveMapper is almost there)
3) schema migration tools

It already takes care of some of the things that people want SQLObject to do.

> Speaking of widgets, it also wouldn't hurt to generate KID-html from a
> widget so you can do tweaking by hand. I think that would be very cool,
> it takes almost no time to use a widget, but if you want something
> custom you have to do it from the ground up -- so why not combine the
> two?

This was actually part of the original concept. I had imagined
something in the toolbox that would let you hand it a form definition
and get back the necessary Kid to drop into a template for full
tweaking. You can certainly edit the template for individual widgets,
but this route is more designer friendly because they have access to
the whole page.

(At a minimum, the Widget Browser should show you the template source
so that you can copy that into your code for modification).

Back on the subject of Summer of Code: there are some good ideas out
there. I would encourage people to specifically state "I'd like to be
a student participant" or "I'd like to be a mentor" and the types of
things you'd like to work on. If we can get the right people matched
up, we'll see if we can run everything through the PSF's sponsorship
in the Summer of Code.

Kevin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to