Re: Hot Web Topic - SWI - Software Index

[Fred Kiefer]

Hi Lars,

if you prefer to rewrite the SWI with GNUstepWeb this is fine for me. It is 
surely a great idea and you will learn a lot. For me the problem is that I 
don’t have the time for it. Getting this running in PHP would surely cost me 
less time. But things seem to be different for you. So feel free to take up 
this project. If you fail for some reason there is still a chance for me to try.

Cheers,
Fred


> Am 30.07.2024 um 13:31 schrieb lars.sonchocky-helldorf@hamburg.de:
>> Am 30.07.2024 um 13:18 schrieb lars.sonchocky-helldorf@hamburg.de:
>> 
>>> Am 30.07.2024 um 08:41 schrieb Fred Kiefer <fredkiefer@gmx.de>:
>>> 
>>>> Am 27.07.2024 um 22:47 schrieb Ivan Vučica <ivan@vucica.net>:
>>>> 
>>>> On Thu, Jul 25, 2024 at 12:43 PM H. Nikolaus Schaller <hns@goldelico.com> 
>>>> wrote:
>>>> The benefit of SWI would be that it is agnostic to the distribution - 
>>>> which can also be a bad thing if dependencies are not available... So it 
>>>> works for binary .app-Bundle downloads only if there is a 100% stable API 
>>>> and set of Frameworks.
>>>> 
>>>>> what's your point?
>>>> 
>>>> So if nobody cares about SWI any more, Wiki Pages are a better solution 
>>>> than nothing.
>>>> 
>>>> "Nobody cares" is strong: I care mainly from a preservationist point of 
>>>> view -- if I were to get it back up, I'd likely rewrite it in Go since 
>>>> that's what I'm most familiar with nowadays. Alternatively, some slightly 
>>>> more modern PHP, using as much from SWI as possible (but reworking queries 
>>>> themselves a lot).
>>>> 
>>>> GSWeb would be really nice, but I am not familiar with it, and I am not 
>>>> sure if I were to do it, that writing it would be fast enough.
>>>> There's also the option of getting it up and running inside a 
>>>> Docker/Podman container with older PHP, Apache2 etc.
>>>> 
>>>> All in all, I think the concern is "should we duplicate the information 
>>>> longer-term", not so much "nobody cares"...
>>>> 
>>>> So If anyone else feels like rewriting it, for preservation purposes, 
>>>> please go ahead; I'm unlikely to find the time, even though I'd like to. 
>>>> Hosting something with available source code and reviewed by us, 
>>>> especially containerized, is not a problem.
>>> 
>>> I am willing to spend that time for the rewrite. Could you please send me 
>>> the PHP code for the SWI? I think I once had it, but don’t remember where I 
>>> put it. For some strange reasons I had to learn PHP and modern PHP isn’t as 
>>> bad as it used to be.
>> 
>> Well PHP might be a bit better than it was today, but REALLY?
>> 
>> Why not learn WebObjects, er I meant GNUstepWeb? It’s not that difficult, 
>> have a look here:
>> 
>> https://en.wikibooks.org/wiki/WebObjects/Hands_On:_Hello_World_-_Your_First_WebObjects_Application
>> 
>> and
>> 
>> https://developer.apple.com/library/archive/documentation/LegacyTechnologies/WebObjects/WebObjects_5/GettingStartedOnWindows/WOGettingStarted.pdf
> 
> 
> After sending my mail I found this guide:
> 
> https://developer.apple.com/library/archive/documentation/LegacyTechnologies/WebObjects/WebObjects_4.5/System/Documentation/Developer/WebObjects/GettingStarted/GettingStarted.pdf
> 
> Maybe it’s better suited for the purpose since WO 4.5 is closer to GNUstepWeb 
> than 5.0 (which was ported to Java).
> 
> 
> Kind regards,
> 
> Lars