As more I look at Jabaco, as more it looks like a Patchwork.
So this is not a bug-report. But a suggestion for improvement.
If you choose in the "Properties" field on the right side of the IDE a SuperClass, the path-seperator is like in Java-classes itself the slash ("/"). For example in Modules and Classes it is as default "java/lang/Object".
If you want to use a class with its path in the editor, then the Path-seperator is the hash ("#"). (For example: Dim f as javax#swing#JFrame)
And in the generated SourceFiles, when you save your programs? They have again the slash as path-seperator.
Ok, have a look at a *.jba file:
|
Source code
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
<?xml version="1.0" encoding="UTF-8"?>
<Project>
<Param Name="(Name)" Value="Project"/>
<Param Name="Author" Value=""/>
<Param Name="Copyright" Value="(C) 2010"/>
<Param Name="Description" Value=""/>
<Param Name="Company" Value=""/>
<Param Name="Comment" Value=""/>
<Param Name="JRE (minimum)" Value="1.4"/>
<Param Name="Version" Value="01.00.000"/>
[...]
<Implements Name="com/eaio/nativecall/Holder"/>
<Implements Name="com/eaio/nativecall/IntCall"/>
<Implements Name="com/eaio/nativecall/NativeCall"/>
<Implements Name="com/eaio/nativecall/Verifier"/>
<Implements Name="com/eaio/nativecall/Verifiers"/>
<Implements Name="com/eaio/nativecall/VoidCall"/>
<Implements Name="com/eaio/nativecall/Win32Verifier"/>
<Implements Name="com/eaio/util/lang/NativeLoader"/>
<Implements Name="net/java/plaf/ClientProperties"/>
<Implements Name="net/java/plaf/Environment"/>
[...]
|
You see slash as file-seperator. And the clases are integrated with ....
implements!
If you write code in an editor, then "implements" means in Java and Jabaco, to use an interface. In the class, which uses the interface, you have to implement all mentioned functions of the interface.
But that is not what the "Implements" in the XML-Code of the *.jba files mean. They mean the equivalent of
import in Java and Jabaco editor files!