[Gambas-user] Documenting a gambas project.

[Jussi Lahtinen]

In my huge project I have the source code in multiple folders, which are
named by the category of what the code does.
Also modules, classes, etc have been named as descriptive as possible.

Be careful when fixing things like that after wise, it's easy to left some
instance renamed or called from old location (always do global search after
the edit).

What kind of things you have problems to find?
If you wonder what some of your function does, just double click on it (or
select the text in any other way) and press F2.


Jussi

On Mon, Aug 17, 2015 at 1:13 PM, richard terry <rterry at ...1823...>
wrote:

> Hi List,
>
> I wonder if anyone has good advice/method for documenting the code
> within a gambas project to make it easy to find stuff.
>
> Our medical records project which has been in use for a number of years
> now is really quite huge.
>
> the Postgresql backend currently has 33 schema's with  many hundreds of
> tables, that is not so much of an issue.
>
> However when one hasn't worked with the gambas code for a long time,
> though I've been pretty good about documenting it, I still  have to
> scratch my head sometimes to remember where stuff is
>
> This is obviously very bad for maintenance.
>
> Any ideas appreciated. What do others do?
>
> Regards
>
> Richard
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Gambas-user mailing list
> Gambas-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-user
>