August 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Moose-dev] feenk log
by Tudor Girba Aug. 17, 2018

Aug. 17, 2018

Hi, Bindings is an issue indeed. They are at the same level as theming and we are not at that level yet. At present time we are focused on showing the breadth of what we can achieve with the new infrastructure. We are currently using only the Bloc keybinding mechanism (equivalent to Keymapping). We did explore the use of Commander, but it was not a match for our initial work. This does not mean that itâs not a good library. Just that we are still exploring and still need to learn what we need. Our focus is on an infrastructure for actions that is as close as possible to Bloc, and to figure out which parts need to go at which level of abstraction. Cheers, Doru > On Aug 17, 2018, at 5:14 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi Doru > > this is great. We are brainstorming to see if and how Commander should be tuned to offer a smoother extensibility. > Julien was developing commands for all his spec tools and guille used commander for Iceberg. > We plan to have a meeting brainstorming about commands and context when guille is back from vacation (before > ESUG). On your side what did you use for the key binding? > > I would like to able to have pluggable binding so that we can have emacs like ctrl a / ctrle â¦ > > Stef > >> On 17 Aug 2018, at 06:47, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> We again got carried away and forgot to update the world about what is up in our corner. Here is a summary: >> >> -- >> Bloc & Brick >> -- >> >> - Text editor stability has been significantly improved >> - Improved support for selection in the text editor >> - Support for typical editing keybindings (copy, cut, paste) >> - Text editor debuggability: >> https://twitter.com/feenkcom/status/1024680215379959808 >> https://twitter.com/feenkcom/status/1020768298017992704 >> - The text editor can handle emojis: >> https://twitter.com/feenkcom/status/1021872214151507968 >> >> -- >> GT >> -- >> >> - Inspector >> We now have an initial version of a working inspector with resizable panes: >> https://twitter.com/feenkcom/status/1030091849795612672 >> https://twitter.com/feenkcom/status/1030314856736538624 >> It shows a display string for the current object: >> https://twitter.com/feenkcom/status/1024564065870512129 >> It can handle errors in the definition of views gracefully: >> https://twitter.com/feenkcom/status/1009174937217720320 >> We now have multiple extensions expressed in the new Inspector: >> https://twitter.com/feenkcom/status/1024321868566814720 >> https://twitter.com/feenkcom/status/1022393383850008576 >> >> - Documenter saw multiple enhancements. >> We can now resize various previews live: >> https://twitter.com/feenkcom/status/1002851190475026432 >> https://twitter.com/feenkcom/status/1001407762285375490 >> https://twitter.com/feenkcom/status/1001152789874167808 >> It now relies on the annotation mechanism from Pillar: >> https://twitter.com/feenkcom/status/1006508725409079298 >> We can now link classes and expand their definition: >> https://twitter.com/feenkcom/status/1014609460520775681 >> https://twitter.com/feenkcom/status/1029085603948843008 >> The preview of examples can handle errors gracefully: >> https://twitter.com/feenkcom/status/1022123808524836864 >> We can run examples in place, enabling a smoother tutorial experience: >> https://twitter.com/feenkcom/status/1028390957023223809 >> We have new documentation expressed in it: >> https://twitter.com/feenkcom/status/1007008814204444672 >> >> >> >> Have fun, >> The feenk team >> >> -- >> www.feenk.com >> >> "Presenting is storytelling." >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

1 0

feenk log
by Tudor Girba Aug. 17, 2018

Aug. 17, 2018

Hi, We again got carried away and forgot to update the world about what is up in our corner. Here is a summary: -- Bloc & Brick -- - Text editor stability has been significantly improved - Improved support for selection in the text editor - Support for typical editing keybindings (copy, cut, paste) - Text editor debuggability: https://twitter.com/feenkcom/status/1024680215379959808 https://twitter.com/feenkcom/status/1020768298017992704 - The text editor can handle emojis: https://twitter.com/feenkcom/status/1021872214151507968 -- GT -- - Inspector We now have an initial version of a working inspector with resizable panes: https://twitter.com/feenkcom/status/1030091849795612672 https://twitter.com/feenkcom/status/1030314856736538624 It shows a display string for the current object: https://twitter.com/feenkcom/status/1024564065870512129 It can handle errors in the definition of views gracefully: https://twitter.com/feenkcom/status/1009174937217720320 We now have multiple extensions expressed in the new Inspector: https://twitter.com/feenkcom/status/1024321868566814720 https://twitter.com/feenkcom/status/1022393383850008576 - Documenter saw multiple enhancements. We can now resize various previews live: https://twitter.com/feenkcom/status/1002851190475026432 https://twitter.com/feenkcom/status/1001407762285375490 https://twitter.com/feenkcom/status/1001152789874167808 It now relies on the annotation mechanism from Pillar: https://twitter.com/feenkcom/status/1006508725409079298 We can now link classes and expand their definition: https://twitter.com/feenkcom/status/1014609460520775681 https://twitter.com/feenkcom/status/1029085603948843008 The preview of examples can handle errors gracefully: https://twitter.com/feenkcom/status/1022123808524836864 We can run examples in place, enabling a smoother tutorial experience: https://twitter.com/feenkcom/status/1028390957023223809 We have new documentation expressed in it: https://twitter.com/feenkcom/status/1007008814204444672 Have fun, The feenk team -- www.feenk.com "Presenting is storytelling."

3 2

Trait method override
by Vitor Medina Cruz Aug. 17, 2018

Aug. 17, 2018

Hello, In a class that uses a Trait, how can I override one of it's method by appending behavior to the method implemented by the Trait? In a typical override, this is done by calling super: method super method "extended behavior" ... Is there a way to change "super" to a reference the Trait? Regards, Vitor

3 6

Is the debugger known to be unstable on recent Pharo 7?
by Tim Mackinnon Aug. 17, 2018

Aug. 17, 2018

Hi, Iâm doing some travelling and had a stretch on a plane with Pharo 7 - 64bit b166, and was trying out some changes to Calypso to plug in some potential keyboard extensions. Anyway, in figuring stuff out I noticed the debugger had a number of issues - which I can try to investigate more but wanted to say something before ploughing on. When I hit a method invoked from the keyboard which has self halt (not a soft breakpoint, as I was changing code and didnât want to keep losing the breakpoint) - when I made a change and hit save I get an extra empty predebug window ? The older debug window also has a my single method but no stack and is not debuggable. The upshot is that I have to start debugging all over again? I also noticed that when I hit an error and got a debugger and then fixed the error, resumed but then hit another - the title of the window was still the old error msg and not the new one (so quite confusing). Has there been recent work done in the debugger that might explain these? Tim Sent from my iPhone

1 1

separate native window of same Pharo image
by Peter UhnÃ¡k Aug. 17, 2018

Aug. 17, 2018

Hi, did anyone play around with launching a separate native window for Pharo? E.g. I have normal window in which Pharo is, and then I open a separate native window that shows just e.g. Transcript. I know that there are some projects like OSWindow-SDL and OSWindows-UI (using WinAPI), but both of them are aimed at opening windows with non-pharo content, which is not what I want. Any pointers? Thanks, Peter

4 7

Re: [Pharo-users] Zinc loading problems (as project dep) - versions mess
by Sven Van Caekenberghe Aug. 16, 2018

Aug. 16, 2018

Yes, those .TheIntegrator versions are not real, can't explain that further. If you want to go to the very latest version, you also have to load the latest version of ConfigurationOfZincHTTPComponents first, else you get an older latest version (yes this is a bit confusing, but it makes perfect sense when you think of it). All this is normally done by the Metacello mechanism. Here is how you can do that in direct scripting: Metacello new configuration: 'ZincHTTPComponents'; repository: 'http://mc.stfx.eu/ZincHTTPComponents'; version: #stable; load: #('Core' 'WebSocket' ). (Untested though). > On 16 Aug 2018, at 19:45, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-users] Zinc loading problems (as project dep) - versions mess > Date: 16 August 2018 at 19:45:41 GMT+2 > To: pharo-users(a)lists.pharo.org > > > I can't understand a mess in Zinc packages versions. I downloaded fresh 6.1 (32bit) image from pharo.org, opened Monticelo Browser and searced for 'Zinc-HTTP' package. > There is version Zinc-HTTP (TheIntegrator.461). Repository info points to "http://mc.stfx.eu/ZincHTTPComponents" by default, so I opened the repository and there is no packages with "TheIntegrator". Even version numbers are different - version SvenVanCaekenberghe.461 is different if I diff it. It looks like the version TheIntegrator.461 is close to SvenVanCaekenberghe.453. > > Next test: when I run this code in fresh image: > > ConfigurationOfZincHTTPComponents project load: #stable > > there is Zinc-HTTP (SvenVanCaekenberghe.453) after load. Why not 475 (it's stable or not)? > > And now, I'm totally confused. > > pf > > >> Hi Petr, >> >> I also have >> >> project: 'ZincHTTPComponents' with: [ >> spec >> className: 'ConfigurationOfZincHTTPComponents'; >> repository: 'http://mc.stfx.eu/ZincHTTPComponents'; >> loads: #('Core' 'Tests' 'REST' 'AWS'); >> versionString: #stable ]; >> >> in my main project, which has not changed in years and always works, AFAIK. >> >> I also use(d) the load expression >> >> ConfigurationOfZincHTTPComponents project load: #stable >> >> a lot and it normally works. >> >> Metacello sometimes acts weird when you already have code/projects loaded. >> >> I am afraid I don't know what could be wrong. >> >> Sven >> >>> On 16 Aug 2018, at 17:09, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> >>> From: Petr Fischer <petr.fischer(a)me.com> >>> Subject: Zinc loading problems (as project dep) >>> Date: 16 August 2018 at 17:09:41 GMT+2 >>> To: pharo-users(a)lists.pharo.org >>> >>> >>> Hello, >>> >>> I am trying to load stable Zinc as dependency in my project, like this: >>> >>> ... >>> project: 'ZincHTTPComponents' with: [ >>> spec >>> className: #ConfigurationOfZincHTTPComponents; >>> versionString: #'stable'; >>> loads: #('Core' 'WebSocket' ); >>> repository: 'http://mc.stfx.eu/ZincHTTPComponents/' ]. >>> ... >>> >>> I need WebSocket package, whiuch is not loaded by default and updated Core package (there is new method ZnClient defaultEncoder: - I need this). >>> >>> Actual stable version of ZincHTTPComponents is 2.9.4 (for Pharo 6.x) and in this 2.9.4 stable version, there is Zinc-HTTP package with version Zinc-HTTP-SvenVanCaekenberghe.475. >>> >>> Default version in Pharo 6.1 image is Zinc-HTTP-TheIntegrator.461. >>> >>> After my project configuration load, there is no updated Zinc in my image. >>> >>> When I try to load manually by: >>> >>> ConfigurationOfZincHTTPComponents project load: #stable. >>> >>> error dialog occurs complaining about Zinc-HTTP have unsaved changes in the image (load/merge/cancel) - so, maybe, automatic load of Zinc as project depenedency is ignored due to this reason. >>> >>> How to solve this situation? Can I force dependency to load (in my project ConfigurationOf)? >>> >>> Thanks! Petr Fischer >>> >>> >>> >>> >>> >> > > >

2 1

Re: [Pharo-users] Zinc loading problems (as project dep)
by Sven Van Caekenberghe Aug. 16, 2018

Aug. 16, 2018

Hi Petr, I also have project: 'ZincHTTPComponents' with: [ spec className: 'ConfigurationOfZincHTTPComponents'; repository: 'http://mc.stfx.eu/ZincHTTPComponents'; loads: #('Core' 'Tests' 'REST' 'AWS'); versionString: #stable ]; in my main project, which has not changed in years and always works, AFAIK. I also use(d) the load expression ConfigurationOfZincHTTPComponents project load: #stable a lot and it normally works. Metacello sometimes acts weird when you already have code/projects loaded. I am afraid I don't know what could be wrong. Sven > On 16 Aug 2018, at 17:09, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Zinc loading problems (as project dep) > Date: 16 August 2018 at 17:09:41 GMT+2 > To: pharo-users(a)lists.pharo.org > > > Hello, > > I am trying to load stable Zinc as dependency in my project, like this: > > ... > project: 'ZincHTTPComponents' with: [ > spec > className: #ConfigurationOfZincHTTPComponents; > versionString: #'stable'; > loads: #('Core' 'WebSocket' ); > repository: 'http://mc.stfx.eu/ZincHTTPComponents/' ]. > ... > > I need WebSocket package, whiuch is not loaded by default and updated Core package (there is new method ZnClient defaultEncoder: - I need this). > > Actual stable version of ZincHTTPComponents is 2.9.4 (for Pharo 6.x) and in this 2.9.4 stable version, there is Zinc-HTTP package with version Zinc-HTTP-SvenVanCaekenberghe.475. > > Default version in Pharo 6.1 image is Zinc-HTTP-TheIntegrator.461. > > After my project configuration load, there is no updated Zinc in my image. > > When I try to load manually by: > > ConfigurationOfZincHTTPComponents project load: #stable. > > error dialog occurs complaining about Zinc-HTTP have unsaved changes in the image (load/merge/cancel) - so, maybe, automatic load of Zinc as project depenedency is ignored due to this reason. > > How to solve this situation? Can I force dependency to load (in my project ConfigurationOf)? > > Thanks! Petr Fischer > > > > >

2 1

Zinc loading problems (as project dep)
by Petr Fischer Aug. 16, 2018

Aug. 16, 2018

Hello, I am trying to load stable Zinc as dependency in my project, like this: ... project: 'ZincHTTPComponents' with: [ spec className: #ConfigurationOfZincHTTPComponents; versionString: #'stable'; loads: #('Core' 'WebSocket' ); repository: 'http://mc.stfx.eu/ZincHTTPComponents/' ]. ... I need WebSocket package, whiuch is not loaded by default and updated Core package (there is new method ZnClient defaultEncoder: - I need this). Actual stable version of ZincHTTPComponents is 2.9.4 (for Pharo 6.x) and in this 2.9.4 stable version, there is Zinc-HTTP package with version Zinc-HTTP-SvenVanCaekenberghe.475. Default version in Pharo 6.1 image is Zinc-HTTP-TheIntegrator.461. After my project configuration load, there is no updated Zinc in my image. When I try to load manually by: ConfigurationOfZincHTTPComponents project load: #stable. error dialog occurs complaining about Zinc-HTTP have unsaved changes in the image (load/merge/cancel) - so, maybe, automatic load of Zinc as project depenedency is ignored due to this reason. How to solve this situation? Can I force dependency to load (in my project ConfigurationOf)? Thanks! Petr Fischer

1 0

Dynabook and interest based learning
by Hilaire Aug. 16, 2018

Aug. 16, 2018

How can Dynabook and interest based learning can be related? http://blog.drgeo.eu/post/2018/Interest-based-learning Hilaire -- Dr. Geo http://drgeo.eu

2 1

XML Writer not pretty printing
by Peter Uhnak Aug. 16, 2018

Aug. 16, 2018

Hi, I am trying to output a pretty printed document, but it seems that the configuration is being ignored doc := '<root> <tab/> <twoSpaces/> <fourSpaces/> </root>' parseXML. String << [ :stream | doc printOn: stream beforeWritingDo: [ :writer | writer enablePrettyPrinting; enablePlatformSpecificLineBreak. writer formatter indentString: ' '. ] ] produces "'<root> <tab/> <twoSpaces/> <fourSpaces/> </root>'" I thought that maybe #preservesIgnorableWhitespace: has something to do with it, but whether it is true or false, the output is not pretty printed (not to mention, that pretty printing should ignore any preserved whitespaces anyway). Is this a bug? Should I print it in a different way? Thanks, Peter

2 2

Re: [Pharo-users] Is there a project Label for packages
by Eric Gade Aug. 14, 2018

Aug. 14, 2018

Unless I'm mistaken, the `BaselineOfXXX` is, in part, a description of all the packages used by a given project. On Sat, Aug 11, 2018 at 1:18 PM, Alidra Abdelghani via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Alidra Abdelghani <alidrandco(a)yahoo.fr> > To: pharo-users(a)lists.pharo.org > Cc: > Bcc: > Date: Sat, 11 Aug 2018 18:18:17 +0100 > Subject: Is there a project Label for packages > 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 > > > > -- Eric

3 2

code completion - order classes suggested by match then package reference count?
by PAUL DEBRUICKER Aug. 13, 2018

Aug. 13, 2018

Hi - When I want to use an OrderedCollection in Pharo 6.1 the code completion has me write "Ordere" before it is the one selected. If I have ever used an OrderPreservingDictionary (which comes up first) I've forgotten, but daily use OrderedCollections. Is there a way now to change the sort order of classes so that they sort by # of uses/references in the image or package I'm developing in? I'm using the default E completion if it matters. Thanks Paul

2 1

Deprecation rewrite introduces infinite recursionâ¦ how to prevent that?
by Damien Pollet Aug. 13, 2018

Aug. 13, 2018

I have a double-dispatch chain: x generic: y â y firstDispatch: x â x secondDispatchFromY: y However this has been added after the fact, so there are direct uses of the secondDispatchFromY: layer, which I'd like to deprecate/rewrite to use the generic: one. But if I do so, the intermediate firstDispatch: gets rewritten in the process, and this results in an infinite recursion. Is there a way to formulate the rewrite rule to avoid that? I could make a whole new set of secondDispatchFromYbis: methods, change the firstDispatch: ones to use those, and then the rewrite would be ok, but it seems like a lot of noise in the code for a small deprecationâ¦ Thinking of it, this is not really a deprecation, more like an advice on proper useâ¦ -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

1 1

mustache bug?
by Peter UhnÃ¡k Aug. 13, 2018

Aug. 13, 2018

Hi, I'm using Mustache for Pharo, and according to mustache docs ( https://mustache.github.io/mustache.5.html ), when a key is not found, it should look into parents contexts. However that does not seem to be the case: str := '{{root}} {{#items}} {{root}}.{{name}} {{/items}}'. data := { 'root' -> 'ROOT'. 'items' -> { { 'name' -> 'first' } asDictionary. { 'name' -> 'second' } asDictionary. } } asDictionary. (MustacheTemplate on: str) value: data. I should get "ROOT.first", etc., but instead I get ".first", ".second". Thanks, Peter

3 3

[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

BS Web and Pharo
by Tim Mackinnon Aug. 7, 2018

Aug. 7, 2018

Hey guys - when reading about the BS web (great article btw - https://pxlnv.com/blog/bullshit-web/ ) it reminded me about the constant pestering to sign up for the Pharo newsletter. Given I am signed up - how can I stop it always popping up? Itâs in the list of the BS web... so do we really need it to do this? At least it should be a cookie that if I have it it goes away, or better still - just put it as a menu entry and let people sign up if they like out stuff? Given our community fights the BS can't we lead better? Tim Sent from my iPhone

6 6