[Gambas-user] Re: new Gambas documentation (Rob)

[Peski -]

Joseph Murphy,

For your comment, I think you only see a "demo" of new gambas documentation 
system located in http://64.128.110.55/help

If you open Gambas IDE and see help section, you can found many information 
about Gambas programming interface. You can also see the source code of some 
component as example and learn from it. But, of course, you have the 
necessary documentation (I think) in gambas help.

Regards,
Peski

PD: If you haven't installed GambasIDE, you can found same documentation in 
http://www.binara.com/gambas-wiki/bin/view/Gambas/




>From: Daniel Campos <danielcampos at ...282...>
>Reply-To: gambas-user at lists.sourceforge.net
>To: gambas-user at lists.sourceforge.net
>Subject: Re: [Gambas-user] Re: new Gambas documentation (Rob)
>Date: Sun, 31 Jul 2005 00:55:25 +0200
>
>I do not understand very well what you say... the documents about the 
>Gambas programming
>interface for components is placed in the same Gambas sources!!!.
>
>Just open Gambas help at look at "How to program components"!!!
>
>Regards,
>
>D. Campos
>
>
>
>
>Joseph Murphy escribió:
>
>>The new docs look good but I was locked out on many of the hyper links.
>>
>>I would also like to make a request for addition to the docs. This is 
>>listed in the docs for component programming:
>>
>>The components and the interpreter communicate through the Gambas 
>>Programming Interface.
>>
>>They are executed in the interpreter environment, and so must not do 
>>whatever they want.
>>
>>
>>
>>What is this interface?  I would like to see a detailed explanation of 
>>this interface.  Also what are the restrictions on components?  The docs 
>>say that they "must not do whatever they want" but it doesn't go into 
>>detail about that.
>>
>>The ability of a programmer to extend gambas by adding a component is one 
>>of the strong points of gambas.  But it is being weakened by the time and 
>>effort needed to just get up to speed on component writing.
>>
>>I understand that writing documentation is the gritty part of a project 
>>and nobody likes doing it.  But, in many ways, it is the most important 
>>part of the project.  I forget who said this but it is one of the best 
>>explanation of documentation I have heard:  Documentation is like sex.  
>>When it's good it's very good, when it's bad it's better then nothing.
>>
>>Joseph
>>
>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>>informative Webcasts and more! Get everything you need to get up to
>>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>>_______________________________________________
>>Gambas-user mailing list
>>Gambas-user at lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/gambas-user
>>
>>
>>
>>
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
>_______________________________________________
>Gambas-user mailing list
>Gambas-user at lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/gambas-user