> Hi Stef, > > what would be the suggested API then ? All RPackage methods without the compatibility layer.
> And in announcements, would that change the returned type of some events > (MCWorkingCopyCreated / MCWorkingCopyDeleted) ? > > For Alt-Browser to navigate through the packages, I use MCWorkingCopy and > PackageInfo. Is this the way it should be done ? Should I use RPackage > instead ? yes. We will remove PackageInfo. The first step will be to keep inside PackageInfo only the methods used. Then make sure that we can have the same behavior with RPackage. MCWorkingCopy is just the repository for MC world. > Thierry > ________________________________________ > De : [email protected] > [[email protected]] de la part de Stéphane Ducasse > [[email protected]] > Date d'envoi : dimanche 5 août 2012 13:28 > À : [email protected] Development > Objet : [Pharo-project] About the migration from PackageInfo to RPackage > > Hi guys > > PackageInfo has a large APi that is often not used. > So I would suggest that we reduce the PackageInfo API first because it will > lower the stress on RPackage to be offer a > compatible interface. > All the methods in the compatibility should somehow disappear or only serve > as purpose to help temporary > backwards compat. > > What do you think? > > Stef >
