Small problem with SciTE

[Arnold]

Hi Charles,

most of the time I use PsPad for editing my files, because I can tile windows, can use highlighting and because I can start my files with o2 too. So I did not bother much about this little problem with SciTE:

For instance I load e.g. examples\wingui\childwin.o2bas, then open examples\math\Align.o2bas, then \examples\math\inProgress\Average.o2bas. After this "Go" or pressing F5 will only work with the last file. Changing the tabs and pressing F5 will give this message: Error 3: file empty or not found ...

I tried to change in \ide\Oxygen.properties line 79 and line 86 to:

command.go.subsystem.*.bas

(without =2)
and then all worked as expected. I have no idea why this is the case, or if this only works on my system.

In SciTEGlobal.properties I also changed line 91 to:

   command.scite.help="file://$(SciteDefaultHome)\ide\SciTEDoc.html"

(inserting ide\)
to get access to the SciTE help file.

Is there a way to show the full path of the .o2bas file in the windows title of SciTE? This is not a big problem though as I can see a tooltip when I move with the mouse over the tab.

Roland

[Arnold]

This is curious. When I started my system again and used SciTE then running the files had no effect. So I modified my lines 79 and 81 back. I do not know what happened. I thought I had a solution.

[Charles Pegge]

Hi Roland,

I noticed that it won't execute a program (F5) while the help file is open (F1).

You could try subsystem ... =1 instead of =2

I had no problems switching between tabs with different filepaths, and executing code (F5) with this setting.

[Arnold]

Hi Charles,

unfortunately setting =1 does not work in every case neither, e.g. in projectA\Leanlisp the files will not show the console. Some demos show the results in the output window.
If I understand the helpfile of SciTe correctly, =2 means using ShellExecute. I do not know anything about property files, but somehow there should be a parameter for the directory which can basically be used with ShellExecute.

Roland

[Arnold]

At least I found that I could insert in SciTEGlobal.properties after line 38:

title.full.path=1

to see the full pathname in the Windows Titel.
In a dos window I would enter this to run a .o2bas file:

cd c:\oxygenbasic\examples\basics
c:\oxygenbasic\gxo2.exe arrays.o2bas

In the help file of SciTE the command cwd: is mentioned, but I cannot find out if this can be used somehow.

[Arnold]

Hi Charles,

I searched in Internet for some SciTE properies files and came to the conclusion that there is actually nothing wrong with Oxygen.properties. It seems that some properties files are used with some helper files. Some properties files use $(FileDir) so I tried as a last option after line 69:

# RUN FROM SOURCE
# basgo="$(SciteDefaultHome)\gxo2" " $(FileNameExt)"
basgo="$(SciteDefaultHome)\gxo2" "$(FileDir)\$(FileNameExt)"

I did nothing change for compile and build. This does work to a certain extent. Sometimes I must still use "Build" or "Compile" for a tab, then "Go" will work again.

Roland

[Charles Pegge]

Hi Roland,

I am updating The Scite property files with the changes you have tested. Are you going for subsystem 1 or subsystem 2 ?

But I think it's time to leave Scite out of /Oxygen, (It can go on the WebSite as a separate download) and focus on Oxide, which supports compilation in all modes, drag-and-drop editing and execution. It need syntax highlighting and multi-doc support, and for me to stop using Notepad as my main editor

[JRS]

Charles,

You should really give UltraEdit a try before investing in yet another IDE. You can compile directly from UE. You can try it for free for 30 days to see how you like it. I have been using it since Ian (author) released his first version.

John

[Aurel]

But I think it's time to leave Scite out of /Oxygen, (It can go on the WebSite as a separate download) and focus on Oxide, which supports compilation in all modes, drag-and-drop editing and execution. It need syntax highlighting and multi-doc support, and for me to stop using Notepad as my main editor

well
is there a still interest i can continue to work on ASciEdit which is completely written in Oxygen?
OxIDE is not bad at all 

[Charles Pegge]

Hi John,

Oxide is Oxygen-native, though rather spartan in its current form. It is very simple to add tools and provide tighter integration with the compiler. And it will always be open source - in fact small enough to run directly from script, without using a binary.

Scite was never intended to be a permanent fixture

[Charles Pegge]

Hi Aurel,

You are very welcome to continue developing AsciiEdit, if you like. I have learned a lot already from studying your code, since my knowledge of both Windows-API and Scintilla is very limited.

[Arnold]

Hi Charles,

I use subsystem 2, because subsystem 1 does not keep the console window e.g. in \LeanLips\*.o2bas files. The change which I did for "Go" does not always work, but the message is not because of a missing file, but because of the include statement. The message goes away after doing a "Build".

Offering SciTE as a separate download would be an interesting option. This way everybody can decide which editor he would like to use. I myself use PsPad and could provide instructions how I added highlighting and the macros for running the files. John could do this for UltraEdit, and maybe this can be done with NotePad++, TextPad or FBEdit too.

And the best idea of course is to proceed with OxIde, which already runs fine. This would be much learning fun.

Roland

[Aurel]

You are very welcome to continue developing AsciiEdit, if you like. I have learned a lot already from studying your code, since my knowledge of both Windows-API and Scintilla is very limited.

Hi Charles...
ok there is no problem at all..
ASciEdit is a very primitive and simple editor, but have tabs and SDI interface
and is really very easy to use with Toolbar buttons( maybe i can add Menu-s).
it is written in Oxygen Basic.
Also i always prefer to use editor which is specific for given compiler /interpreter
 

[Arnold]

Hi Charles,

experimenting with the properties files I maybe found a solution finally. Sometimes I had to delete properties.lnk files in AppData and subfolders as they were interfering sometimes.

My problem was that with several tabs when changing to another tab, I can see the correct directory, but opening a file shows a different folder. I examined the original SciteGlobal.properties and copied part of the Checking section to OxygenBasic's SciteGlobal.properties. In Oxygen.properties I used the subsystem=2 again and for basgo I used $(FilePath). Until now everything works as expected.

As your last build does not include SciTE, I copied a previous ide folder to OxygenBasic and renamed the subfolder to SciTE, copied SciTE.exe, SciLexer.dll and SciteGlobal.properties into it and adapted the properties files. In case you intend to provide the ide subfolder with SciTE as a separate download maybe you will check the attached files.

I also tried to copy the latest SciTE.exe and SciLexer into the ide(SciTE) folder and this worked too. Deleting these two files and using instead the latest sc353.exe, which is a standalone application did also work.

As hh.exe is only a single instance application, I do not yet know how to prevent opening the help file several times. But somehow it must be possible.

SciTE has some advantages and it is free. The problem seems to be mastering the properties files.

Roland

.

[Charles Pegge]

Thanks Roland,

I have now uncoupled SciTE from OxygenBasic, but ir can be dowloaded separately from the website downloads page.

Should I overwrite the property files with yours?

Oxide has advanced quite a lot this week. It has Scintilla syntax highlighting, and is best used with drag-and-drop. The left panel is for proj files, which is mainly for file-switching. First drag new.proj onto this panel. Then you will be able to drag any file onto the panel and its name will be added to the file list. double-click on files  to load them into the right panel for editing.


.