This is the version I will be moving all my development for work to, meaning I will be upgrading that environment to 3.19.6 (-> upgraded this to 3.18.4 in Dec. 2023). Originally I wasn't planning to move to a newer Gambas at work for a few more years. This earlier planned moved to 3.19.6 has got all to do with my development system always running the same version I use at work. And I want it be on par with the GambOS version, for developing the GambOS core applications. So, yes a migration to a higher Gambas version as work because of GambOS
BTW, the applications that will be in the guides will be developed on GambOS itself as gbuser. Stuff like Dashboard, Learning, Software Center will not be part of the guides and can be developed on my system.
Gambas 3.19.6 and all backports are working just fine, but there is a tiny little problem, reported back to me by Poly. The Gambas Farm doesn't work!! Since, I haven't used the Farm since it's introduction (I think in 3.8) days, I wasn't aware of the problem but did see it reported for Gambas 3.20-series and partly fixed (works for more recent Debian and Ubuntu's but only partly on older ones)
The Gambas 3.18.4 I have currently running on my Debain 12 has the farm error and so has 3.19.6 version used on GambOS and the 3.20.3 version running in vm. So, the most logical solution to me is backport this fix as well.
First I only backported the code in the httpclient.c from gb.net.curl, as that fixed it for the master branch (https://gitlab.com/gambas/gambas/-/comm ... bd74750fb6). I packaged my new source archive, created a repo, installed it on vm and nope... same error. So, I compared the complete gb.net.curl folder (master source to 3.19.6 source) using meld and decided to merge all changes into the 3.19.6 branch, basicly giving me the master gb.net.curl in 3.19.6. Again, I packaged, created binaries and a repository, installed and...still same error
Ok, next 'meld' session was to compare ALL source from master to my backported 3.19.6 source. I noticed a few changes to gb.net (dnsclient and socket), don't think they are in anyway related to the problem, but I merged then anyway (hoping dnsclient might somehow be involved) and did all above again. Still NO luck (see below).
Above 3.19.6 has gb.net and gb.net.curl completely backported from master, to no avail. And while writing this I realize I didn't check if farm part in IDE has undergone any changes. Might have a look at that later.
The mentioned httpform is a class written in Gambas part of gb.net.curl and hasn't been changed between 3.19.6 and current master. I'm having a hard time finding where things go wrong as gb.net.curl is a mix of Gambas and C code, but I will keep digging into it. Only annoyance is that it keeps me from further working on GambOS Learning and the first guide content concerns, like layout, code boxes, teminal boxes, background boxes etc,
All that involving expanding my private editor last night, to support expanded html editing (read insert pre set html and put that behind a button, so inserting a code box is a matter of a click, with cursor positioned to type the code -> see image below). Yes, the guides will be html based and I'm figuring out how to create a separate .deb package for them (so only documentation and no code), so guides and GambOS Learning can be separately updated.
I might have to write my own packager for that, to also create combined packages like a gambos-core package (providing GambOS Dashboard, GambOS Learning, GambOS Software Center and GambOSGuides packages) in one meta package (like Gambas3 is). Yes, I keep running into new applications to develop to support the making of GambOS
I have chosen this approach as I need to take into account the logistics of updating in future. All will be using the regular debian mechanisms of distribution being repo's, so all tools for software installation/updating on Debian can be used. So, an 'apt-get update && apt-get upgrade' should give you latest version of all that is GambOS related (including guides).
But as long as the GambOS repo is a file repo, updating means new .iso, new install as repo is on GambOS itself. As soon as a webrepo will be possible the .iso updating can stop as update will be pulled from web. It will also make pre installing GambOS applications a lot easier, as now I have to do some hacks to get that done as all GambOS binaries are pulled from local file repo on an installed GambOS itself.
Yeah, there is a whole lot more involved that it might seem at first sight...
Enjoy...