Dear visitor, welcome to Jabaco - Community. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Date of registration: Jul 16th 2008
Location: Erlangen, Germany
Occupation: Software Developer
Hobbies: Jabaco, game theory, text-mining
Friday, October 16th 2009, 9:40pm
We've discussed this topic enough for the moment. You know my position.
Quoted
Do it like Game Editor and IntelliJ - make Jabaco OpenSource:
Very misleading. You can write platform independent software with Jabaco. Let's define your statement more detailed and neutral. If you would like to write normal software with VB6 you need: the IDE, the Compiler and the VB6-Runtimes. If you would like to write software with Java you need: the IDE, the Compiler and the Java-Runtimes. If you would like to write software with Jabaco you need: the IDE, the Compiler and the Java-Runtimes. If you would like to run VB6 applications you need the VB6 Runtimes (Windows only). If you would like to run Java or Jabaco Software you need the Java Runtimes (platform independent).
The current Jabaco is "only" a half step. Make a full step!
To use Visual Basic 6, you need only Windows. No JVM or other thing are needed.
To use Java you need ony a any hardware and OperatingSystem, on which runs the JDK.
But Jabaco is between two chairs: You need Windows (or in the future WINE) and the JVM.
This have a lot of disadvantages.
It's VB6, C++ and Java. I'll switch to Jabaco, C++ and Java in future.
There is anytime the question, why Jabaco is written in Visual Basic and not in Java.
Ok. Let's see what you mean:
So, all reasons for a Jabaco written in VB6 are reasons against Jabaco itself.
There are several good Java Frameworks. It's not a reason against Java/Jabaco.
- The Jabaco IDE is better integrated in Windows
The only reason why it runs fast enough is C++. Java, Jabaco and C++ are much much faster than VB6.
- The Compiler is in native-code and runs so faster
Jabaco too.
- It is easier to develop
There are several reasons why you should use Jabaco instead. And there are much more in future (mobile development, enterprise applications, web applications).
[...] also reasons to use Visual Basic 6 or Visusal Basic .net instead of Jabaco [...]
I'll translate several parts to C++ and Jabaco.
But with this, we are already at the beginning: Why then using VB6 for Jabaco?
I'll improve the Design-Editor and rewrite in C++ with Jabaco/JNI-connection. I've completed several tests successfully. Version 1.6 will handle the Java LAF in the Designer
Other disadvantages of a Jabaco in VB6 are:
- The programs in the designer are looking with its Look And Feel different, then at the result
It's already in my planning.
- Java-IDEs using for example Java-Beans:
Very similar to the Jabaco philosophy. The Jabaco Framework is Open Source. It's not possible to compare the QT Framework with the Jabaco Compiler / the Jabaco IDE. QT is a C++ framework used by C++ developers. The Jabaco framework is a Java/BASIC framework used by Java/BASIC developers. How many QT developers are able to improve the C++ compiler? Anytime when I use QT it was never necessary to modify the C++ compiler. The Jabaco framework is Open Source with a very free license. You can extend and modify anything.
Matthias Ettrich says:
We - the developer of Qt - having Qt always used ourself and the reached experience, integrated in the product. I think, that the half of the improvements and extensions of Qt, have found its beginnings in our team
Btw. You've started this topic several times ago in several threads. Would be great if you can focus this topic in one thread in future.
Friday, October 16th 2009, 10:07pm
The only reason why it runs fast enough is C++.
- The Compiler is in native-code and runs so faster
The Compiler is written in C++? I thoughted, that nearly all of the IDE and Compiler are VB6.
There are several reasons why you should use Jabaco instead. And there are much more in future (mobile development, enterprise applications, web applications).
Yes, for the JVM written programs can also be started per Webstart. With this, there comes lots of more possibilities.
I'll translate several parts to C++ and Jabaco.
Sounds nice. :-)
I'll improve the Design-Editor and rewrite in C++ with Jabaco/JNI-connection. I've completed several tests successfully. Version 1.6 will handle the Java LAF in the Designer
Hmmm... lets see at Version 1.6.
It's already in my planning.
- Java-IDEs using for example Java-Beans:
Sure, if you port the IDE to the JavaVM, then its no problem.
Greatings
theuserbl
Date of registration: Jul 16th 2008
Location: Erlangen, Germany
Occupation: Software Developer
Hobbies: Jabaco, game theory, text-mining
Friday, October 16th 2009, 11:14pm
Many parts are written in VB6 and I tried to use VB6 only. But it's not possible to reach acceptable performance without C++.
The Compiler is written in C++? I thoughted, that nearly all of the IDE and Compiler are VB6.
The only reason why it runs fast enough is C++.
- The Compiler is in native-code and runs so faster
This process will take some time.
Sure, if you port the IDE to the JavaVM, then its no problem.
