Using Windows/Linux IDE for RISC OS source code

I would like to get an overview of parts of the RISC OS source code and I would like to use IDE features for it so that I can quickly jump to definitions and use some more advanced features which StrongED/Zap are lacking. Also it would allow me to use Git until it is available for RISC OS. So I would prefer to use Visual Studio (Code) on Windows (maybe Linux – but would need to set it up first also I am more used to Windows). My two main questions are:

I don’t need to build it on Windows. So I guess the work flow would be like:

I someone is working this way I would be interested in some best practice advice and information on your setup.

Hey Michael,
I use Visual Code studio on both Windows and Linux (and ARMLinux).

VSCode has a lot of plugins which includes ARM Assembly, BBC BASIC and ANSI C. Unfortunately none of the ones I use support !ObJAsm syntax, so there you may find some initial difficulties.

For what concern the workflow:

• If you use it on Windows be careful when you edit sources, Windows will add \r\n while both Linux and RISC OS uses just \n at the end of the line. However:
  • you can still use !ToANSI to convert Windows C sources or specify -pcc in ROOL DDE
  • you can specify the source it’s a Linux file for example
  • if you want to use-and-forget approach then I think choosing Linux as a platform may have benefits on both file editing and git (I personally find git better on Linux, just personal tastes, nothing more).
• You can use SAMBA to share your sources with RISC OS and you can compile straight on the SMB share from RISC OS, works fine and with RISC OS 5.28 it seems even more stable.
  • For easiest approach remember to enable SMBv1 on your Samba Server or enable SMBv1 on your Windows 10 if you use Windows 10
• About Git there are some really cool plugins for VSCode which also allow you to see then each line of RIS COS Sources were committed etc…
  • Git History is nice
  • Git History Diff
  • GitHub Pull Requests is also useful if you have a github.com account

Alternative approach:

• If you really prefer Windows, then you can use VSCode on Windows, set a linux box on an Rpi or a VM, use remote coding from your VSCode to the Linux System , I use this technique with GCCSDK which works better on old Ubuntu and run VSCode on my own Linux distro which is super fast and responsive, then share the built stuff on GCCSDK ubuntu 14 with RISC OS via SAMBA.

No promises, but if there are enough people interested, we could work out a VSCode Studio plugin for ObjAsm and Norcroft C, I just didn’t bother only for myself

Thanks Paolo for your hints, I will setup a Linux-VM and try it out!

There was a thread recently created that provided links to download RISC OS syntax for several different Window/Linux editors → https://www.riscosopen.org/forum/forums/1/topics/15487

Thinking about it, it’s probably a good idea to add these to an existing developers wiki page so new coders know that there is a way to (hopefully) use their existing IDE editors with RISC OS syntax. <Action – leave this to me – I’ll do this tomorrow>

Question to others – how easy/how much effort is it to create VSCode plugins to handle different syntax? Anything that helps coders manage RISC OS code easily is worthwhile in my opiniion. Let’s face it, most developers are used to IDE’s, and the likes of Zap and StrongEd (no matter how good they are) are probably going to be a huge shock to any new developers coming from other OS’s.

Question to others – how easy/how much effort is it to create VSCode plugins to handle different syntax?

It’s easier than it would be in Zap. ;)

As I think I mentioned at the time of the other thread, I’ve got a BBC BASIC (text) mode which mostly works — it gets colouring correct, but doesn’t quite get the selection of variables right (it misses the % and $ off the ends when double-clicking to select). There’s no assembler support yet, though.

I’m a step closer to being able to release it, as I now have a GitHub account — which I think is how its done — and could probably get around to making it available sometime.

( Question to others – how easy/how much effort is it to create VSCode plugins to handle different syntax?
( It’s easier than it would be in Zap. ) )

Yup, VSCode is becoming super-popular for this reason.

I’m a step closer to being able to release it, as I now have a GitHub account — which I think is how its done — and could probably get around to making it available sometime.

Cool Steve, I am happy to help testing, I was about to start a plugin for ObjAsm syntax and obviously file handling, but never really started it (just being lazy on this).

Just a quick update, I’ve created a simple wiki page for potential new developers who would like to the source editors they are already experienced with. Just copied and pasted the information from the forum link I posted a few comments above, and sprinkled some Textile magic on it.

Available here → RISC OS Development on other platforms

Good idea Alan! :)