Hi
> I think a such type of "functions catalogue" would be not so difficult to been > maintained by Harbour's developers, in parallel to main changelog. > And then somebody could take this document into a "wiki" host and edit it by > adding a detailed description and some sourcecode examples. > I was thought (and wish) that somebody/somewhere has created such a file and > she/he would be willing to share it with us. If you can, simply visit http://harbour.vouch.info/ I developed this tool almost 3 years back but nobody noticed. The tree is old one but amply shows its power, if one liner is the only solution. Also try to double click anywhere in function prototype, you will be able to view functions complete source also. Regards Pritpal Bedi, a student of software analysis and design http://www.vouch.in | Vouch, the software that GROWS with you http://www.vouch32.com | Home of Vouch32 ActiveX Server http://www.vouchcac.com/vouch32/vouch32.htm | A Free Windows Extended Utilities Library for Clipper, Xbase++ and (x)Harbour http://www.help.vouch.info | Online Vouch Help http://www.harbour.vouch.info | Online Harbour Help > To: [email protected] > From: [email protected] > Date: Fri, 12 Feb 2010 08:37:02 +0000 > Subject: [Harbour-users] Re: Harbour documentation > > Massimo Belgrano <mbelgr...@...> writes: > > > > Complete info are wirtten only in changelog.txt > Hi Massimo > > Thank you for your reply. > Changelog.txt is a huge ( I 'd say chaotic ) file, from which is very > difficult > to extract those pieces of text that could be considered as documentation. > I was thinking about a small file with simple structure containing a minimum > (even 'oneliner') > description of Harbour functions. > An such "ideal" document could consist of paragraphs like this: > <p> > FUNCNAME : Slice( <cStr>, <nSlices>, [<nRetSlice>] ) --> cStrSlice > SHORTDESC: Cut off the <cStr> to <nSlices> pieces and return the nRetSlice > piece, (or the first piece, if nRetSlice omitted). > </p> > > I think a such type of "functions catalogue" would be not so difficult to been > maintained by Harbour's developers, in parallel to main changelog. > And then somebody could take this document into a "wiki" host and edit it by > adding a detailed description and some sourcecode examples. > I was thought (and wish) that somebody/somewhere has created such a file and > she/he would be willing to share it with us. > > (About HBIDE, until now i have difficulties to build it from sources, so it > would be helpful if you could post a compiled binary for testing.) > > regards, > > --- > Pete > > > > _______________________________________________ > Harbour-users mailing list (attachment size limit: 40KB) > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour-users _________________________________________________________________ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/201469227/direct/01/_______________________________________________ Harbour-users mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour-users
