On Sun, Feb 15, 2009 at 4:56 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Begin forwarded message:
From: Philippe Marschall <philippe.marschall@gmail.com> Date: February 15, 2009 4:02:05 PM CEST To: Seaside - general discussion <seaside@lists.squeakfoundation.org> Subject: Re: [Seaside] don't update to the latest Pharo Reply-To: Seaside - general discussion <seaside@lists.squeakfoundation.org
2009/2/15, Adrian Lienhard <adi@netstyle.ch>:
he filed an issue: http://code.google.com/p/pharo/issues/detail? id=527
added as comment to issue If you add "asString" in the call in Kom it should work on both Squeak and Pharo. Making a fork most likely will be necessary at some point anyways, so changing Kom to work with proper MIME type objects would a step in the right direction IMHO. Decoupling would reduce reuse of existing classes. Reverting the change would break consistency of method naming. Michael
Further analysis shows there are additional problems: MIMEDocument defaultContentType returns now an instance of MIMEType instead of a String which doesn't understand #indexOf:
*must not add troll comment about static typing*
I see three ways how "we" (= you & Giovanni) can proceed - make a fork of Kom for Pharo - decouple Kom from MIMEDocument - revert the changes done to MIMEDocument
Additionally there is: http://bugs.squeak.org/view.php?id=7285
Cheers Philippe _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project