Respondió en el hilo
I mean, it doesn't look as gorgeous on #elementaryOS, but still, it works.
Administrado por:
#webobjects
0 publicaciones0 participantes0 publicaciones hoy
Respondió en el hilo
Ok, it even works using JDK 17 when you add `--add-exports java.base/sun.security.action=ALL-UNNAMED` as JVM option.
Respondió en el hilo
Respondió en el hilo
Think I got it running. It is aged. But aged very well. The client of this almost 30 years old example runs quite nicely, errors only point to SQL/model setup.
Respondió en el hilo
Think I‘ll reread that #WebObjects Desktop Application docs. They are just delicious.
Hm, really tired of this #MSAccess, #LibreOfficeBase database application stuff. I need a quick way to create a "main/detail" GUI from a database.
There once was #WebObjects and that really nice #JavaClient stuff.
Is there anything else, existing to this day?
I know of
- #Apache #Cayenne (only ORM, no GUI generation)
- #ManyDesigns #Portofino (very close, but only web GUI. Thanks to @peter for that hint some time ago).
Do you know of anything? @helge
Continuó el hilo
I think for that you don’t want structural identity because the structure will eventually change.
But assigning global identity (like a DOM id) conflicts with componentization. There has to be something in the middle, a path builder that is not tied to the exact structure. #WebObjects #SwiftUI
Continuó el hilo
It’s not usually an issue in SwiftUI because an app upgrade implies a restart, but I wonder whether such things leak in for stuff like state restoration #WebObjects #SwiftUI
Do you remember those #WebObjects links like “http://Dodge.woa/wo/2.3.2.4.1.1.1.1.2.3.4.5”? Those (usually numeric paths) are essentially a representation of the thing that is called “structural identity” in #SwiftUI.
I.e. the button in the pic would produce a link like `.woa/wo/2.2` to represent a click on the second item in the `ForEach`.
It's problematic on the web, because links can be long-living, but the server may upgrade and have a different structure.
I am installing @mattl's favourite framework ever rn
Great news for all of us, old #WebObjects dinosaurs!
Our team will be very happy to help with this initiative, that was announce at #serversideswift2024 After all, I think we have the largest WebObjects installed base outside Apple.
GitHubGitHub - swiftlang/swift-javaContribute to swiftlang/swift-java development by creating an account on GitHub.
Respondió a Dr. Matt Lee (1800www.com)
@mattl "You know, I wanna be noticed" 
Bad quality, but available: https://youtu.be/BgOUaSmXfUU?si=xaYcG9UDfkNwW7a2&t=2005
#NeXT #WebObjects
Does anyone else think about the Dodge virtual showroom demo of WebObjects every day or two or is that just me?
Ever heard about WebScript? It was an interpreted, Mini-#ObjC that came w/ #WebObjects. IIRC using WO w/ WebScript was free, building apps w/ ObjC required the $$$$ expensive license.
WebScript even had a "modern syntax" (I think this must be ~1998?) w/o the brackets (but `function doIt() { }` style).
https://developer.apple.com/library/archive/documentation/LegacyTechnologies/WebObjects/WebObjects_3.1/PDF/DEVGUIDE/SCRIPT.PDF
Respondió en el hilo
@chris Maybe it would be OK to say that body returns a list, but even that is not really true, it might return a container.
BTW: As usual it is the same in #WebObjects, it also has the „content“ thing not as an array, but as a single type that can be a container of some form.