I know we are tired, the time has passed and we had no solution for VB6 to date.
I also know that there are some projects going on, like TwinBasic, I wish the best luck and great success, and I hope they will have something working as soon as possible.
But we can't just sit back and wait any longer for something to happen.
If we keep waiting, doing nothing, the things will become only worse over time.
My suggestion/proposition is:
To split the large problem into smaller pieces.
No one needs to develop a full VB6 replacement, but can contribute with some part.
But... for that, we need to know what are these pieces. And then how can anybody contribute with a part of a piece.
If someone thinks he has to do everything, it will be until 2050 to be able to show something.
I don't think I am the one to lead this project, because if I was, I would not be askling this question, but giving the answer: describing what are the pieces already isolated and specifying clearly how they must interact with each other.
But it is a proposition for the ones that has knowledge on this field.
Myself I don't have a C or ASM background.
OK, I could learn, but that would take too long. It is not practical (and we are too late already).
These pieces, I think, they would be the IDE, compiler, runtime, etc.
More and smaller pieces there are, the better.
I could contribute with some parts I think, if there was a project like this.
Maybe the Printer object, some functions.
We already have Krool's controls. The PictureBox is not covered but it could be done, I have the SStab too.
Let's start doing something. Something that can be scaled/perfected.
It does not need to be fully optimized in the first version. I mean, if some function, lets say [tt]Split[tt], is not as fast as the VB6 one, no problem. It can be optimized later.
I suggest the first goal not to try to make something better than the original VB6, the first goal is to replace the original VB6 as it is.
But with the source code, where we can build over it and develop further.
Not to be compilable on Linux, 64 bits, etc.
64 bits support will be of cource one of the first steps further, but first the first.
Do not expect too much for the first version, just to replace what we have now (and only then start dreaming).
I do not expect someone to post a full specification tomorrow, but perhaps some day.
If at a point only some part is done, OK, we will have a new IDE, or a new compiler. Not the whole project but at least some part was already replaced.
Please let me know what do you think (specially the ones capables of doing this separation and specification).
But also the question: is this possible? Does this proposition make sense?
PS: this should have happened like 10 years ago at least, but OK, it didn't happen, and we are here and still need it.
This should not be something about egos, we all know who the geniuses are, don't need to prove it any more. What we do need is a new VB (at least the same, but with future).
I also know that there are some projects going on, like TwinBasic, I wish the best luck and great success, and I hope they will have something working as soon as possible.
But we can't just sit back and wait any longer for something to happen.
If we keep waiting, doing nothing, the things will become only worse over time.
My suggestion/proposition is:
To split the large problem into smaller pieces.
No one needs to develop a full VB6 replacement, but can contribute with some part.
But... for that, we need to know what are these pieces. And then how can anybody contribute with a part of a piece.
If someone thinks he has to do everything, it will be until 2050 to be able to show something.
I don't think I am the one to lead this project, because if I was, I would not be askling this question, but giving the answer: describing what are the pieces already isolated and specifying clearly how they must interact with each other.
But it is a proposition for the ones that has knowledge on this field.
Myself I don't have a C or ASM background.
OK, I could learn, but that would take too long. It is not practical (and we are too late already).
These pieces, I think, they would be the IDE, compiler, runtime, etc.
More and smaller pieces there are, the better.
I could contribute with some parts I think, if there was a project like this.
Maybe the Printer object, some functions.
We already have Krool's controls. The PictureBox is not covered but it could be done, I have the SStab too.
Let's start doing something. Something that can be scaled/perfected.
It does not need to be fully optimized in the first version. I mean, if some function, lets say [tt]Split[tt], is not as fast as the VB6 one, no problem. It can be optimized later.
I suggest the first goal not to try to make something better than the original VB6, the first goal is to replace the original VB6 as it is.
But with the source code, where we can build over it and develop further.
Not to be compilable on Linux, 64 bits, etc.
64 bits support will be of cource one of the first steps further, but first the first.
Do not expect too much for the first version, just to replace what we have now (and only then start dreaming).
I do not expect someone to post a full specification tomorrow, but perhaps some day.
If at a point only some part is done, OK, we will have a new IDE, or a new compiler. Not the whole project but at least some part was already replaced.
Please let me know what do you think (specially the ones capables of doing this separation and specification).
But also the question: is this possible? Does this proposition make sense?
PS: this should have happened like 10 years ago at least, but OK, it didn't happen, and we are here and still need it.
This should not be something about egos, we all know who the geniuses are, don't need to prove it any more. What we do need is a new VB (at least the same, but with future).