don't update to the latest Pharo

Hi

The latest updates for Pharo break Kom. If you use Seaside and Kom
don't update until the issue has been resolved.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Can you tell us more and report it on the Pharo mailing-list?


On Feb 14, 2009, at 9:52 PM, Philippe Marschall wrote:

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

he filed an issue: http://code.google.com/p/pharo/issues/detail?id=527

Adrian

On Feb 15, 2009, at 15:48 , stephane ducasse wrote:

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2009/2/15, Adrian Lienhard <[hidden email]>:
> he filed an issue: http://code.google.com/p/pharo/issues/detail?id=527

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
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside