And another with NT and another with 98 and another on the way.

Cliff

Michael A. Hess wrote

I think it is something that is needed but maybe it should be combined with the documation, documotion, docu....oh whatever it's called.

Hehe, "Real programmers don't document... Documentation, weee don't neeeed no steeenking documentation!"

I haven't had an opportunity yet. Like you say, it does require work on the programmers part, which isn't a bad thing. What I was planning on doing was making an inititial page with the contents of the lcl directory, then running CVS with the right options to determine which files had changed on a fairly regular basis (not every day, I don't have that much time!). For each file that changed, I could then use the changes to update the page.

PS: By the way Jeff your reply to still is being forced.

Hmm, that must have been sent from my work account. Sometimes I forget to change the sender. Was it If so, then that explains it, as the did have the reply-to removed. I removed it from the other as well, but it may cause confusion in my work mail (I'm postmaster anyway, so I'll get it even if it misaddresses...)

Jeff.

I think it is something that is needed but maybe it should be combined with the documation, documotion, docu....oh whatever it's called.

Did you look at the tool that MVC talked about. It looks really neat and would kill 2 birds with one stone. It would make building the files you are talking about real easy. As the files change just run it through the tool again to build your new file.

Of course this will rely on comments and information being made available in the source code itself. However if you use this on the files it will then help point out exactly what needs to have comments added.

http://www.geocities.com/SiliconValley/Lakes/6686/pasdoc.html

I like this because it means that all the developers then will be lending a hand to the actual documunchin .... I'll get it yet. :-)

PS: By the way Jeff your reply to still is being forced.

Jeff Wormsley wrote

Hehe, "Real programmers don't document... Documentation, weee don't neeeed no steeenking documentation!"

Here is the exact saying:

"Real programmers don't document. If it was hard to write it should be hard to understand". :-)

I have a button that says this. Always unnerves people I am working for.

I haven't had an opportunity yet.

Check it out. It builds the html write from the source. Then you don't have to do any of that checking which file changed and update your pages. If you just run the tool on all of the source files it will create the HTML docs that you just need to load on your site with links from the component page. Then every day or so rerun the tool incase something has changed. You could even cron it for every evening.

>PS: By the way Jeff your reply to still is being forced. Hmm, that must have been sent from my work account.

Not sure what the other one was but this one still does it to.

This one is from.

"Jeff Wormsley"

and the headers reply-to field has been preset by you email package to:

If the header already has a reply-to set the mailing list server doesn't overwrite it with it's reply-to. This just makes it a pain for someone replying to your email on the list.

I bet you got that one with your first copy of Microsoft Windows 95 :-)

Michael.

Hello all,
I've had an idea for the component site that I think would be very useful, both now during development, and later during documentation (docu-what???). I would like to make a page for each component (or an inpage link into one big page), linked off of the component page. Each component would have a list of each property/method/event, current implementation status of each, and a brief list of known issues. I can do most of this work fairly easily, especially since the components have been split into their own .inc files, but I may need a little help, especially with the known issues part, if you decide to let me go forward.

What do you think, is it worth the effort?

Jeff.

Jeff Wormsley wrote

Is this a Linux or Windows app. If Linux, then I'm stuck, as I still can't get RH6.0 to work correctly.

It is FPC source code. Build it were you want to use it. It reports that it works in Linux, Win32, DOS.

I'm surprised to hear you actually have customers left then :-) Ours would quickly find another contractor :)

Michael.

Michael Van Canneyt wrote

I'm surprised to hear you actually have customers left then :-) Ours would quickly find another contractor :)

In reality I have only worn it with a select few customers who get the joke and can appreciate the humor and reason behind it. In fact I haven't worn it in over 9 years, not sure I can even find it any more. My other button says, "It's not a bug, it's an undocumented feature".

Is this a Linux or Windows app. If Linux, then I'm stuck, as I still can't get RH6.0 to work correctly.

Grrrrr. The setup screen for the account has "Reply to Address" field blank now!!! I have no idea why it is in there. I will dig around and see if there is a switch to hide that field altogether.

Jeff.