July 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] Win32 Pharo setup 0.0.0.5. (based on Pharo0.1-10371)
by Torsten Bergmann July 7, 2009

July 7, 2009

A new win32 setup is available at https://gforge.inria.fr/frs/download.php/22616/setup_pharo_0.0.0.5.exe which is based on pharo0.1-10371dev09.07.1.zip (see http://lists.gforge.inria.fr/pipermail/pharo-project/2009-July/010436.html Previous Win32 Setups are still available on: https://gforge.inria.fr/frs/?group_id=1299 Have fun Torsten -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

1 0

[Pharo-project] Loads of Pharo development process questions
by Reinout Heeck July 7, 2009

July 7, 2009

I'm having trouble wrapping my head around how the Pharo development/ maintenance process is supposed to work. Most of these seem to be missing info on the wiki which merely need fleshing out there, I would update the wiki pages myself if only I knew what to write... Please bear in mind that I'm a newbie to Squeak, so some of these questions may be rather naive. One of my motivations is to evaluate the future viability of Pharo as a vehicle for commercial applications and whether it warrants to lobby for resources being allocated to its development. So here goes: The wiki mentions 'kernel' and 'MiniImage' as not being in scope of Pharo. What does that entail, does this mean that discussions about allowing nil in Sets are out of scope? What is the status of the dev-image? As delivered the tools are broken (because context menus on the source pane raise an UHE that is induced by OB-Enhancements, issue 904), is it actively used by the main committers or is the core image the place to be? Even more confusingly the above issue has been marked as fixed this night but if I do a World->System->Software Update the bug persists in my image. When I looked into fixing it myself I got confused (because I looked at InstallScript.st), it seems the code comes from various repositories -- not a single Pharo respository/branch. Are these various repositories Pharo-specific and maintained over Pharo-Inbox or do I need to submit fixes to different places? I guess as a Squeak newbie I need a high-level overview on the wiki on how code and fixes flow within Pharo, towards Squeak and towards the various tool maintainers (and back to Pharo of course, the upstream/ downstream story). What is the story when such tools and Pharo become incompatible and need to fork (or are they already forked)? Is there a vision on long-term support? Pharo wants to be agile and be free to change at will (IMO a good decision) but if it is to be viable at my job there need to be versions that receive long-term support (the 'professional' aspect of Pharo). At least bug fixes (and hopefully speed enhancements) need to be ported back to an 'LTS' release for quite a while (I'm thinking three to four years here) and on a consistent/reliable basis if Pharo is to be viable for the kind of projects I work on. Porting our projects (and project specific tool enhancements) forwards turns out to be very expensive (even in a 'conservative' environment like VisualWorks) so a mechanism needs to be in place to avoid needing too many porting moments over the lifetime of our projects (think 10+ years). The process of updating the dev image is excruciatingly slow, is this normal? The process seems to be CPU bound and takes ages for what I consider a small amount of changes - in its current state it would be unusable for the process we use at work, it will need to be brought back to well under a minute as opposed to the twenty (or so) minutes it took me yesterday. What is the background and vision for the future on this issue? Let me finish with a quick and easy newbie question: where do I find the profiler tools for Pharo? Thanks! Reinout -------

7 14

[Pharo-project] [ANN][Dev-Images] July 2009 versions
by Damien Cassou July 6, 2009

July 6, 2009

Hi, I've just uploaded new dev and web images based on Squeak3.9.1-7075, Squeak3.10.2-7179 and Pharo0.1-10371. More information and download: http://damiencassou.seasidehosting.st/Smalltalk/squeak-dev Pharo-based images can be downloaded at: http://pharo-project.org/pharo-download Download statistics at http://damiencassou.dabbledb.com/publish/dev-imagesdownloads Changes in this version: --------------------------- - Pharo images are based on version 10371 - New version of OCompletion for Pharo - Lots of bug fixes in Seaside, Pier and Magritte Contained packages: ------------------------ This image contains the following packages (some packages are only in the squeak-web image): Aida version 5.6 Algernon version 1.2 AST version 164 AutomaticMethodCategorizer version 0.25 AutomaticMethodCategorizerOB version 0.2 DynamicBindings version 2.7 eCompletion version 0.102 eCompletion-Traits version 0.1 eCompletionOmniBrowser version 0.5 Installer version 4.3 Installer-Core version 4.3.313 Installer-Formats version 4.3.3 Installer-Scripts version 4.3.8 KomHttpServer version 7.0.45 KomServices version 1.19 Magritte-Model version 1.1.1.349 Magritte-Seaside version 1.1.1.302 Magritte-Tests version 1.1.1.153 OB-Enhancements version 0.328 OmniBrowser version 0.447 OmniBrowser-Algernon version 0.5 OmniBrowser-Full version 0.27 OmniBrowser-Morphic version 0.88 OmniBrowser-Refactory version 145 OmniBrowser-Regex version 0.18 OmniBrowser-Standard version 0.406 Pier version current Pier-Blog version 1.1.1.117 Pier-Documents version 1.1.1.15 Pier-EditorEnh version 1.1.1.48 Pier-Model version 1.1.1.328 Pier-Seaside version 1.1.1.419 Pier-Security version 1.1.1.141 Pier-Tests version 1.1.1.137 Polymorph EventEnhancements version 1.1 Polymorph Geometry version 1.1 Polymorph TaskbarIcons version 1.0 Polymorph ToolBuilder version 1.3 Polymorph Tools Diff version 1.3 Polymorph Widgets version 1.4 Refactoring Core version 48 Refactoring Spelling version 5 RoelTyper version 0.60 RSRSS2 version 2.8.4.12 Scriptaculous version 2.8.4.250 ScriptManager version 0.6 Seaside version 2.8.4.591 Seaside-Adapters-Core version pmm.2.mcz Seaside-Adapters-Swazoo version 9 Seaside-Squeak-Adapters version pmm.3.mcz SeasideAdaptersCompatibility version pmm.1.mcz Shout version 3.15-tween.72 ShoutWorkspace version 1-tween.4 SmaCC runtime version 13 Sport version 2.31 Squeak dev packages version 0.28 Squeak web packages version 0.2 SUnit-improved version 4.0.118 SUnitGUI-improved version 4.0.50 Swazoo version 2.1 Universes version 52 Universes OmniBrowser version 0.38 VBRegex version 1.9 YAXO version 14 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

4 6

[Pharo-project] Download URL changed??
by Damien Cassou July 6, 2009

July 6, 2009

Hi, I've just noticed that http://pharo-project.org/download has been changed to: http://pharo-project.org/pharo-download Is there a good reason? I used the first url in many emails and announcements. I think this will confuse people. Moreover, Google search also provides a link to the first url. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

3 2

[Pharo-project] Problem with fork
by Mariano Martinez Peck July 6, 2009

July 6, 2009

Hi folks! I am doing some benchmarks and I having problems with fork (I think). I have this method collect: collect |semaphores tr| semaphores := Array new: 10. tr := ThreadSafeTranscript new. tr open. 1 to: 10 do: [ :index | semaphores at: index put: Semaphore forMutualExclusion ]. 1 to: 10 do: [:i | [ tr show: 'one fork'; cr. (semaphores at: i) signal. ] fork ]. semaphores do: [:each | each wait ]. tr show: 'all forks proccesed'; cr. What I want is that the method collect returns when ALL of the forks created inside, are finished. Obviously in my real code, I don't do a transcript show: but another thing. I would expect something like this: one fork one fork one fork one fork one fork one fork one fork one fork one fork one fork all forks proccesed But the output is: all forks proccesed one fork one fork one fork one forkone fork one fork one fork one forkone fork one fork one fork one forkone fork So, I guess it isn't working :( I don't know too much about forks so any help is welcome! can be a problem with ThreadSafeTranscript ? If so, how could I test if my code is working as expected ? Thanks, Mariano

5 7

[Pharo-project] Issue 936: Traits package not browseable in Monticello
by Pavel Krivanek July 6, 2009

July 6, 2009

Traits package is not browseable in Monticello. http://code.google.com/p/pharo/issues/detail?id=936 It is the consequence of the patch in the issue 804 (Merging in presence of traits). Cheers, -- Pavel

1 0

[Pharo-project] Fwd: [squeak-dev] SkipLists removal
by Damien Cassou July 6, 2009

July 6, 2009

---------- Forwarded message ---------- From: Ken Causey <ken(a)kencausey.com> Date: Sat, Jul 4, 2009 at 8:08 PM Subject: [squeak-dev] SkipLists removal To: Squeak Devel List <squeak-dev(a)lists.squeakfoundation.org> Cc: stephane ducasse <stephane.ducasse(a)free.fr>, Tom Koenig <tomkoenig(a)mindspring.com> SkipLists contains code under SqueakL as well as under MIT. Â Two contributors have not signed the agreement and appear to be uncontactable. Â SkipLists are not used in the image and are easily extractable. Â To that end I have done so and published a new version of Collections without them and an external package. References: http://bugs.squeak.org/view.php?id=7359 http://source.squeak.org/trunk/Collections-klc.93.mcz http://www.squeaksource.com/SkipLists.html Ken -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

4 4

[Pharo-project] Alternative Linux VM link is not closure support
by Mariano Martinez Peck July 6, 2009

July 6, 2009

If you follow the link of "alternative" for Linux, you will get the link http://squeakvm.org/unix/ squeak-vm_3.10-5_i386.deb seems not to have the closure enables and you get the error: This interpreter (vers. 6502) cannot read image file (vers. 6504). This is confusing for new people. We should remove that link or put the same as the first one (exupery). cheers, Mariano

2 1

July 6, 2009

Begin forwarded message: > From: Pavel Krivanek <pavel.krivanek(a)gmail.com> > Date: July 6, 2009 2:26:56 PM CEDT > To: stephane ducasse <stephane.ducasse(a)free.fr> > Subject: issue 348 > > Hi Stef, > > I updated the issue http://code.google.com/p/pharo/issues/detail? > id=348 > > Cheers, > -- Pavel

1 0

[Pharo-project] clean out Undeclared
by Pavel Krivanek July 6, 2009

July 6, 2009

Hi, the patch in the issue http://code.google.com/p/pharo/issues/detail?id=637cleans out Undeclared in the image 10342. -- Pavel

2 1