I have been using Turbine 2.3.1 for 4 years at my current company
(previous versions since 2001). It has been a very flexible, expandable
technology.

Frankly 2.3.1 has been very solid, to the extent that I haven't yet
upgraded to a newer version...  though I am sure that I will get to this
eventually.

I have wondered at times about the cool things that others have done or
are trying to do with Turbine.  The obvious thing that seems to attract
developers to tools is new and useful features, or even useful
approaches.

It sometimes seems as if people only submit to this site when they have
some immediate problem to solve.  It would be great to hear about
other's techniques, and solutions or just something that they came
across that is cool.  Answers to individual questions are great, but
collaborative discussions, debates, etc, are what keep larger groups of
people interested and help technologies like Turbine thrive and grow.

>From personal experience, I would guess that knowing that something can
be done with Turbine, or that there is an accessible approach/solution
would provide enough motivation for new developers to take the time to
learn and become proficient with Turbine.

One thing that I created for use with Turbine is a very basic approach
for re-skinning the same VM in multiple languages.  I also find it
useful for customizing/re-purposing the same page without having to
re-code the logic.  We support multiple affiliates who want their own
flavors of our products, etc.
 
I am quite certain that better minds than mine would look at my approach
for the above and say "I can do it even better than that", or "there is
already  a better solution", etc.  This is the whole point.  

Tony Oslund

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to