You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Mus <m....@man.ac.uk> on 2002/01/11 11:37:32 UTC
scree_placeholder
Hi folks,
Can anyone explain what is the role of $screen_placeholder and how it calls
the portlets,,,Please?
Thanks
Mus
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: scree_placeholder
Posted by Paul Spencer <pa...@apache.org>.
Mus,
Simply, $screen_placeholder is variable used by Velocity that contains
the result of portlet's get_content().
If you need a more detail answer, one of the other developers should be
able to provide it. Just ask.
Paul Spencer
Mus wrote:
> Hi folks,
>
> Can anyone explain what is the role of $screen_placeholder and how it calls
> the portlets,,,Please?
>
> Thanks
>
> Mus
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Turbine source for "turbine-2.b1-20011123.jar"
Posted by "Frank T. Villarreal, Jr." <fv...@directhitdata.com>.
Thanks Paul and Santiago for those CVS tutorials ... I needed it. I'll keep
an eye out for that new turbine.jar ... thanks again guys!
- Frank
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Turbine source for "turbine-2.b1-20011123.jar"
Posted by Paul Spencer <pa...@apache.org>.
Frank,
Their was a patch to Turbine required by Jetspeed that was not committed
at the time the jar file was placed in Jetspeed's CVS. I believe the
turbine patch has since been committed. I have request another Turbine
patch. When that one is committed, I will update Turbine.jar.
As a general rule you can use the -D flag on the CVS checkout command
to get the source as of the date specified, the date in this case is
23-Nov-2001. Thus their is no need to maintain the turbine source code
in Jetspeed. In this case, you could argue the path to turbine should
be in Jetspeed's CVS
Paul Spencer
Frank T. Villarreal, Jr. wrote:
> Hello All!
>
> I am attempting custom modifications to Jetspeed and by default Turbine
> code. I noticed that the lastest "release" of Jetspeed utilizes
> turbine-2.2b1-20011123.jar. When I go to retrieve Turbine's source from CVS
> ... I'm getting Turbine's HEAD code ... does anyone know the CVS module name
> for the Turbine source code associated with the aforementioned jar ... I
> would like to make sure my Turbine modifications are in sync with the
> Jetspeed release's source code since they are inter-dependant. Please tell
> me there is a snapshot module of the source code for that jar ... or am I
> out of luck? If I am out of luck, can I make a humble suggestion? In future
> releases of Jetspeed, can we make sure there is a CVS Turbine source code
> module available for the jar that is included with Jetspeed? Just a thought
> ... it would probably save a lot of headaches for developers trying to
> modifiy the code. Anyway, thanks for any help!
>
> -Frank
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Turbine source for "turbine-2.b1-20011123.jar"
Posted by Santiago Gala <sg...@hisitech.com>.
Frank T. Villarreal, Jr. wrote:
>Hello All!
>
>I am attempting custom modifications to Jetspeed and by default Turbine
>code. I noticed that the lastest "release" of Jetspeed utilizes
>turbine-2.2b1-20011123.jar. When I go to retrieve Turbine's source from CVS
>... I'm getting Turbine's HEAD code ... does anyone know the CVS module name
>
Try cvs update -D "2001-11-23" after checkout to get this dated version.
I'm not sure if you can specify this argument straight into the
checkout, it used to be impossible due to a bug.
Even when there is no branch, you can do this. The date spec is in the
local timezone, and I'm not completely sure about granularity of time,
but it should be enough given the activity level in turbine-2.
The change is sticky, so you should "update -A" to get HEAD again.
>
>for the Turbine source code associated with the aforementioned jar ... I
>would like to make sure my Turbine modifications are in sync with the
>Jetspeed release's source code since they are inter-dependant. Please tell
>me there is a snapshot module of the source code for that jar ... or am I
>out of luck? If I am out of luck, can I make a humble suggestion? In future
>releases of Jetspeed, can we make sure there is a CVS Turbine source code
>module available for the jar that is included with Jetspeed? Just a thought
>... it would probably save a lot of headaches for developers trying to
>modifiy the code. Anyway, thanks for any help!
>
cvs keeps track of every single change in turbine code. It means that
you can recover any atomic change (each commit is considered to be
atomic) in the code base, even use "update -D yesterday" or update "-D
'1 month ago'", according to man pages. It is very handy to get diffs,
for instance, all diffs in the week.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Turbine source for "turbine-2.b1-20011123.jar"
Posted by "Frank T. Villarreal, Jr." <fv...@directhitdata.com>.
Hello All!
I am attempting custom modifications to Jetspeed and by default Turbine
code. I noticed that the lastest "release" of Jetspeed utilizes
turbine-2.2b1-20011123.jar. When I go to retrieve Turbine's source from CVS
... I'm getting Turbine's HEAD code ... does anyone know the CVS module name
for the Turbine source code associated with the aforementioned jar ... I
would like to make sure my Turbine modifications are in sync with the
Jetspeed release's source code since they are inter-dependant. Please tell
me there is a snapshot module of the source code for that jar ... or am I
out of luck? If I am out of luck, can I make a humble suggestion? In future
releases of Jetspeed, can we make sure there is a CVS Turbine source code
module available for the jar that is included with Jetspeed? Just a thought
... it would probably save a lot of headaches for developers trying to
modifiy the code. Anyway, thanks for any help!
-Frank
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>