Magritte 3 Pier 3

Hi, I've completed an initial port of Pier to Magritte with pragma instance side descriptions - now known as Magritte 3. The Pier port is now named Pier 3. In addition to base systems I've ported the following: Magritte 3 ported addons: -------- Magritte-Json MAgritte-XMLBinding Pier 3 ported addons: ----- Pier-Admin Pier-Blog Pier-Book Pier-Desihn Pier-Documents Pier-EditorEnh Pier-FileUpload-* Pier-Google Pier-JQuery Pier-Kernel-Distributions Pier-LinkChecker Pier-Shout Pier-Wysiwyg Pier-Exporter-Code Pier-Randomizer Pier-Setup Pier-Twitter Note I've moved the Pier-Blog and Pier-Book to the Pier 3 add-ons repository (http://source.lukas-renggli.ch/pier3addons) The repositories are: http://source.lukas-renggli.ch/pier3 http://source.lukas-renggli.ch/magritte3 http://source.lukas-renggli.ch/magritte3addons http://source.lukas-renggli.ch/pier3addons Note: I've deleted "Pier 2 unstable" and "Magritte 2 unstable" repositories - all the code has migrated to the repositories above. There are four supporting configurations: ConfigurationOfMagritte3 ConfigurationOfMagritte3AddOns ConfigurationOfPier3 ConfigurationOfPier3AddOns Try it out with: Gofer it squeaksource: 'MetacelloRespository'; package: 'ConfigurationOfPier3AddOns'; load. ConfigurationOfPier3AddOns project stableVersion load: 'Pier-Admin' the above will pull in a significant portion of the add ons and core libraries and give you a sense of how stable the code is. Caveats: ---- All the tests are green, but I've only applied limited testing. I've tested the above 'Pier-Admin' loading on a clean Pharo 1.3 image. I've removed the Gemstone information from the configurations. I guess once everything is stable on Pharo we can consider a Gemstone port. Let me know how you get on Nick