If it is just the Url class, then I can't imagine the difference between the old Url class and the new ZnUrl to be very large. An abstraction layer is probably not needed, both should understand #asUrl and should have quite a lot of common methods. The HTTP client is another story ;-)
On a more philosophical note, there is not much point in us trying to make Pharo better, adding new and improved API, and then not using it because external libraries must be compatible (of course this is the choice of the authors). Also, doing things x-platform in Smalltalk is hard, especially if you do not use the other dialects. I would not want this to be a burden for newcomers to contribute. Julien, talk again to Paul, you wil figure something out together, I am sure. If you need help to translate between the old and new, just ask. Sven > On 13 May 2015, at 16:03, Sean P. DeNigris <s...@clipperadams.com> wrote: > > EstebanLM wrote >> It is not a demand. Just a suggestion. You can do whatever you want and >> nobody can impose you how to handle your code :) > > +1. And to clarify, the suggestion is not that /you/ implement code for > Squeak, Pharo, and Gemstone, but that you abstract a Url layer so that other > interested parties can. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Enhancing-ICal-library-tp4825990p4826198.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >
