(Environment name: 'Application') importSmalltalk; import: #Seaside aliases: {#Session -> #SeasideSession}; import: #Magma aliases: {#Session -> #MagmaSession}; fileIn: 'Application.st'.
Enhancement proposal:
how about making this aliasing automatic, happening when the 'ambiguous' class is imported to begin with? Eg when Magma is first imported (into its own environment), the system is smart enough to discover that there are two environments with a class named Session, and automatically creates an alias to both of them, by prefixing the environment name (Seaside and Magma, respectively) to the class name (SeasideSession, MagmaSession).
All users of the Seaside and Magma environments now have access to disambiguated names 'for free', without having the responsability to manually maintain a list of name-clashes in the world outside themselves (ie in the packages they depend on).