[Pharo-dev] OpenBuildService
After hearing Esteban mention it, I investigated http://openbuildservice.org/ and it seems really exciting. IIUC, we can create one Fedora-style packag Spec file, and have Pharo built on just about all distributions. There is even a community server (https://build.opensuse.org/). I've set up an account there for test purposes and started playing. The initial results are at https://github.com/pharo-project/pharo-openbuildservice. I also wrote some notes at https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/OpenBuildService.md. I've gotten through the build process and I'm stuck on the installation step. - Cheers, Sean -- View this message in context: http://forum.world.st/OpenBuildService-tp4820143.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] Permission denied issue when moving Bloc to PharoExtras
---BeginMessage--- Hello all, Here are the Gofer invocations I used. The fetch is ok but the push ends-up in a ‘Permission denied’ error. what is wrong in my Gofer push invocation ? Thanks Cheers Alain Gofer it smalltalkhubUser: 'AlainPlantec' project: 'Bloc'; package: 'Bloc-Core'; package: 'Bloc-Core-MorphCompatibility'; package: 'Bloc-Halo'; package: 'Bloc-Halo-MorphCompatibility'; package: 'Bloc-Widgets'; package: 'ConfigurationOfBloc'; fetch. Gofer it smalltalkhubUser: 'PharoExtras' project: 'Bloc'; package: 'Bloc-Core'; package: 'Bloc-Core-MorphCompatibility'; package: 'Bloc-Halo'; package: 'Bloc-Halo-MorphCompatibility'; package: 'Bloc-Widgets'; package: 'ConfigurationOfBloc'; push. ---End Message---
Re: [Pharo-dev] GTSpotter and example previews
Hi, It's in the release because it is useful :). Indeed, some previews related to fonts do not render well, but you get the same problem in the Inspector. But, most previews are not that bad. See for example: [image: Inline image 1] But, there is another point. This mechanism allows people to hook their examples in the basic spotter. For example, Roassal examples can be found there. Cheers, Doru On Fri, Apr 17, 2015 at 12:48 AM, Nicolai Hess nicolaih...@web.de wrote: Why is this in the release? GTSpotter now shows the result of gtExamples in the preview. This looks so ugly. (for example browse the Examples cateogry for GLMCompositeBrick) If new features aren't mentioned anywhere, it is pretty difficult to test or to review them. -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] OpenBuildService
That would be a good step. I wanted to do that but didn't find the time. Norbert Am 17.04.2015 um 08:12 schrieb Sean P. DeNigris s...@clipperadams.com: After hearing Esteban mention it, I investigated http://openbuildservice.org/ and it seems really exciting. IIUC, we can create one Fedora-style packag Spec file, and have Pharo built on just about all distributions. There is even a community server (https://build.opensuse.org/). I've set up an account there for test purposes and started playing. The initial results are at https://github.com/pharo-project/pharo-openbuildservice. I also wrote some notes at https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/OpenBuildService.md. I've gotten through the build process and I'm stuck on the installation step. - Cheers, Sean -- View this message in context: http://forum.world.st/OpenBuildService-tp4820143.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] New User Question on Reddit
Hello Sean, I will be able to update the PPA on the weekend. Kind regards, Markus On 2015-04-17 00:58, Sean P. DeNigris wrote: https://news.ycombinator.com/item?id=9390760 I installed this for Ubuntu 12.04. When I fired it up, it requested I choose and build a source file (different from Pharo 3). Then when it started, it said, Pharo cannot locate the source file named /usr/lib/pharo-vm/PharoV40.sources. Any ideas what to do? TIA, Steve
Re: [Pharo-dev] GTSpotter and example previews
2015-04-17 10:28 GMT+02:00 Tudor Girba tu...@tudorgirba.com: Hi, It's in the release because it is useful :). Indeed, some previews related to fonts do not render well, but you get the same problem in the Inspector. But, most previews are not that bad. See for example: [image: Inline image 1] But, there is another point. This mechanism allows people to hook their examples in the basic spotter. For example, Roassal examples can be found there. Indeed, for this example it looks really good (and is useful). I was afraid all examples, rendering some UI-Component, would look so ugly. How it comes the other examples doesn't look like this one? Cheers, Doru On Fri, Apr 17, 2015 at 12:48 AM, Nicolai Hess nicolaih...@web.de wrote: Why is this in the release? GTSpotter now shows the result of gtExamples in the preview. This looks so ugly. (for example browse the Examples cateogry for GLMCompositeBrick) If new features aren't mentioned anywhere, it is pretty difficult to test or to review them. -- www.tudorgirba.com Every thing has its own flow
[Pharo-dev] communicating pharo 4.0
Hi, In case you were wondering about the details behind the visualization that came with the Pharo 4.0 announcement, here is a more detailed explanation: http://www.humane-assessment.com/blog/communicating-pharo-4-0 Cheers, Doru -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Permission denied issue when moving Bloc to PharoExtras
---BeginMessage--- yep! it works. Thanks Guille Alain On 17 Apr 2015, at 10:05, Guillermo Polito guillermopol...@gmail.com wrote: I see you're already there in the permission list. I think you should go to the monticello browser and add the pharo extras repository with your user and password. Then Gofer will be able to find your password to commit. Sorry I skipped that detail when giving you the scripts :/. Guille El vie., 17 de abr. de 2015 a la(s) 10:03 a. m., Alain Plantec via Pharo-dev pharo-dev@lists.pharo.org mailto:pharo-dev@lists.pharo.org escribió: Hello all, Here are the Gofer invocations I used. The fetch is ok but the push ends-up in a ‘Permission denied’ error. what is wrong in my Gofer push invocation ? Thanks Cheers Alain Gofer it smalltalkhubUser: 'AlainPlantec' project: 'Bloc'; package: 'Bloc-Core'; package: 'Bloc-Core-MorphCompatibility'; package: 'Bloc-Halo'; package: 'Bloc-Halo-MorphCompatibility'; package: 'Bloc-Widgets'; package: 'ConfigurationOfBloc'; fetch. Gofer it smalltalkhubUser: 'PharoExtras' project: 'Bloc'; package: 'Bloc-Core'; package: 'Bloc-Core-MorphCompatibility'; package: 'Bloc-Halo'; package: 'Bloc-Halo-MorphCompatibility'; package: 'Bloc-Widgets'; package: 'ConfigurationOfBloc'; push. ---End Message---
Re: [Pharo-dev] Permission denied issue when moving Bloc to PharoExtras
I see you're already there in the permission list. I think you should go to the monticello browser and add the pharo extras repository with your user and password. Then Gofer will be able to find your password to commit. Sorry I skipped that detail when giving you the scripts :/. Guille El vie., 17 de abr. de 2015 a la(s) 10:03 a. m., Alain Plantec via Pharo-dev pharo-dev@lists.pharo.org escribió: Hello all, Here are the Gofer invocations I used. The fetch is ok but the push ends-up in a ‘Permission denied’ error. what is wrong in my Gofer push invocation ? Thanks Cheers Alain Gofer it smalltalkhubUser: 'AlainPlantec' project: 'Bloc'; package: 'Bloc-Core'; package: 'Bloc-Core-MorphCompatibility'; package: 'Bloc-Halo'; package: 'Bloc-Halo-MorphCompatibility'; package: 'Bloc-Widgets'; package: 'ConfigurationOfBloc'; fetch. Gofer it smalltalkhubUser: 'PharoExtras' project: 'Bloc'; package: 'Bloc-Core'; package: 'Bloc-Core-MorphCompatibility'; package: 'Bloc-Halo'; package: 'Bloc-Halo-MorphCompatibility'; package: 'Bloc-Widgets'; package: 'ConfigurationOfBloc'; push.
Re: [Pharo-dev] OpenBuildService
Le 17/4/15 08:12, Sean P. DeNigris a écrit : After hearing Esteban mention it, I investigated http://openbuildservice.org/ and it seems really exciting. IIUC, we can create one Fedora-style packag Spec file, and have Pharo built on just about all distributions. that would be really awesome. Thanks for trying and pushing in that direction. There is even a community server (https://build.opensuse.org/). I've set up an account there for test purposes and started playing. The initial results are at https://github.com/pharo-project/pharo-openbuildservice. I also wrote some notes at https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/OpenBuildService.md. I've gotten through the build process and I'm stuck on the installation step. - Cheers, Sean -- View this message in context: http://forum.world.st/OpenBuildService-tp4820143.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] [pharo-project/pharo-core]
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core
Re: [Pharo-dev] [update 5.0] #50001
Marcus Denker-4 wrote 15288 Shortcuts in text editor are hardcoded Sounds like a good one to start off 5.0! - Cheers, Sean -- View this message in context: http://forum.world.st/update-5-0-50001-tp4820189p4820201.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] [Moose-dev] communicating pharo 4.0
Yes, we start to have a stack of very cool tools and engines! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Apr 17, 2015, at 6:42 AM, Tudor Girba tu...@tudorgirba.com wrote: Hi, In case you were wondering about the details behind the visualization that came with the Pharo 4.0 announcement, here is a more detailed explanation: http://www.humane-assessment.com/blog/communicating-pharo-4-0 http://www.humane-assessment.com/blog/communicating-pharo-4-0 Cheers, Doru -- www.tudorgirba.com http://www.tudorgirba.com/ Every thing has its own flow ___ Moose-dev mailing list moose-...@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
[Pharo-dev] [pharo-project/pharo-core] c0a7e5: 50001
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c0a7e5ef202f88248174a95b999024c64a23576f https://github.com/pharo-project/pharo-core/commit/c0a7e5ef202f88248174a95b999024c64a23576f Author: Jenkins Build Server bo...@pharo-project.org Date: 2015-04-17 (Fri, 17 Apr 2015) Changed paths: M Komitter.package/KomitNewSlice.class/instance/accessing/remote.st M Komitter.package/extension/MCHttpRepository/class/pharoLocations.st M Monticello.package/MCHttpRepository.class/class/instance creation/pharoInboxRepository.st M Monticello.package/MCHttpRepository.class/class/instance creation/pharoRepository.st R ScriptLoader40.package/Loader.class/README.md R ScriptLoader40.package/Loader.class/class/private/packageToBeTestedFolderName.st R ScriptLoader40.package/Loader.class/class/private/waitingCacheFolder.st R ScriptLoader40.package/Loader.class/definition.st R ScriptLoader40.package/Loader.class/instance/accessing/currentMajorVersionNumber.st R ScriptLoader40.package/Loader.class/instance/accessing/currentMajorVersionNumberWithoutDot.st R ScriptLoader40.package/Loader.class/instance/compute/currentChangedPackages.st R ScriptLoader40.package/Loader.class/instance/compute/currentVersionsToBeSaved.st R ScriptLoader40.package/Loader.class/instance/elementary steps/diffPackages.st R ScriptLoader40.package/Loader.class/instance/initialization/initialize.st R ScriptLoader40.package/Loader.class/instance/mc related utils/allCurrentVersions.st R ScriptLoader40.package/Loader.class/instance/private/markPackagesBeforeNewCodeIsLoaded.st R ScriptLoader40.package/Loader.class/instance/private/packagesNotToSavePatternNames.st R ScriptLoader40.package/Loader.class/instance/private/resetPackagesBeforeLastLoad.st R ScriptLoader40.package/Loader.class/instance/private/theScriptLoaderPackageName.st R ScriptLoader40.package/ScriptLoader.class/README.md R ScriptLoader40.package/ScriptLoader.class/class/loadscripts/gofer.st R ScriptLoader40.package/ScriptLoader.class/class/loadscripts/initialize.st R ScriptLoader40.package/ScriptLoader.class/class/menu/currentlyIntegratingChanges.st R ScriptLoader40.package/ScriptLoader.class/class/menu/hideIntegrationMenu.st R ScriptLoader40.package/ScriptLoader.class/class/menu/menuCommandOn_.st R ScriptLoader40.package/ScriptLoader.class/class/menu/showIntegrationMenu.st R ScriptLoader40.package/ScriptLoader.class/class/menu/theme.st R ScriptLoader40.package/ScriptLoader.class/class/private/defaultMCWaitingFolder.st R ScriptLoader40.package/ScriptLoader.class/class/private/loadLatestPackage_fromHub_.st R ScriptLoader40.package/ScriptLoader.class/class/private/loadLatestPackage_fromRepository_.st R ScriptLoader40.package/ScriptLoader.class/class/private/loadLatestPackage_from_.st R ScriptLoader40.package/ScriptLoader.class/class/private/rootURLString.st R ScriptLoader40.package/ScriptLoader.class/class/public/checkImageInSyncWithUpdate.st R ScriptLoader40.package/ScriptLoader.class/class/public/checkImageInSyncWithUpdate_.st R ScriptLoader40.package/ScriptLoader.class/class/public/currentMajorVersionNumber.st R ScriptLoader40.package/ScriptLoader.class/class/public/currentMajorVersionNumber_.st R ScriptLoader40.package/ScriptLoader.class/class/public/releaseMenu.st R ScriptLoader40.package/ScriptLoader.class/class/source/latestSource_location_.st R ScriptLoader40.package/ScriptLoader.class/class/source/latestVersionOf_location_.st R ScriptLoader40.package/ScriptLoader.class/definition.st R ScriptLoader40.package/ScriptLoader.class/instance/accessing/allManagers.st R ScriptLoader40.package/ScriptLoader.class/instance/accessing/diffServerRootString.st R ScriptLoader40.package/ScriptLoader.class/instance/accessing/gofer.st R ScriptLoader40.package/ScriptLoader.class/instance/accessing/inboxRepository.st R ScriptLoader40.package/ScriptLoader.class/instance/accessing/inboxRepositoryDefault.st R ScriptLoader40.package/ScriptLoader.class/instance/accessing/repository.st R ScriptLoader40.package/ScriptLoader.class/instance/accessing/repositoryTaskForces.st R ScriptLoader40.package/ScriptLoader.class/instance/accessing/repository_.st R ScriptLoader40.package/ScriptLoader.class/instance/ci/checkImageIsUptodateSilently.st R ScriptLoader40.package/ScriptLoader.class/instance/ci/compileNewUpdateMethodSilentlyConfigurations_preLoad_postLoad_.st R ScriptLoader40.package/ScriptLoader.class/instance/ci/decodeFromPrint_.st R ScriptLoader40.package/ScriptLoader.class/instance/ci/doneApplyingChangesSilentlyComment_configurations_preLoad_postLoad_.st R ScriptLoader40.package/ScriptLoader.class/instance/ci/doneApplyingChangesSilentlyIssues_preLoad_postLoad_.st R
Re: [Pharo-dev] Is Pharo Launcher Ready?
Le 16/4/15 14:14, Dale Henrichs a écrit : Thanks Damien, I will give it a go when I get a chance ... because it broke about 2 months ago and my mail to this list went unanswered, I've since removed it from my scripts (in an emergency no less, because the scripts were failing) and I have become a bit gunshy about relying on something that drops from support without warning Believe me I did not want to learn about `ldd` and the 12.04 pharo dependencies, but I had no choice:( I would like to be able to depend upon the zero conf scripts, because they are very convenient, but I am still hazy on the policy towards older releases and zero conf. It would be very convenient if the scripts worked forever for the old releases (pharo3.0 will be old in a year:) they don't need to be kept up to date with respect to the latest vm, but should be frozen at the last stable vm for that platform/release ... if that were true then I would be comfortable leaning heavily on zero conf for the installation/update scripts...if not... Yes I agree with you. now we have reached a stable point where we can avoid to have latest vm creeping in old scripts. If I understood correctly what esteban told me. Dale On 4/16/15 1:52 AM, Damien Cassou wrote: Dale Henrichs dale.henri...@gemtalksystems.com writes: On 4/13/15 10:01 AM, Sean P. DeNigris wrote: IIUC we are planning on making Pharo Launcher the default download. Not sure whether this is the right thread or not... Keep in mind that the last time I tried to use the Pharo Launcher (a couple of months ago) on ubunutu12.04 the Ubuntu packaged failed to be found and I had to abandon my use of Pharo Launcher since Ubuntu12.04 is still in common use ... I think Ubuntu 12.04 is supported now. See https://launchpad.net/~pharo/+archive/ubuntu/stable?field.series_filter=precise
Re: [Pharo-dev] New Cog VMs available
... at http://www.mirandabanda.org/files/Cog/VM/VM.r3311/. These should fix the regression introduced by the map changes in 3308. They certainly fix the two crashes I've looked at, one an update of a squeak trunk image and the other the startup of recent Newspeak images. Apologies for the inconvenience. Well, this is embarrassing as usual but I'm still seeing crashes in the image update. So I'll have to look deeper. At least the Newspeak fix was real, but it didn't fix everything. :) Hi eliot How can we help? Would it make sense to have some more ci jobs for testing the VM? Stef CogVM binaries as per VMMaker.oscog-eem.1204/r3311 Cogits: Fix regression in map machinery due to adding AnnotationExtension scheme. findMapLocationForMcpc:inMethod: must not be confused by IsDisplacementX2N bytes. This is likely the cause of the recent crashes with r3308 and earlier. Introduce marryFrameCopiesTemps and use it to not copy temps in Spur context creation trampolines. Change initial usage counts to keep more recently jitted methods around for longer, and do *not* throw away PICs in freeOlderMethodsForCompaction, so that there's a better chance of Sista finding send and branch data for the tripping method. extendedPushBytecode /does/ need a frame. Don't save the header in a scratch register unless it is useful to do so in the Spur at:[put:] primitives. Fix slip in genGetNumBytesOf:into:. And notice that genGetFormatOf:into:baseHeaderIntoScratch: et al can use byte access to get at format, as intended in the Spur header design. Fix unlinking dynamic super sends. Reduce false positives in access control violation reporting by marking the super send we actually use as privileged. Remove unused Newspeak bytecodes. Internal: Fix code generation bug surfaced by inline primitives. On x86 movb N(%reg),%rl can only store into al, bl, cl dl, whereas movzbl can store into any reg. On ARM move byte also zero-extends. So change definition of MoveMbrR to always zero-extend, use movzbl on x86 and remove all the MoveCq: 0 R: used to zero the bits of the target of a MoveMb:r:R:. And now that we have genGetNumSlotsOf:into:, use it. Fix a slip in genTrinaryInlinePrimitive:, meet constraint that the target must be in ReceiverResultReg, and do a better job of register allocation there-in. Do dead code elimination for the branch following an inlined comparison (this is done in genBinaryInlineComparison:opFalse:destReg: copying the scheme in genSpecialSelectorEqualsEquals). Do register allocation in the right place in genUnaryInlinePrimitive:. Fix overflow slot access in genGetNumSlotsOf:into: et al. Fix several slips in inline primitive generation: Objectat:put: needs to include a store check. Some register allocation code was wrong. Some results needed converting to SmallIntegers and recording results as pushed on the sim stack. Change callPrimitiveBytecode to genCallPrimitiveBytecode in the Cogit. remove the misnomer genConvertIntegerToSmallIntegerInScratchReg: Type of AbstractInstruction opcode must be unsigned now that we have more than 128 opcodes (XCHGRR pushed things over the top). Lay the groundwork for 32-bit intra-zone jumps and calls on ARM by introducing CallFull and JumpFull (and rewrites thereof) that are expected to span the full address space, leaving Call/JumpLong to span merely the 16mb code zone. On x86 CallFull and JumpFull simply default to Call/JumpLong. Replace bytecode trapIfNotInstanceOf by jumpIfNotInstanceOfOrPop. Rewrote the JIT logic for traps to be able to write trap trampolines calls at the end of the cogMethod. Refactor the slot store and store check machinery to take an inFrame: argument and hence deal with the store check in genInnerPrimitiveAtPut: on ARM. Fix limitation with MoveRXbrR; can only do movb from %al through %dl, so swap with %eax around movb. Fix mistake with genGetNumBytesOf:into: by refactoring genGetFormatOf:into:baseHeaderIntoScratch: into genGetBits:ofFormatByteOf:into:baseHeaderIntoScratch: and hence fetching and subtracting only odd bits of format. Correct the in-line primitive SmallInteger comparisons; CmpXR is confusing ;-) Fix var op var unsafe byte at:. Result must be converted to SmallInteger. Correct the generated Slang for the new register allocation code by adding a read-before-written pass to C generation that initializes variables read-before-written with 0 (the C equivalent of nil). fix a bug where sometimes register allocation was marking ReceiverResultReg as dead whereas it was still alive. Added some abstraction over register allocation. This is now used in inline primitives.
Re: [Pharo-dev] Rubric and Bloc are now in PharoExtras
Thanks Alain! Doru On Fri, Apr 17, 2015 at 12:56 PM, Alain Plantec via Pharo-dev pharo-dev@lists.pharo.org wrote: -- Forwarded message -- From: Alain Plantec alain.plan...@yahoo.com To: Pharo Development List pharo-dev@lists.pharo.org Cc: Date: Fri, 17 Apr 2015 12:56:26 +0200 Subject: Rubric and Bloc are now in PharoExtras Hello all, Please update your configurations. Cheers Alain -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] pharo home page tagline
I just point them to my own Pharo website which I think it gives a more clear picture what Pharo is all about , but hey , I am biased :) http://thekilon.wix.com/pharo-about On Fri, Apr 17, 2015 at 6:58 AM, Ben Coman b...@openinworld.com wrote: On reddit I see some questions regarding the IDE and OS rolled into one tagline on the pharo homepage. Of course it makes sense to me, but I can see how it might not be clear to others, who might even think I don't need that, I already have an OS. I think the tagline would be strong enough without it - less is more. cheers -ben
Re: [Pharo-dev] Rubric and Bloc are now in PharoExtras
I think we should use the PharoInbox only for issues of things that are part of the core. If not it will be easily polluted. What do you think? Guille El vie., 17 de abr. de 2015 a la(s) 1:54 p. m., Sean P. DeNigris s...@clipperadams.com escribió: Thank you!!! Quick question. What is our procedure about contributing to projects which we own but are not part of Core? Should we commit to the inbox or directly to the project repo? At the moment, I'm thinking of non-controversial things like fixing comment typos... - Cheers, Sean -- View this message in context: http://forum.world.st/Rubric-and-Bloc-are-now-in-PharoExtras-tp4820182p4820186.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] [Vm-dev] [ANN] Pharo 4.0 is released!
I will be teaching at Lviv but esteban or marcus should be available. Le 16/4/15 23:02, p...@highoctane.be a écrit : stef what about next tuesday? phil Le 16 avr. 2015 22:44, stepharo steph...@free.fr mailto:steph...@free.fr a écrit : yes phil tell us. Stef Le 16/4/15 12:11, p...@highoctane.be mailto:p...@highoctane.be a écrit : Le 16 avr. 2015 11:56, Tudor Girba tu...@tudorgirba.com mailto:tu...@tudorgirba.com a écrit : Great job! Thank you everyone for the contributions, support and trust. One more out of the door. That's great. Anyone interested in doing a podcast episode on this releasr? Chime in. Phil Cheers, Doru On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano esteba...@gmail.com mailto:esteba...@gmail.com wrote: Please spread widely. Sorry for multiple posts. (this post can be see here: http://pharo.org/news/pharo-4.0-released) Dear World, Pharo 4.0 (http://www.pharo.org) is here. Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. Many things have changed in Pharo. Here are some highlights: - Inspector/Playground/Spotter are new moldable development tools for inspecting, coding and searching objects. - Slots model instance variables as first class entities and enable meta-programming on this level. - ShoreLine reporter introduces a way to report system errors and collect statistics, that we will use for future improvements - Dark theme. These are just the more prominent highlights, but the details are just as important. We have closed 1697 issues in Pharo 4. Take a moment to go through a more detailed recount of the progress: https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md Pharo is improving on many fronts, but one of the most prominent changes is the addition of moldable tools for inspection and search. These tools provide extension mechanisms that allow every object to define ways in which it can be understood effectively. To provide an idea of the impact of the already existing extensions, the map below shows the Pharo classes grouped in packages, highlighting in red those parts of the system that have at least one such custom view coming with the main distribution. The spread of these extensions shows that moldability is powerful mechanism that can be used in many contexts. Remember that Pharo is your platform. We thank all the contributors of this release: Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin And all those who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... Pharo 4.0 is another big step. And, the best is yet to come. Enjoy! The Pharo Team -- www.tudorgirba.com http://www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Rubric and Bloc are now in PharoExtras
Thank you!!! Quick question. What is our procedure about contributing to projects which we own but are not part of Core? Should we commit to the inbox or directly to the project repo? At the moment, I'm thinking of non-controversial things like fixing comment typos... - Cheers, Sean -- View this message in context: http://forum.world.st/Rubric-and-Bloc-are-now-in-PharoExtras-tp4820182p4820186.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Rubric and Bloc are now in PharoExtras
For rubric and gtools, unless it's a really urgent bug you should commit the fix in the project's repository. Cheers, Andrei On Fri, Apr 17, 2015 at 1:40 PM, Sean P. DeNigris s...@clipperadams.com wrote: Thank you!!! Quick question. What is our procedure about contributing to projects which we own but are not part of Core? Should we commit to the inbox or directly to the project repo? At the moment, I'm thinking of non-controversial things like fixing comment typos... - Cheers, Sean -- View this message in context: http://forum.world.st/Rubric-and-Bloc-are-now-in-PharoExtras-tp4820182p4820186.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] [update 5.0] #50001
50001 - 15288 Shortcuts in text editor are hardcoded https://pharo.fogbugz.com/f/cases/15288
Re: [Pharo-dev] Rubric and Bloc are now in PharoExtras
You should still make an issue on the bug tracker and the mark it as Fixed Upstream. Cheers, Andrei On Fri, Apr 17, 2015 at 2:00 PM, Andrei Chis chisvasileand...@gmail.com wrote: For rubric and gtools, unless it's a really urgent bug you should commit the fix in the project's repository. Cheers, Andrei On Fri, Apr 17, 2015 at 1:40 PM, Sean P. DeNigris s...@clipperadams.com wrote: Thank you!!! Quick question. What is our procedure about contributing to projects which we own but are not part of Core? Should we commit to the inbox or directly to the project repo? At the moment, I'm thinking of non-controversial things like fixing comment typos... - Cheers, Sean -- View this message in context: http://forum.world.st/Rubric-and-Bloc-are-now-in-PharoExtras-tp4820182p4820186.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] [update 5.0] #50001
make me wonder what pharo version 5001 will look like in 4996 years, but I guess I can compromise for version 5 for now :) keep up the great work On Fri, Apr 17, 2015 at 3:00 PM, Marcus Denker marcus.den...@inria.fr wrote: 50001 - 15288 Shortcuts in text editor are hardcoded https://pharo.fogbugz.com/f/cases/15288
Re: [Pharo-dev] PharoLauncher and Pharo 5.0
Thanks! I was about to ask about this. :) Also could there be an option to reuse parameters provided to the pharo(launcher) image? I always have to manually rewrite PhLimagelaunch: to fix encoding. ^OSProcess command: vmCommand , ' --textenc UTF-8 ' , imagePath, ''. Peter On Fri, Apr 17, 2015 at 4:39 PM, Torsten Bergmann asta...@gmx.de wrote: Hi Damien, I added a 0.2.5 version to PharoLauncher now including Pharo 5.0. Also Pharo 4.0 was switched from beta to stable. Locally it works and I can download a Pharo 5.0. Please review. I'm also not able to trigger the CI job: https://ci.inria.fr/pharo/view/Launcher Can you run the build? Thx T.
Re: [Pharo-dev] Launcher Mac CI - Broken Executable
Damien Cassou-2 wrote The Pharo_0.2.6.dmg seems to work fine for me http://forum.world.st/file/n4820289/Screenshot_2015-04-17_14.png - Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-Mac-CI-Broken-Executable-tp4820123p4820289.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Launcher Mac CI - Broken Executable
- Mail original - De: Sean P. DeNigris s...@clipperadams.com À: pharo-dev@lists.pharo.org Envoyé: Vendredi 17 Avril 2015 07:35:31 Objet: Re: [Pharo-dev] Launcher Mac CI - Broken Executable Sean P. DeNigris wrote Pharo is damaged and can't be opened. You should move it to the Trash. All broken back to build #24 from Feb 25th. It was very tedious to find that out, since the builds all claim to produce Pharo_0.2.4 The Pharo_0.2.6.dmg seems to work fine for me. It looks like files.pharo.org does not contain the file yet. Please use: https://ci.inria.fr/pharo/view/all/job/Launcher-Mac/44/artifact/Pharo_0.2.6.dmg
Re: [Pharo-dev] Rubric and Bloc are now in PharoExtras
---BeginMessage--- On 17 Apr 2015, at 13:40, Sean P. DeNigris s...@clipperadams.com wrote: Thank you!!! Quick question. What is our procedure about contributing to projects which we own but are not part of Core? Should we commit to the inbox or directly to the project repo? At the moment, I'm thinking of non-controversial things like fixing comment typos… super, maybe wait that I make a pass because some of them are obsolete. Thanks Alain - Cheers, Sean -- View this message in context: http://forum.world.st/Rubric-and-Bloc-are-now-in-PharoExtras-tp4820182p4820186.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. ---End Message---
Re: [Pharo-dev] New Cog VMs available
On Fri, Apr 17, 2015 at 3:41 AM, stepharo steph...@free.fr wrote: ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3311/. These should fix the regression introduced by the map changes in 3308. They certainly fix the two crashes I've looked at, one an update of a squeak trunk image and the other the startup of recent Newspeak images. Apologies for the inconvenience. Well, this is embarrassing as usual but I'm still seeing crashes in the image update. So I'll have to look deeper. At least the Newspeak fix was real, but it didn't fix everything. :) Hi eliot How can we help? Would it make sense to have some more ci jobs for testing the VM? Yes, that always helps. But we have to accept that that means a) these CI jobs will detect failures caused by regressions etc b) we need to mark builds as bleeding edge last known good etc, and set these pointers b) I have yet to set up. But yesterday and today a wonderful thing has happened. Clément has understood the core optimization and code generation structures in the JIT as well as I do and is now both improving the code quality and implementing more aggressive optimizations. This is /so/ satisfying. You know how good Clément is. His input is so strong. I am /very/ happy. For example, Clément is currently modifying #== in the Spur JIT so that the code checks for forwarders only if #== is false, and that if #== is false and either object is a forwarder, it/them is/are followed and the #== retried. This should speed up #== by 50%. It won't make much difference at the macro level but this is a non-trivial optimization to write and so now we have two people who really understand the core optimizing JIT and I can now happily run in front of a bus. Stef CogVM binaries as per VMMaker.oscog-eem.1204/r3311 Cogits: Fix regression in map machinery due to adding AnnotationExtension scheme. findMapLocationForMcpc:inMethod: must not be confused by IsDisplacementX2N bytes. This is likely the cause of the recent crashes with r3308 and earlier. Introduce marryFrameCopiesTemps and use it to not copy temps in Spur context creation trampolines. Change initial usage counts to keep more recently jitted methods around for longer, and do *not* throw away PICs in freeOlderMethodsForCompaction, so that there's a better chance of Sista finding send and branch data for the tripping method. extendedPushBytecode /does/ need a frame. Don't save the header in a scratch register unless it is useful to do so in the Spur at:[put:] primitives. Fix slip in genGetNumBytesOf:into:. And notice that genGetFormatOf:into:baseHeaderIntoScratch: et al can use byte access to get at format, as intended in the Spur header design. Fix unlinking dynamic super sends. Reduce false positives in access control violation reporting by marking the super send we actually use as privileged. Remove unused Newspeak bytecodes. Internal: Fix code generation bug surfaced by inline primitives. On x86 movb N(%reg),%rl can only store into al, bl, cl dl, whereas movzbl can store into any reg. On ARM move byte also zero-extends. So change definition of MoveMbrR to always zero-extend, use movzbl on x86 and remove all the MoveCq: 0 R: used to zero the bits of the target of a MoveMb:r:R:. And now that we have genGetNumSlotsOf:into:, use it. Fix a slip in genTrinaryInlinePrimitive:, meet constraint that the target must be in ReceiverResultReg, and do a better job of register allocation there-in. Do dead code elimination for the branch following an inlined comparison (this is done in genBinaryInlineComparison:opFalse:destReg: copying the scheme in genSpecialSelectorEqualsEquals). Do register allocation in the right place in genUnaryInlinePrimitive:. Fix overflow slot access in genGetNumSlotsOf:into: et al. Fix several slips in inline primitive generation: Objectat:put: needs to include a store check. Some register allocation code was wrong. Some results needed converting to SmallIntegers and recording results as pushed on the sim stack. Change callPrimitiveBytecode to genCallPrimitiveBytecode in the Cogit. remove the misnomer genConvertIntegerToSmallIntegerInScratchReg: Type of AbstractInstruction opcode must be unsigned now that we have more than 128 opcodes (XCHGRR pushed things over the top). Lay the groundwork for 32-bit intra-zone jumps and calls on ARM by introducing CallFull and JumpFull (and rewrites thereof) that are expected to span the full address space, leaving Call/JumpLong to span merely the 16mb code zone. On x86 CallFull and JumpFull simply default to Call/JumpLong. Replace bytecode trapIfNotInstanceOf by jumpIfNotInstanceOfOrPop. Rewrote the JIT logic for traps to be able to write trap trampolines calls at the end of the cogMethod. Refactor the slot store and store check machinery to take an inFrame: argument and hence deal with the store check in
Re: [Pharo-dev] PharoLauncher and Pharo 5.0
Jan Blizničenko blizn...@fit.cvut.cz writes: In settings, there used to be option to switch off categories of image sources/templates, like hide Pharo 2 category, but this option seems to be missing now. yes, I removed it because it was too costly to maintain. And one more thing ... GUI has some weird colors (well, I think it is actually missing colors). Screenshot: https://monosnap.com/file/Fs6rfZTlstzqkKzyReRnPUVa28FVZe.png However, this one is not today's change, because this morning I tried updating launcher (to find out whether it supports Pharo 5 :) ) and colors were already like this. I confirm and I don't know why. -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. --Winston Churchill
Re: [Pharo-dev] PharoLauncher and Pharo 5.0
Peter Uhnák i.uh...@gmail.com writes: Thanks! I was about to ask about this. :) Also could there be an option to reuse parameters provided to the pharo(launcher) image? I always have to manually rewrite PhLimagelaunch: to fix encoding. ^OSProcess command: vmCommand , ' --textenc UTF-8 ' , imagePath, ''. please try to implement it. -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. --Winston Churchill
Re: [Pharo-dev] Launcher Mac CI - Broken Executable
Sean P. DeNigris s...@clipperadams.com writes: Damien Cassou-2 wrote The Pharo_0.2.6.dmg seems to work fine for me http://forum.world.st/file/n4820289/Screenshot_2015-04-17_14.png I don't know why it doesn't work for you :-(. Are there other people with the same problem? -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. --Winston Churchill
Re: [Pharo-dev] Launcher Mac CI - Broken Executable
This is where calling PharoLauncher Pharo is confusing. There is Pharo 0.2.4 and also Pharo 4.0. What is a newcomer to think? Cheers -ben On 17/04/2015 11:58 pm, Damien Cassou damien.cas...@inria.fr wrote: - Mail original - De: Sean P. DeNigris s...@clipperadams.com À: pharo-dev@lists.pharo.org Envoyé: Vendredi 17 Avril 2015 07:35:31 Objet: Re: [Pharo-dev] Launcher Mac CI - Broken Executable Sean P. DeNigris wrote Pharo is damaged and can't be opened. You should move it to the Trash. All broken back to build #24 from Feb 25th. It was very tedious to find that out, since the builds all claim to produce Pharo_0.2.4 The Pharo_0.2.6.dmg seems to work fine for me. It looks like files.pharo.org does not contain the file yet. Please use: https://ci.inria.fr/pharo/view/all/job/Launcher-Mac/44/artifact/Pharo_0.2.6.dmg
