Hi Jürgen. I don´t use turbine since I ported my last application to guara. Guara borrows many concepts from turbine but it´s much more simple in many ways. It also has Ajax integration support using a specific pipeline. IMHO Turbine should keep it´s pipeline, but make it suitable for ajax.
What is centralized Page Authorization Concept? Cheers -- Leandro Rodrigo Saad Cruz CTO - InterBusiness Technologies db.apache.org/ojb guara-framework.sf.net xingu.sf.net On 6/23/06, Jürgen Hoffmann <[EMAIL PROTECTED]> wrote:
Hi All, since Development on Turbine is stalling a bit, I am asking the folks who know best :) What is the future of Turbine? is it the t2.3.2 branch, or the 2.4 branch with pipelining support? Is it the t2.3.2 branch with fulcrum components? Questions over questions. From my understanding there are 2 parties. One using happily 2.3.2 and one using 2.4 happily. Do I see this wrong? Where are the points at which these two could merge together, and what would be next? t2.5 or rather turbine3? when someone contributes to the codebase, where is it to be done best? Turbine has in my eyes so many features, that other popular frameworks lack. But has some major disadvantages. One of them is lacking AJAX support. We have used json 1.0 in some of our projects and are very happy with it. I would be willing to again contribute the JSON Screen, that we have developped for that and which is based upon the link found at the wiki... Another is Lack of RAD Tools Support, and a centralized Page Authorization Concept (correct me if i am wrong). I just want to minimize my effort in integrating this into 3 different codebases all the time. So what I really want to start is development into turbines future again and make people use this great framework more. Kind regards Juergen Hoffmann
