On Jun 26, 2007, at 8:26 AM, [EMAIL PROTECTED] wrote:

>
> On 6月25日, 上午9時52分, "Mark Ramm" <[EMAIL PROTECTED]>  
> wrote:
>> We're done sprinting on pylons/turbogears integration for the  
>> weekend.
>>   But we've managed to accomplish a lot.
>>
>> 1) Object dispatch with extensible lookup in TurboGears style
>> controller on pylons
>>
>> 2) @expose and other decorators add attributes to regester behavior
>> rather than act as wrapper functions.
>>
>> 3) Stacked @expose is now signifcantly less complicated and easier to
>> work with.
>>
>> 4) We worked out lots of content negotiaton issues to make stacked
>> @expose work even better.  Some of which remains to be implemented.
>>
>> 5) You can now have pylons controllers with routes in the same
>> application as turbogears controllers with object dispatch.
>>
>> 6) Object dispatch is now much easier to overide with custom
>> behaviors, paving the way for restful  controllers and other cool
>> stuff.
>>
>> 7) Startup time and memory footprint of TurboGears is  
>> significantly reduced.
>>
>> 8) We have a paster template that makes a default turbogears style  
>> application.
>>
>> 9) You now have a way to pass widgets and other variables into
>> templates outside of the return dictionary.   This is useful for the
>> case where you want to jsonify the return dictionary, but also  
>> want to
>> use widgets in your template.
>>
>> 10) Turbogears applications now have access to beaker for sessions,
>> and lots and lots of other WSGI goodness that's already baked into
>> Pylons.
>>
>> Given that there were just a handful of people working on this, I
>> think this little experiment is an huge success.
>>
>> There are a few things that remain to be implemented.   We don't have
>> transaction middleware, and we have database configuration  
>> improvement
>> ideas that aren't implemented.   But even with all that's  
>> remaining to
>> be done, I think we are at a place where the code is actually usable.
>>
>
> Hi, it looks nice.
>
> I took a quick glance on it. It seems 'rulddispatch' is no longer
> required for decorator,
> Does it means pygears branch is pure python?

Yup. Unless you need TurboJSON which relies on RD for "jsonify" no C  
extension code will be involved. As a matter of fact, we're even  
considering porting "jsonify" to use PEAK-Rules instead of  
RuleDispatch which is pure-python.

Alberto 
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to