November 2018 - Pharo-dev - lists.pharo.org

PharoLauncher : Image version determination error
by Julien Nov. 9, 2018

Nov. 9, 2018

Hello, Is there something wrong with the latest Pharo 7.0 32bits image? I got this error from Pharo Launcher: Cannot determine image version: image version file not found! Try to run this command in a shell to get more information on the problem: cd "/Users/julien/Documents/Pharo/vms/private/6521/Pharo.app/Contents/MacOS" && "/Users/julien/Documents/Pharo/vms/private/6521/Pharo.app/Contents/MacOS/Pharo" --headless "/Users/julien/Documents/Pharo/images/RTFExperiment-Iceberg/RTFExperiment-Iceberg.image" eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor| major := SystemVersion current major. minor := SystemVersion current minor. (major = 6 and: [ SystemVersion current highestUpdate >= 60509 ]) ifTrue: [ minor := 1 ]. stream << major asString; << minor asString ]" When trying to start it. If I run this script in the terminal, nothing is print but the process crashes returning 1 as exit code. Can someone relate this issue as well? Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

9 20

[Pharo 7.0-dev] Build #1374: 22650-add-Operations-as-Reifications
by ci-pharo-ci-jenkins2＠inria.fr Nov. 9, 2018

Nov. 9, 2018

There is a new Pharo build available! The status of the build #1374 was: SUCCESS. The Pull Request #1961 was integrated: "22650-add-Operations-as-Reifications" Pull request url: https://github.com/pharo-project/pharo/pull/1961 Issue Url: https://pharo.fogbugz.com/f/cases/22650 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1373: 22639-Clean-ComposablePresenter-icon-API
by ci-pharo-ci-jenkins2＠inria.fr Nov. 8, 2018

Nov. 8, 2018

There is a new Pharo build available! The status of the build #1373 was: SUCCESS. The Pull Request #1959 was integrated: "22639-Clean-ComposablePresenter-icon-API" Pull request url: https://github.com/pharo-project/pharo/pull/1959 Issue Url: https://pharo.fogbugz.com/f/cases/22639 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

glamorous toolkit - moldable method coder
by Tudor Girba Nov. 8, 2018

Nov. 8, 2018

Hi, We design the Glamorous Toolkit to enable moldable development. This is a new take on programming that is predicated on the idea that tools must adapt to the context of the software system in order to be effective. Until now, we mainly applied moldability to how we inspect/debug/search existing code and objects. The first incarnation of GT, the tools that are present in the Pharo distribution, already showed how moldable development can provide dramatic productivity gains, especially when combined with examples. To make the experience complete, more recently we started to build moldability into Coder, the new set of tools for creating code. The first tool we created is Method Coder, an editor for a single method. This is a working editor that has multiple new features, one of which being that it can be collapsed to only see the method pattern (header), and that the body is editable without affecting the method pattern. This editor is versatile and can be used in various places, such as class coder or a search: https://twitter.com/feenkcom/status/1058003761262743552 Yesterday, we reached a new milestone. In the example below we see how adding/removing <gtExample> to a method changes the shape of the method Coder dynamically without requiring a save. In our case, the changes affect: the example status label, the in-place example expanding toggle, and the run button. https://twitter.com/feenkcom/status/1060290294749560833 This just an example that is specific to the examples engine, but it shows how typing can be linked live to all details that make the surrounding tool. Of course, the mechanism behind the scene is available for you to adapt the editor to your code. This is a whole new uncharted world, and we think there is a great deal of potential in this area. Have fun, The feenk team -- www.feenk.com âHow do you feenk today?"

1 0

Cannot use Zinc in Pharo7 anymore
by Norbert Hartl Nov. 8, 2018

Nov. 8, 2018

I asked this before because I donât get it. External packages like Zinc seem to be modified when integrated into pharo. Looking at the changes between to newest Zinc from Svenâs repository and the one in pharo there are a few differences. As an example there is ZnCharacterReadWriteStream>>#tab writeStream tab Where is this method added? Are the changes pushed back to Sven? In my project I use Zinc-REST. So I need to add the repository for Zinc and load the REST group. When this is loaded it pulls in the other Zinc packages which removes the methods like the one above and my image gets stuck because Epicea relies on that method and I get a debugger. So at the moment I can only create a new image when I disable Epicea. Why is it done that way? Best would be to use the version from Sven and make changes there. If that is not possible it would be good to use an extra package that does extension methods to Zinc. But this way is asking for trouble IMHO. Norbert

11 31

Infinite error recursion while saving Pharo70 alpha
by Aliaksei Syrel Nov. 7, 2018

Nov. 7, 2018

Hello, When saving one of the latest pharo70 image I got an infinite recursion loop due to message not understood. Force closing it probably lead to image corruption and it became un-openable anymore. Any idea what is going on? It does not look like a unique case because there are a few pharo70 images that already died in front of me... [image: Screen Shot 2018-11-07 at 09.55.07.png] VM: Mac OS - x64 - 1013.5 - CoInterpreter VMMaker.oscog-eem.2461 uuid: > b3cd33f5-6309-43a1-b669-7a1805111f34 Oct 31 2018 > StackToRegisterMappingCogit VMMaker.oscog-eem.2464 uuid: > 0b1fa0a3-a781-4fd5-b1cf-1809796ccbbf Oct 31 2018 > VM: 201810311808 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > Date: Wed Oct 31 11:08:29 2018 CommitHash: c7a9b1f Plugins: 201810311808 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git > Image: Pharo7.0.0alpha [Build information: > Pharo-7.0.0+alpha.build.1361.sha.011b7c939adeb52338baad16a694cab2e7a54d74 > (64 Bit)] Cheers, Alex

5 7

[Pharo 7.0-dev] Build #1372: 22638-usage-of-readlink-f-breaks-macOS-bootstrap
by ci-pharo-ci-jenkins2＠inria.fr Nov. 7, 2018

Nov. 7, 2018

There is a new Pharo build available! The status of the build #1372 was: SUCCESS. The Pull Request #1958 was integrated: "22638-usage-of-readlink-f-breaks-macOS-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1958 Issue Url: https://pharo.fogbugz.com/f/cases/22638 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1371: 22641-Semantic-analysis-needs-to-take-instead-preambles-into-account
by ci-pharo-ci-jenkins2＠inria.fr Nov. 7, 2018

Nov. 7, 2018

There is a new Pharo build available! The status of the build #1371 was: SUCCESS. The Pull Request #1960 was integrated: "22641-Semantic-analysis-needs-to-take-instead-preambles-into-account" Pull request url: https://github.com/pharo-project/pharo/pull/1960 Issue Url: https://pharo.fogbugz.com/f/cases/22641 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Iceberg v1.4.0
by Cyril Ferlicot Nov. 7, 2018

Nov. 7, 2018

Hello! This week we are releasing the version v1.4.0 of Iceberg. (https://github.com/pharo-vcs/iceberg/releases/tag/v1.4.0) This version is available in the latest Pharo 7. This release fixes a bug introduced in v1.3. It also add new features in the repository view, add some cleaning and also re-introduce a feature that was lost. Thanks to all contributors. Enjoy! Full changelog: Bugfixes #1068 'There is no associated repository configured.' warning on right clicking missing repository Features #1077 Repository view: Allow to collapse branches/remotes/tags trees #847 Move tags under remotes in Repository view #1070 set upstream if missing Cleanups #1066 Pharo 7: PackageManifest subclasses should be packaged with "Manifest" #1015 Replace usages of Glamour in the Github Plugin #1063 1061-Introduce-iconNamed-in-IceDefinition-and-IceTipModel-and-remove-all-the-terrible-Smalltalk-ui-icons -- Cyril Ferlicot https://ferlicot.fr

2 1

[Pharo 7.0-dev] Build #1370: 22629-Secondary-selection-is-too-bright-when-switching-to-the-dark-theme
by ci-pharo-ci-jenkins2＠inria.fr Nov. 7, 2018

Nov. 7, 2018

There is a new Pharo build available! The status of the build #1370 was: FAILURE. The Pull Request #1953 was integrated: "22629-Secondary-selection-is-too-bright-when-switching-to-the-dark-theme" Pull request url: https://github.com/pharo-project/pharo/pull/1953 Issue Url: https://pharo.fogbugz.com/f/cases/22629 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Slow writing to Transcript (stderr) in Windows 10 PharoConsole.exe -headless
by Christopher Fuhrman Nov. 7, 2018

Nov. 7, 2018

Hello, I encountered a performance bug in Pharo 6 under Windows 10 with Moose, starting from the Moose 6.1 (beta) image in Pharo Launcher. I migrated my code from Pharo 5 and it uses a PharoCommandLineHandler to load an MSE file, which sometimes has many (15K) warnings/errors. It was taking over a minute to run something that in Moose takes only a few seconds. To debug and make a minimal example, I removed the Moose file part of my CommandLineHandler and simulated the writing of errors (i/o) with a loop. I believe the I/O to the stderr is why the performance is bad. In Windows 10 Task Manager, I can see that the process is not using much CPU. As I recall, my code didn't have this performance problem in Pharo 5. The command in windows to execute my minimal sample is something like: C:\Users\me>Documents\Pharo\vms\61-x86\PharoConsole.exe -headless "C:\Users\me\Documents\Pharo\images\Moose Suite 6.1 (beta)\CommandHandler VM slow bug.image" mooseminer --msefile blah The last part (--msefile blah) is needed because I didn't want to remove the argument validation. Here's a copy of the image: https://www.dropbox.com/s/7cgt37lef2xh2ut/CommandHandler%20VM%20slow%20bug.… A workaround is to run without -headless (or to not have so many errors). I hope this is useful to someone. For RMOD people I'm happy to demo this on my machine. Cheers, -- Christopher Fuhrman, P.Eng, PhD *Professor in the DÃ©partement of Software and IT EngineeringÃTS (Ãcole de technologie supÃ©rieure)* http://profs.etsmtl.ca/cfuhrman +1 514 396 8638 *L'ÃTS est une constituante de l'UniversitÃ© du QuÃ©bec*

1 0

[ANN] Pharo v7.0.0-rc1 released!
by Esteban Lorenzano Nov. 7, 2018

Nov. 7, 2018

Greetings! Iâm announcing today we reach Pharo 7.0.0-rc1! This is the first step to release a definitive version, and while we will continue integrating bug fixes, API change Pull Requests will be delayed until the open of Pharo 8.0.0 development. Now, you would wonder what is the ChangeLog of this releaseâ¦ and answer is we still do not have one (btw, we should find a way to automate this). Anywayâ¦ we are very close to release now :) Please download, test, report issues. Esteban

4 3

Re: [Pharo-dev] [ANN] The STON Specification, Cog speed, and namespaces/modules
by Shaping Nov. 7, 2018

Nov. 7, 2018

Hi Eliot. Pharo (& Squeak & Cuis) Float subclass BoxedFloat64 maps exactly to VW's Double. In 64-bit SmallFloat64 maps exactly to SmallDouble. But I wonder whether there is any issue here. STON would use the print strings for (PSC) Float / (VW) Double, and so deseerialization on Pharo would automatically produce the right class. Going in the other direction might need some help. APF needs support in PSC before one can port, but are representable as suitably-sized word arrays. There is no support for __float128 anywhere in the VM (e.g. not even in the FFI) on PSC as yet. I see Pharoâs WordArray. Iâll work on an APF for Pharo, as time permits. Iâm using APFs in VW in the 300-bit range, and want to reduce the needed precision to 64 bits, to save space and time on large (5 million+) scalar time-series, both on the heap and during BOSSing (25 m save-time now). The problem is not so much an issue for the JulianDayNumber (JDN)-precision, which is adequate in this app at 14 to 15 digits (even though my JDN class subclasses APF, for now). Other calculations need the more extreme precision. I think I can make 128-bit floats work, and would really like to see a small, fast, boxed 128-bit float implementation in Pharo or VW. The APFs are big and slow. Where in the queue of planned improvements to Pharo does such a task lie? I suspect itâs not a very popular item. Broadening the issue somewhat, Iâm trying to find as many good reasons as possible to justify the work needed to port all my VW stuff to Pharo. Iâve seen the references to Cogâs speed and coming speed-up. Are there recent (say, in the last year) benchmarks comparing VW and Pharo? Any details here would be very much appreciated. Having no namespaces in Pharo is, I think, the biggest impediment. I prefer not to prefix class names, but there may be fewer name-collisions than I suppose--maybe none. Still, I need to know how VW and Pharo classes map in order to place overrides and extensions correctly. Besides the mentioned float-class mappings is there a reference on this? Object allSubclasses in Pharo 7 64-bit, produces 14946 classes. Pharo is a little bigger than it used to be. I suppose I donât need to check all unloaded packages because all classes in each of those will have the same unique prefix. Is that correct? Or, I could just load every package I can find, before I check names. But that little experiment has never gone well in the past. Is the Pharo-with-namespaces issue dead or merely suspended, awaiting a more fitting idea than what VW currently offers? Shaping On Tue, Nov 6, 2018 at 12:56 AM Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: STON is able to serialise Pharoâs Floats, what do you mean by double ? Floating-point numbers in IEEE 64-bit format, 14 or 15 significant digits, with a range between =10^307 and 10^307. Additionally, I recently asked Sven if t would be possible to store ScaledDecimals (I think it implements what you call ArbitraryPrecisionFloats) without loss of precision. Iâm referring to VWâs Double (and SmallDouble in 64-bit engines/images). APFs are binary representations that can be arbitrarily large, using Integers (LargePositiveIntegers for example) to model the bits of the mantissa. Before, because STON extends JSON, it was storing all kind of numbers either as float or integer. Now, thanks to Sven, STON stores ScaledDecimals correctly (without loss of precision through serialisation as float, what was done before). But I do not know if this change is integrated in recent images yet. â¦.. Number subclass: #Float instanceVariableNames: '' classVariableNames: 'E Epsilon Halfpi Infinity Ln10 Ln2 MaxVal MaxValLn MinValLogBase2 NaN NegativeInfinity NegativeZero Pi RadiansPerDegree Sqrt2 ThreePi Twopi' poolDictionaries: '' category: 'Kernel-Numbers' My instances represent IEEE-754 floating-point double-precision numbers. They have about 16 digits of accuracy and their range is between plus and minus 10^307. Some valid examples are: 8.0 13.3 0.3 2.5e6 1.27e-30 1.27e-31 -12.987654e12 â¦. I see that Pharoâs Float is VWâs Double. So then I just need to be able to serialize APF. â¦. FIFloatType subclass: #FFIFloat128 instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'UnifiedFFI-Types' I'm a 128bits (cuadruple precision) float. It is usually not used, but some compiler modes support it (__float128 in gcc) THIS IS NOT YET SUPPORTED â¦. The class above is also from the Pharo 7 image. This is the largest of the c-type FFIFloats. Any Float classes of this size and larger for the Smalltalk heap on 64-bit Pharo? Cheers, Shaping Le 6 nov. 2018 Ã 06:58, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > a Ã©crit : (Having domain problems recently. Please excuse this posting if you have seen it twice. I've not seen it appear yet on the list.) Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? Shaping -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of David T. Lewis Sent: Wednesday, October 31, 2018 14:58 To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] [ANN] The STON Specification This is very clear and well written. Dave Hi, Since there can never be enough documentation I finally took some time to write a more formal description of STON as a data format. https://github.com/svenvc/ston/blob/master/ston-spec.md The idea is to let this stabilise a bit and to then update the two other documents describing STON, where necessary: https://github.com/svenvc/ston/blob/master/ston-paper.md https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuc cessfulBuild/artifact/book-result/STON/STON.html Also, the latest changes in STON have to make their way to the Pharo image as well. https://github.com/svenvc/ston All feedback is welcome. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org -- _,,,^..^,,,_ best, Eliot

1 0

Porting from VW to Pharo
by Shaping Nov. 6, 2018

Nov. 6, 2018

Can someone point me to the best tools for porting from VW 7.10 to Pharo 7 64-bit (or maybe 6.1)? I'm not sure what to do about the namespaces. I realize that VW's namespace solution is just a good hack and that the true nature of the problem runs much deeper--but it does a good job of avoiding class-name collisions, which is mostly what I need it for, and I can control exactly how imports work. Any suggestions are welcome. Thanks. Shaping

2 1

[Pharo 7.0-dev] Build #1369: 22636 - Integrate Iceberg 1.4.0
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2018

Nov. 6, 2018

There is a new Pharo build available! The status of the build #1369 was: SUCCESS. The Pull Request #1956 was integrated: "22636 - Integrate Iceberg 1.4.0" Pull request url: https://github.com/pharo-project/pharo/pull/1956 Issue Url: https://pharo.fogbugz.com/f/cases/22636 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Looking for a good shortcut for "contextual spotter"
by Esteban Lorenzano Nov. 6, 2018

Nov. 6, 2018

Hello, Most of you donât know it, but Calypso incorporates an option to show a âcontextual spotterâ which will list all available commands in the context you selected. This is meant to help on discoverability and reachability of commands available. This is *in addition to shortcuts* not a replace of them (but lets be honest, we have far more commands than those that are possible to handle with a simple shortcut). Anyway, originally I mapped this command to meta+/, which fitted well with my keyboard and language, but seems is not the case for many others (and this is not working at all on windows). So. Iâm looking for options :) So far I have this two ideas: 1- alt+enter 2- meta+h First one looks nice, but Iâm not sure it will work on all platforms/combinations. What do you think? Esteban Ps: I will also add an icon somewhere to expose the contextual spotter.

7 13

[Pharo 7.0-dev] Build #1368: 22239-DataAndTimeTesttestAsDateAndTime-is-meaningful-2
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2018

Nov. 6, 2018

There is a new Pharo build available! The status of the build #1368 was: FAILURE. The Pull Request #1948 was integrated: "22239-DataAndTimeTesttestAsDateAndTime-is-meaningful-2" Pull request url: https://github.com/pharo-project/pharo/pull/1948 Issue Url: https://pharo.fogbugz.com/f/cases/22239 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1367: 22560-Clean-magic-numbers-in-InputEventHandler-subclasses
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2018

Nov. 6, 2018

There is a new Pharo build available! The status of the build #1367 was: FAILURE. The Pull Request #1896 was integrated: "22560-Clean-magic-numbers-in-InputEventHandler-subclasses" Pull request url: https://github.com/pharo-project/pharo/pull/1896 Issue Url: https://pharo.fogbugz.com/f/cases/22560 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1365: 22635-Welcome-help-should-show-build-hash-
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2018

Nov. 6, 2018

There is a new Pharo build available! The status of the build #1365 was: SUCCESS. The Pull Request #1955 was integrated: "22635-Welcome-help-should-show-build-hash-" Pull request url: https://github.com/pharo-project/pharo/pull/1955 Issue Url: https://pharo.fogbugz.com/f/cases/22635 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #1366: 22621-FileReferencemoveTo-doesnt-work-with-directories
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2018

Nov. 6, 2018

There is a new Pharo build available! The status of the build #1366 was: SUCCESS. The Pull Request #1949 was integrated: "22621-FileReferencemoveTo-doesnt-work-with-directories" Pull request url: https://github.com/pharo-project/pharo/pull/1949 Issue Url: https://pharo.fogbugz.com/f/cases/22621 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Zinc Websockets
by Shaping Nov. 6, 2018

Nov. 6, 2018

Hi all. What is the easiest way to port Zinc Websockets to VW? Has this been done? Shaping

3 2

[Pharo 7.0-dev] Build #1364: 22634-SystemVersionTesttestDoNotBreakSmalltalkVersion
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2018

Nov. 6, 2018

There is a new Pharo build available! The status of the build #1364 was: FAILURE. The Pull Request #1954 was integrated: "22634-SystemVersionTesttestDoNotBreakSmalltalkVersion" Pull request url: https://github.com/pharo-project/pharo/pull/1954 Issue Url: https://pharo.fogbugz.com/f/cases/22634 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] The STON Specification
by Sven Van Caekenberghe Nov. 6, 2018

Nov. 6, 2018

Hi, Since there can never be enough documentation I finally took some time to write a more formal description of STON as a data format. https://github.com/svenvc/ston/blob/master/ston-spec.md The idea is to let this stabilise a bit and to then update the two other documents describing STON, where necessary: https://github.com/svenvc/ston/blob/master/ston-paper.md https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… Also, the latest changes in STON have to make their way to the Pharo image as well. https://github.com/svenvc/ston All feedback is welcome. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

5 8

Unable to repair repository
by Alistair Grant Nov. 6, 2018

Nov. 6, 2018

Hi Everyone, In the latest Pharo (88c6b8d), attempting to repair the pharo repository, i.e. clone it, first a warning is raised: "There is no associated repository configured." and then a DNU: #pathString was sent to nil. The DNU is because IceTipCopyCommitishCommand>>canBeExecutedInContext: now sends #commitId instead of #shortCommitId. IceTipRepositoryModel>>shortCommitId has an exception handler, while #commitId doesn't. Can someone explain why the warning was added? It is a bit annoying to have to click through dialogs telling me that the repository I'm trying to create needs to be created. Using the generic Error exception handler has the risk of hiding other problems. Wouldn't it be better to create a IceRepositoryMissing error, or similar? Thanks, Alistair

2 2

[ANN] Iceberg v1.3.1
by Cyril Ferlicot Nov. 6, 2018

Nov. 6, 2018

Hello! This week we are releasing the version v1.3 of Iceberg. (https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.0 +https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.1) This version will be available after we merge this PR: https://github.com/pharo-project/pharo/pull/1951 This release contains some new features such as the support of self hosted gitlab, integration with github, etc. It also contains multiple bug fixes, cleanups and enhancements. On the CI part, Guille made the Appveyor build green! This will increase the stability of the windows support. Thanks to all contributors. Enjoy! Full changelog: Features #1021 Self hosted gitlab support #1027 Improved new tag dialog to generate semantic versionning tags #1044 Show a button "View on Github" when creating a PR #1008 Add "create branch from GitHub issue" option #1048 Add commands to open remotes on Github #1010 Add menu entry in extras to force calculate diff Bug corrections #975 Metacello asks too many times what to install when there are conflicting versions #980 Iceberg should Identify better the packages and the normal files #982 The Edit Project should have a Warning if it will affect the packages #986 Iceberg does not realize changes in extended classes #999 Pulling and pushing to a gitolite server asks password #984 Conversion to Tonel generates corrupted .properties #1041 Filter in repository view don't work with capital letters #1019 Metacello Integration leaves Monticello leftover repositories #859 Creating a branch and pushing does not sets the upstream #1043 Packages starting with lowercase not recognized #991 Error on right click in the project editon wizard #775 Reviewing a PR is broken #1036 Debugger if we try to merge without selecting a branch #1064 Fix failing tests regarding clean code in Pharo Enhancements #988 Iceberg should load the packages in a single MCLoader (This will make the loads of packages atomic) #1001 Use "instance creation" instead of "instance-creation" for method protocol name #1004 Use displayScaleFactor in UI #977 Add ToolTip help to the Commands #1030 Better support for binary files #1034 SSH passphrase is now hidden Cleanups #1018 Iceberg UI relies on deprecated classes from Spec and Commander #1051 Clean useless huge hierarchy in Github plugin UI Infrastructure Enhancements #1023 Fix CI for windows -- Cyril Ferlicot https://ferlicot.fr

2 2

Now this is fun ...
by Sven Van Caekenberghe Nov. 5, 2018

Nov. 5, 2018

https://github.com/pharo ;-)

6 6

[Pharo 7.0-dev] Build #1363: 22627-Integrate-Iceberg-131
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

There is a new Pharo build available! The status of the build #1363 was: SUCCESS. The Pull Request #1951 was integrated: "22627-Integrate-Iceberg-131" Pull request url: https://github.com/pharo-project/pharo/pull/1951 Issue Url: https://pharo.fogbugz.com/f/cases/22627 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] 22477 DelayScheduler cleanup and refactoring [was: Where do we go now ?]
by Ben Coman Nov. 5, 2018

Nov. 5, 2018

On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Do we really need 8 delay schedulers (DelayMicrosecondScheduler, > DelayMillisecondScheduler, DelayNullScheduler, > DelayExperimentalSpinScheduler, DelaySpinScheduler, DelayTicklessScheduler, > DelayExperimentalCourageousScheduler, DelayExperimentalSemaphoreScheduler) > ? > I've cleaned the delay scheduling subsystem [1] to condense these alternatives and separate orthogonal functionality. After a couple of reviews this was integrated and made active in last week's Build 1273. Could anyone with test scenarios from previous issues with delays have a bash at stressing the latest build. The old(existing) DelaySpinScheduler remains in the system so it can be activated as a point of comparison (System > Settings > System > Delay Scheduler). Pending any adverse reports the final step will be to remove the old hierarchy next week. There remain separate mutex and semaphore based schedulers since: * they differ by only a couple of overridden methods * their slightly different implementations help highlight the core algorithm * they provide a simple in-Image example of different synchronisation mechanisms. * in isolating edge cases its useful to be able to compare results between implementations I've retained both microsecond and millisecond operation, but extracted into "ticker" classes orthogonal to the "scheduling" classes since: * it makes the core scheduling algorithm independent of time base * millisecond (or other custom) timebase might(?) be more efficient on smaller 32-bit embedded systems * tests can now simulate ticker time to avoid tests interfering with system's-active-scheduler VM interaction (which may be the source of some random CI failures) * delay scheduler tests are now independent of real-time (which may be the source of some random CI failures where delays are affected by varying CI server loads) * when multi-threaded FFI callbacks become available, may facilitate experimenting with: * wake-up from native timers * wake-up of embedded Pharo from the encompassing system Other refactors: * during system snapshot, save/restore of resumption times was happening at user priority which risks a race condition reported at [2]. *All* modification of resumption times now occurs at timing/highest priority. [1] https://pharo.manuscript.com/f/cases/22477/DelayScheduler-cleanup-and-refac… [2] https://pharo.manuscript.com/f/cases/18359/

5 6

[Pharo 7.0-dev] Build #1362: 22627-Integrate-Iceberg-131
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

There is a new Pharo build available! The status of the build #1362 was: FAILURE. The Pull Request #1951 was integrated: "22627-Integrate-Iceberg-131" Pull request url: https://github.com/pharo-project/pharo/pull/1951 Issue Url: https://pharo.fogbugz.com/f/cases/22627 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1361: 22620-Move-zippedunzipped-from-String-to-ByteArray
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

There is a new Pharo build available! The status of the build #1361 was: FAILURE. The Pull Request #1947 was integrated: "22620-Move-zippedunzipped-from-String-to-ByteArray" Pull request url: https://github.com/pharo-project/pharo/pull/1947 Issue Url: https://pharo.fogbugz.com/f/cases/22620 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1360: 22625-FileReferencenextVersion-gets-stuck-at-11
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

There is a new Pharo build available! The status of the build #1360 was: SUCCESS. The Pull Request #1950 was integrated: "22625-FileReferencenextVersion-gets-stuck-at-11" Pull request url: https://github.com/pharo-project/pharo/pull/1950 Issue Url: https://pharo.fogbugz.com/f/cases/22625 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1359: 22614-Integrate-Calypso-v0120
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

There is a new Pharo build available! The status of the build #1359 was: SUCCESS. The Pull Request #1943 was integrated: "22614-Integrate-Calypso-v0120" Pull request url: https://github.com/pharo-project/pharo/pull/1943 Issue Url: https://pharo.fogbugz.com/f/cases/22614 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 29 October 2018
by estebanlm＠gmail.com Nov. 5, 2018

Nov. 5, 2018

Hello! This is my weekly ChangeLog, from 29 October 2018 to 4 November 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=29/10/2018&to=4/11/2018 ChangeLog ========= 29 October 2018: ---------------- * I made a PR to update [Calypso in Pharo 7 to version 0.12.0](https://github.com/pharo-project/pharo/pull/1943). While this should be very easy, in case of Calypso it is a but harder because of its dependency graph, that looks a bit like this : Calypso ClassAnnotation Commander ClassAnnotation SystemCommands Commander ClassAnnotationAnyway, in the medium term, I want to create a tool to do "chained-releases", which is not so easy because we need to modify baselines and do commits, pushs and tags. But it will be possible to do :) cheers! Esteban

1 0

FFI interfacing to thin C layers over C++ libraries [was Re: [squeak-dev] Squeak and Tesseract]
by Ben Coman Nov. 4, 2018

Nov. 4, 2018

While I've done a lot of C programming that is useful for FFI interfacing, I've not done much C++. So just sharing something new I learnt today to help with FFI interfacing to combined C/C++ libraries. I thought maybe others in the same boat could be interested in this. [Original question asked in squeak-dev, cross-posting to pharo-dev] On Fri, 2 Nov 2018 at 21:06, Ben Coman <btc(a)openinworld.com> wrote: > > On Fri, 2 Nov 2018 at 18:44, Edwin Ancaer <eancaer(a)gmail.com> wrote: > >> As I'm looking at a way to automate the search of documents in my humble >> administration, I read some articles about OCR. I came along an article >> about using Python with Tesseract, to transform an scan of a document into >> text, that is searchable. >> >> My question now is if I can do something similar with Squeak. To my >> inexperienced eye, it seems like I should use FFI to call the functions in >> the Tesseract API, but this API is in C++, and I don't know if it is >> possible to use FFI to call C++ functions? >> > > You are right C++ is difficult because of the name mangling of function > symbols, > but good fortune I notice Tesseract has C bindings... > https://github.com/tesseract-ocr/tesseract#for-developers > https://github.com/tesseract-ocr/tesseract/blob/master/src/api/capi.h > so it looks like you are in the clear. > Browsing a deeper I got quite confused for a while. I could see a typedef definition for TessResultRenderer here... https://github.com/tesseract-ocr/tesseract/blob/master/src/api/capi.h#L83 "typedef struct TessResultRenderer TessResultRenderer" which I understood to must refer to *existing* struct, but I couldn't find the definition of that struct anywhere. In particular... $ git clone git@github.com:tesseract-ocr/tesseract.git $ cd tesseract $ find . -type f -name "*h" -exec grep -Hn TessResultRenderer {} \; but didn't find any struct definitions. I could only find TessResultRenderer as a class definition... https://github.com/tesseract-ocr/tesseract/blob/master/src/api/renderer.h#L… and the only thing that I guessed could possibly make sense was that C++ classes and structs could be used interchangeably. My google-fu failed to find anything useful, so an experiment... $ vi test.cpp #include <stdio.h> class SomeClass { public: int a; int b; }; typedef struct SomeClass SomeTypeDef; int main() { SomeTypeDef x; x.a = 5; x.b = 7; printf("Answer is %d\n", x.a + x.b); } $ gcc test.cpp $ ./a.out Answer is 12 Now I noticed that the TessResultRenderer member variables were private... https://github.com/tesseract-ocr/tesseract/blob/master/src/api/renderer.h#L… and curious about that I changed my test example from public to private which somewhat expectedly produced compile errors. So those TessResultRenderer member variables must only be accessed from a member function, but how is that C++ member function called from C to operate on a particular object? An example is TessResultRendererInsert... C Declaration: https://github.com/tesseract-ocr/tesseract/blob/c375f4fbf73b8f761b2e65e0e3a… C Definition: https://github.com/tesseract-ocr/tesseract/blob/c375f4fbf73b8f761b2e65e0e3a… C++ Declaration: https://github.com/tesseract-ocr/tesseract/blob/master/src/api/renderer.h#L… C++ Definition: https://github.com/tesseract-ocr/tesseract/blob/master/src/api/renderer.cpp… So in the C Defintion "the C++ member-function insert() as being called via a function pointer in the struct." (is that a reasonable way to describe it?) In this case, because of the private member variables, our FFI would treat TessResultRenderer as an opaque object, which simplifies things. I would guess in-Image direct access to the member variables from would need to account for the offset due to variables holding the function pointer to the member functions. cheers -ben P.S. for Tesseract FFI it might be good to start with reproducing this example... https://github.com/tesseract-ocr/tesseract/wiki/APIExample#example-using-th…

1 0

Where to discuss strategies and tools for a comeback of Smalltalk using Scratch as entrance
by Bernhard HÃ¶fner Nov. 2, 2018

Nov. 2, 2018

> Hello Group. I like to discuss about the subject and have also some ideas. But I want to ask first for the proper list within the forum. I heard that there is a discussion ongoing and want to participate. > > I will send this question to Squeak and Pharo usegroup and to the Phratch-developer. I assume that there is a common discussion about the subject. Hopefully there is no need to open on each platform an individual thread. > > Regards, Bernhard

2 2

FFI test Smalltalk code
by Eliot Miranda Nov. 2, 2018

Nov. 2, 2018

Hi All, I'm looking at a bug with the Win64 FFI when there are more than four arguments. The test functions are in platforms/Cross/plugins/SqueakFFIPrims/sqFFITestFuncs.c and the SUnit code is in FFI-Tests, e.g. on http://source.squeak.org/FFI. But whereas sqFFITestFuncs.c already contains functions such as ffiTestInts8, ffiTestFloats7, ffiTestFloats13, there are no test for these in FFI-Tests. Can anyone point me to such tests, and/or commit them to FFI-Tests on http://source.squeak.org/FFI? AdvThanksance _,,,^..^,,,_ best, Eliot

1 0

Source/changes file suffixes constants
by Sven Van Caekenberghe Nov. 1, 2018

Nov. 1, 2018

Hi, Current FileStream holds (in the protocol 'file reader services') some constants regarding source/changes file suffixes. Where should we move these to (as FileStream is deprecated) ? There is a class SourceFile, there is PharoFilesOpener, neither seems to fit that well. Suggestions ? Sven

2 2

ClyMethodGroup>>#fileOut dead code ?
by Sven Van Caekenberghe Nov. 1, 2018

Nov. 1, 2018

Hi, ClyMethodGroup>>#fileOut seems like dead code (it sends #trailer to a WriteStream which DNUs). It also uses the deprecated FileStream. Can it be removed ? Sven

3 2