On Apr 12, 2007, at 3:12 PM, Steve Bergman wrote:

>
> Hi,
>
> I'm thinking about starting a new project.  It's not time critical, so
> I could wait some time for actual deployment (if ever).  Rather than
> continuing along that path of:
>
> CP2
> SQLObject
> Kid
> TG Widgets
>
> I'd really like to start learning:
>
> CP3
> SQLAlchemy/Elixir
> Genshi
> ToscaWidgets
>
> It's hard to get excited about leaning more of things which are soon
> to become obsolete.
>
> Starting from the current trunk, would I be crazy to start a project
> with the above stack today?

The trunk is unstable at this moment. The controller tests are  
failing and need to be rewritten because they are too tightly bound  
to CherryPy2. There are also some issues with the config. OTOH, a  
quickstarted app seems to run fine on top of CP3 so there's something  
tangible to hack on if you feel inclined. Take a look at #1181 (and  
the links in the ticket) and #1342 if you want to lend a hand.

If  you're not in a tight schedule and willing to hack on TG then  
it's a great opportunity to use the trunk. If it's not the case and  
want to stick with stable code then use the 1.0 branch and integrate  
newer components like Jonathan has suggested.

> Also, ToscaWidgets seems kind of opaque wrt documentation.  Where is
> the best place to go to learn more about using TW?

Yep, widgets documentation is a long standing issue... It's medium on  
my priority list ATM (highest is paid job and high is making the  
tests at trunk pass). For the meantime I'll do my best to help out in  
TW's mailing list [1]

Alberto

[1] http://groups.google.com/group/toscawidgets-discuss/

--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to