Quote: "Does anyone have it? The link no longer exists "
Was that editor ever finished?
Quote: "I found a generic editor that could be used for DBC"
What editor is that? I ask because depending on the editor, there could be different steps you may need to take. In general, to run DBC directly from an editor, the editor would have to have a function or menu item that can access the command line or the shell; either automatically or manually.
Also, if you wanted syntax highlighting, the editor would need to have some kind of language editor or manager.
If the editor has a shell function, you can usually assign a key combination or a function key to execute a specific commandline instruction. In the case of DBC, you would need to execute any of the following commands:
1. Compiling Externally
DB.EXE -c test.dba
2. Running Externally
DB.EXE -x test.dba
3. Building An Executable Externally (no media)
DB.EXE -b "small.exe" test.dba
4. Building An Executable Externally (with media)
DB.EXE -f "large.exe" test.dba
5. Using Relative and Absolute Paths
C:\Program Files\Dark Basic Software\Dark Basic\DB.EXE -f "d:\mywork\large.exe" test.dba
Substitute the names and paths for your files.
Quote: "How did DarkEdit do this?"
There's another layer to consider. Usually when an editor executes a shell command on a file you are working on, the editor needs to save the file first. This is good and bad. If you want to test changes on the fly, you may not want those changes saved in your true source. DarkEDIT creates a temp file to which it saves your current changes and the then shell executes db.exe and identifies the temp file. This allows you to test whatever you want without those changes being committed to your actual source. When you are satisified with your changes, you can then save youe source.
I've messed around with several different editors and very few have a simple means of saving a temp file and not the true source and then running commandline instructions (compiling) on that temp file. Most will save the current file and then run the shell on that. But it's not necessary to create the tempfile to get your code compiled and ran.
However, I prefer compiling a temp file so my original source isn't changed and saved until I want it to be so.
Do you not have DarkEDIT?
Quote: "Is there a command line variable or something to make the DBC.exe run the code instead "
You can also execute the command line instructions outside of the editor using the command console. That means you could basically use any text editor you want to write your code, then compile it at the DOS prompt.
Enjoy your day.