- Pharo-users - lists.pharo.org

[ANN] Magritte moved to github
by Norbert Hartl Aug. 12, 2018

Aug. 12, 2018

I moved magritte code today from smalltalkhub to github. I also changed the dependencies of magritte for grease and seaside to be the github repositories and not smalltalkhub. Please let us work on github for magritte and update smalltalkhub when necessary. Hope you like it! Travis build has also been added. Norbert

4 5

How to resume the debugger in code without extra debug window?
by Tim Mackinnon Aug. 11, 2018

Aug. 11, 2018

Iâm wondering if someone knows the trick to programmatically restarting the debugger (or pre-debugger) without getting an extra window? In my debug action (a button) I have some code that does: aContext stack second restart However this gives me a second pre-debug window? Any thoughts?

2 2

Pharo 7 file streams guideline
by Pavel Krivanek Aug. 11, 2018

Aug. 11, 2018

Hello, I've prepared a draft of a short document that should help you with the transition to the "new" file streams API in Pharo 7. https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD Pull requests are welcome. Cheers, -- Pavel

11 25

Is there a project Label for packages
by Alidra Abdelghani Aug. 11, 2018

Aug. 11, 2018

Hi, I would like to filter Packages according to the project they have been developed in (For instance, the Roassal packages, the Seaside packages, the Moose packages,â¦) So I am wondering if there is any way to question a package about the project(s) it belong to? If not in Pharo, maybe there such a thing in Famix? If not, is there a way to reach this information (a repo, a web site, â¦.) NB. I could use the prefix of the name of the package, but this does not seem to be always accurate (for the Pharo project for instance) Thanks a lot in advance Abdelghani

1 0

Why is there no #assert:notEquals: or #shouldnt:equal: or #deny:equals: method?
by Tim Mackinnon Aug. 10, 2018

Aug. 10, 2018

Iâm trying to write more exercism tests and Iâm baffled why there isnât the inverse equivalent of #assert:equals: which shows a useful test response where you can easily see whatâs going on. #assert:equals: is very nice, showing you a diff browser - I kind of expect the opposite to be there, but it all looks like a bit of mess with assert vs should and deny vs shouldnât -did we change tact somewhere over the years and not deprecate stuff? Tim

4 4

Re: [Pharo-users] Dynabook concept under Dr. Geo perspective
by Hilaire Aug. 10, 2018

Aug. 10, 2018

In the cited post bellow, I pointed to the wrong text regarding Dr. Geo and Dynamic media. Here is the right one: http://blog.drgeo.eu/post/2018/Dr.-Geo-and-Dynamic-media Hilaire Le 19/07/2018 Ã 15:19, Hilaire a Ã©critÂ : > Hi, > > The Dynabook concept and Dr. Geo share some values. > > Here is how http://blog.drgeo.eu/post/2018/The-Dynabook-Concept > > Hilaire -- Dr. Geo http://drgeo.eu

1 0

New Iceberg Version 1.2.1
by tesonep＠gmail.com Aug. 9, 2018

Aug. 9, 2018

New Iceberg Version 1.2.1 [ https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.0 + https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.1] Thanks to all brave users, issue reporters, and contributors :). This version includes the implementation of projects. Projects are a way of defining basic metadata of the repository. Now, this metadata just includes the source directory. This means that people do not need anymore to provide ALL THE TIME the source directory. Instead, every repository includes a project file that provides it. Iceberg will guide people to create the given file. This file is managed by Iceberg and people should not touch it from the outside or accept the consequences :). This version is integrated in the latest Pharo 7 images. #New Features - #866 Introduce first version of Projects #Infrastructure - #870 Improving tests of Metacello Integration - #903 Split basic tests from metacello tests in CI - #914 Sync Wiki with documentation directory automatically - #934 Manually check metacello integration dialogs - #935 Try to refrite the metacello integration tests. - #940 Installation in new Pharo should also bootstrap pharo repository #Enhancements - #675 The History of a Method in Calypso should show a progress bar. - #788 Show progress during network operations (fetch,push, ...) Libgit. - #875 Tonel plugin does not delete .filetree Migration - #897 Update to OSSubprocess 1.0.1 - #911 Repair Checkout branch should appear in "no project found" - #933 Fix Edit repository dialog - #939 IceInteractiveErrorVisitor duplicates IceTipInteractiveErrorVisitor - #944 Extract pharo repository bootstrap code into iceberg #Bug Fixes - #828 Convert sources to tonel raises an Exception - #839 Infinite loop in IceGitLocalRepositoryType if the path is wrong - #849 VM crash while saving credentials Credential Manager - #851 .properties file is not create if project is imported and not cloned. - #869 Error msg after an http timeout is unreadable - #873 Error with credential provider Credential Manager - #874 The integration with Metacello does not work when there is a src directory, but not project file. - #880 Putting "." in project src field gives dnu - #884 Edit Project Dialog tries to select 'src' folder as default, but does not handle if it does not exists - #886 Edit Project Dialog does not allow to select the root of the repository as source directory - #888 Could not locate repository does not have subdirectory anymore. - #889 Loading an unborn project through metacello does not work - #894 GitHubAPI fails when the API responds with a 204 No Content - #901 I get a DNU projectName.... - #902 Edit project metadata does not detect default format - #918 Cloning pharo from a sync'ed repository does not correctly show dirty packages - #928 Pull request cancel - #930 Changed ivar/slot name in stateful trait not recognized as a change - #931 DNU when trying to unload an Iceberg pkg where underlying Pharo pkg has been removed - #932 Pharo repository forgets packages - #938 Do not catch assertion failures - #941 Iceberg pre-installed repository has wrong repair action - #946 Fixing Metacello Integration Tests - #948 Cloning from github creates an invalid remote - #950 Iceberg v1.2.0 breaks projects Metacello Integration bug - #951 New project window should be coherent on the vocabulary UI enhancement - #953 Make remote request anonymous enhancement - #952 Cannot Clone Pharo Repository Pharo plugin bug - #955 Repair actions for repositories with fetch required are wrong UI bug -- Pablo Tesone. tesonep(a)gmail.com

5 11

Dynabook and group learning
by Hilaire Aug. 9, 2018

Aug. 9, 2018

Some though on Dynabook and learning in group. http://blog.drgeo.eu/post/2018/Learning-in-group -- Dr. Geo http://drgeo.eu

1 0

Dynabook and learning by doing
by Hilaire Aug. 7, 2018

Aug. 7, 2018

How could Dynabook and learning by doing could be related? http://blog.drgeo.eu/post/2018/Learning-by-doing Hilaire -- Dr. Geo http://drgeo.eu

1 0

Re: [Pharo-users] Pharo Launcher & Stored Settings
by werner kassens Aug. 7, 2018

Aug. 7, 2018

On 08/07/2018 02:15 AM, Evan Donahue wrote: > Yes, that's right. As long as I don't "store settings" everything is > ok, but if I do find myself wanting to change a global setting of some > kind, and I hit "store," it /also/ stores the metacello paths, which > will then be incorrect for the next new image I create. Also, even if > I delete them, it seems to autogenerate one (but not both) of the > paths incorrectly (with that crazy /build) path. > > More generally though, all I was trying to do was use Pharo launcher > and keep repositories separate, which I was advised to do by the list. Hi Evan, yes exactly. the defaultÂ if i dont change & _store_ settings is: i make via launcher a pharo6.1blabla, it has its own repository-directory; i make the next one, pharo6.1blabla-01, open monticello and it has another package-cache. i did not test this, but i guess it could be possible that if you store settings just once even _without_ changing anything, the local cache directory will be stored, as the class-var-accessor produced a valid path, and from then on this setting will not change anymore for new builds via launcher. you either reset the settings via deleting the monticello records in the settings file found via StartupPreferencesLoader preferencesVersionFolder. or if you need to store changed settings in a general way eg for all 6.1 versions, you do that deleting afterwards. i agree that the 2 monticello-settings behave differently and that this is either irritating or probably a bug (because the second behaviour can make storing other settings difficult), but then <shrugging shoulders> i have to admit i was never bothered by this behaviour. werner

1 0