|
From: Everson D. <DAE...@AG...> - 2001-09-14 22:12:21
|
FYI. This is an email that I posted to the Turbine user mailing list. -----Original Message----- From: Everson Dave To: tur...@ja... Sent: 9/14/01 2:44 PM Subject: Turbine 2.x vs Turbine 3.0 I want to follow-up on a couple of messages that have been posted this week dealing with Turbine 2.x and Turbine 3.0. We are looking at starting a new development project using the Turbine platform. In a post earlier this week, someone asked when 3.0 would be released. The response was: "It's not scheduled for release. Right now it's still changing on a daily basis, so I'd say that it is still going to be quite some time before the release happens. I would suggest using 2.1 or the upcoming 2.2 for now for any serious development work." OK, that is fine, we should use 2.x. But then today, in response to a generic question about "getScreen" and "getScreenTemplate", "setScreen" and "setScreenTemplate". The following sentence was posted: "In Turbine 3.0 there are no such things as screens, navigations and layouts. There are just modules and they can be aggregated in an arbitrary fashion to render content." Since I am new to the whole Turbine framework, I am wondering exactly how different is Turbine 3.0 from Turbine 2.x. Will much of what we implement with Turbine 2.x have to be rewritten or modified in 3.0? Is there a list of functionality that is being modified or removed in 3.0? Knowing such details may have an impact on how I design and write an application using 2.x so that the migration to 3.0 someday would be less painful. Thanks. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: tur...@ja... For additional commands, e-mail: tur...@ja... |