March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Cocoa Squeak VM 5.7.4.1 (non-Cog) released

by Igor Stasenko

On 9 March 2011 09:31, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Mar 9, 2011, at 9:16 AM, Noury Bouraqadi wrote: > >> Thanks Esteban. >> >> BTW, I was expecting to find it on Â hudson server. I think we should have everything gathered there. >> >> > Not yet. > > the day has just 24 hours... > yes.. Esteban, You are the first in a line. :) > Â Â Â Â Marcus > > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Best regards, Igor Stasenko AKA sig.

March 9, 2011

Re: [Pharo-project] InterpreterSimulator reloaded

by Pavel Krivanek

Hi Stef, yes. I would chnage the packages on SqueakSource directly but in case of VMMaker we must pay attention to compatibility of forks etc. If I look at ConfigurationOfVMMaker hacks, it is not the right way how the interfork project should be done. -- Pavel On Wed, Mar 9, 2011 at 10:04 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks pavel > These are the changes you changed to david? so normally we do have to take actions? > > Stef > > On Mar 8, 2011, at 11:25 PM, Pavel Krivanek wrote: > >> I collected the changes from the image. See the attachment. >> >> To load the simulator in Pharo 1.3 do: >> >> Gofer new >> Â Â squeaksource: 'MetacelloRepository'; >> Â Â package: 'ConfigurationOfVMMaker'; >> Â Â load. >> >> (ConfigurationOfVMMaker project version: '1.5') load. >> >> proceed all deprecation warnings... >> load the attached fix. >> run the simulator: >> >> (InterpreterSimulator new openOn: 'cuis.image') test >> >> A good option is the Juan's small Cuis image (1.9MB with some next >> shrinking). The classical mini.image doesn't work on this version of >> the interpreter. >> >> Cheers, >> -- Pavel >> >> >> >> On Tue, Mar 8, 2011 at 10:47 PM, Pavel Krivanek >> <pavel.krivanek(a)gmail.com> wrote: >>> Hi, >>> >>> I tried to make the IneterpreterSimulator working on and with latest >>> images. The result is a Pharo image that you can download here: >>> >>> https://gforge.inria.fr/frs/shownotes.php?release_id=5897 >>> >>> It is still far from perfect however it can be used for simulations of >>> small headless images etc. It would be great if some VM guy will help >>> with integration of the changes. >>> >>> Cheers, >>> -- Pavel >>> >> <InterpreterSimulatorFix.1.cs> > > >

March 9, 2011

Re: [Pharo-project] PharoOneClick .lnk file

by Tudor Girba

+1. Doru On 9 Mar 2011, at 10:32, Geert Claes wrote: > > Torsten Bergmann wrote: >> >> I expect a windows user to be more satisfied with a typicall installer >> that also set up program group, ... >> and allows also to uninstall. And this installer download is also smaller >> than the OneClick since Linux/Mac VMs are not necessary. >> > > I don't think we need to have a full blown installer which creates a > shortcut to the program group with an uninstaller. I would prefer your > suggestion to simply put the Pharo.exe on the top level. I like the fact > OneClick has Windows, Mac and Linux i none download and I don't think the > size is a problem at all. > > -- > View this message in context: http://forum.world.st/PharoOneClick-lnk-file-tp3342350p3343156.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

March 9, 2011

Re: [Pharo-project] PharoOneClick .lnk file

by Geert Claes

Torsten Bergmann wrote: > > I expect a windows user to be more satisfied with a typicall installer > that also set up program group, ... > and allows also to uninstall. And this installer download is also smaller > than the OneClick since Linux/Mac VMs are not necessary. > I don't think we need to have a full blown installer which creates a shortcut to the program group with an uninstaller. I would prefer your suggestion to simply put the Pharo.exe on the top level. I like the fact OneClick has Windows, Mac and Linux i none download and I don't think the size is a problem at all. -- View this message in context: http://forum.world.st/PharoOneClick-lnk-file-tp3342350p3343156.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 9, 2011

Re: [Pharo-project] InterpreterSimulator reloaded

by StÃ©phane Ducasse

Thanks pavel These are the changes you changed to david? so normally we do have to take actions? Stef On Mar 8, 2011, at 11:25 PM, Pavel Krivanek wrote: > I collected the changes from the image. See the attachment. > > To load the simulator in Pharo 1.3 do: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfVMMaker'; > load. > > (ConfigurationOfVMMaker project version: '1.5') load. > > proceed all deprecation warnings... > load the attached fix. > run the simulator: > > (InterpreterSimulator new openOn: 'cuis.image') test > > A good option is the Juan's small Cuis image (1.9MB with some next > shrinking). The classical mini.image doesn't work on this version of > the interpreter. > > Cheers, > -- Pavel > > > > On Tue, Mar 8, 2011 at 10:47 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: >> Hi, >> >> I tried to make the IneterpreterSimulator working on and with latest >> images. The result is a Pharo image that you can download here: >> >> https://gforge.inria.fr/frs/shownotes.php?release_id=5897 >> >> It is still far from perfect however it can be used for simulations of >> small headless images etc. It would be great if some VM guy will help >> with integration of the changes. >> >> Cheers, >> -- Pavel >> > <InterpreterSimulatorFix.1.cs>

March 9, 2011

[Pharo-project] SmalltalkEcole: Slides of Tuesday

by Marcus Denker

Theo DâHondt: SLIP: a simple language implementation platform http://dl.dropbox.com/u/2753738/SLIP-LILLE%208-03-2011.pdf Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 9, 2011

Re: [Pharo-project] Fwd: [squeak-dev] sustainable Monticello

by StÃ©phane Ducasse

thanks If somebody want to get the code and prepare it for pharo this will help. Stef On Mar 8, 2011, at 10:38 PM, Janko MivÅ¡ek wrote: > > > -------- Original Message -------- > Subject: [squeak-dev] sustainable Monticello > Date: Tue, 8 Mar 2011 15:33:19 -0600 > From: Chris Muller <asqueaker(a)gmail.com> > Reply-To: ma.chris.m(a)gmail.com, The general-purpose Squeak developers > list <squeak-dev(a)lists.squeakfoundation.org> > To: squeak dev <squeak-dev(a)lists.squeakfoundation.org> > > This will probably be a long post, but I would like to tell you about > the Monticello upgrades I'm about to move to the trunk. > > Monticello has several repository types: > > MCRepository #('creationTemplate' 'storeDiffs') > MCDictionaryRepository #('description' 'dict') > MCFileBasedRepository #('cache' 'allFileNames') > MCDirectoryRepository #('directory') > MCCacheRepository > #('packageCaches' 'seenFiles') > MCSubDirectoryRepository #() > MCFtpRepository #('host' 'directory' > 'user' 'password' 'connection') > MCHttpRepository #('location' 'user' > 'password' 'readerCache') > MCSMCacheRepository #('smCache') > MCGOODSRepository #('hostname' 'port' > 'connection') > MCWriteOnlyRepository #() > MCSMReleaseRepository #('packageName' > 'user' 'password') > MCSmtpRepository #('email') > > but MCFileBasedRepository is the one that has been given all of the > focus, the other repository types have been ignored over the years. > MCHttpRepository is the one that interfaces with SqueakSource, and > MCDirectoryRepository are pretty much the only types being used. > > I know this because external users of MCRepository API, like the > Repository-browser tools and MC-Configurations and Installer; these > are all using API's that are specific to MCFileBasedRepository - not > generally understood by the other repository-types or the abstract API > in MCRepository. > > This is worthy of concern because of the access-limitations of a > MCFileBasedRepository. Unlike a MCGOODSRepository, for example, a > file-system-based repository cannot efficiently meet the demands of > being a MCRepository without, at some points, needing to enumerating > ALL version names (files) in its file-system location. > > As the number of versions in a repository reaches 1-million and > beyond, performance will grind to a halt due to the number of files > that must be constantly downloaded into RAM (another area of > unscalability and unsustainability related to FileBased Repository's). > A purging of old versions could be done, but a philosophy of > Monticello, from the outset, has been that repository's are intended > to contain "all" of version history. > > I have therefore reworked the MCRepository API's and external tools to > talk using only an API that is understood by any repository that > implements the methods identified as #subclassResponsibility in > MCRepository. This minimally-required API is now: > > #allPackageNames - answer a list of package names in this repository. > #basicStoreVersion: - add a Version to this repository. > #includesVersionNamed: - does a version with this name exist in this > repository? > #versionNamed: - answer the first Version object with the given name. > #versionNamesForPackageNamed: - answer the version names for the > given package name. > #versionWithInfo:ifAbsent: - answer the Version object with the > given unique VersionInfo > > In deference to the limitations of FileBasedRepository's, we only ask > for the _names_ of things rather than the whole object, because the > names are all that is needed to satisfy tool requirements, except in > cases where we need a single Version object (like loading). FileBased > cannot access the Version objects quickly, just the (file)names (incl. > author & version-number). > > During the process of this refactoring, I was able to signficantly > improve the coherence of the code. It was really, really bad in some > areas. > > I've also verified the viability of this API by updating > MCMagmaRepository, and demonstrating using Magma as a > totally-sustainable and scalable MC repository. Employing a > Magma-based Repository also affords some additional benefits, which I > will describe in a separate follow-up mail. > > I think SqueakSource will eventually have to change to something more > scalable. At least now we have have a viable alternative, and with > much cleaner MC code in the process. > > Please load my latest versions of Monticello, > MonticelloConfigurations, Installer and Tests from the Inbox and let > me know if you experience any issues. You should not see any > difference in day-to-day operations. > > - Chris > > >

March 9, 2011

[Pharo-project] Issue 3795 in pharo: MC repository

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com New issue 3795 by stephane...(a)gmail.com: MC repository http://code.google.com/p/pharo/issues/detail?id=3795 -------- Original Message -------- Subject: [squeak-dev] sustainable Monticello Date: Tue, 8 Mar 2011 15:33:19 -0600 From: Chris Muller <asqueaker(a)gmail.com> Reply-To: ma.chris.m(a)gmail.com, The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> To: squeak dev <squeak-dev(a)lists.squeakfoundation.org> This will probably be a long post, but I would like to tell you about the Monticello upgrades I'm about to move to the trunk. Monticello has several repository types: MCRepository #('creationTemplate' 'storeDiffs') MCDictionaryRepository #('description' 'dict') MCFileBasedRepository #('cache' 'allFileNames') MCDirectoryRepository #('directory') MCCacheRepository #('packageCaches' 'seenFiles') MCSubDirectoryRepository #() MCFtpRepository #('host' 'directory' 'user' 'password' 'connection') MCHttpRepository #('location' 'user' 'password' 'readerCache') MCSMCacheRepository #('smCache') MCGOODSRepository #('hostname' 'port' 'connection') MCWriteOnlyRepository #() MCSMReleaseRepository #('packageName' 'user' 'password') MCSmtpRepository #('email') but MCFileBasedRepository is the one that has been given all of the focus, the other repository types have been ignored over the years. MCHttpRepository is the one that interfaces with SqueakSource, and MCDirectoryRepository are pretty much the only types being used. I know this because external users of MCRepository API, like the Repository-browser tools and MC-Configurations and Installer; these are all using API's that are specific to MCFileBasedRepository - not generally understood by the other repository-types or the abstract API in MCRepository. This is worthy of concern because of the access-limitations of a MCFileBasedRepository. Unlike a MCGOODSRepository, for example, a file-system-based repository cannot efficiently meet the demands of being a MCRepository without, at some points, needing to enumerating ALL version names (files) in its file-system location. As the number of versions in a repository reaches 1-million and beyond, performance will grind to a halt due to the number of files that must be constantly downloaded into RAM (another area of unscalability and unsustainability related to FileBased Repository's). A purging of old versions could be done, but a philosophy of Monticello, from the outset, has been that repository's are intended to contain "all" of version history. I have therefore reworked the MCRepository API's and external tools to talk using only an API that is understood by any repository that implements the methods identified as #subclassResponsibility in MCRepository. This minimally-required API is now: #allPackageNames - answer a list of package names in this repository. #basicStoreVersion: - add a Version to this repository. #includesVersionNamed: - does a version with this name exist in this repository? #versionNamed: - answer the first Version object with the given name. #versionNamesForPackageNamed: - answer the version names for the given package name. #versionWithInfo:ifAbsent: - answer the Version object with the given unique VersionInfo In deference to the limitations of FileBasedRepository's, we only ask for the _names_ of things rather than the whole object, because the names are all that is needed to satisfy tool requirements, except in cases where we need a single Version object (like loading). FileBased cannot access the Version objects quickly, just the (file)names (incl. author & version-number). During the process of this refactoring, I was able to signficantly improve the coherence of the code. It was really, really bad in some areas. I've also verified the viability of this API by updating MCMagmaRepository, and demonstrating using Magma as a totally-sustainable and scalable MC repository. Employing a Magma-based Repository also affords some additional benefits, which I will describe in a separate follow-up mail. I think SqueakSource will eventually have to change to something more scalable. At least now we have have a viable alternative, and with much cleaner MC code in the process. Please load my latest versions of Monticello, MonticelloConfigurations, Installer and Tests from the Inbox and let me know if you experience any issues. You should not see any difference in day-to-day operations. - Chris

March 9, 2011

Re: [Pharo-project] PharoOneClick .lnk file

by Marcus Denker

On Mar 8, 2011, at 11:21 PM, Torsten Bergmann wrote: >> .. and this should probably be Pharo.exe with a nice Pharo icon :) > > I already created a custom Pharo VM (a standard one and a > Cog VM, both with Pharo icon and resource section) > and gave this to Marcus. > I guess he just has to find the time to include it in the One click. yes... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 9, 2011

Re: [Pharo-project] [ANN] Cocoa Squeak VM 5.7.4.1 (non-Cog) released

by Marcus Denker

On Mar 9, 2011, at 9:16 AM, Noury Bouraqadi wrote: > Thanks Esteban. > > BTW, I was expecting to find it on hudson server. I think we should have everything gathered there. > > Not yet. the day has just 24 hours... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 9, 2011