- Pharo-users - lists.pharo.org

Re: [Pharo-users] IdentityDictionary reset

by Alistair Grant

Hi Dario, On 9 April 2018 at 10:00, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> wrote: > Ciao, > > in the Pharo 4.0 image i have a IdentityDictionary with ten items. > > Now when i reset the dictionary the system behaves as follows: > > Version A) resetAllLocks > > locks keysAndValuesDo:[:k :v | locks removeKey: k ifAbsent: [self halt]] > > > Not all items are removed fro the dictionary. > > > Version B) resetAllLocks > > locks keys do:[:k | locks removeKey: k ifAbsent: [self halt]] > > All the items are always removed. > > > Considerations about it? The first version modifies the collection while iterating over it - generally a bad thing to do. The second version creates a new collection of keys and then uses it to remove the items - much safer. If you set a breakpoint in the methods and step into each message send you'll be able to see the difference. Cheers, Alistair

April 9, 2018

IdentityDictionary reset

by Trussardi Dario Romano

Ciao, in the Pharo 4.0 image i have a IdentityDictionary with ten items. Now when i reset the dictionary the system behaves as follows: Version A) resetAllLocks locks keysAndValuesDo:[:k :v | locks removeKey: k ifAbsent: [self halt]] Not all items are removed fro the dictionary. Version B) resetAllLocks locks keys do:[:k | locks removeKey: k ifAbsent: [self halt]] All the items are always removed. Considerations about it? Thanks, Dario

April 9, 2018

Re: [Pharo-users] SmalltalkCI now supports loading tonel-based projects

by Peter UhnÃ¡k

> do you use filetree:// or tonel:// ? Neither. as I said, it requires no change in the configuration. But naturally it requires tonel in the image, so Pharo 6.1+ I don't know what's the purpose of your set-up.st ... that's SmalltalkCI's responsibility to load the code. Peter On Mon, Apr 9, 2018 at 2:05 AM, Bernardo Ezequiel Contreras < vonbecmann(a)gmail.com> wrote: > i changed the pharo version from 6.0 to 6.1, and use tonel:// > and then it worked! > > https://travis-ci.org/vonbecmann/linked-list/builds/363909898 > > thanks. > > > On Sun, Apr 8, 2018 at 8:15 PM, Bernardo Ezequiel Contreras < > vonbecmann(a)gmail.com> wrote: > >> do you use filetree:// or tonel:// ? >> >> thanks in advance. >> >> >> On Sat, Apr 7, 2018 at 6:28 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >>> Hi, >>> >>> SmalltalkCI now supports loading tonel-based projects, so feel free to >>> start using it. >>> >>> The configuration is still the same. >>> >>> Please note that coveralls support for tonel is not yet in place, but >>> that's just a cherry on top. :-) >>> >>> Cheers, >>> Peter >>> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. >> > > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. >

April 9, 2018

Re: [Pharo-users] SmalltalkCI now supports loading tonel-based projects

by Bernardo Ezequiel Contreras

i changed the pharo version from 6.0 to 6.1, and use tonel:// and then it worked! https://travis-ci.org/vonbecmann/linked-list/builds/363909898 thanks. On Sun, Apr 8, 2018 at 8:15 PM, Bernardo Ezequiel Contreras < vonbecmann(a)gmail.com> wrote: > do you use filetree:// or tonel:// ? > > thanks in advance. > > > On Sat, Apr 7, 2018 at 6:28 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Hi, >> >> SmalltalkCI now supports loading tonel-based projects, so feel free to >> start using it. >> >> The configuration is still the same. >> >> Please note that coveralls support for tonel is not yet in place, but >> that's just a cherry on top. :-) >> >> Cheers, >> Peter >> > > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

April 9, 2018

Re: [Pharo-users] SmalltalkCI now supports loading tonel-based projects

by Bernardo Ezequiel Contreras

do you use filetree:// or tonel:// ? thanks in advance. On Sat, Apr 7, 2018 at 6:28 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > SmalltalkCI now supports loading tonel-based projects, so feel free to > start using it. > > The configuration is still the same. > > Please note that coveralls support for tonel is not yet in place, but > that's just a cherry on top. :-) > > Cheers, > Peter > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

April 8, 2018

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

by Tudor Girba

Hi, > On Apr 8, 2018, at 10:27 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Tudor, > > Very nice! Thank you for sharing, this seems to be hard work. Thanks. > If you welcome some feedback: > > Live tab: > - When I select "Figure" button, then choose from the figures toolbar and put a figure, the selection focus goes back to the "Select" button loosing the figures toolbar. It would be nice to save some clicks by staying in the Figure when putting a lot of figures. Indeed, we are thinking about keeping the Figure mode when pressing Shift. > - The "Figure" are actually UML figures? It would be cool to categorize the types of figures available in a toolbar. The Figures is actually any figures. The figures available are there for validation to show that both simple figures and complicated one (such as a UML class) can work fine. But, you can define your own stencils (factories of figures) and they will appear there. > - Clicking "Line" button does not display any lines to select (maybe ToDo?) ToDo indeed :). > Events tab > - I guess is used for Undo/Redo > "User data", "Resizers", and "Transformation" > - I didn't understood what are they for. These are element specific views in the inspector, each interesting for different purposes. For example, the Events presentation shows a log of all events that reached the element - a very useful input when debugging UI logic. > I am intrigued by the "inject visual attributes" per-instance, maybe something like the old Parts Workbench from VisualSmalltalk? I do not know what the Parts Workbench is. In our case, we want to be able to specify the look of an element independent from the element itself, and we want to be able to do that per element instance, not per type, and not as a global behavior (like in the current theme). Cheers, Doru > Cheers, > > HernÃ¡n > > > > > 2018-04-07 13:39 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > 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 > <diagrammer-overview.png> > > > 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." > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Sometimes the best solution is not the best solution."

April 8, 2018

Re: [Pharo-users] Black screen on Mac OSX

by Hilaire

It is strange. The image in the package should be fine because it is working on Linux and windows. I will try too in a computer of the school next week. Thanks for the test! Hilaire Le 07/04/2018 Ã 17:43, Stephane Ducasse a Ã©critÂ : > Hi Hilaire > > The app goes to the dock but nothing happens. What is strange is that > it is assigned to none display. > I tried to open the drgeo.image with my working Pharo6.1VM and it did not work. > I tried to open the drgeo.image with my working Pharo70VM and it did not work. > => did not open. > > I could open one of my Phaor 70 images with the VM you ship. > > I have no log files or others. So I do not know what to do. > > Stef -- Dr. Geo http://drgeo.eu

April 8, 2018

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

by HernÃ¡n Morales Durand

Hi Tudor, Very nice! Thank you for sharing, this seems to be hard work. If you welcome some feedback: Live tab: - When I select "Figure" button, then choose from the figures toolbar and put a figure, the selection focus goes back to the "Select" button loosing the figures toolbar. It would be nice to save some clicks by staying in the Figure when putting a lot of figures. - The "Figure" are actually UML figures? It would be cool to categorize the types of figures available in a toolbar. - Clicking "Line" button does not display any lines to select (maybe ToDo?) Events tab - I guess is used for Undo/Redo "User data", "Resizers", and "Transformation" - I didn't understood what are they for. I am intrigued by the "inject visual attributes" per-instance, maybe something like the old Parts Workbench from VisualSmalltalk? Cheers, HernÃ¡n 2018-04-07 13:39 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > 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." > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > >

April 8, 2018

[ann] gt diagrammer

by Tudor Girba

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

Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

by Stephane Ducasse

Because now when I load pillar Metacello new baseline: 'Pillar'; repository: 'github://pillar-markup/pillar:newpipeline/src'; load I get an error because Magritte-MOrph-SeasnDeNigris.95 is not found So I cannot build pillar anymore! :(

April 7, 2018