On 7/19/01 10:23 AM, "Stephane Bailliez" <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I'm currently trying to set up a quick prototype using Turbine/Velocity.
> It is not going bad so far, but it looks like Turbine is actively being
> changed at this time.
>
> I tried to do my prototype with the 2.2a version, but could not reach a
> stable state so far between sources and binaries release. As well a lot of
> classes changed from 2.1 like VelocityScreen, Context, etc... this makes it
> a nightmare for the learning curve.
You're getting two issues confused. Learning 3.0 will be a lot easier as
there will be a defined API. Converting your sources is a whole other
ball game and if you choose to try it now you're not going to get very
far. Scarab is having a hard time keeping up and its developers are
intimately familiar with Turbine. I am actually taking Jyve which is
a 2.1 application and trying to get it to work with 3.0. This will be
done with a combination of adapter code, a migrator to transform sources
that use classes that cannot be adapted, and a migration document.
What is in the 3.0 tree is meant to be clean. When 3.0 is complete than
I will come up with a process for conversion.
> I then saw the 3.0 release from yesterday, I tried to set it up without
> success.
I'm not surprised. The sample TDK app is small but demonstrates all the
basics and is always kept up to date.
> I tried to build it from CVS so that I had a match source/binaries, I did
> not succeed without having an impressive list of errors during the build and
> did not have the time to investigate.
I would strongly suggest sticking to 2.1.
> It looks like there is a massive change (thus the 3.0 version I guess) going
> on currently and I think the torque separation does not help. Right now.
I definitely don't agree. Again I would strongly recommend you stick with
2.1.
> I switched back to 2.1 and I'm now able to debug the source code of my
> screens and all things that were not working in 2.2 and 3.0 are working
> perfectly in 2.1 (delta the change in the layout for $renderer and such).
Good plan.
> Mainly:
>
> - doing a $page.setTitle() in a screen and doing a $page.Title in the
> layout works in 2.1, not in 3.0, it sends back nothing.
Yes, this isn't working. I broke it, haven't fixed it yet.
> What is supposed to
> be the evaluation order between layouts, screen and navigations ?
Read the notes, the order is defined by a pipeline. In 3.0 it can
be whatever you want.
> - I'm not able to get my screen objects (ie classes) to be loaded for some
> reasons in 3.0 (I could not set up the environment quickly so I did not dig
> into it) while it works in 2.1.
It works fine. Please look at the sample app if you want to see something
that works.
> I just saw that the 1 parameter Class.forName() is used to get the classes
> in 3.0...Is that really appropriate ? I would use the
> ThreadContextClassLoader here...
Can you explain in a little more detail?
> All in all, congrats to everyone here, the code is incredibly clean.
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
