The next friendly fireside chat for people interested in RISC OS software development will take place at 7:30pm on Saturday, 9th August. Taking place online via the Zoom video conferencing service, these meetings are intended as an informal way of allowing RISC OS programmers, and anyone interested in the subject, to get together online to discuss relevant matters.
With no specific topic planned, discussions are steered by what people bring up, so that could be their current works-in-progress, development of RISC OS itself, the tools available, and so on – and very often, that will include people seeking advice from others present. For example, at the last meeting discussion topics included a discussion of the 64-bit problem and how the RISC OS on Linux port works, the problems emulating a RISC OS system on modern Apple computers and whether RPCEmu could be compiled to run on it (sadly unresolved), and (much later) an interesting ‘feature’ was pondered upon when generating random numbers in BASIC in a program run from within StrongED.
The group also saw and explored a newly created Discord discussion forum – The RISC OS Coding Community, intended as a way for participants of these fireside chats to continue discussions after the meetings have ended.
The meetings are open to anyone, regardless of their programming prowess – you could be someone with no programming experience looking for advice on where to begin and what tools to use, an expert with many years of development behind you, or anything between the two extremes; all are welcome.
To join the meeting, you will need a platform on which Zoom can be run, along with the meeting credentials. If you’ve joined a previous fireside chat, those credentials remain unchanged, but if not you can get them via one of these routes:
- You can contact Andrew McCarthy on Twitter or Mastodon – or indeed from your RISC OS computer using ChatCube.
- Or you can send an email to me here in the RISCOSitory bunker. Please note, though, that any emails sent to me on the day of the meeting itself will not receive a reply until very close to the meeting’s start time!