ajones wrote:
> 
> Karl Guertin wrote:
>> On 4/17/06, Igor Murashkin <[EMAIL PROTECTED]> wrote:
>>> Sooo, anyone want to mentor us CS students? :)
>> You don't want my mentoring!
> 
> Mine either, but it would be nice to see some turbogears related stuff
> happen. Some of the ideas I have had:
> 
> * Google/Yahoo/Whatever widget library: Would be nice to be able to
> supply a widget with the appropriate account information and have
> support for maps/adsense/whatever integration from inside turbogears.
> At the upper limit of the idea it would essentially be "from mashup
> import *".
> 
> * SQLObject schema interpreter: Reads pre-existing tables and generates
> SQLObject classes based on their contents. Probably not possible to
> make it 100% accurate, but it would be a nice headstart.
> 
> * Database schema versioning: Similar to Ruby on Rails migrate system.
> Basically allow for alterations to be made to an existing database
> according to migrate rules. This obviously would require that SQLObject
> be capable of altering existing tables. (Is it? Has it always been able
> to? I don't know)
> 
> * TurboGears documentation: Mwuhahaha mwuhahahaha the perfect inter^W
> student project. Seriously though it could be a decent project if it
> involved development work on Docudo.
> 
> Anyone else have ideas? Who wants to badger Kevin into seeing if he
> will find/be a mentor for this?

How about creating a specification similar to our template protocol for 
widgets and separate them from TG core. This would be beneficial to the 
whole Python web community (and a step closer to a franken-framework 
that not just kicks but pulverises ass ;)).

Cheers,
Simon

--~--~---------~--~----~------------~-------~--~----~
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