martin p cristia
2014-01-21 20:57:41 UTC
Stepping in this old conversation to point out my take:
-computers nowadays are fast enough to run a VM that's fast enough to
run a normal aplication
-If Benoit says it's complicated, what's left for us ??????????????????
- so instead of trying to port gambas, why not making a installer that
sets everything up for the inexperinced user??? Something like the
SmallTalk approach.
Making a small footprint VM+Linux+Gambas...they're all opensource, we
can get rid of everyhing that Gambas dont need...even more, making a
ligth weight Gambas or tagging components as "portable" and others "not"
Say it's a 500MB installer? C'mon my android phone has "Hello world"
like apps that weight 30MB, half giga is 15m download...even here in the
ass of the world (small town Argentina)
As for porting Gambas, it will be really good. I have the time (but not
the brain) to help anyone that joins the party and has the know-how for
a start.
the use
something for
by RMS
to make
things too
like mine
code, by
maker/maintainer.
. :-)
all part
way to
subject of
is not
take
support.
to you
i worked on gambas' portability (OS X and *BSD) and i can say
we need a new structure of code to make a good portability
but mainly a proper maintenance.
Gambas is too linked to Linux. I can understand Benoit isn't
interesting to spend time in the developing to port Gambas,
but Benoit MUST review its code.
At the moment, Gambas is not coded to port properly on
others OS.
a lot of routines is too linked to Linux (i say it again).
Add new components and features is great, but it is
preferable to focus time to make it better.
i hope a work will be done in the gambas code to have
a "modular code". Separate X11 in a single code is
better for us, developers who wants to work on
portability of Gambas!
in this manner, each developer can works on a code
for OS X, for Windows and so on ...
X11 for OS X is ugly.
X11 for Windows is ugly.
Use translated X11 routines are ugly.
Benoit, we don't ask you to port Gambas to OS X & Windows,
just to re-structure code of Gambas so that we can works
efficiently!
While this change will not be applied,
i would not be motivated to work on any Gambas port again...
« [hide part of quote
<http://gambas.8142.n7.nabble.com/Gambas-Future-or-what-kind-of-Gambas-we-want-td44034.html#>]
1) The interpreter relies on some kernel features that are not exactly
implemented in the Windows kernel, especially the fork() system call.
The Cygwin emulation layer is too slow.
2) I don't care about Windows. Doing the port is a big job. I started to
did it on Windows XP + Cygwin years ago. It worked, but there was the
fork() system call emulation that was slow.
3) There is X11 code in gb.gtk, gb.qt4 and gb.desktop.
4) For gb.gtk: as GTK+ 2 is deprecated, gb.gtk should be ported to GTK+
3. This implies removing all the X11 specific code.
5) For gb.qt4: the X11 specific code is there to workaround some
problems, but should not exist theoritically.
6) For gb.desktop: the desktop routines relies on the X11 window manager
protocols and freedesktop.org standards. A lot of things cannot be
ported, but some things can.
7) Many components are interfaces to libraries that do not necessarily
exist on other systems. It could be a problem.
I think there is not a lot of thing to do to port the interpreter, the
compiler and the other tools, as I already did that on Windows.
As for the X11 stuff, of course you're right. It must be encapsulated
somewhere so that it can be easily replaced. I already planned to do
that, but never had the time.
At the moment, I'm busy with fixing Gambas packager as soon as possible,
so that a Gambas 3.5.1 could be released.
--
Benoît Minisini
-computers nowadays are fast enough to run a VM that's fast enough to
run a normal aplication
-If Benoit says it's complicated, what's left for us ??????????????????
- so instead of trying to port gambas, why not making a installer that
sets everything up for the inexperinced user??? Something like the
SmallTalk approach.
Making a small footprint VM+Linux+Gambas...they're all opensource, we
can get rid of everyhing that Gambas dont need...even more, making a
ligth weight Gambas or tagging components as "portable" and others "not"
Say it's a 500MB installer? C'mon my android phone has "Hello world"
like apps that weight 30MB, half giga is 15m download...even here in the
ass of the world (small town Argentina)
As for porting Gambas, it will be really good. I have the time (but not
the brain) to help anyone that joins the party and has the know-how for
a start.
After long talk with many gambas developpers, after years of joy on
of this language, I want to talk about its future... its persistance.
Benoit for me is a little bit like our Linus. He have done
Benoit for me is a little bit like our Linus. He have done
itself and it's today one of the better tool ever see. (Umm ... ;-))
Now, for me one thing lock down Gambas... why can't it be more known ?
Because it is close to Linux world. Theire is no possibility to use it
natively on other system ... this problem what explicitely exposed
Now, for me one thing lock down Gambas... why can't it be more known ?
Because it is close to Linux world. Theire is no possibility to use it
natively on other system ... this problem what explicitely exposed
in the past in a mail sended to us. Yes in his request he wanted us
the interpreter generate a cil code for interpreter like java/.net or
parrot. Well today we know java isn't a sure way, and we can do
parrot. Well today we know java isn't a sure way, and we can do
without.
I have a request to Benoit, and i know it's time is precious and
I have a request to Benoit, and i know it's time is precious and
rare. I want him to concentrate on make it's code portable... separate
specific linux part to allow all our friend that want to help to port
gambas to stars to make theire job.
By doing this, most people can participate on compiler/interpreter
specific linux part to allow all our friend that want to help to port
gambas to stars to make theire job.
By doing this, most people can participate on compiler/interpreter
having Gambas on other system we can have more component
At the end Benoit can take hollidays and come take a Cognac at home
I know this is a huge job as he/we need to take the time to mark
of the code that is hard linked on Linux system, and then choose a
separate it to symplify the maintainment
Same thing for the toolkits but it's at a first time not the
Same thing for the toolkits but it's at a first time not the
today.
Now we have hands that can help... but it can't be done if the code
Now we have hands that can help... but it can't be done if the code
structured for.
So for the Undred time ... Benoit ... Please, let us helping you.
To all, the gambas user/dev, this exchange is for you so even if it
So for the Undred time ... Benoit ... Please, let us helping you.
To all, the gambas user/dev, this exchange is for you so even if it
thouthen of mail, please give us your impress and your ideas, your
Please, don't look at the spelling fault, it will take to many time
;-)
Fabien's right!i worked on gambas' portability (OS X and *BSD) and i can say
we need a new structure of code to make a good portability
but mainly a proper maintenance.
Gambas is too linked to Linux. I can understand Benoit isn't
interesting to spend time in the developing to port Gambas,
but Benoit MUST review its code.
At the moment, Gambas is not coded to port properly on
others OS.
a lot of routines is too linked to Linux (i say it again).
Add new components and features is great, but it is
preferable to focus time to make it better.
i hope a work will be done in the gambas code to have
a "modular code". Separate X11 in a single code is
better for us, developers who wants to work on
portability of Gambas!
in this manner, each developer can works on a code
for OS X, for Windows and so on ...
X11 for OS X is ugly.
X11 for Windows is ugly.
Use translated X11 routines are ugly.
Benoit, we don't ask you to port Gambas to OS X & Windows,
just to re-structure code of Gambas so that we can works
efficiently!
While this change will not be applied,
i would not be motivated to work on any Gambas port again...
<http://gambas.8142.n7.nabble.com/Gambas-Future-or-what-kind-of-Gambas-we-want-td44034.html#>]
1) The interpreter relies on some kernel features that are not exactly
implemented in the Windows kernel, especially the fork() system call.
The Cygwin emulation layer is too slow.
2) I don't care about Windows. Doing the port is a big job. I started to
did it on Windows XP + Cygwin years ago. It worked, but there was the
fork() system call emulation that was slow.
3) There is X11 code in gb.gtk, gb.qt4 and gb.desktop.
4) For gb.gtk: as GTK+ 2 is deprecated, gb.gtk should be ported to GTK+
3. This implies removing all the X11 specific code.
5) For gb.qt4: the X11 specific code is there to workaround some
problems, but should not exist theoritically.
6) For gb.desktop: the desktop routines relies on the X11 window manager
protocols and freedesktop.org standards. A lot of things cannot be
ported, but some things can.
7) Many components are interfaces to libraries that do not necessarily
exist on other systems. It could be a problem.
I think there is not a lot of thing to do to port the interpreter, the
compiler and the other tools, as I already did that on Windows.
As for the X11 stuff, of course you're right. It must be encapsulated
somewhere so that it can be easily replaced. I already planned to do
that, but never had the time.
At the moment, I'm busy with fixing Gambas packager as soon as possible,
so that a Gambas 3.5.1 could be released.
--
Benoît Minisini