Oolite Bulletins

hiran wrote: ↑Thu Jun 13, 2024 8:57 pm

MrFlibble wrote: ↑Wed Jun 12, 2024 9:33 pm

hiran wrote: ↑Wed Jun 12, 2024 6:43 pm

This is the currently stable one:
https://github.com/OoliteProject/Oolite ... ag/v0.1.31

I think if you stick to the builds on the master branch it would be fully sufficient. Experimental versions all have a branch name, as currently 'gelsemium'.

Cool. I cheated, 'cos I skipped the Maven headache by re-using the jar from the generic dist. I've managed to knock together a build script that does it all with little editing. Should be able to repeat this by just changing the version number.

Here's the app, simply zipped.
OoliteStarter-0.1.31-MacOS-x86_64.zip (56.96 MB)
And here, wrapped up in an installer.
OoliteStarter-0.1.31-x86_64.pkg (56.67 MB)

Thank you! I cannot check the content, but I added them to the stable release.

MrFlibble wrote: ↑Wed Jun 12, 2024 9:33 pm

These uploads will self-destruct on July 12th at about 22:22.

Ummmm - I hope I understand the scope right...

MrFlibble wrote: ↑Wed Jun 12, 2024 9:33 pm

Edit: I had failed to get maven build working due to

Code: Select all

src/test/java/oolite/starter/OoliteTest.java:        command.add("/usr/bin/ls");

/bin and /sbin were traditionally the home of stuff needed to boot the system and effect simple repairs before even mounting /usr (which might have been an NFS share).
It's ONLY at the more standard /bin/ls on the Mac. Most Linuxes these days assume a largely flat filesystem, with a symlink /usr/bin to /bin so 'ls' appears in both places.
IMHO, /bin/ls is a more robust choice. I've patched around it in my MacOs-x86_64 build script with sed, and can now build from scratch in one hit.

Ok, that unit test is no good choice. I just checked, and on Ubuntu ls is in the path I gave. But you are right, /bin is a symlink to /usr/bin so I can follow your suggestion.

MrFlibble wrote: ↑Wed Jun 12, 2024 9:33 pm

All I need to do is edit the version number. Output files in $HOME/starter/build/target. I've pasted the build script below in case I have a nasty run in with the 'goids.

Code: Select all

#!/bin/bash

distVER=0.1.31
arch=x86_64

#Builder for Mac.
distURL=https://codeload.github.com/OoliteProject/OoliteStarter/zip/refs/tags/v$distVER
builddir=$HOME/starter/build

kaput(){ echo "$1" ; exit 2 ; }

[ "x$distVER" = "x" ] && kaput "Version is nonsense"
#jpackage won't accept the first digit of version being zero.
# so we patch it here.
MacVER=$(echo "$distVER" | sed 's@^0\.@1.@')

mkdir -p "$builddir" && cd "$builddir" || kaput "Can't make build dir $builddir"

getTar(){
	curl -L -o dist-${distVER}.zip $distURL
	unzip -qq dist-${distVER}.zip
	ls -al
}

doMaven(){
	#PATCH FOR MAC.
	#BSD sed insists on a suffix for backup when using -i to edit inline.
	sed -i flibble 's@/usr/bin/ls@/bin/ls@' \
 	 OoliteStarter-$distVER/src/test/java/oolite/starter/OoliteTest.java
	export PATH="$PATH:$HOME/maven/bin"
	cd OoliteStarter-$distVER || kaput "failed to cd to source" 
	mvn versions:set "-DnewVersion=$distVER"
	mvn -B package -e --file pom.xml
	cd -
}

doBuild(){
echo "$distVER"
jpackage \
 --type app-image \
 --app-version $MacVER \
 --copyright Copyright \
 --description "OoliteStarter $distVER" \
 --name "OoliteStarter" --dest target/appimage \
 --temp target/oolite-starter-tmp --vendor "OoliteProject" --verbose \
 --icon OoliteStarter-$distVER/src/main/resources/oolite_logo.png \
 --input OoliteStarter-$distVER/target/dist \
 --main-jar OoliteStarter-$distVER.jar \
 --main-class oolite.starter.MainFrame --mac-package-name "OoliteStarter" \
 --resource-dir OoliteStarter-$distVER/src/jpackage/resources-mac \
 --vendor OoliteProject
}

doApp(){
 jpackage \
  --type pkg \
  --verbose \
  --app-version $MacVER \
  --app-image target/appimage/OoliteStarter.app \
  --name "OoliteStarter" \
  --icon OoliteStarter-$distVER//src/main/resources/oolite_logo.png \
  --dest target \
  --resource-dir OoliteStarter-$distVER/src/jpackage/resources-mac \
  --vendor OoliteProject
}

makeZipDist(){
 cd target/appimage
 zip -qr ../OoliteStarter-${distVER}-MacOS-$arch.zip  *
 cd - ; cd target
 mv OoliteStarter-${MacVER}.pkg OoliteStarter-${distVER}-$arch.pkg
}

getTar
doMaven
doBuild
doApp
makeZipDist

Let's add that to the project. Just give it a meaningful name, add comments inside what it intends to do and stuff it besides pom.xml. I'm happy to accept a pull request.
Obviously I will never run that script, so maintenance is on you.

mosquitto_sub -h localhost -p 1883 -u admin -P "simple" -t '#' -v
users/mcflibble/games/oolite/starter connection test
users/mcflibble/games/oolite/starter started
users/mcflibble/games/oolite/starter Oolite started
users/mcflibble/games/oolite/starter Oolite stopped

 Debug_OXP

...in debugConfig.plist. For external console support on the same computer under Mac OS X, console-host must be explicitly set to “127.0.0.1”; if this is not done, the integrated JavaScript console will be used instead.

DebugConsole: ERROR    Unsupported var console-host: 127.0.0.1, type: <class 'str'>
DebugConsole: ERROR    Unsupported var console-port: 8563, type: <class 'str'>

python3 -B pySimpleConsole.py
Python Oolite debug console
Type /quit to quit.
Waiting for connection...

Opened connection to Oolite version 1.90

echo "Debugger" | sed 's/De//'

MrFlibble wrote: ↑Tue Jun 25, 2024 5:00 pm

Testing this on the Mac. A couple of issues.

Selecting a pre-saved Jameson (found by starter in ~/Documents) and hitting resume opens Oolite 1.90 on the main menu. Saving as a new name while "starter-started" makes no odds. Resume doesn't resume, it loads. Still one can open the savegame from the game main menu.

MrFlibble wrote: ↑Tue Jun 25, 2024 5:00 pm

With a low-ish res, the problem of MQTT topics extending beyond the screen limit (1280x800) is beyond cosmetic. It actually pushes the save/cancel buttons so far off the bottom that even with dock-autohide on, you can't click them. You can use tab to highlight, and space to accept, as you can see about a pixel row to know which one is selected. One more topic, and no more buttons!

MrFlibble wrote: ↑Tue Jun 25, 2024 5:00 pm

MQTT ouptut is somewhat lacking:

Code: Select all

mosquitto_sub -h localhost -p 1883 -u admin -P "simple" -t '#' -v
users/mcflibble/games/oolite/starter connection test
users/mcflibble/games/oolite/starter started
users/mcflibble/games/oolite/starter Oolite started
users/mcflibble/games/oolite/starter Oolite stopped

That's from loading commander, launching, and changing speed. The last three lines simply repeat on re-attempt. I tried opening up the mosquitto acl for mcflibble, but it doesn't look like writes are attempted elsewhere.

hiran wrote: ↑Tue Jun 25, 2024 6:48 pm

MrFlibble wrote: ↑Tue Jun 25, 2024 5:00 pm

Testing this on the Mac. A couple of issues.

Selecting a pre-saved Jameson (found by starter in ~/Documents) and hitting resume opens Oolite 1.90 on the main menu. Saving as a new name while "starter-started" makes no odds. Resume doesn't resume, it loads. Still one can open the savegame from the game main menu.

Unfortunately a known bug in Oolite:
viewtopic.php?p=291772#p291772

hiran wrote: ↑Tue Jun 25, 2024 6:48 pm

MrFlibble wrote: ↑Tue Jun 25, 2024 5:00 pm

With a low-ish res, the problem of MQTT topics extending beyond the screen limit (1280x800) is beyond cosmetic. It actually pushes the save/cancel buttons so far off the bottom that even with dock-autohide on, you can't click them. You can use tab to highlight, and space to accept, as you can see about a pixel row to know which one is selected. One more topic, and no more buttons!

Could I have a screenshot please? And do you have an idea how a fix could look like? (on the screen, not in code)

Oolite will use this as a parent topic: users/mcflibble/games/oolite
It will subscribe to this/these topics beneath that: input
And publish to these: /, /alert, /commandAcknowledge, /comms, /configuration,
 /console, controls, log, showConsole, starter, unknown, worldEvent

------------------------------------------------------------------------
|Scan|Add|Edit|Remove| etc.                                            |
|----------------------------------------------------------------------|   VERTICAL
| Installation 1        | Home dir [                              ] |##| <-ELEVATOR
| Installation 2        | Version  [                              ] |##|
|  etc.                 | Execu... blah!                            |  |
|                       |                                           |  |
|                       |: <-HORIZONTAL RESIZER                     |  |
|                       |                                           |  |
|                       |                                           |  |
|      vert resizer     |                                           |  |
|          v            |                                           |  |
|         ..            |                                           |  |
|-----------------------|                                           |  |
|pub|                   |                                           |  |
|sub| topic             |                                           |  |
|-----------------------|   VERTICAL                                |  |
|sub|topic/thing     |##| <-ELEVATOR                                |  |
|pub|topic/ver       |  |                                           |  |
|pub|topic/verylong/t|  |                                           |  |
|pub|topic/a         |  |                                           |  |
|pub|topic/b         |  | More Conf....                             |  |
|--------------------|  |                                           |  |
|##                  |  | (extends below window hence elevator)     |  |
------------------------------------------------------------------------
       ^
    HORIZONTAL
    ELEVATOR

hiran wrote: ↑Tue Jun 25, 2024 6:48 pm

MrFlibble wrote: ↑Tue Jun 25, 2024 5:00 pm

MQTT ouptut is somewhat lacking:
...
So yes, there are a number of issues in the Oolite Mac version that do not exist the same way on other platforms. Again it shows we lost Mac support long time ago...

hiran wrote: ↑Fri Jun 28, 2024 9:46 pm

Ok, here's the fix: OoliteStarter v0.1.32-gelsemium.12

MrFlibble wrote: ↑Fri Jun 28, 2024 10:29 pm

hiran wrote: ↑Fri Jun 28, 2024 9:46 pm

Ok, here's the fix: OoliteStarter v0.1.32-gelsemium.12

Nice solution!

Here are the x86_64 builds. I fixed the filename on the pkg to include 'MacOS'.

Links valid for a month.

hiran wrote: ↑Mon Jul 01, 2024 7:27 am

MrFlibble wrote: ↑Fri Jun 28, 2024 10:29 pm

hiran wrote: ↑Fri Jun 28, 2024 9:46 pm

Ok, here's the fix: OoliteStarter v0.1.32-gelsemium.12

Nice solution!

Here are the x86_64 builds. I fixed the filename on the pkg to include 'MacOS'.

links

Thanks.
Now that I am back online I can take a look and find them already uploaded to Github. What a service!

MrFlibble wrote: ↑Mon Jul 01, 2024 8:37 am

I don't have access to edit starter releases pages. I had a look. A penny dropped! Seems I should have been using OpenJDK but may or may not have stumbled on the path of least resistance at my first pass of this (whoops!). Please zap the links in your reply to me, and upload the versions below.

another_commander wrote:

phkb wrote:

MrFlibble wrote: ↑Mon Jul 01, 2024 8:37 am

These are built using OpenJDK 22.0.1, which was quite strongly offered at the OpenJDK download page when I went looking for 21.

another_commander wrote: ↑Mon Jul 01, 2024 1:00 pm

MrFlibble has now Maintainer level access to the OoliteStarter repository.

You can’t use this version of the application “OoliteStarter” with this version of macOS.

You have macOS 10.15.3. The application requires macOS 11.0 or later.

Cholmondely wrote: ↑Thu Jul 04, 2024 8:42 pm

Alas, MrF's most recent (OoliteStarter-0.1.32-gelsemium.12) requires me to update my OS which I'm loathe to do...

You can’t use this version of the application “OoliteStarter” with this version of macOS.

You have macOS 10.15.3. The application requires macOS 11.0 or later.

Oolite used to be playable with old machines, which meant that for example, those in third world countries with old machines could join us.

Now, not only do we not have versions which they can play (Spara's woes, passim), but we require them to update everything too!



Is this really the path we should be treading?

MrFlibble wrote: ↑Thu Jul 04, 2024 10:00 pm

I'll look at whether I can do something to reduce need to update. Did my previous builds work? It may just be the version of Java I'd switched up to (as the previous one was no longer getting updates).