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

DateAndTime Offset Bug Proposal

by Sean P. DeNigris

I was bitten by this very annoying bug again. As most of us probably know due to the steady stream of confused ML posts in the past, the bug in summary is that we have an incomplete timezone implementation that doesn't properly take into account historical DST changes. This flares up without warning especially when DST toggles. I created a wiki page to document the situation: https://github.com/seandenigris/pharo/wiki/Time-Zone-Fiasco Here's an example blowup: at 11:59pm before DST changes, eval aDate := '1/1/1901' asDate. Now, wait two minutes and at 12:01am eval self assert: '1/1/1901' asDate = aDate andâ¦ whammo, an exception! The "different" offsets render equal dates unequal depending on when the objects were created. The more I think about it, the more I think that we should just assume UTC for all Date[AndTime]s that don't explicitly specify an offset, rather than pretend to set an offset which is only sometimes correct. More advanced users can use one of the available libraries to get full timezone support. What do you think? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 8, 2018

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

by Sean P. DeNigris

Peter UhnÃ¡k wrote > Is this the canonical repo? I'm still depending on the version in > SmalltalkHub. I would say it's a judgement call because the original author is no longer active in the community. I originally was pushing all my fixes to the StHub repo, but I started to break the Squeak CI builds, so I forked and made many significant enhancements since. I always depend on my fork and use it in most of my projects, both personal and production. I would say that there is no downside as long as one is using it in Pharo exclusively. I would guess it wouldn't be super complicated to fix for Squeak and sync everything, but so far no one has voiced a need. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 8, 2018

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

by Sean P. DeNigris

Stephane Ducasse-3 wrote > Ok when I will do a pass I will have a look. My goal is to improve for > Pharo. At some point we should do a spike to see how we would implement today now that we have slots. While we're on the subject, I was thinking that for less-than-trival slot layouts, the class definition will start to grow to a very-non-smalltalkish length. Have we thought at all about that and how to maybe present it in more manageable chunks? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 8, 2018

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

by Peter UhnÃ¡k

> > But why it's not a 6.2 version? It would be more clear since this is > continuation of version 6 with new changes. How one would revert to > original 6.1 if this new version isn't working for him? > In the same way as any previous image version... e.g. Pharo 6 is actually Pharo 60508 and lower, Pharo 6.1 is Pharo 60509-60539, and Pharo 6.2 is Pharo 60540+ (give or take couple of versions, don't remember the precise boundaries) and you can download any specific image version you want https://files.pharo.org/image/60/ (it is a bit confusing, but Pharo 6 is not yet using git and the existing infrastructure is not keen on minor releases) Peter

April 8, 2018

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

by Peter UhnÃ¡k

Is this the canonical repo? I'm still depending on the version in SmalltalkHub. Thanks, Peter On Sun, Apr 8, 2018 at 1:22 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ok when I will do a pass I will have a look. My goal is to improve for > Pharo. > > Stef > > On Sun, Apr 8, 2018 at 2:50 AM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > Stephane Ducasse-3 wrote > >> I will work on magritte. > > > > Great, have a look at my fork [1], which contains many enhancements. I > > didn't port them back to the main library because they are only known to > > work in Pharo, I don't know of anyone maintaining from the Squeak side, > and > > I didn't want to break it. > > > > 1. https://github.com/seandenigris/Magritte3 > > > > > > > > ----- > > Cheers, > > Sean > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837. > html > > > >

April 8, 2018

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

by Stan Krupoderov

It's a great new! But why it's not a 6.2 version? It would be more clear since this is continuation of version 6 with new changes. How one would revert to original 6.1 if this new version isn't working for him? On Sun, Apr 8, 2018, 09:56 Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Excellent! Thanks! > > Alexandre > > > On Apr 7, 2018, at 10:48 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > You don't even need to refresh the list; downloading a particular pharo > version (5, 6, 7, ...) always downloads the latest image version available. > > This has been the case for years. Normally you only need to update > PharoLauncher every major release (so e.g. once Pharo 7 is released, etc.) > > > > Peter > > > > On Sat, Apr 7, 2018 at 8:50 AM, Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > > > In "official distributions", just download a new Pharo 61 version from > > > the launcher and it will be this version by default. > > > > > > It should be build 60540 I think. > > > > I do not quite understand. I installed the launcher several months ago. > Should I update the launcher? I think no. > > I see Pharo 6.1(stable), but I am not sure which build it is exactly. > > > > If I refresh the template list, does it ensure that I will have the last > Pharo 6.1? > > > > Alexandre > > > > > > > >> Alexandre > > >> -- > > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > >> Alexandre Bergel http://www.bergel.eu > > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >> > > >> > > >> > > >>> On Apr 5, 2018, at 10:00 AM, Esteban Lorenzano <estebanlm(a)gmail.com > > >>> <mailto:estebanlm@gmail.com>> wrote: > > >>> > > >>> > https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1 > > >>> > > >>> > > >> > > > > > > > > > -- > > > Cyril Ferlicot > > > https://ferlicot.fr > > > > > > > > > > > >

April 8, 2018

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

by Stephane Ducasse

Ok when I will do a pass I will have a look. My goal is to improve for Pharo. Stef On Sun, Apr 8, 2018 at 2:50 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Stephane Ducasse-3 wrote >> I will work on magritte. > > Great, have a look at my fork [1], which contains many enhancements. I > didn't port them back to the main library because they are only known to > work in Pharo, I don't know of anyone maintaining from the Squeak side, and > I didn't want to break it. > > 1. https://github.com/seandenigris/Magritte3 > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

April 8, 2018

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

by Alexandre Bergel

Excellent! Thanks! Alexandre > On Apr 7, 2018, at 10:48 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > You don't even need to refresh the list; downloading a particular pharo version (5, 6, 7, ...) always downloads the latest image version available. > This has been the case for years. Normally you only need to update PharoLauncher every major release (so e.g. once Pharo 7 is released, etc.) > > Peter > > On Sat, Apr 7, 2018 at 8:50 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > In "official distributions", just download a new Pharo 61 version from > > the launcher and it will be this version by default. > > > > It should be build 60540 I think. > > I do not quite understand. I installed the launcher several months ago. Should I update the launcher? I think no. > I see Pharo 6.1(stable), but I am not sure which build it is exactly. > > If I refresh the template list, does it ensure that I will have the last Pharo 6.1? > > Alexandre > > > > >> Alexandre > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >>> On Apr 5, 2018, at 10:00 AM, Esteban Lorenzano <estebanlm(a)gmail.com > >>> <mailto:estebanlm@gmail.com>> wrote: > >>> > >>> https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1 > >>> > >>> > >> > > > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > > > >

April 8, 2018

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

by Sean P. DeNigris

Stephane Ducasse-3 wrote > I will work on magritte. Great, have a look at my fork [1], which contains many enhancements. I didn't port them back to the main library because they are only known to work in Pharo, I don't know of anyone maintaining from the Squeak side, and I didn't want to break it. 1. https://github.com/seandenigris/Magritte3 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 8, 2018

Re: [Pharo-dev] [ann] gt diagrammer

by Stephane Ducasse

Super cool. I would like to see if we can extend to support simple BPMN elements (now my plate is full several level deep). This is a super nice foundation for future student projects :) Stef On Sat, Apr 7, 2018 at 6:39 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > We are happy to announce an initial version of GT Diagrammer, an engine > for constructing diagrams interactively. This is the newest addition to > the next generation GT built on Bloc. > > It looks like this: > https://twitter.com/feenkcom/status/976341449267531776 > > > > We chose to work on Diagrammer for multiple reasons. First, developers > often need to create hand built diagrams to communicate intentions, and an > integrated experience should not require us to leave our environment to > create them. At the same time, Diagrammer is an application that requires > a widgets and interactions, and thus it is a nice exercise for Bloc and > Brick. > > One requirement we had from the beginning was to make it work with any > Bloc element. This means that the editing part had to be reasonably > generic. To this end, we now have elements that can define visual editors. > This is somewhat a combination between Magritte descriptions, and > inspector extensions. An interesting side effect is that now we can edit > visual properties when inspecting any element. In other words, we got the > basic infrastructure of a UI painter. It looks like this: > https://twitter.com/feenkcom/status/982656456968241152 > > The user interface essentially relies on two widgets: scrollable list and > toggle button. While the visual look of the toggle button is inspired from > material design, the most interesting part is that now we have an > implementation for controlling looks per element instance. A key issue here > is that looks can react to events coming from the element and inject visual > attributes and possible even change behavior (for example, changing an icon > while pressing a button). We will post more about looks soon. > > We now also have a nice solution for overlays. For example, we have an > overlay showing selection and an overlay for resizing elements. > > Perhaps less obvious, Diagrammer also offers a basic infrastructure for > the area of visual languages. As Diagrammer works with any Bloc elements, > we can simply create dedicated visual elements. As an example, Diagrammer > comes with an implementation of a UML class figure. Furthermore, as > the functionality does not impose a specific model, custom language > semantics can be mapped on visual actions. > > There are several things to do still for it to become a mature solution. > An important next step is to serialize a diagram scene in a reproducible > manner. Currently, the diagram (or any element) can be exported as pdf ( > https://twitter.com/feenkcom/status/976580153802358786) svg ( > https://twitter.com/feenkcom/status/976578060429484032) png, gif or jpeg > by directly using the low level canvas. However, for the diagram to be > truly useful we need to store the result in either code or another > reloadable form such as STON. Other future directions are related to figure > controlling (for example, custom anchors or line bending points) and > to enhanced editors. > > To play with it, the easiest way is to download the new GT in a Pharo 6.1 > image: > Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > > And then inspect: > GtDiagrammerElement new > > Cheers, > The feenk team > > > -- > www.tudorgirba.com > www.feenk.com > > "Presenting is storytelling." > >

April 7, 2018