Magma

magma@lists.squeakfoundation.org

722 discussions

Re: [Pharo-users] Problem installing Magma
by Mariano Martinez Peck 10 Jun '11

10 Jun '11

ConfigurationOfOSProcess (used by Magma) was wrong: version440: spec <version: '4.4.2' imports: #('4.4-baseline' )> spec for: #'common' do: [ spec blessing: #'release'. spec description: 'Version 4.4.2'. spec author: 'MiguelCoba'. spec timestamp: '5/29/2011 12:34'. spec package: 'OSProcess' with: 'OSProcess-dtl.61'; package: 'OSProcess-Tests' with: 'OSProcess-Tests-dtl.4'. ]. Now it seems to be fixed: Name: ConfigurationOfOSProcess-mt.16 Author: mt Time: 9 June 2011, 1:28:23.772 pm UUID: 7155a747-e91a-194e-9030-8e211f37b1a9 Ancestors: ConfigurationOfOSProcess-AdrienBarreau.15 - recovered 4.4.0 - added 4.4.2 as stable (like it was in AdrienBarreau.15 in modified #version440) reason: to not break dependent projects assumptions (i.e., version 4.4.0 could not be found anymore) On Fri, Jun 10, 2011 at 5:26 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Nope, the typo is in the ConfigurationOfMagma class, which is looking for a > version 4.4.0 of OSProcess, which actually does not exist :/. > I'll see if I can fix it in a while. > > Guille > > > On Fri, Jun 10, 2011 at 12:19 PM, Alan Rodas <alanrodas(a)gmail.com> wrote: > >> Sorry Mariano, didn't catch you there. >> Do you mean a typo in this sentence? >> >> ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load >> >> beacause even if I try to use the stable version, it still does not work. >> So >> >> ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load >> >> gives the same result. >> >> So I don't get where the typo is, although you may be refering to a typo >> somewhere else. >> >> Cheers >> -- >> Alan Rodas Bonjour >> >> > -- Mariano http://marianopeck.wordpress.com

1 0

Re: [Pharo-users] Problem installing Magma
by Mariano Martinez Peck 09 Jun '11

09 Jun '11

Alan we have reported this several times...... it is a TYPO. Can someone fix it ? thanks On Thu, Jun 9, 2011 at 6:08 AM, Alan Rodas <alanrodas(a)gmail.com> wrote: > I would really love to, and I promised myself that I will as soon as I make > myself some time. > > Unfortunately there still much I would love to test and learn in Pharo > before getting myself dirty. Mariano's blog about VM and Morphic are some of > my pending accounts. So maybe after the winter holidays (Argentina's winter) > if I have some time, i will start doing some more things in Pharo. > > Collaborating a little bit on PBE Spanish translation thou. Trying to give > my 2 cents back to the community. > > > Back to the problem: I checked in the MetacelloRepository for OSProcess, > and found out that latest version is 4.4.2. So I downloaded the > ConfigurationOfMagma from MetacelloRepository for Pharo 1.2...but then I > found out that I dont understand anything about Metacello or how it > works...so even if I tried to found a reference for OSProcess 4.4.0, i was > not able to find it. > Metacello added to my pending accounts list. Geez... every time it gets > larger and larger. > > > Cheers. > -- > Alan Rodas Bonjour > > -- Mariano http://marianopeck.wordpress.com

1 0

Personalized systems with Treated
by Chris Muller 05 May '11

05 May '11

To support Magma 1.2, I introduced some changes to OrderedCollection into the Squeak trunk some time ago. To deliver Magma to Pharo users, I needed to have these same enhancements in Pharo 1.1 and 1.2. But they were already released, so how was this solved? My first instinct was to deliver a change-set; the classical way to modify the system. But I know dirty packages are unattractive, and besides that the only way to achieve one-click load of something involving a change-set + MC-packages in Pharo is with a SAR - overkill since Magma is just MC packages; no resources. I really wanted to release Magma 1.2 to Pharo with just a Gofer script. So, I decided to import the same changes I made to Squeak's OrderedCollection into Pharo's and then save that new version to the Inbox and adjusted my Gofer script for loading Magma to merge that version of Collections from repositories: Pharo, Inbox, TreatedInbox. I knew they would accept it, thank you Pharo, BUT it's nice to know that I could actually deliver my application without having to wait for it to be integrated, or worry even if it didn't get accepted; that chain of repositories should work immediately and forever, no matter the outcome of acceptance. Thanks to MC merging, this is as unintrusive as it can be; in case someone runs with their own "personalizations" to the Collections package, loading Magma won't clobber them; nor will updating with official Pharo-released patches, because those are merged too. With the context of this experience, I came to view the "Treated" repository with a new respect; enabling a non-core developer to personalize system packages for my application.. - Chris

3 5

Confused about MagmaCollections
by Thierry Lebourque 03 May '11

03 May '11

Hi, Diving into Magma, I have found some information that look, to me, quite contradictory about MagmaCollections. Here: http://wiki.squeak.org/squeak/2639 I understand that they are a good choice for large collections of objects. And here: http://wiki.squeak.org/squeak/2986 it is said that they should not be used. Well, I have a large collection of objects and MagmaCollections seemed to meet my requirements in terms of accessing, but, according to the wiki, not in terms of performances. So my question is: are they usable or should I implement my own version ? Regards, Thierry

2 2

Re: [ANN] Magma 1.2
by Miguel Cobá 02 May '11

02 May '11

El lun, 02-05-2011 a las 15:05 -0400, Marco A. Gonzalez escribió: > Miguel, > > I've been able to figure out how to use the Pharo One-click installer on my MacBookPro running OS X 10.6, and deploy it on eapps.com, a Linux VPS hosting company, in my account running CentOS Linux. I don't know what I would need to do with the "individual" downloads to make Pharo work both on my development machine (Macintosh) and the production environment (CentOS linux). Umm, better yet, no windows, that is a win for sure. This is old and maybe doesn't work anymore but you can give it a try, as a one click isn't really suited for deployment: http://miguel.leugim.com.mx/index.php/2009/09/22/deploying-seaside-install-… Cheers > > Thank you for the initial posting with the clear steps. I know I tried to do something different than what you posted by using the one-click. However, I do think the one-click installer eventually OUGHT to be able to have Magma 1.2 installed in it, so that's what I'd like to wait for. > > I'm happy that you're pushing to have Magma in Pharo... I'd really like to use it and eventually, when I have more experience with everything, would like to contribute. > > Looking forward to anything you can tell me to get the one-click installer with Magma working, > > - Marco A. > > On May 2, 2011, at 1:53 PM, Miguel Cobá wrote: > > > El lun, 02-05-2011 a las 13:01 -0400, Marco A. Gonzalez escribió: > >> Miguel, > >> > >> I read your posting of http://forum.world.st/ConfigurationOfMagma-with-support-for-Magma-1-2-and-s… and tried your instructions but using the Pharo 1.2.1 One-Click installer. You had already answered a previous posting of mine indicating the following: > >> "The problem here is that the class SHParserST80 isn't anymore in the image and is used by OContext of the package OCompetion. You can open a ticket with this problem in the issue tracker in order to not forget it." > >> However, I'm still a newbie in that I don't feel like I know enough to be able to write a useful ticket. I think anyone would see the problem they tried to use the current Pharo 1.2.1 One-Click installer and tried to install Magma 1.2. > >> > > > > I already opened the ticket. > > > >> The short story is that I'd like to be able to install Magma in a Pharo One-Click installer, and I currently can't seem to be able to do that either with Metacello or filing in using the ".st" script that Chris provided. I was drawn to Pharo for its clean, smooth interface and architecture which includes Metacello. Do you know of a way to install Magma 1.2 with a Pharo one-click installer? If so, would provide the steps to do that like you did your "ConfigurationOfMagma-with-support-for-Magma-1-2-and-symbolic-versions" posting? > >> > > > > I can't promise anything, but I will give it a try more deeply this > > night. Now, if you are only trying to test Magma on Pharo, use a pharo > > core image and install it there. Isn't hard. > > > > 1. Download image, changes and sources files (PharoCore-1.2.1.zip): > > > > http://www.pharo-project.org/pharo-download/stable-core > > > > Unzip the file and you get: > > > > PharoCore-1.2.1-12345.changes > > PharoCore-1.2.1-12345.image > > PharoV10.sources > > > > 2. Get a vm for your OS (don't know which do you use) suppose is > > windows. The download from the Virtual Machines section on > > http://www.pharo-project.org/pharo-download page for Windows (4.1.1) is: > > > > http://gforge.inria.fr/frs/download.php/28468/PharoVM-Win32-4.1.1-bin.zip > > > > unzip it to the same folder where you have the .image, .changes > > and .sources files. You get the following files: > > > > Pharo.exe > > SqueakFFIPrims.dll > > FT2Plugin.dll > > splash.bmp > > > > then open a MS-DOS window (or CMD) and change dir to the folder where > > you have all the files and execute: > > > > Pharo.exe PharoCore-1.2.1-12345.image > > > > The Pharo image should run. From there you can follow the instruction > > from the ConfigurationOfMagma announcement. > > > > You can also try the Windows installer from Torsten (in the same Pharo > > download page) if that is easier. > > > > Cheers > > > > > > > > 2. Download > >> - Marco A. > >> > >> 2:13 PM, Miguel Cobá wrote: > >> > >>>> despite trying the different ways to get Magma loaded (including Miguel Coba's ConfigurationOfMagma). > >>>>> Can you give me any suggestions? > >>> > >>> > >>> Marco, I can't see the date of the original message you sent to Chris > >>> but thanks to Chris Magma 1.2 runs now on Pharo 1.1 and Pharo 1.2 (I > >>> only test on PharoCore images but aside from the problem with the > >>> workspace that show up yesterday and that is a problem with OCompletion > >>> and not with Magma, it shouldn't have any problem in Pharo Deve images). > >>> > >>> So, if you tested with the test with the new version of > >>> ConfigurationOfMagma announced on april 27, 2011 it should work > >>> correctly on Pharo. If you have any problem with the installation please > >>> post the details here so we can work them out. > >>> > >>> > >>>> Use the official installation scripts provided on the wiki page. > >>> > >>> Yes, use the official scripts if you're using Squeak. Also Chris has > >>> made a big effort to bring from the dead SqueakMap that appears that is > >>> the way to install things in Squeak again. But SqueakMap isn't anymore > >>> in Pharo and won't be any time soon if ever. > >>> > >>> But for Pharo we are pushing Metacello and you're expected to use the > >>> ConfigurationOfMagma for installing on Pharo. As I said before if you > >>> found a problem with the configuration please report it and I will take > >>> care of this (if it is a problem of the configuration and if it is a > >>> problem with Magma I will pass it to Chris, because most times they are > >>> outside my knowledge and expertise). > >>> I have a great interest in having Magma working in Pharo, the Pharo way > >>> (that is with metacello) and I try to not bother Chris with problems in > >>> the metacello config by trying to be alert for posts in the mailing list > >>> related to the configuration so that he can focus on Magma per se. When > >>> a new release is made I examine their scripts and translate them to a > >>> new ConfigurationOfMagma release. This, I think, is the best arrange to > >>> keep things going on in Magma and Pharo. > >>> > >>> Cheers > >>> > >>>> > >>>> - Chris > >>> -- > >>> Miguel Cobá > >>> http://twitter.com/MiguelCobaMtz > >>> http://miguel.leugim.com.mx > >>> > >>> > >>> > >>> _______________________________________________ > >>> Magma mailing list > >>> Magma(a)lists.squeakfoundation.org > >>> http://lists.squeakfoundation.org/mailman/listinfo/magma > >> > >> ------------------------------------------------------ > >> Marco A. Gonzalez, President > >> Amagavi, Inc. > >> Developer of database-driven web sites > >> > >> web: http://www.amagavi.com/ > >> email on iPhone: marcoinc(a)mac.com > >> cell: 202-222-5137 > >> > >> > >> > >> > > > > -- > > Miguel Cobá > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > ------------------------------------------------------ > Marco A. Gonzalez, President > Amagavi, Inc. > Developer of database-driven web sites > > web: http://www.amagavi.com/ > email on iPhone: marcoinc(a)mac.com > cell: 202-222-5137 > > > > -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

1 0

Re: [ANN] Magma 1.2
by Miguel Cobá 02 May '11

02 May '11

El lun, 02-05-2011 a las 13:01 -0400, Marco A. Gonzalez escribió: > Miguel, > > I read your posting of http://forum.world.st/ConfigurationOfMagma-with-support-for-Magma-1-2-and-s… and tried your instructions but using the Pharo 1.2.1 One-Click installer. You had already answered a previous posting of mine indicating the following: > "The problem here is that the class SHParserST80 isn't anymore in the image and is used by OContext of the package OCompetion. You can open a ticket with this problem in the issue tracker in order to not forget it." > However, I'm still a newbie in that I don't feel like I know enough to be able to write a useful ticket. I think anyone would see the problem they tried to use the current Pharo 1.2.1 One-Click installer and tried to install Magma 1.2. > I already opened the ticket. > The short story is that I'd like to be able to install Magma in a Pharo One-Click installer, and I currently can't seem to be able to do that either with Metacello or filing in using the ".st" script that Chris provided. I was drawn to Pharo for its clean, smooth interface and architecture which includes Metacello. Do you know of a way to install Magma 1.2 with a Pharo one-click installer? If so, would provide the steps to do that like you did your "ConfigurationOfMagma-with-support-for-Magma-1-2-and-symbolic-versions" posting? > I can't promise anything, but I will give it a try more deeply this night. Now, if you are only trying to test Magma on Pharo, use a pharo core image and install it there. Isn't hard. 1. Download image, changes and sources files (PharoCore-1.2.1.zip): http://www.pharo-project.org/pharo-download/stable-core Unzip the file and you get: PharoCore-1.2.1-12345.changes PharoCore-1.2.1-12345.image PharoV10.sources 2. Get a vm for your OS (don't know which do you use) suppose is windows. The download from the Virtual Machines section on http://www.pharo-project.org/pharo-download page for Windows (4.1.1) is: http://gforge.inria.fr/frs/download.php/28468/PharoVM-Win32-4.1.1-bin.zip unzip it to the same folder where you have the .image, .changes and .sources files. You get the following files: Pharo.exe SqueakFFIPrims.dll FT2Plugin.dll splash.bmp then open a MS-DOS window (or CMD) and change dir to the folder where you have all the files and execute: Pharo.exe PharoCore-1.2.1-12345.image The Pharo image should run. From there you can follow the instruction from the ConfigurationOfMagma announcement. You can also try the Windows installer from Torsten (in the same Pharo download page) if that is easier. Cheers 2. Download > - Marco A. > > 2:13 PM, Miguel Cobá wrote: > > >> despite trying the different ways to get Magma loaded (including Miguel Coba's ConfigurationOfMagma). > >>> Can you give me any suggestions? > > > > > > Marco, I can't see the date of the original message you sent to Chris > > but thanks to Chris Magma 1.2 runs now on Pharo 1.1 and Pharo 1.2 (I > > only test on PharoCore images but aside from the problem with the > > workspace that show up yesterday and that is a problem with OCompletion > > and not with Magma, it shouldn't have any problem in Pharo Deve images). > > > > So, if you tested with the test with the new version of > > ConfigurationOfMagma announced on april 27, 2011 it should work > > correctly on Pharo. If you have any problem with the installation please > > post the details here so we can work them out. > > > > > >> Use the official installation scripts provided on the wiki page. > > > > Yes, use the official scripts if you're using Squeak. Also Chris has > > made a big effort to bring from the dead SqueakMap that appears that is > > the way to install things in Squeak again. But SqueakMap isn't anymore > > in Pharo and won't be any time soon if ever. > > > > But for Pharo we are pushing Metacello and you're expected to use the > > ConfigurationOfMagma for installing on Pharo. As I said before if you > > found a problem with the configuration please report it and I will take > > care of this (if it is a problem of the configuration and if it is a > > problem with Magma I will pass it to Chris, because most times they are > > outside my knowledge and expertise). > > I have a great interest in having Magma working in Pharo, the Pharo way > > (that is with metacello) and I try to not bother Chris with problems in > > the metacello config by trying to be alert for posts in the mailing list > > related to the configuration so that he can focus on Magma per se. When > > a new release is made I examine their scripts and translate them to a > > new ConfigurationOfMagma release. This, I think, is the best arrange to > > keep things going on in Magma and Pharo. > > > > Cheers > > > >> > >> - Chris > > -- > > Miguel Cobá > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > _______________________________________________ > > Magma mailing list > > Magma(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/mailman/listinfo/magma > > ------------------------------------------------------ > Marco A. Gonzalez, President > Amagavi, Inc. > Developer of database-driven web sites > > web: http://www.amagavi.com/ > email on iPhone: marcoinc(a)mac.com > cell: 202-222-5137 > > > > -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

1 0

Re: [ANN] Magma 1.2
by Chris Muller 02 May '11

02 May '11

> I noticed that at the bottom of the page http://wiki.squeak.org/squeak/2657 the link with text "Pharo1.2-load-magma.st" is http://wiki.squeak.org/squeak/uploads/2657/Pharo1.1.2-load-magma.st. Note the "Pharo1.1.2"... was that intentional? It's because the wiki keeps every version of every file ever uploaded to the page. The name of the first version of the link was the actual filename, "http://wiki.squeak.org/squeak/uploads/2657/Pharo1.2-load-magma.st". But I had to upload a new version of that file, and the algorithm the wiki follows is to assume the original file was in teh format, "filename.txt" and it then makes it, "filename.1.txt" and begins to increment that version number in the middle for all new versions going forward. Whew! So, that's the answer to your question. > Using TestRunner from the World Menu, I ran the tests for "Ma special collections-Dictionarys-Auto-Tests" and got the following: > 104 run, 99 passes, 1 expected failures, 2 failures, 2 errors, 0 unexpected passes The failed tests are all related to using nil as a key in the dictionary which, to my knowledge, is not supported by any Dictionary in Squeak and nor does Magma depend on storing anything at a nil key in any Dictionary. > In a Workspace window, I evaluated "MaClientServerTestCase suite maDebug" and got the following: > Could not connect to port, waiting... 1314. > Could not connect to port, waiting... 1314. > Could not connect to port, waiting... 1314. > > Until I stopped it using "cmd-period" on my Mac Book Pro. I do not have access to a Mac. That test suite works on Linux. Those messages _are_ normal when the test starts up, but you should have seen a lot more messages after that. The MaClientServerTestCase fullSuite takes a total of 16 seconds to run. You will have 3 additional images spawned. > I assume this is not standard behavior, and I don't know how to proceed from here to get Magma working in Pharo. I'm still learning Smalltalk/Pharo/Seaside and would really like to use Magma with it but have yet not been able to do so, despite trying the different ways to get Magma loaded (including Miguel Coba's ConfigurationOfMagma). > Can you give me any suggestions? Use the official installation scripts provided on the wiki page. - Chris > > - Marco A. > > On Apr 19, 2011, at 6:08 PM, Chris Muller wrote: > >> Magma 1.2 is now finally released for Squeak 4.2, Pharo 1.1 and Pharo >> 1.2. This new release offers improved performance thanks to >> minimizing the problem associated with finalization, as well as >> avoiding Squeak's slow become except once every 30 seconds. See >> >> http://wiki.squeak.org/squeak/6163 >> >> for release-notes details. >> >> I just went through all of the wiki pages and fixed / updated several >> of them, including new, clean, one-click installation scripts for for >> Pharo: >> >> http://wiki.squeak.org/squeak/2657 >> >> Squeak users may install with one-click directly from the SqueakMap >> Catalog user-interface. I hope Pharo will consider bringing this back >> into a future version; SqueakMap already has several projects that >> load from Metacello. >> >> I also realized several of Magma's special capabilities have been >> undocumented. I've now documented them. >> >> http://wiki.squeak.org/squeak/6164 >> >> This release is, exactly, one year since Magma 1.1, thank you for your >> patience. As before, support for Magma is described at: >> >> http://wiki.squeak.org/squeak/5818 >> _______________________________________________ >> Magma mailing list >> Magma(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/magma > > ------------------------------------------------------ > Marco A. Gonzalez, President > Amagavi, Inc. > Developer of database-driven web sites > > web: http://www.amagavi.com/ > email on iPhone: marcoinc(a)mac.com > cell: 202-222-5137 > > > > >

2 1

Pharo support for magma repositories
by Markus Fritsche 02 May '11

02 May '11

Hello, I registered a project at squeaksource: http://www.squeaksource.com/MagmaPharoSupport.html In my pharo image ;-) (I will check loading in a clean pharo image in a bit) this enables using (local, server not yet tested) magma repositories with the Pharo version of Monticello. It also alters the cleanup-method of MagmaSession to be working with Pharo (PointerFinder vs. ProtoObject>>#pointersTo). If anyone wants to join the project, you're welcome. Pharo version: Pharo1.3a Latest update: #13177 Magma: Ma client server cmm.217 Ma base additions cmm.187 Magma server cmm.425 Kind regards, Markus Fritsche

3 8

Re: ConfigurationOfMagma with support for Magma 1.2 and symbolic versions
by Miguel Cobá 01 May '11

01 May '11

Hi Marco, this is a problem caused by running the update process on a Pharo image. The update process is enabled only on PharoCore image precisely to avoid this problem, that is, that the update process break some package installed (or some overriden method from some package) by updating the method with an uncompatible version. The problem here is that the class SHParserST80 isn't anymore in the image and is used by OContext of the package OCompetion. You can open a ticket with this problem in the issue tracker in order to not forget it. Cheers El dom, 01-05-2011 a las 10:31 -0400, Marco A. Gonzalez escribió: > First, Thank you Miguel and Chris for working to get Magma working with Pharo. > > I ran into the following problem while attempting to get Magma installed into Pharo. After updating the image to version 12351, and I try to type anything into the Workspace window, I get a dialog with the following message: > MessageNotUnderstood: AnObsoleteSHParserST80>>rangesIn:classOrMetaClass:workspace:environment: > > I don't know where to go from there. I'm stuck. What's the best way to report this? Who do I report it to? Is there another one-click that I can use Magma with? > > Here's what to do to reproduce the problem. > > 1. Download Pharo 1.2.1 one-click image (standard VM) from http://www.pharo-project.org/pharo-download/ > NOTE: I wanted to use the one-click because I know how to deploy it on my web host and I don't know how to deploy a non-one-click image. > > 2. In a Workspace window, I evaluated the following: > SystemVersion newVersion: 'Pharo1.2.2a'. > > (this didn't appear to do anything) > > 3. From the World menu, choose System > Software Update > It took a few minutes, less than 5 minutes I think. Then a dialog window titled "Information" displayed with "6 new update file(s) processed." in the content area. > > 4. Then when I went to install Magma by typing into the Workspace window, the error message appeared. > > > - Marco A. > > On Apr 27, 2011, at 12:35 PM, Miguel Cobá wrote: > > > Hi all, > > > > I'm glad to announce a new version of ConfigurationOfMagma with support > > for Magma 1.2. This configuration has been tested on > > > > PharoCore 1.1.x > > PharoCore 1.2.x > > > > Thank you very much to Chris Muller who, as always, is working hard to > > keep Magma running on Squeak and Pharo. I used the same versions of > > packages he used in his scripts for Squeak in order to update the > > configuration. > > > > You must download the latest PharoCore image or update a existing one > > before installing Magma, as Magma needs some changes that were applied > > to Pharo post-release and are available in the update stream. > > > > > > Pharo 1.1.x > > ------------ > > > > Download PharoCore 1.1.2 from: > > > > https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip > > > > Update it if necessary and save it. > > > > > > Pharo 1.2.x > > ------------ > > > > You have two options: > > > > 1. Take a released 1.2.1 from: > > > > http://www.pharo-project.org/pharo-download/stable-core > > > > This is actually image update 12345. Evaluate: > > > > SystemVersion newVersion: 'Pharo1.2.2a'. > > > > update the image (it will update to 12350, at this time) and save it. > > > > 2. Take a snapshot of the upcoming 1.2.2 release of Pharo 1.2.x line > > from: > > > > https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip > > > > update the image (it will update to 12350, at this time) and save it. > > > > > > Install Magma > > -------------- > > > > Ok, now you have an updated image. Load the configuration by evaluating: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfMagma'; > > load. > > > > And depending on which of client, server or the full suite of Magma do > > you want, evaluate: > > > > - Magma client > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Client'. > > > > > > - Magma server > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Server'. > > > > - Magma tester > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Tester'. > > > > For example, to load the full magma suite evaluate: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfMagma'; > > load. > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Tester'. > > > > This will load client, server and test of Magma. > > > > > > Running tests > > ------------- > > To run the tests evaluate: > > > > MagmaTestCase allowWriteBarrier: false. > > MagmaTestCase fullSuite maDebug. > > > > > > Stable versions > > --------------- > > > > This release of ConfigurationOfMagma includes support for Metacello's > > symbolic versions. Currently the #stable version of Magma is configured > > like this: > > > > Pharo version #stable version > > ------------- --------------- > > Pharo 1.1.x 1.2 > > Pharo 1.2.x 1.2 > > Pharo 1.3.x 1.2 > > > > That is, Magma 1.2 is the #stable version for Pharo 1.1, Pharo 1.2 and > > Pharo 1.3. > > > > Known issues > > -------------- > > > > Magma 1.2 loads correctly and appears to work for the basic things > > (create a repo, add data, commit, etc) in PharoCore 1.3 and Pharo 1.3, > > but the full suite hasn't ran correctly in the current unstable Pharo. > > So use Magma 1.2 on Pharo 1.3 on your own risk and not for production > > yet. When the issues (including the Transcript revert that should happen > > in Pharo soon) are addressed, a new announce will be made for Magma on > > Pharo 1.3 > > > > Any feedback welcome. > > > > Enjoy. > > -- > > Miguel Cobá > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > > > > > _______________________________________________ > > Magma mailing list > > Magma(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/mailman/listinfo/magma > > > > > -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

1 0

Difficulties setting up Magma Monticello Repository
by Markus Fritsche 30 Apr '11

30 Apr '11

Hello, I tried to set up a remote repository on a networked machine. When I define a repository (local or remote) I get a DNU for Dictionary>>#indexOf: coming from MCRepositoryInspector>>#versionSelection versions is a Dictionary, in the other Repository, it's a nested Array. I use Pharo1.3a Latest update: #13177 (but I also tried it with Squeak 4.2) and the 1.2alpha1.mcm from the MagmaTester repository. Regards, Markus

2 3

← Newer
1
...
4
5
6
7
8
9
10
...
73
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma