Hi Lars,
> Am 31.07.2024 um 23:35 schrieb [email protected]: > > Hi Fred, > > fair enough, I came up with the idea so I should pursue it. In order to get > to get an impression of the situation I cloned > https://github.com/goldelico/swi.git and had a look at it. The coding style > seems to be rather unconventional (to avoid other words, everything (PHP, > HTML, shell commands like „echo“ and SQL are intermingled) That is PHP style... "echo" is a PHP command which happens to resemble a shell command. There are no shell commands involved. SQL statements are passed as a string to the query() function. > and incomplete: I could not find a database schema or some SQL script to > create the database tables. Well, this wasn't done that way more than 15 years ago... Although it would be useful to include it in the git repo. If you have direct access to the existing database you can clone it since the data collected so far is more important than creating an empty fresh SQL table. So I have extracted it from a non-GNUstep SWI copy I have and attached. Hope it helps anyone. Well, I would use CHARSET=utf8 nowadays. > I advice you to have a look yourself and be „surprised“. However, the amount > of code is manageable. But all I can says that I lack the PHP skills to get > an idea what SWI looked and worked like from just looking at the code > > Despite you assuming otherwise, my spare time is also limited. I think I > won’t be ready before Christmas (I have some vacation planned before > Christmas), if the GNUstep Software Index is more urgent, you should go on > and try to bring the PHP up to date. It seems to be PHP 5.5 and MySQL 5.6. BR, Nikolaus > > kind regards, > > Lars > >> Am 30.07.2024 um 23:41 schrieb Fred Kiefer <[email protected]>: >> >> 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 [email protected]: >>>> Am 30.07.2024 um 13:18 schrieb [email protected]: >>>> >>>>> Am 30.07.2024 um 08:41 schrieb Fred Kiefer <[email protected]>: >>>>> >>>>>> Am 27.07.2024 um 22:47 schrieb Ivan Vučica <[email protected]>: >>>>>> >>>>>> On Thu, Jul 25, 2024 at 12:43 PM H. Nikolaus Schaller >>>>>> <[email protected]> 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 >> >> >> >
swi.sql
Description: Binary data
