- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: I'm interesting in knowing more on your atomic loading
by StÃ©phane Ducasse July 3, 2008

July 3, 2008

Begin forwarded message: > From: Matthew Fulmer <tapplek(a)gmail.com> > Date: July 3, 2008 8:38:24 PM CEDT > To: stephane ducasse <stephane.ducasse(a)free.fr> > Cc: Matthew Fulmer <tapplek(a)gmail.com>, Keith Hodges <keith_hodges(a)yahoo.co.uk > > > Subject: Re: I'm interesting in knowing more on your atomic loading > > On Thu, Jul 03, 2008 at 07:21:21PM +0200, stephane ducasse wrote: >> Hi matthew >> >> how can i learn about your atomic loading? >> >> Stef > > ===== History ===== > > Atomic loading is a feature Colin Putney implemented for MC2, > then released as a separate, quite unstable library: > SystemEditor > > http://www.squeaksource.com/SystemEditor/ > > Goran and I picked up this library as a core component of > DeltaStreams, and we fixed many bugs it had with loading > different combinations of things, due to not being tested in > production. In the meantime, Keith Hodges wrote a new package > loader for Monticello 1.5 that hooked into SystemEditor to take > advantage of it's atomic loading property. It hardly worked at > all, but the principle was there. See the class MCPackageLoader2 > in Monticello 1.5: > > http://www.squeaksource.com/mc/ > > I have since stopped working on DeltaStreams and started working > heavily with Keith in improving the basic tools in the image and > making new ones. Since I was already familiar with SystemEditor > due to my work on DeltaStreams, I volunteered to work on package > loader 2. I fixed a dozen or so bugs in both package loader 2 > and SystemEditor, and now it is able to load quite a few > packages. It is still beta phase though. It is not yet able to > cope with the following: > > Byte/Word/Weak classes > Traits > Tweak classes > > I'm fixing those inadequacies in the order listed. Once they are > fixed, we will release PackageLoader2 as the default in > Monticello, and increment the version number of Monticello to > 1.6. > > ===== How it works ==== > > SystemEditor has a set of classes (editor classes) that respond > to the same protocol as Class, Metaclass, MethodDictionary, > ClassOrganizer, SystemDictionary, and other related core > classes. Each one acts as an "editor" on an existing object in > the system. These editors respond to the same protocol as the > object they edit, but maintain changes internally, usually as a > list of additions/removals. When the time comes to commit the > changes (See SystemEditor>>commit), all these editors are passed > a MigrationTransaction object, and are asked to submit the old > and new copy of the object they are editing, which will be > swapped at commit time. When all objects have done this, > MigrationTransaction builds two arrays: one of old objects, and > one of new, and invokes the primitive > Array>>exchangeElementIdentityWith: , which does a bulk identity > swap (see MigrationTransaction>>commit). Everything that needs > to change is swapped: Recompiled classes, instances of those > classes, new methodDictionaries for classes that don't need > recompiling, Smalltalk, the SystemDictionary instance, > ClassOrganization instances, and so on, all during one > primitive. > > ===== Status ===== > > I'm fairly confident in Monticello1.6-beta, as it currently > exists. I use it as my default loader in all of my images, > except when I am dealing with Tweak in my croquet images. > > To try it out, do the following: > HTTPSocket httpFileIn: 'installer.pbwiki.com/f/LPF.st'. > Installer install: 'Monticello16-Beta' > > This loads LevelPlayingField (= Installer and MC1.5) and then > runs my script to load SystemEditor and activate PackageLoader2. > > Pages you may want to read: > > LevelPlayingField: a script to load Installer and MC1.5 into > most any image in use: > http://installer.pbwiki.org/LevelPlayingField > > The script that loads MC1.5: > http://installer.pbwiki.org/LevelPlayingField-Monticello15 > > The script that activates MCPackageLoader2 (it is under > "Contributed Scripts" in the sidebar) > http://installer.pbwiki.org/Monticello16-Beta > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ >

1 0

[Pharo-project] About a file abstraction layer
by StÃ©phane Ducasse July 3, 2008

July 3, 2008

Hi guys With mike we also discussed about URI and the way sophie people used to abstract away from the file system. The idea (may be I'm summarizing a bit wrong), is to use URI consistently even to access local file. He told me that with this practice they got away from platform dependent code in Sophie. Mike also rewrote and clean a large part of the network-package. We got some trouble to load it in pharo since this was not made to be loaded in pharo. Mike will work on a loadable version. Stef

2 2

[Pharo-project] Re: Pharo Smalltalk
by StÃ©phane Ducasse July 3, 2008

July 3, 2008

> Couldn't you do this on Squeak? but we are doing that starting with squeak 3.9 :) > How much Pharo will differ from Squeak? We do not know but it will. > Do you intend to rebase with a new VM or do you intend to just > improve Smalltalk code? For the moment we do not have the expertise to change the VM and we will reuse the one of Squeak. There will be also a MIT VM with a JIT so :) And also Squeak VM running on ipod :) > What about license issues? I've seen Pharo is MIT. Yes all the code of pharo will be MIT. We will only include MIT code and all the commiters have to sign the agreement. > I've seen many developers and a busy mailing list, I expect more improvements to come when the people interested by software development will join. For the moment we are in warm up mode. > what will be the future of Squeak? I do not know. FunSqueak ;D >> Well what I will have in mind depends on what you reply to the >> above questions :P > > Thanks for your reply.

1 0

[Pharo-project] Re: Pharo Smalltalk
by StÃ©phane Ducasse July 3, 2008

July 3, 2008

Hi bruno > I've head about your new project Pharo. Good :) > I'm the author of Smalltalk YX (Syx) http://syx.googlecode.com. I had a look a while back. > Another developer recently developed a VM inspired to Syx and now > we're going to merge the projects, since we have the same vision. Excellent! Join forces :) > This is the post in the mailing list: http://groups.google.com/group/syx-discuss/browse_thread/thread/55507afadab… > > I'd like to know the main purposes of your new implementation, Produce a good Smalltalk with nice, well documented and libraries so that people can develop cool projects and others can learn from the system. We want to remove cruft from the system. > are you interested in a possible collaboration? yes! Tell us what you have in mind. > I haven't seen any source code yet. I think our two projects have > many things in common. The code is available on the ugly pharo web page http://pharo.gforge.inria.fr/ Stef > > > Let me know please. > Best regards, > > - -- > http://syx.googlecode.com - Smalltalk YX > http://lethalman.blogspot.com - Thoughts about computer technologies > http://www.ammazzatecitutti.org - Ammazzateci tutti > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFIbXq1w9Qj+8Kak3ERAmZBAJ4ng2GLUD+rVuuhu2kAFjeKozyW5QCeO+WG > /tnA/LYuTonX9bzJDZBu5bs= > =og7s > -----END PGP SIGNATURE-----

1 0

[Pharo-project] Discussions with mike (one)
by StÃ©phane Ducasse July 3, 2008

July 3, 2008

hi guys (and marcus in particular) I'm at RMLL and we are discussing with mike about infrastructure for pharo. I will summarize some of the discussions in the following posts. Mike suggested that we really use the NewCompiler for Pharo. Marcus can you comment on that. Stef

3 2

Re: [Pharo-project] UI plans Question
by michael_atkisson＠comcast.net July 3, 2008

July 3, 2008

Perhaps I don't know the right terminology. Anyway I was thinking of a ui environment like the commercial smalltalks. Where when you started up Pharo you would have a main Window, from there any window you opened up such as a browser would be independent from the main window, it would open up outside the bounds of the main window and not be constrained by the main window. -------------- Original message ---------------------- From: "Serge Stinckwich" <serge.stinckwich(a)doesnotunderstand.org> > No i don't think so. What is your idea ? > > 2008/7/2 <michael_atkisson(a)comcast.net>: > > Are there any plans to make it possible to be able to move windows out of > > the main ui environment window. > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > Serge Stinckwich > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

4 3

[Pharo-project] issue 26 / squeak 7073
by Norbert Hartl July 3, 2008

July 3, 2008

I've uploaded a new slice which incorporates the squeak update changes for version 7073. SLICE-squeakUpdate7073-noha.5 I can't change the status of the ticket as google is not allowing me to do any single action today :) First I got captchas for submitting issues and now I'm locked out. "You have performed the requested action too many times in a 24-hour time period. Or, you have performed the requested action too many times since the creation of your account." The last sentence makes me a bot afraid :) Norbert

2 2

[Pharo-project] 3.9.1, version numbers and fixes
by Norbert Hartl July 3, 2008

July 3, 2008

I'm a little bit confused. I started to have a look at the squeak fixes of 3dot10 we like to integrate. Looking at the version number I marked all version number up to 7075 as being duplicate (in the issue trackr) as we started from 3.9.1 which is 7075. But now I think I misunderstand something. I tried to merge squeak version 7076 into pharo. I did some stuff manually to be able to merge the monticello packages of that release. But the changes are massive. It's collections, collectionstests and kernel. There are even changes for widestring which I don't found in previous updates. Can somebody explain where we started off and what needs to be included. Pharo seems to be completely out of sync with 3.10. Norbert

3 2

[Pharo-project] Broken tests in Pharo-dev
by Oscar Nierstrasz July 3, 2008

July 3, 2008

Hi Folks, Just for phun, I checked the status of broken tests in the pharo-dev image. Since the Test Runner froze up on me, I tried to find out which are the offending test packages. Here is what I found: - Installer-Test brings up the Pre-Debugger due to non-existent classes (ClassClonerTestResource etc.) - Refactoring-Engine-Testing freezes with a Syntax Error window popping up. (Didn't yet find out which test is causing this.) - VB-Regex-Test stops due to a self halt in RxParserTest>>testMatchesInwW The remaining tests run, with a few uglies. Some tests are creating OB Package Browser windows and not cleaning them up. There are also some tests that prompt for user input. Otherwise there are 2329 run, 2302 passes, 15 expected failures, 12 failures, 0 errors, 0 unexpected passes amongst the remaining tests. Once we get core pharo cleaned up, it would be nice to get the tests running in pharo-dev too. - on

2 1

[Pharo-project] Fix for Issue 113 in PharoInbox
by Serge Stinckwich July 3, 2008

July 3, 2008

Look at : http://code.google.com/p/pharo/issues/detail?id=113 -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

1 0