Java-OS4 stands on a great deal of prior work, with gratitude:
JAmiga by jaokim — the Java-on-Amiga effort this project revives and extends. The AmigaOS 4 JamVM port and the IcedTea 8 build harness are the foundation we built on.
Quote:
First beta release of Java-OS4 — a Java 8 runtime for AmigaOS 4 (PowerPC): JamVM 2.0 + the OpenJDK 8 class library on clib4, with a native AWT/Swing toolkit so Java GUIs run in Workbench windows.
What works Headless Java 8 programs — collections, streams/lambdas, NIO, reflection, serialization, zip, text. Swing/AWT GUIs in Intuition windows: real mouse and keyboard input, window resize, modal dialogs, fonts via FreeType. Zero-flag GUI launch: java -cp app.jar Main starts a Swing app with no special options.
It said "Java GUIs run in Workbench windows" , it mean not proper integration with menus and co, but main intution window in which all "alien" interface are ? Just like it was with firefox/timberwolf ?
Anyway, is there anything which were tested and worked which can show how it all ? I mean, not simple test cases, but something which using swing/awt so we can have see how it acts now on os4 ?
- you added Assign >NIL: JAVA: "path:Java/" , to user-startup, but didn't mention user need to reboot before he can run "java" binary. - also, with this one assign you can't run "java" bin from anywhere, you need to run it like "java:java -version", because pure "java" will not find it, as JAVA: assing isnt' added as system one. - "java" file is script, but not marked as executable. Probably you pack archive wrong or forget about bit set (or copy it from pc where it looses). protect +es fixed it.
Didn't find any working test examples in archive, but so far it seems to runs, and -version working.
- also, with this one assign you can't run "java" bin from anywhere, you need to run it like "java:java -version", because pure "java" will not find it, as JAVA: assing isnt' added as system one.
isn't that just a matter of running it once with the path, and then it will be in APPDIR:, which by default is in the system path?
Intuition and graphics.library, is correct approach sense just lowlevel api's the JavaVM has to interface with.. Reaction/Mui is too highlevel, Java has its own GUI system.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
1) keys are not working 2) When I close the window the system freeze. With sashimi I can see amiga_exit but the window is not closed and of course it doesn't return to console
I've compiled in on Linux with java 11 and tested on OS4
Probably the standard problems, none initialized pointers (causes random pointer values), and not checking if they allocated before freeing, freeing things twice, (freeing things while things are in-use. Async issues)…
I have noticed when vibe coding that AI’s often write code as examples not production code. I think Vibe coding might work better in Phyton and other languages where don’t need to be so picky.
It can well be that on Windows if free object it also close it, that is not true for AmigaOS. I doubt AI knows the different behavior of different OS's.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
I think the important thing on vibe coding is - don‘t let it do the whole stuff. Do it one method at a time or at least class at a time. And do a manual review of the produced code, at least roughly.
Let it do repetitive and copy/paste work or api replacement. But the real big stuff and architectural work do yourselves.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
