@Kamelito
Thanks Jamie,
I just downloaded it.
There's a bug I guess but it may be in the autodoc and not in your software.
Libraries>Xena>choose either AlloRsource or FeeResource the autodoc can't be find while it exist. (xenares.doc)
it's maybe due to the autodoc header which contain duplicated entries and is not well formatted for or one of those entry.
http://wiki.amigaos.net/amiga/autodocs/xenares.doc.txt
Kamelito
Hi Kamelito,
Thanks for trying the software, and pointing this one out.
The actual "problem" is that the AutoDoc itself was not
named to follow the interface definition.
So, while the SDK:Include/interfaces/xena.xml file gives a
library name of "xena", the actual AutoDoc found in
SDK: Documentation/AutoDocs/ is called "xenares.doc";
so the SDK Browser does not find it.
There are a couple of "non-standard" naming issues within
the SDK's Autodocs, and for those I have some exception
code it the SDK Browser to handle finding them. I will release
an update which knows to look for "xenares.doc", in addition
to "xena.doc" for this one.
The immediate work-around for this one of course, is to simply
copy (or rename) the AutoDoc itself, so that you have the expected
"SDK: Documentation/AutoDocs/xena.doc" file in your AutoDocs
path.
I did this by myself as a test, by first switching to the "AutoDocs"
list in the SDK Browser, clicking on the "xenares.doc" file to read
it, selected "File -> Open in New Shell...", which takes you right
to the SDK: Documentation/AutoDocs/ path, and typed
"copy xenares.doc to xena.doc". Then I went back to the
"Libraries" list in the SDK Browser, typed "x" to quick jump right
to "+ xena [IXena]" in the Libraries list, and it immediately loaded
the AutoDoc file to match it.
The fact that the AutoDocs files do/did not always match the "expected"
name of the file (as per the XML description), is exactly why I originally
added the direct listing of the AutoDocs files within the SDK Browser
in the first place. It is important to have those raw files directly available
to you, so that you can find odd ones like this, and find "AutoDoc"
files for things that do not have a corresponding XML interface file.
Is syntax highlighting in the browser something in your to do list?
Most definitely. This one will take more work since I will most likely
have to replace the use of the standard "texteditor.gadget" for
the main text display with something else I have more control of,
like my own custom BOOPSI gadget class.
Currently the plan is to make that happen by the v3 release.
Best Regards,
Jamie Krueger
BITbyBIT Software Group LLC