[OldBones]

I have inherited a bit of a problem, In the past we built a lot of custom post processors for different projects using NX postbuilder. However nothing is documented, and it is really difficult for new users to understand how each post is configured and use what we have.
I would like to start documenting what I have to make managing the system easier, and to allow us to merge similar posts in the future. However I have no idea where to start.
Does anyone have a template for documenting a custom post and UDE?

[blmmdes]

Dear Friend,

TCL code is a document itself. If you can follow the procs one by one.

NX post is nothing but top-to-bottom reading. Just like reading a newspaper...In front page you will find...goto page so and so and in that page you will find go to page so and so and so on...

[OldBones]

Dear Friend,

TCL code is a document itself. If you can follow the procs one by one.

NX post is nothing but top-to-bottom reading. Just like reading a newspaper...In front page you will find...goto page so and so and in that page you will find go to page so and so and so on...

My problem is getting other people to understand my intent while debugging or updating a post that I created.
Up to now We have been depending on people's ability to read the code and comments to infer the intent with mixed results.

[nximran]

ilh;pik;jk