Feb. 27, 2009
2:58 a.m.
Philippe Marschall wrote:
There is actually on more method (attached) that we need to add to either Kom or Seaside to make Pharo and Squeak compatible on the API level.
Sorry but no, see previous posts. Have a look at Seaside2.8a1-pmm.583 for what I would find acceptable.
OK, can you explain how I should make Seaside work on both Pharo and Squeak? I spent two days figuring out a minimal set of changes that would not require doing some ugly hack testing for which underlying platform you are dealing with and you say that is not acceptable? You *want* ugly hacks? I don't understand... I'm not even touching seaside (except the one method rename/addition for a method being called by Seaside). Michael