Michael Rueger wrote: > Philippe Marschall wrote: >> Stéphane Ducasse wrote: >>> I have problems to understand why this would be not reasonable that >>> people load a give kom version for seaside on squeak >>> and one for seaside on pharo. >> Loading is one thing. What bothers we more is the maintenance situation. >> Let's face it, there are far too resources behind something as important >> as Kom. Making a fork of it cuts these resources in half. > > Hmm, I think most of the discussion is simply a misunderstanding, I'm > not forking anything. > > With my changes to Pharo (which of course first need to be integrated), > the changed (not forked!) version of Kom and the few changes for Seaside > (which need to be integrated) there is no need for a fork!!! > > Those versions should work on both Squeak and Pharo.
Very well then. Can you contact Giovanni to have your changes integrated at: http://www.squeaksource.com/KomHttpServer.html > It's not monkey patching, none of the packages touch other stuff any > more than they did before. I just changed Kom so its monkey patching now > works on both Seaside and Pharo. > > And that's where I need you help testing. I did a short test with Seaside 2.8 and Squeak 3.9 and it seems to work. Cheers Philippe _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
