No subject

>avoid needing to compile all the gambas stuff (45' minutes in a
>poweful PC) whenever a "make clean" is executed

Oh, I don't know... My laptop's 3 years old and even Gambas 1.9.3 only=20
takes half an hour to compile.... on battery. On the workstation I=20
use at one of my client sites (a fairly powerful one but not top-end,=20
P4-2800) it takes about 12 minutes.

I mean, I agree with you 1000% about needing to be able to make a=20
separate package with just the API-related stuff (I tried in the past=20
to make a gambas-devel package but ended up making a gambas-source=20
package instead) but I think having to distribute a gigantic source=20
RPM with every stand-alone component is a worse problem than compile=20
time.

>We spent also a lot of time talking about the ideas that Beno=EEt &
>Daniel had about the possibility of using Gambas as a web development
>platform. The easiest taking off could be exporting gb.form to HTML +
>CSS. Then, if XForms becomes standard that would be the way to=20
follow.

I am working on a project for a client that involves recreating a very=20
large Access application as a set of CGI's.  The client wants the=20
resulting web forms to resemble the Access forms as much as possible=20
(uggggh....) and in my quest to do this I started working on a Gambas=20
form to HTML+CSS translator, using absolute positioning, just so I=20
could use Gambas' form editor rather than NVU's awkward one or doing=20
everything by hand.  I didn't realize anyone else would want to do=20
such a thing, but if anyone else cares, I can try to rewrite in=20
gambas2 (it's in perl now, of course), polish it up and post it.

Rob