Re^2: Create and edit new scripts

in reply to Re: Create and edit new scripts
in thread Create and edit new scripts

Your suggestions make a lot of sense. Documentation is a very good thing that I'm not very good at. I will have to get to grips with POD but it's something I have been putting off.

The use of a command-line option would indeed make things easier but I wanted to use ALRM handling just to learn how to do it. I wrote this some years ago and the first cut of the ALRM stuff was pretty crude. I tweaked it more recently with the countdown, again because I thought it would be interesting to learn. I'm not sure about your "... and a lot easier to use." There's not a lot of difference between

% newscript -e fred
[download]

and

% newscript fred
... prompt ... y
[download]

Thank you for the feedback,

JohnGG

Comment on Re^2: Create and edit new scripts Select or Download Code

Replies are listed 'Best First'.
Re^3: Create and edit new scripts by wazoox (Prior) on May 06, 2006 at 14:50 UTC
Your suggestions make a lot of sense. Documentation is a very good thing that I'm not very good at. I will have to get to grips with POD but it's something I have been putting off.</blocckquote> I know this is mere proselytism, anyway in case you don't really get into POD you could give ROBODoc a try. It has a couple of advantages: It sucks up much less space than POD; It mixes up fine with code and comments (you can easily make documentation from your comments); It works with any language I know of, so you can ROBODoc your Java, your html, your C and your PHP too. ROBODoc can build a one-document digest from a whole code tree; You can anyway generate HTML, RTF, PDF... from ROBODoc as well as POD; Last, you can also generate POD with the ROBODoc to Pod translator script.	[reply]

Replies are listed 'Best First'.

Re^3: Create and edit new scripts
by wazoox (Prior) on May 06, 2006 at 14:50 UTC

Your suggestions make a lot of sense. Documentation is a very good thing that I'm not very good at. I will have to get to grips with POD but it's something I have been putting off.</blocckquote>
I know this is mere proselytism, anyway in case you don't really get into POD you could give ROBODoc a try. It has a couple of advantages:

It sucks up much less space than POD;

It mixes up fine with code and comments (you can easily make documentation from your comments);

It works with any language I know of, so you can ROBODoc your Java, your html, your C and your PHP too.

ROBODoc can build a one-document digest from a whole code tree;

You can anyway generate HTML, RTF, PDF... from ROBODoc as well as POD;

Last, you can also generate POD with the ROBODoc to Pod translator script.

[reply]

In Section Cool Uses for Perl