Administrator
|
I committed a new Metacello config, and copied it to sqs/Meta...Repo, and ss3...MetaRepoForPharo20 with the following changes:
* Bless 3.0 as stable (it was already declared as such by the symbolic version) * Create new 3.1 development version, using semantic enhancement minor version bump, to incorporate Morphic enhancements * Declare 3.1 as the symbolic development version The Morphic enhancements are: * Implement basic working One-to-many relationship in Morphic with edit and remove features * Refactor Morph building * Initial implementation of Morphic One-to-one relationships * Use DateModel (from Spec) for Dates in Morphic
Cheers,
Sean |
Hi all,
Before my holidays I started on making the code exporter for pier3 work easy. I had some issues, and fixed most of the before my holidays. But now after my holidays I had time to test the entire path, so we can deploy our website www.legacycode.nl from continuous integration. We now can use the following script on a clean pharo 2.0 image: " load the configuration and from the configuration the code exporter for pier " Gofer new url: 'http://smalltalkhub.com/mc/Pier/Pier3Addons/main'; package: 'ConfigurationOfPier3AddOns'; load. ((Smalltalk at: #ConfigurationOfPier3AddOns) project version: #'stable') load: 'Code-Exporter-Pier3'. " load and start the webserver. For Pharo this we use Zinc " ((Smalltalk at: #ConfigurationOfSeaside3) project version: '3.1.0') load: 'Zinc-Seaside'. (Smalltalk at: #ZnZincServerAdaptor) startOn: 8080. " load your own exported code and perform line below to recreate the kernel PRKernelCreatorForPier register and copy the files pier created (css) to the correct folder (default .../Resources/files/* ) Note: the pier image sets the folder to a fixed location in MAExternalFileModel. To reset this: MAExternalFileModel baseDirectoryPath: nil Setting this folder is also possible if you want to use a location outside of your image for your css files. I.e. MAExternalFileModel baseDirectoryPath: '~/css' " Stephan and Diego _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
On Aug 19, 2013, at 13:41 , Diego Lont wrote: > We now can use the following script on a clean pharo 2.0 image: > " load the configuration and from the configuration the code exporter for pier " > Gofer new > url: 'http://smalltalkhub.com/mc/Pier/Pier3Addons/main'; > package: 'ConfigurationOfPier3AddOns'; > load. > ((Smalltalk at: #ConfigurationOfPier3AddOns) project version: #'stable') load: 'Code-Exporter-Pier3'. > > " load and start the webserver. For Pharo this we use Zinc " > ((Smalltalk at: #ConfigurationOfSeaside3) project version: '3.1.0') load: 'Zinc-Seaside'. > (Smalltalk at: #ZnZincServerAdaptor) startOn: 8080. > > " load your own exported code and perform line below to recreate the kernel > PRKernelCreatorForPier register > > and copy the files pier created (css) to the correct folder (default .../Resources/files/* ) > Note: the pier image sets the folder to a fixed location in MAExternalFileModel. To reset this: > MAExternalFileModel baseDirectoryPath: nil > Setting this folder is also possible if you want to use a location outside of your image for your css files. I.e. > MAExternalFileModel baseDirectoryPath: '~/css' That comes pretty close to working on Pharo 3 too. Only changes needed was replacing ensureDirectory by ensureCreateDirectory in MAExternalFileModel For production you'd of course want to remove the default applications and set the loaded kernel as default application. Stephan _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki |
Free forum by Nabble | Edit this page |