Search results
Search results 121-140 of 500.
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.
The Microsoft data model in VB6 is more convenient here. A "Node" has a "Text", a "Key" and a "Tag" property. Ample opportunities to store DB keys. The same level of flexibility can be achieved in Jabaco by extending the Jabaco Framework. "Somebody" has to rework the classes "Nodes" and "Node". Volunteers wanted! Greetings A1880
The "key" is just used to be able to access the node items by key searching the Nodes collection. If you would like to retrieve the key for a given node, you'd have to remember the node/key pairs in a separate collection. To my knowlegde, it is generally the case that collection keys are just used for access. You can't retrieve the key from a collection item unless you have explicitely stored it somewhere beforehand. Does this makes sense to you? Greetings A1880
Die Klasse DataBase enthält in ihrer Initialisierung: Jabaco Source 1 2 3 Public Sub Class_Initialize Call Class.forName("sun.jdbc.odbc.JdbcOdbcDriver") End Sub Damit wird der ODBC-Treiber als Standard vereinbart. Auf Nicht-PCs gibt es keinen ODBC-Treiber in der rt.jar. Daher die ClassNotFoundException. Dies kann man an der Zeile "at VB.DataBase.Class_Initialize(DataBase.jsrc)" im Stack Trace erkennen. Um diesen Umstand zu umgehen, könntest Du entweder auf "DataBase" verzichten (siehe mein Beisp...
Wenn H2 die Tabelle "TEST" nicht findet, wird sie in der gerade verbundenen Datenbank nicht enthalten sein. Du kannst ja in der interaktiven H2-Oberfläche nachschauen, ob und wo dein CREATE geklappt hat. Im Ausgangsbeispiel heißt ja nur die Datenbank "TEST", nicht die Tabelle in der Datenbank. Die genaue Wirkung der Häkchen in der Projektverwaltung habe ich noch nicht nachvollzogen. Sieh mal mit einem Texteditor in der *.jba Projektdatei nach.Das geht am besten, wenn du die Datei in xxx.xml umbe...
Jabaco findet den H2-Treiber, indem man die *.jar-Datei im Projekt angibt: Taste "F1"; "Add Jar-Archive" Standardmäßig sind nur Jabaco.jar und rt.jar im Zugriff. Die "#Import"-Statements bewirken, dass Jabaco Klassennamen findet, ohne dass man den kompletten Pfad angibt. Ich kann dann also "Statement" statt "java#sql#Statement" schreiben. Die Falle besteht darin, dass manche Klassennamen in mehreren Paketen auftauchen. Ein Beispiel ist die Klasse "Statement". Jabaco findet java#beans#Statement s...
Das folgende Beispiel klappt bei mir: Jabaco Source 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 Option Explicit #Import java.sql.* Public Sub Command1_Click() Dim conn As Connection Dim qry As String Dim st As java#sql#Statement Dim Meta As DatabaseMetaData Dim rs As ResultSet Dim tableNames As String Dim s As String Dim arr() As String java#lang#Class.forName("org.h2.Driver") conn = DriverManager.getConnection(...
Jabaco *.jar files are just Java executables which run inside a Java Virtual Machine. This should not influence your Macbook as nothing is "installed". Obviously, one can write damaging or disturbing Java code. But if your tool is clean and not actually running, there should be no problem. A complete re-install is quite frequently proposed by service people who have not enough time or knowlegde to find the reason of failure. It is rather simple for them to do. The re-install requires only a few ...
Please search this forum for "serial" to find out how to deal with COMx: ports. I haven't seen a video sample for Jabaco yet. But it should be feasible. You might want to look at the sound samples first. Again, the search facility of this forum is your friend Greetings A1880
Just search this forum for "ZOrder" to get an answer. Greetings A1880
The following demo sample shows how to use freetts as speech output: Jabaco Source 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 Option Explicit ' ' Demo inspired by: ' http://www.developers-guide.net/c/115-einstieg-in-das-java-speech-api.html ' ' This project requires freetts.jar to be part of the classpath: ' http://sourceforge.net/projects/freetts/files/FreeTTS/FreeTTS%201.2.2/freetts-1.2.2-bin.zip/download ' Import com.sun.s...
This article might contain useful hints. Please post your solution here! A1880
Thanks for the hints and the new Jabaco.jar You are obviously right: The Jabaco source objects are depending on the Java source objects. No surprise there. But the ordering of the classes in the list generated by the dependency analyzer does show internal dependencies within the packages. This could be a starting point to split the set of classes in two or three subsets without violating dependencies. Greetings A1880
I just have been playing around with Class Dependency Analyzer: VB depends on: Jabaco Source 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 VBA Constants VBA Conversion VBA ErrObject VBA ExceptionDialog VBA IResource VBA IVBArray VBA Information VBA Interaction VBA Interaction$1 VBA JabacoEventQueque VBA Math VBA MultiLineLabelUI VBA Strings VBA TabAction VBA TabAction$1 VBA TabAction$2 VBA VBAppWinStyle VBA VBArra...
First of all: Thank you for your brave efforts to provide a proper Jabaco.jar again. There are probably only two or three developers who are compiling Jabaco framework components. Unfortunately, I am none of these. My guess is, that a precompiled Jabaco.jar is needed for compilation due to problems of compilation order. The classes in the framework might not be compiled in an order where all forward references to other (still uncompiled) classes can already be resolved. To circumvent that, you m...
The following sample demonstrates how to check on an already active instance: Jabaco Source 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Option Explicit ' a tcp/ip server socket is used as ' limited resource to check on a running ' application instance Private sso As java#net#ServerSocket ' change to suitable port number as desired Const appSpecificPort = 12589 Public Function isAppAlreadyStarted() As Boolean On Error Goto ErrHandler sso = New ServerS...
There might be still a misunderstanding. I am talking of a small number of two, three or four *.jba projects. Each of them should be compiled independently. Afterward, the resulting *.class files are copied together in one central *.jar file. So, the resulting framework looks like today. In case of a change in a given class, only the respective *.jba has to be recompiled and the merge repeated. This should always be faster than a complete recompile of today. Greetings A1880
By compilation in parts I mean the following: One could try to split the Jabaco framework classes in two or more independent sets where no class in set A refers to a class in set B and vice versa. The next step would be to compile the resulting sub-projects (one project per set). Finally, the generated class files have to be merged into one Jabaco.jar framework library file using copy commands and the jar archiving tool. Whenever a change occurs, only the respective sub-project has to be recompi...
Yes, I've noticed that recent framework download files are too small to be complete. Would it make sense, as a workaround, to compile the framework in two or more parts and merge the resulting classes afterwards? Happy compiling! A1880
Thanks for this hint! I've written the following cmd file "build.cmd": Source code 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 @echo on :: we assume that the project name equals the directory name call :doit "%cd%" goto xit ::==================================================================== :doit set project=%~n1 echo %project% c:\Programme\Jabaco\Jabaco.exe -projectpath=%project%.jba -d=.\classes goto :EOF :xit Compiling a project with a deliberate fault, I get a log file "build.log" in my ...
In Jabaco you have to use the project classpath to define the referenceable Java libraries. Press key F1 in the IDE to view or edit the list of Jar files. To actually use a specific class, you can either use the "import" statement in you source or explicitely write out the path. Example: you could write "import java#io" to use "File", or you could write "java#io#File" The Jabaco IDE provides a set of predefined controls in the toolbar. Additionally to that, you can add your own class definitions...
