[Gambas-devel] gambas source code structure

José L. Redrejo Rodríguez jredrejo at ...101...
Mon Jan 3 12:42:10 CET 2005


Hi Benoît, I would like you to think about modifying the source code
structure for gambas.  Your project has grown up a lot, and everyday is
harder to maintain the components as a whole, because of their
interdependencies.  I would like to see a model similar to most
programming languages in the linux world (python, perl, C, etc.). I.E. a
separated api that allows to compile the different components of
libraries outside from the main tree.

So if I would like to get only the net component I only would need the
gambas headers (and library), net libraries and net component source
code to compile it.   

This would make distro maintainers life much easier, because we would
have the source code split. Nowadays if only a component fails, all the
gambas components are stopped because they share the same source code
package. I am in charge of the development of the LinEx distribution (a
regional Debian based distribution) and I have included gambas-runtime &
gambas-qt components in the last linex cd version. That means that in a
couple of months more than 60.000 computers will be upgraded to that
version and will have the ability of run the gambas apps we have made.
Maintaining such network is harder if I have to recompile the gambas
code everytime a component is updated or a bug is corrected.

Component developers life would also be easier for the same reasons,
they wouldn't have to worry about inserting their code inside your core
source tree. You could even share your work easily giving some
components administration to some volunteers and you would only work in
your favorite components and the gambas core.

It is a suggestion, but I think it would be a useful step in gambas
development, and it doesn't mean a lot of work to do.

Regards.





More information about the Devel mailing list