Before you decide to do this installation, at least read the documentaton written below. This is NOT a download or clone, and then compile and run. You will need to have some understanding of the compile directory structure, make some modifications to your RED file, and when you compile, you will need to resolve any issues that just might happen with the other installed software you have.
What this series of steps will get you once completed, is an evironment that will allow you to compile, modify and run some of the DEVUNA tools. And you will have spent considerable less time in doing this, than taking all the original DEVUNA GitHub repositories, and figuring out the process from scratch.
There have been a few individuals that have downloaded this repository and got it running. Their testing has been very helpful. Some of the documentation has been enhanced because of these efforts. And through the generosity of these individuals, I have received additional RED files that you can inspect as examples of environment setups.
Any enhancements or changes to any part of the original source code, that you decide to make public for use by others, should be submited back to Mr. Randy Rogers at the GitHub https://github.com/Devuna website, by whichever mechanism or procedure that he has defined.
After reading the documentation, send e-mail questions to this address.
roberto.artigas.dev@gmail.com
DEVUNA directory arranged as a Clarion IDE set of directories. What has been done, is a compile of the existing sources using the RED file provided that points to the LibSrc and Template directories for these specific applications. Everything is issolated in it's own directories so you do not have to add all the DEVUNA classes and templates into your common Clarion directories.
IMPORTANT IMPORTANT IMPORTANT -->
These separate directories get merged into your IDE environment. This means these directories will have to be in any other RED files that you use in other projects. When you bring up another project that uses a different RED and you find these templates missing,
you will need to add the directory entries of your DEVUNA project to this specific RED file.
If you rather not have this type of split directory environment, just put all the correct directories into your standard Clarion enviroment locations (as Mr. Mark Riffey did), set up your compile project directory as you normally would, and go make the changes you want.
<-- IMPORTANT IMPORTANT IMPORTANT
This is my personal directory with changes to the original applications for the executable versions that are used in my Clarion development. These are NOT the original sources.
The KSS application directory is Mr. Mark Riffey's sources with all his changes. The Class Viewer application directory is currently the sources from the DEVUNA directory with some version enhancements and code refactoring. If you want to see what has been done, then download the sources and look at them. Compare them to the original. See if you want to use this specific version.
If you need the original sources to start with, download the current directory structure, get it to compile. Then get the original sources from the DEVUNA directories, put it in the correct place for your specific compile directory structure, and then do your compiles.
This will get you started compiling some of the sources with a minimal amount of effort. A lot less effort that it took for Mr. Mark Riffey or I, to get our versions running from the original sources.
You will need the Capesoft StringTheory, WinEvent and xFiles templates, since they are part of the KSS search utility.
I personally own the icetips, capesoft, superstuff, and other vendor templates.
So this was not a missing set of items for myself and the additional individuals that tested.
The positble requirements reported missing are now documented. The specifics templates are not, but if you do not have them,
they can can be removed by the IDE and you will have to deal with the funtionality that might be missing.
The ABCVIEW class viewer untility should not have any additional vendor requirements.
Your mileage may vary depending on other vendor's templates you use.
My disk drive compiler directory path: C:\_GIT_\Devuna\__IDE__\*
That above location is the compile directory path that is being used to compile the applications on my disk drive. All the references showing in the documentation will be based on that compiler directory structure.
Your disk drive compiler directory path: Drive:\RootFolder\DEVUNA__IDE__\*
When you press the Code button and unzip the structure, or you clone into your directory your directory will match your structure above
and you will have to change some of your references to the directory structures to match your specific directory location choice.
Above you are viewing the directory structure of the GitHub directory on my development machine.
Once you move into the application directory you will see the different applications that are currently available.
In each application directory there is a local RED file that will be picked up by the IDE when you open the application.
This is the specific KSS aplication directory.
In each application there is a Setup Builder directory and this will contain the SetupBuilder script that allows creation of a
install script using the RunTime directory for the currently compiled version.
This is for the specific ClassViewer aplication directory.
In each application there is a Help and Manual directory and this will contain the source files that allows creation of the
help files necessary for the RunTime directory for the currently compiled version.
This is for the specific ClassViewer aplication directory.
Using the KSS application as an example I opened the RED file from the IDE and you can see that all there is an include the specfic RED file
that is being used.
Please recall that you will need to change the C:\_GIT_\Devuna\__IDE__\BIN\*.RED file entry to that you are using to the Drive:\RootFolder\DEVUNA__IDE__\BIN\*.RED that matches your directory structure.
The RED entries that are used by the IDE that apply to the Devuna locations for my directory setup are shown above.
They point to were the class sources and templates are located so when the IDE opens it can find classes and templates.
Please recall that you still have to register the templates from the specific directory location.
If you want to use your personal RED file, the entries will have to be copied from this RED file to your RED file, and your RED file directory locations changed for your Clarion IDE setup to where you have located your Devuna directories.
There may be a couple of additional entries need in your RED file to pick up the images that are for each application that are location in each specific image directory for that application.
Please recall that you will need to change the C:\_GIT_\Devuna\__IDE__\* REDirection entries to that you are using to the Drive:\RootFolder\DEVUNA__IDE__\* format that matches your directory structure.
Do not forget to register these templates at the directory location that you have put them in. If your RED file is set up correctly they will be picked up when you re-start the IDE or load a new application for modification.
If you do not have them installed in your LibSrc already, you might need to add Mark Goldberg's debuger class
and additional source files in your LibSrc directory. They are debuger.inc, debuger.clw, TUFO.int, and FileAccessModes.EQU.
They are included in the LibSrc directory with underscores in case you do not have them.
A simple removal of the underscores will get you those files. You can also get the files from the GiHub repository at
https://github.com/MarkGoldberg/ClarionCommunity/tree/master/CW/Shared/Src where those files are located.
The debuger class is used in the csciviewer.inc, and csciviewer.clw. That class is used in the Class Viewer utility, and the relevant debuger code items
in those two class files have been commented out.
This contains the RunTime environment directories for each utility with all the necessary files to
be able to run the utility. After compiling the utility and getting a clean compile, move the EXE to the appropriate utility
RunTime directory and you should be able to test.
The projects have been changed to compile directly to the Runtime directories. Once compiled, you can run the EXE from that location.
It is probably useful to setup the applications as pinned to the taskbar when you run them the first time.
This is the run time environment for the Class Viewer utility.
This is the run time environment for the Source Search utility.
If your get the Unknown identifier error messages above when you compile, uncomment the two lines with the identifier definitions
and you should be good to recompile. Some installations have those items already defined and you will get duplicate definitions.
If you have this error, delete kss.res from the Libraries, Objects and Resource Files list.
Be aware, if you setup from this repository you will not need kss.res. I am not aware, if it is needed, or not needed in the original sources compile.
ClarionLive : 644 : Jan 21, 2022 : https://www.youtube.com/watch?v=ZZDxJDUnoRc
Clarioneros : 212 : 2022-01-29 : https://clarionlive.com/clarioneros.htm (OneDrive link)
I didn’t like all this mystery business long before I ever did anything about it, and when I did do something about it, I found that I was right, that all mystery is in the eye of the beholder and that we are free to stop seeing mystery whenever we decide to open our eyes and actually look. This is no small point. We have to look hard at this mystery business in order to get past it.
-Jed McKenna’s Theory of Everything: The Enlightened Perspective