RE: Jetspeed documentation

[Alberto Rodriguez Galdo]

I'm still thinking there's a need of written documentation, i'm not part
of the jetspeed developer team, so if i want to know how jetspeed works
i need someone to assist me.

I would be very pleased of contributing doc but first i need to
understand how it works, and that's something i cannot do alone...


El lun, 26-04-2004 a las 18:39, Mark Orciuch escribió:
> Search the archives, post your questions to the list but don't expect anyone
> to write a book on Jetpeed in the near future. I'd love to do that but I
> must pay my bills first ;-)
> 
> You should get most of your questions answered via the list and, with some
> diligence, you'll find lots of information in the mailing list archives. If
> you're really serious about using Jetspeed-1, please get involved in
> improving the existing documentation. Such is the way of open source.
> 
> Best regards,
> 
> Mark C. Orciuch
> Next Generation Solutions, Ltd.
> e-Mail: [EMAIL PROTECTED]
> web: http://www.ngsltd.com
> 
> 
> > -Original Message-
> > From: David Cornide Albo [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 26, 2004 11:16 AM
> > To: Jetspeed Users List
> > Subject: RE: Jetspeed documentation
> >
> >
> > Alberto you are very right.
> >
> > It is necessary more documentation and some explanations about
> > architectural design and decissions.
> >
> > Best regards.
> >
> >
> >
> >
> > At 18.12 26/4/04 +0200, you wrote:
> > >I've already read the tutorial and there's no such lot of documentation,
> > >only hello world-alike examples
> > >
> > >At 10.34 26/4/04 -0500, you wrote:
> > >>Try the tutorial - lots of documentation there.
> > >>
> > >>Best regards,
> > >>
> > >>Mark C. Orciuch
> > >>Next Generation Solutions, Ltd.
> > >>e-Mail: [EMAIL PROTECTED]
> > >>web: http://www.ngsltd.com
> > >>
> > >>
> > >> > -Original Message-
> > >> > From: Alberto Rodriguez Galdo [mailto:[EMAIL PROTECTED]
> > >> > Sent: Monday, April 26, 2004 7:42 AM
> > >> > To: [EMAIL PROTECTED]
> > >> > Subject: Jetspeed documentation
> > >> >
> > >> >
> > >> > Hey guys, seems that you've made a first-class quality job
> > with jetspeed,
> > >> > but how can we use properly Jetspeed without documentation
> > >> >
> > >> > It is the time to stop and write some documentation, i'm sure
> > >> > there's lots
> > >> > of people willing to use jetspeed in their projects but they
> > can't only
> > >> > because the lack of documentation
> > >> >
> > >> > I've been almost one week trying to guess how Velocity, Torque
> > >> > and Turbine
> > >> > work altogether, now i'm tired of trying to guess how in
> > hell jetspeed
> > >> > manages to fill and use $jslink variables, now i'm thinking
> > in throwing
> > >> > jetspeed off and have some retirement in the woods...
> > >> >
> > >> > Please, let's make some documentation!!
> > >> >
> > >> > greetings
> > >> >
> > >> > p.s.- I know writing docs is not as exciting as writing
> > software, i'm a
> > >> > programmer too, but it's necesary as projects grow and grow
> > >> >
> > >> >
> > >> >
> > >> > -
> > >> > 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]
> > >
> > >
> > >-
> > >To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > David Cornide Albo
> > [EMAIL PROTECTED]
> > Departamento de Telmática
> > Centro de Innovación y Servicios de Galica, CIS D&T
> > A Cabana sn, Ferrol
> > Tlfno: 981337125
> > Fax:   981337171
> >
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
Alberto Rodriguez Galdo
GPG id 747A7479


signature.asc
Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada	digitalmente

RE: Jetspeed documentation

[Mark Orciuch]

Search the archives, post your questions to the list but don't expect anyone
to write a book on Jetpeed in the near future. I'd love to do that but I
must pay my bills first ;-)

You should get most of your questions answered via the list and, with some
diligence, you'll find lots of information in the mailing list archives. If
you're really serious about using Jetspeed-1, please get involved in
improving the existing documentation. Such is the way of open source.

Best regards,

Mark C. Orciuch
Next Generation Solutions, Ltd.
e-Mail: [EMAIL PROTECTED]
web: http://www.ngsltd.com


> -Original Message-
> From: David Cornide Albo [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 26, 2004 11:16 AM
> To: Jetspeed Users List
> Subject: RE: Jetspeed documentation
>
>
> Alberto you are very right.
>
> It is necessary more documentation and some explanations about
> architectural design and decissions.
>
> Best regards.
>
>
>
>
> At 18.12 26/4/04 +0200, you wrote:
> >I've already read the tutorial and there's no such lot of documentation,
> >only hello world-alike examples
> >
> >At 10.34 26/4/04 -0500, you wrote:
> >>Try the tutorial - lots of documentation there.
> >>
> >>Best regards,
> >>
> >>Mark C. Orciuch
> >>Next Generation Solutions, Ltd.
> >>e-Mail: [EMAIL PROTECTED]
> >>web: http://www.ngsltd.com
> >>
> >>
> >> > -Original Message-
> >> > From: Alberto Rodriguez Galdo [mailto:[EMAIL PROTECTED]
> >> > Sent: Monday, April 26, 2004 7:42 AM
> >> > To: [EMAIL PROTECTED]
> >> > Subject: Jetspeed documentation
> >> >
> >> >
> >> > Hey guys, seems that you've made a first-class quality job
> with jetspeed,
> >> > but how can we use properly Jetspeed without documentation
> >> >
> >> > It is the time to stop and write some documentation, i'm sure
> >> > there's lots
> >> > of people willing to use jetspeed in their projects but they
> can't only
> >> > because the lack of documentation
> >> >
> >> > I've been almost one week trying to guess how Velocity, Torque
> >> > and Turbine
> >> > work altogether, now i'm tired of trying to guess how in
> hell jetspeed
> >> > manages to fill and use $jslink variables, now i'm thinking
> in throwing
> >> > jetspeed off and have some retirement in the woods...
> >> >
> >> > Please, let's make some documentation!!
> >> >
> >> > greetings
> >> >
> >> > p.s.- I know writing docs is not as exciting as writing
> software, i'm a
> >> > programmer too, but it's necesary as projects grow and grow
> >> >
> >> >
> >> >
> >> > -
> >> > 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]
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
> David Cornide Albo
> [EMAIL PROTECTED]
> Departamento de Telmática
> Centro de Innovación y Servicios de Galica, CIS D&T
> A Cabana sn, Ferrol
> Tlfno: 981337125
> Fax:   981337171
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Jetspeed documentation

[David Cornide Albo]

Alberto you are very right.

It is necessary more documentation and some explanations about 
architectural design and decissions.

Best regards.



At 18.12 26/4/04 +0200, you wrote:
I've already read the tutorial and there's no such lot of documentation, 
only hello world-alike examples

At 10.34 26/4/04 -0500, you wrote:
Try the tutorial - lots of documentation there.

Best regards,

Mark C. Orciuch
Next Generation Solutions, Ltd.
e-Mail: [EMAIL PROTECTED]
web: http://www.ngsltd.com
> -Original Message-
> From: Alberto Rodriguez Galdo [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 26, 2004 7:42 AM
> To: [EMAIL PROTECTED]
> Subject: Jetspeed documentation
>
>
> Hey guys, seems that you've made a first-class quality job with jetspeed,
> but how can we use properly Jetspeed without documentation
>
> It is the time to stop and write some documentation, i'm sure
> there's lots
> of people willing to use jetspeed in their projects but they can't only
> because the lack of documentation
>
> I've been almost one week trying to guess how Velocity, Torque
> and Turbine
> work altogether, now i'm tired of trying to guess how in hell jetspeed
> manages to fill and use $jslink variables, now i'm thinking in throwing
> jetspeed off and have some retirement in the woods...
>
> Please, let's make some documentation!!
>
> greetings
>
> p.s.- I know writing docs is not as exciting as writing software, i'm a
> programmer too, but it's necesary as projects grow and grow
>
>
>
> -
> 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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
David Cornide Albo
[EMAIL PROTECTED]
Departamento de Telmática
Centro de Innovación y Servicios de Galica, CIS D&T
A Cabana sn, Ferrol
Tlfno: 981337125
Fax:   981337171

RE: Jetspeed documentation

[Alberto Rodriguez Galdo]

I've already read the tutorial and there's no such lot of documentation, 
only hello world-alike examples

At 10.34 26/4/04 -0500, you wrote:
Try the tutorial - lots of documentation there.

Best regards,

Mark C. Orciuch
Next Generation Solutions, Ltd.
e-Mail: [EMAIL PROTECTED]
web: http://www.ngsltd.com
> -Original Message-
> From: Alberto Rodriguez Galdo [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 26, 2004 7:42 AM
> To: [EMAIL PROTECTED]
> Subject: Jetspeed documentation
>
>
> Hey guys, seems that you've made a first-class quality job with jetspeed,
> but how can we use properly Jetspeed without documentation
>
> It is the time to stop and write some documentation, i'm sure
> there's lots
> of people willing to use jetspeed in their projects but they can't only
> because the lack of documentation
>
> I've been almost one week trying to guess how Velocity, Torque
> and Turbine
> work altogether, now i'm tired of trying to guess how in hell jetspeed
> manages to fill and use $jslink variables, now i'm thinking in throwing
> jetspeed off and have some retirement in the woods...
>
> Please, let's make some documentation!!
>
> greetings
>
> p.s.- I know writing docs is not as exciting as writing software, i'm a
> programmer too, but it's necesary as projects grow and grow
>
>
>
> -
> 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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Jetspeed documentation

[Mark Orciuch]

Try the tutorial - lots of documentation there.

Best regards,

Mark C. Orciuch
Next Generation Solutions, Ltd.
e-Mail: [EMAIL PROTECTED]
web: http://www.ngsltd.com


> -Original Message-
> From: Alberto Rodriguez Galdo [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 26, 2004 7:42 AM
> To: [EMAIL PROTECTED]
> Subject: Jetspeed documentation
>
>
> Hey guys, seems that you've made a first-class quality job with jetspeed,
> but how can we use properly Jetspeed without documentation
>
> It is the time to stop and write some documentation, i'm sure
> there's lots
> of people willing to use jetspeed in their projects but they can't only
> because the lack of documentation
>
> I've been almost one week trying to guess how Velocity, Torque
> and Turbine
> work altogether, now i'm tired of trying to guess how in hell jetspeed
> manages to fill and use $jslink variables, now i'm thinking in throwing
> jetspeed off and have some retirement in the woods...
>
> Please, let's make some documentation!!
>
> greetings
>
> p.s.- I know writing docs is not as exciting as writing software, i'm a
> programmer too, but it's necesary as projects grow and grow
>
>
>
> -
> 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]

Jetspeed documentation

[Alberto Rodriguez Galdo]

Hey guys, seems that you've made a first-class quality job with jetspeed, 
but how can we use properly Jetspeed without documentation

It is the time to stop and write some documentation, i'm sure there's lots 
of people willing to use jetspeed in their projects but they can't only 
because the lack of documentation

I've been almost one week trying to guess how Velocity, Torque and Turbine 
work altogether, now i'm tired of trying to guess how in hell jetspeed 
manages to fill and use $jslink variables, now i'm thinking in throwing 
jetspeed off and have some retirement in the woods...

Please, let's make some documentation!!

greetings

p.s.- I know writing docs is not as exciting as writing software, i'm a 
programmer too, but it's necesary as projects grow and grow



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Jetspeed documentation.

[Qualilearning Technical]

Hi,

I'm a newbie in Jetspeed. I have read the documentation and the tutorial
about Jetspeed. Is there other sources of information about Jetspeed
like web sites, pdf, samples...

I have to use Jetspeed to develop a Portal and a CMS solution so I have
to find the maximum info to start in the right way.

Thanks.

Fabiano.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Printing Jetspeed documentation from jakarta.apache.org/jetspeed / printer friendly format ?

[Tuttenuj, Thomas]

Hi,

This is a more general topic:

when trying to print some of the Jetspeed documents
one can hardly read it, because the text is not wrapped on the right border,
not even, when i try to print to print it landscape.

for example this doc:
http://jakarta.apache.org/jetspeed/site/security.html

can I do something to change this ?
could the apache team rethink the formatting ???

kind regards,
and nice holidays !

thomas
germany


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Jetspeed documentation

[Don Clark]

Please keep width to a size that will print.  Most of the doc pages are
wider than will print even in landscape, plus they are harder to read.