I have done a bit more research into the problems with RC3 and the picture
is now much more clear.
A lot of the problems with modules not being executed correctly is due to
the fact that the execution methods, doPerform, doBuild, doBuildTemplate
etc. now receives PiplineData instead of RunData. Further, trere is still a
version of each method left that receives RunData. The effect is that there
are no compliation errors, but the behaviour is changed and sometimes hard
to trace. Some modules, such as Navigation and RawScreen still call their
RunData methods. Others, such as Screen, call the PipelineData method.
I am questioning wether it was a good idea to add PipelineData methods to
all the modules. The methods in the PipelineData interface hardly seems
useful inside a module. The RunData methods however are very useful. If you
look at a lot of the implementations in turbine of Screen, Action, Layout
and the loaders, you can see that they all receive PipelineData and the
first thing they do is to cast it to RunData. Is this not a sign that
RunData would be better? Almost even all the valves use RunData...
Is there any good reason why PipelineData should be used in the modules?
/Ludwig
-----Ursprungligt meddelande-----
From: Thomas Vandahl
Sent: Thursday, June 23, 2011 6:32 PM
To: Turbine Developers List
Subject: Re: [VOTE] Release turbine-4.0-M1 based on RC3
On 22.06.11 03:21, Will Glass-Husain wrote:
No big deal. Just do it again.
Ok, done. I confess, I modified the tag. Please don't shoot me. All
packages have been updated and newly signed. They will need some time to
be mirrored.
Bye, Thomas.
---------------------------------------------------------------------
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]
