On 23 Apr 2012, at 16:04, Göran Krampe wrote: > Ok, let me clarify. I was just wondering how the Pharo community wants to > handle a case where a substantial component (in this case, this new editor) > is not *primarily* developed in Pharo (in this case Cuis).
Göran, You know that many packages, even some very large ones, are reasonably portable. But I guess portability kind of stops when non-trivial GUI usage is involved. Also, as Pharo is making more and more changes, portability will become harder and harder until it is mostly gone. There are only two solutions: - write your own code to a least common feature set and miss all the new APIs - halt all non-compatible changes in Pharo and stop its evolution Neither are attractive options I guess. Sven
