April 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Remove all Configurations in the Pharo 6 release?

by Dale Henrichs

On 04/24/2017 01:49 PM, Thierry Goubier wrote: > Le 17/04/2017 Ã 22:13, Dale Henrichs a Ã©crit : >> >> >> On 04/17/2017 12:47 PM, Thierry Goubier wrote: >>> Hi Dale, >>> >>> Le 17/04/2017 Ã 21:05, Dale Henrichs a Ã©crit : >>>> I would think that a `project list` view that made the Metacello >>>> project >>>> registration visible would help developers keep things straight. >>>> >>>> It seems that the issue here is that developers can't tell what >>>> projects >>>> are already loaded in the current image and also cannot tell what >>>> version of the project is loaded ... if you are using the `Metacello >>>> new` to load projects, then Metacello knows what projects and what >>>> versions are loaded in the image .... and that informatation really >>>> needs to be exposed to the developers ... >>>> >>>> If you have a `project list` then you can do things like automatically >>>> do a get on a configuration/baseline when a project is loaded via the >>>> `project list tool` ... there are additional details that need to be >>>> tracked and managed, but without the a basic `project list` the >>>> developer is responsible for "knowing what to do" and the first >>>> step is >>>> to let the developer know exactly which versions of which projects are >>>> loaded in the base image ... >>> >>> I wrote some code to that effect in the AltBrowser (gives access to >>> the project, and all packages loaded via that project, via a Metacello >>> registry tag). >>> >>> It didn't work as well as I expected, in part due to the interaction >>> between the Metacello registry and package loading into the image. >>> Nothing undoable, but due to the total lack of Metacello state in the >>> default Pharo image (nothing is loaded via Metacello in there) and the >>> Catalog browser not using Metacello as well, it was a bit too early to >>> invest into that. >>> >>> In short, the Metacello registry provides a nice entry point for a >>> system browser view of loaded projects and versions, but the Pharo >>> image building process is not yet there. >>> >>> If someone is interested, one need to look into the GT extensions for >>> Metacello objects ... those extensions are a nice source of knowledge >>> about extracting information from the loaded projects. >> This is unfortunate ... I'm willing to help anyone who wants to tackle >> this problem as well --- I know a thing or two about Metacello myself >> and I've had a working `project list` in tODE for 3-4 years now ... oh >> well ... > > The code isn't lost anyway. I've reintegrated it as classifying based > on exiting ConfigurationOf / BaselineOf objects, relying on the spec > if there is no registering in Metacello (kind of funky in the case of a > ConfigurationOf, since you don't know which version was effectively > loaded... so you just play guesses with the various versions available > in the project). Yeah, bootstrapping the registration is dicey business, because you can fall prey to the very bugs you are trying to avoid --- Metacello does a prime registry as a project load doit when the registration code is initially ... you might look at MetacelloProjectRegistry>>primeRegistryFromImage:baselineClasses:prioritizeConfiguration:, but it sounds like you are doing something very similar ... > > At least, now I can easily see directly in the browser how the Pharo 6 > development is moving packages inside configurations and baselines > from version to version. I'll tackle next integrating that with > Metacello, that is running project-based Metacello commands using that > project structure. Let me know if there are any operations that you should think could/should be included in Metacello itself ... If you are doing things that are similar to what I'm doing in tODE, then it probably makes sense to move the method into Metacello, so that other tool builders cna share common code ... Dale > > Thierry > >> Dale >> >> > >

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Pavel Krivanek

Right, next try... https://goo.gl/photos/YnGoZTrpKjJnSbFU9 -- Pavel 2017-04-24 22:22 GMT+02:00 Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > Le 24/04/2017 Ã 22:13, Pavel Krivanek a Ã©crit : > > New version: > > > > https://goo.gl/photos/66Yz3pSSK62aTYV66 > > > > -- Pavel > > > > Pretty nice but too blurry for me. Especially on the right of the screen. > > But maybe it's just me. > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France > >

April 24, 2017

Re: [Pharo-dev] Remove all Configurations in the Pharo 6 release?

by Thierry Goubier

Le 17/04/2017 Ã 22:13, Dale Henrichs a Ã©crit : > > > On 04/17/2017 12:47 PM, Thierry Goubier wrote: >> Hi Dale, >> >> Le 17/04/2017 Ã 21:05, Dale Henrichs a Ã©crit : >>> I would think that a `project list` view that made the Metacello project >>> registration visible would help developers keep things straight. >>> >>> It seems that the issue here is that developers can't tell what projects >>> are already loaded in the current image and also cannot tell what >>> version of the project is loaded ... if you are using the `Metacello >>> new` to load projects, then Metacello knows what projects and what >>> versions are loaded in the image .... and that informatation really >>> needs to be exposed to the developers ... >>> >>> If you have a `project list` then you can do things like automatically >>> do a get on a configuration/baseline when a project is loaded via the >>> `project list tool` ... there are additional details that need to be >>> tracked and managed, but without the a basic `project list` the >>> developer is responsible for "knowing what to do" and the first step is >>> to let the developer know exactly which versions of which projects are >>> loaded in the base image ... >> >> I wrote some code to that effect in the AltBrowser (gives access to >> the project, and all packages loaded via that project, via a Metacello >> registry tag). >> >> It didn't work as well as I expected, in part due to the interaction >> between the Metacello registry and package loading into the image. >> Nothing undoable, but due to the total lack of Metacello state in the >> default Pharo image (nothing is loaded via Metacello in there) and the >> Catalog browser not using Metacello as well, it was a bit too early to >> invest into that. >> >> In short, the Metacello registry provides a nice entry point for a >> system browser view of loaded projects and versions, but the Pharo >> image building process is not yet there. >> >> If someone is interested, one need to look into the GT extensions for >> Metacello objects ... those extensions are a nice source of knowledge >> about extracting information from the loaded projects. > This is unfortunate ... I'm willing to help anyone who wants to tackle > this problem as well --- I know a thing or two about Metacello myself > and I've had a working `project list` in tODE for 3-4 years now ... oh > well ... The code isn't lost anyway. I've reintegrated it as classifying based on exiting ConfigurationOf / BaselineOf objects, relying on the spec if there is no registering in Metacello (kind of funky in the case of a ConfigurationOf, since you don't know which version was effectively loaded... so you just play guesses with the various versions available in the project). At least, now I can easily see directly in the browser how the Pharo 6 development is moving packages inside configurations and baselines from version to version. I'll tackle next integrating that with Metacello, that is running project-based Metacello commands using that project structure. Thierry > Dale > >

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Graham McLeod

+1 graham Cyril Ferlicot D. wrote: > Le 24/04/2017 Ã 22:13, Pavel Krivanek a Ã©crit : >> New version: >> >> https://goo.gl/photos/66Yz3pSSK62aTYV66 >> >> -- Pavel >> > > Pretty nice but too blurry for me. Especially on the right of the screen. > > But maybe it's just me. >

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Cyril Ferlicot D.

Le 24/04/2017 Ã 22:13, Pavel Krivanek a Ã©crit : > New version: > > https://goo.gl/photos/66Yz3pSSK62aTYV66 > > -- Pavel > Pretty nice but too blurry for me. Especially on the right of the screen. But maybe it's just me. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Alexandre Bergel

Excellent!!! Alexandre > On Apr 24, 2017, at 10:13 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > New version: > > https://goo.gl/photos/66Yz3pSSK62aTYV66 > > -- Pavel > > 2017-04-24 10:36 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > The problem is that we need a proper Roassal integration without the white background :). Otherwise it looks not so nice. > > Doru > > > > On Apr 24, 2017, at 10:14 AM, phil(a)highoctane.be wrote: > > > > Nice, I'd put some more Roassal things, like Sunburst > > > > > > On Mon, Apr 24, 2017 at 9:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I like it ! > > > > > On 24 Apr 2017, at 08:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > > > Hi, > > > > > > I tried to prepare some "geeky" screenshot for Pharo 6 announcements and advertisements. > > > > > > https://goo.gl/photos/NF5EC6dCinXRWosA9 > > > > > > -- Pavel > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > âSoftware has no shape. Actually, it has no one shape. It has many." > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Esteban A. Maringolo

I like the focus of the first with the windows of the second. It is... less blur in the new version or a sharper focus area at least. Anyway I love it. :) Esteban A. Maringolo 2017-04-24 17:13 GMT-03:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > New version: > > https://goo.gl/photos/66Yz3pSSK62aTYV66 > > -- Pavel > > 2017-04-24 10:36 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >> >> The problem is that we need a proper Roassal integration without the white >> background :). Otherwise it looks not so nice. >> >> Doru >> >> >> > On Apr 24, 2017, at 10:14 AM, phil(a)highoctane.be wrote: >> > >> > Nice, I'd put some more Roassal things, like Sunburst >> > >> > >> > On Mon, Apr 24, 2017 at 9:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >> > wrote: >> > I like it ! >> > >> > > On 24 Apr 2017, at 08:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> > > wrote: >> > > >> > > Hi, >> > > >> > > I tried to prepare some "geeky" screenshot for Pharo 6 announcements >> > > and advertisements. >> > > >> > > https://goo.gl/photos/NF5EC6dCinXRWosA9 >> > > >> > > -- Pavel >> > >> > >> > >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> âSoftware has no shape. Actually, it has no one shape. It has many." >> >> >

April 24, 2017

Re: [Pharo-dev] Pharo 6 screenshot

by Pavel Krivanek

New version: https://goo.gl/photos/66Yz3pSSK62aTYV66 -- Pavel 2017-04-24 10:36 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > The problem is that we need a proper Roassal integration without the white > background :). Otherwise it looks not so nice. > > Doru > > > > On Apr 24, 2017, at 10:14 AM, phil(a)highoctane.be wrote: > > > > Nice, I'd put some more Roassal things, like Sunburst > > > > > > On Mon, Apr 24, 2017 at 9:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > I like it ! > > > > > On 24 Apr 2017, at 08:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > > > > Hi, > > > > > > I tried to prepare some "geeky" screenshot for Pharo 6 announcements > and advertisements. > > > > > > https://goo.gl/photos/NF5EC6dCinXRWosA9 > > > > > > -- Pavel > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > âSoftware has no shape. Actually, it has no one shape. It has many." > > >

April 24, 2017

Re: [Pharo-dev] Security in the image

by phil＠highoctane.be

I was reading some Smalltalk/X documentation http://live.exept.de/doc/online/english/programming/doingThingsInST.html and found this that could be useful: |s b codeString allowedMessages| allowedMessages := #( + - * / sqrt squared sin cos value ). codeString := Dialog request:'Give an expression on a and b. Use parenthesis as in (a*5) + (b sin):'. codeString notEmptyOrNil ifTrue:[ s := '[:a :b | ',codeString,']'. b := (Block fromString:s). ((b homeMethod literals) contains:[:msg | (allowedMessages includes:msg) not ]) ifTrue:[ Transcript showCR:'Sorry - the block contains a bad message'. ] ifFalse:[ Transcript show:'The value of "',codeString,'" for a=4,b=5 is '; showCR:(b value:4 value:5). ]. ]. On Sun, Apr 23, 2017 at 1:33 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Generally speaking, and from my understanding, you will not be able to do: > > SomeClass compile: 'initialize > MyEvilHack dostuff. > ^ super initialize ' > > In newspeak. > > And that's because you are not able to do: > > SomeClass compile: '...' > > Newspeak uses object capabilities, and following those principles, you > will only be able to compile and install code in a class, if somebody gives > you a capability to do so. > > Then, the problem is that right now Pharo's reflective API is convoluted > with the base API, and thus from any piece of code you can do e.g.,: > > anyObject superclass superclass allSubclasses... > > A possible solution to this is to separate the reflective API from the > base API. > > On Sun, Apr 23, 2017 at 9:16 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> On Thu, Apr 13, 2017 at 3:54 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> > >> > 2017-04-12 18:32 GMT+02:00 Ben Coman <btc(a)openinworld.com>: >> >> >> >> If you want hostile actors working directly within the Image with a >> full >> >> environment, then Pharo is probably not suitable. Its easy to get >> hold of >> >> global class from the Playground references and overwrite/compile any >> method >> >> in the system like this... >> >> >> >> SomeClass compile: 'initialize >> >> MyEvilHack dostuff. >> >> ^ super initialize ' >> >> >> >> You might want to consider Newspeak, which runs on the same VM as Pharo >> >> and has a focus on security. >> > >> > >> > Interesting how they address your example? >> >> Not a direct response, but in Newspeak forum I see Gliad [1] respond >> to LaeMing... "Newspeak (note the capitalization) fits with your >> concerns around security and asynchrony, though the reality needs >> work. The main implementation runs on Smalltalk and as such is >> insecurable. There are less complete implementations based on >> compiling to Javascript and to the Truffle VM, and Ryan's Psoup VM, >> which is probably the most compliant version." >> >> [1] https://groups.google.com/forum/#!searchin/newspeaklanguage/ >> laeming%7Csort:relevance/newspeaklanguage/0-20dj5m6wo/f5xpYnBFBgAJ >> >> cheers -ben >> >> >

April 24, 2017

Re: [Pharo-dev] [ANN] Pharo Spring Friday, April 28

by Juraj Kubelka

Hi Marcus, it is a detail, but the events mentions Slack. Maybe it should mention Discord. I would like to improve the page http://pharo.org/contribute-events <http://pharo.org/contribute-events> by adding a workflow and link to the Pharo Sprint App. How can I do it? Also it would be nice to have the https://association.pharo.org/event-2492488 <https://association.pharo.org/event-2492488> (and others) visible on that page. Is it possible? Is there any calendar plugin that we can plug to the http://pharo.org/contribute-events <http://pharo.org/contribute-events>? I am happy to collaborate on this, if you (or someone else) explain me how to contribute to the web page. Thanks! Juraj > On Apr 24, 2017, at 10:55, marcus.denker(a)inrira.fr <marcus.denker(a)inria.fr> wrote: > > Hi, > > There will be again a Sprint this Friday. > > More infos here: > > https://association.pharo.org/event-2492488 >

April 24, 2017