December 2018 - Pharo-users

Re: [Pharo-dev] New book: Pharo with Style
by Benoit St-Jean Dec. 31, 2018

Dec. 31, 2018

Besides, I forgot to add one comment : you should have guidelines for protocol naming.Â It's not critical per se but I find it quite annoying to look for stuff in "enumerating" when it's been put in "printing" !Â loll On 2018-12-31 03:51, Stephane Ducasse wrote: > Thanks! Thanks! > I will go over it (now laying on my back :(( stupid muscles strike back!) > > On Mon, Dec 31, 2018 at 2:18 AM Benoit St-Jean <bstjean(a)yahoo.com> wrote: >> On 2018-12-30 16:13, Stephane Ducasse wrote: >>> Hello Fellow Pharoers >>> >>> I'm happy to announce a new little book to improve the culture around Pharo. >>> I will revise it in the future so you can feel free to send feedback >>> and pull requests >>> to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle >>> >>> Stef >>> >>> "The best way to predict the future is to invent" so I do it. >> StÃ©phane, >> >> You'll find, attached, a revised PDF version with my comments. >> >> >> >> -- >> ----------------- >> BenoÃ®t St-Jean >> Yahoo! Messenger: bstjean >> Twitter: @BenLeChialeux >> Pinterest: benoitstjean >> Instagram: Chef_Benito >> IRC: lamneth >> Blogue: endormitoire.wordpress.com >> "A standpoint is an intellectual horizon of radius zero". (A. Einstein) >> -- ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein)

1 0

Re: [Pharo-dev] New book: Pharo with Style
by Benoit St-Jean Dec. 31, 2018

Dec. 31, 2018

On 2018-12-30 16:13, Stephane Ducasse wrote: > Hello Fellow Pharoers > > I'm happy to announce a new little book to improve the culture around Pharo. > I will revise it in the future so you can feel free to send feedback > and pull requests > to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle > > Stef > > "The best way to predict the future is to invent" so I do it. StÃ©phane, You'll find, attached, a revised PDF version with my comments. -- ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein)

1 0

Magritte seaside save
by Vitor Medina Cruz Dec. 30, 2018

Dec. 30, 2018

Hello, So: > > MyObject new asComponent addValidatedForm > How do I define save callBack? I tried: MyObject new asComponent addValidatedForm : {#save -> 'save'. #cancel -> > 'cancel'}. > and defined save in both instance or class side of MyObject, but that didn't work. Regards, Vitor. <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Livre de vÃrus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 2

Re: [Pharo-users] how to use indexes to copy a substring out of a string
by Ben Coman Dec. 30, 2018

Dec. 30, 2018

On Sun, 30 Dec 2018 at 17:53, Roelof Wobben via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Op 30-12-2018 om 02:14 schreef Ben Coman: > > 'abcdefg' asArray overlappingPairsRemainderCollect: [ :a :b :rem | { > a.b.rem } ] > > This was deliberately only half a solution. The block above "[ :a :b :rem | { a.b.rem } ]" is a placeholder only - to show you what data you would have to work with. You need to adapt it. > Sorry, I do not see how this can work so I can find the answer > > qjhvhtzxzqqjkmpb is nice because is has a pair that appears twice (qj) > > so if I try it on the code for overlappingPairsRemainderCollect I see > this as answer : > > "#($q $j #($h $v $h $t $z $x $z $q $q $j $k $m $p $b))" > The line above looks pertinent!! Inside the block you will have... a ==> $q b ==> $j rem ==> #($h $v $h $t $z $x $z $q $q $j $k $m $p $b) <snip> > "#($p $b #())" > > How does help me the output in telling me that there are two pairs that > are there two times > You might start with the following block... [ :a :b :rem | self halt. rem overlappingPairsCollect: [ :a2 :b2 | ...something... ] ] and from in the debugger experiment by inspecting the second half of it. cheers -ben

1 0

Re: [Pharo-users] how to use indexes to copy a substring out of a string
by Roelof Wobben Dec. 29, 2018

Dec. 29, 2018

Op 29-12-2018 om 21:05 schreef HernÃ¡n Morales Durand via Pharo-users: Thanks, I will look at these but I think there are too advanced for Aoc challenges but maybe I see a way to solve it more easily

1 0

Subscribing to streaming input with ZnClient
by Jimmie Houchin Dec. 29, 2018

Dec. 29, 2018

Hello, I am wanting to subscribe to a perpetual stream of JSON data in my app. I have failed to find an example which helps me understand how to do so. It may be there but I have not discovered it. How do I do something like that? A curl example from the website. curl \ -H "Authorization: abcdefg?????" \ "https://stream-mystreamingsite.com/stream?query=whatIwant" *Response Headers* HTTP/1.1 200 OK Access-Control-Allow-Headers: Authorization, Content-Type, Accept-Datetime-Format Access-Control-Allow-Methods: PUT, PATCH, POST, GET, OPTIONS, DELETE Access-Control-Allow-Origin: * Content-Type: application/octet-stream After subscribing to the stream I will need to get and access the JSON data so that my app can process it. Any help and wisdom greatly appreciated. Thanks. Jimmie

2 3

Re: [Pharo-users] [Moose-dev] Re: glamorous toolkit: v0.4.0
by Offray Vladimir Luna CÃ¡rdenas Dec. 29, 2018

Dec. 29, 2018

Hi, I share your feeling of wonder and also concern Luke. In my case, I used (old) GT tools to prototype Grafoscopio and now that the PhD thesis is practically done and only dissertation is pending, I would like to prepare myself to migrate Grafoscopio to Pharo 7, including bug fixing, stability, improved functionality, Iceberg for code management (but supporting Fossil instead of Git). I think that there is a lot of possibilities in the new GT tools and I like some of them going into interactive documentation (a line I was trying to explore with Pharo using Grafoscopio). But anytime I tried to use it I stumble upon a stop: * First time was something related with me having some kind of credential enabled in GitHub to simple use it. I lost a whole morning just enabling that and reporting it. It was related with some mozilla library for font redering that didn't work well at the end. * Today I tried with the prebuild Linux image and Pharo Launcher, but I got an error message about inability to determine proper VM and when I tried installing it from Pharo 7 I got something related with a MemoryFileWriteStream dependency to be resolved before proper installation. I understand that this is alpha software and demos look amazing, but just running them requires a lot of work that previous GT didn't require. This brings me this feeling that these jumps in Pharo put core of the user experience at risk (kind of) and you end wondering how much an old tech will be maintained once the jump to the new shinny stuff is done and which is the migration path. In my case, I would like to have something like a Zeroconf script that just takes care of the external libraries, VM and image, to have a real glipmse of the upcoming future, beside the Tweets (which look great BTW). Maybe it will happen in a year or two, once it is properly integrated with Pharo, Zeroconf and thought for "end users" of interactive documents, which don't want to enable GitHub stuff, deal with external rendering dependencies and so on. Now the experience of using GT is kind of hostile for that users. Anyway, keep the good work and sharing it. Hopefully at some point it will reach the beta status, where users like myself can use it smoothly and build on GT's promises and interesting features. Cheers, Offray On 21/12/18 10:59, Luke Gorrie wrote: > On Thu, 20 Dec 2018 at 10:58, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > The goal of the new GT is to propose a completely reshaped > programming experience that enables moldable development. You will > find the concepts from the old GT in the new world as well. For > example, the Inspector is extensible in similar ways and the API > is similar as well. > > [...]Â > > Does this address the concern? > > > I am not sure yet :). > > Programming is not our main use case for GT. We are using GT as an > object inspector (etc) for examining diagnostic data. We have a > Smalltalk application that's similar to GDB and we are using GT as the > front-end. > > In our world we use the Inspector and the Spotter but all of the > Smalltalk programming views are hidden. GT is "molded" to be a > diagnostic tool *instead of* a programming environment. Specifically, > our main use case is inspecting/debugging the operation of a JIT > compiler written in C. We have Smalltalk code to load binary coredumps > from the JIT, decode them using DWARF debug information, and represent > the application-level compiler data structures as Smalltalk objects. > This way we can use GT to browse generated code, cross-reference > profiler data, examine runtime compilation errors, etc.Â > > The "old" GT is awesome for this. I feel like this application is also > very much in the spirit of the "moldable tools" thesis. Lots of > diagnostic workflows ultimately boil down to drill-down inspecting > and/or searching. > > I don't know where we stand with respect to the "new" GT though. I am > talking about diagnostics, you are talking about programming. I am > talking about zeros and ones, you are talking about feelings. I am > maintaining a stable application, you are talking about rewrites. I am > having a hard time whether I should be switching to the new GT in the > immediate future, or waiting another year or two for it to mature, or > planning to stick with the old GT. > > Hints would be appreciated :) > > I reiterate that I think you guys are doing fantastic work - some of > the most interesting work in the programming universe to my mind. I > hope that this discussion is useful for at least understanding the > thought process of some users / potential users. > > Cheers! > -Luke > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

4 7

Re: [Pharo-users] [Moose-dev] Re: glamorous toolkit: v0.4.0
by Tudor Girba Dec. 28, 2018

Dec. 28, 2018

Hi, The visualization you describe should be easily doable in the new world. Did you write the visualization in plain Roassal or with the RTMondrian API? Cheers, Doru > On Dec 28, 2018, at 11:32 AM, Luke Gorrie <luke(a)snabb.co> wrote: > > Thanks for the explanations! > > I like the separation between selecting (single-click) and spawning (double-click). The miller column panning is indeed working with a two-finger drag on the touchpad. I will need to test whether this gesture works when running GT on Linux and operating it on a Mac via VNC. That's the most common setup for our application. > > Spotter is not urgent for us. I have written some extensions for it but we aren't really using them much yet. If the inspector is working well then that's the main thing. > > I do have one very important Roassal visualization that I need to bring with me smoothly somehow. Question is whether to port if over to the new framework or somehow smoothly embed Roassal in the new GT? > > The visualization is for compile SSA intermediate representation code and looks like this: > > <Screen Shot 2018-12-28 at 11.25.06.png> > There are some important properties about this diagram: > > - These are two digraphs stacked on top of each other. > - Nodes are always placed below their parents. > - Y-position indicates the max number of edges to reach parent nodes. > - Extra edges (red) can create cycles and should be ignored for layout purposes. > - Nodes can be compound shapes i.e. colored opcode and optionally fused immediate operands in white. > - Each node is an object that can be selected and inspected in the next miller column. > > Can this be done in the new framework with similar effort to the old one? > > On Fri, 28 Dec 2018 at 09:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Thanks for the feedback! > > I am happy you like the new possibilities and that you see the incentives to move to the new world :). > > The inspector part is working quite well. The main reason we call it an alpha is because of the missing pieces to get to a full environment. > > You noticed the issue of Spotter. The existing Spotter is the one that is included in the old GT and it lives in the Morphic world. When the focus is in the new inspector, that means that keybindings are handled by Bloc and this is a separate world from Morphic. At present time, we can embed Bloc in Morphic but not the other way around as we want no binding from Bloc to Morphic. For this reason, unhandled keys are not propagated from Bloc to Morphic and that is why pressing Shift+Enter does not open Spotter. > > So, we will have a Spotter, but that will be another implementation. Other unfinished tools are the Debugger and Coder, but these are likely less relevant for your use case. > > A few other missing pieces: > - some widgets such as a tree are not yet implemented. So, we do not yet have a tree view in inspector. > - the text editor requires a few enhancements for navigation support. > - scrollbar > > The Miller-columns interface can be scrolled with the touchpad left-right. Can you confirm? > > About clicking vs double-clicking: Indeed, we now distinguish between selecting and spawning. As soon as there is a page to the right, selecting will populate that page. However, if there is no page to the right, simply selecting in a list will not spawn, like in the old inspector. Like this, you can work on a page without the page scrolling from underneath you. Please note that between pages we have triangles which are actually buttons. Selecting in a list shows a triangle. Clicking on the triangle spawns. So, you can either double-click to spawn, or you can select and then click on the triangle. Once spawned, simple selection is enough. Does this clarify the situation? > > About Roassal: In the new GT we have GtMondrian which is similar to the one from Roassal. We do not yet have support for creating charts (like bar or line charts). > > About the porting strategy: When you have the new GT loaded, the old Inspector will get a _GT pane that will essentially embed the new views in the old inspector. These also allow for interaction. Like this, you can port at your pace and switch only when you are ready. > > Cheers, > Doru > > > > > On Dec 27, 2018, at 11:36 AM, Luke Gorrie <luke(a)snabb.co> wrote: > > > > ... Some comments and questions if I may: > > > > The "+" button to quickly maximize a panel is fantastic. I am often looking at complex visualizations that should really be full-screen and it was always too much trouble to "drag" them to full screen and back. > > > > Is the Spotter still a part of GToolkit? If not then what replaces it? (I can see that it is present in the image but Shift-Return doesn't seem to invoke it when the GTInspector window has focus.) > > > > Is it still possible to pan left-right between "miller columns"? I see the squares at the top representing panes but clicking and dragging them doesn't seem to do anything. > > > > How come a double-click is now needed to inspect an object? Is single-click going to have a new function? > > > > Once more - great work you guys are doing ! > > > > On Thu, 27 Dec 2018 at 11:06, Luke Gorrie <luke(a)snabb.co> wrote: > > Hi Doru, > > > > Thank you very much for the detailed explanation. > > > > I have spent some time with the alpha now. I think it is absolutely fantastic! > > > > I love the new narrative style of the UI. This ties everything together beautifully and makes it easy to explore. That's really what I am lacking in my application. Currently it simply opens to a blank quasi-playground and it is not obvious what to type or how to get started. I started writing a separate HTML manual but I don't think that's the right medium -- much better with something interactive in the image like the Documenter. > > > > Just clicking around everything seemed to work basically smoothly for me. Maybe it's already time for me to port over to the new GT? Or what do you think the most likely obstacles would be in transitioning to this alpha version? > > > > Currently my custom inspector extensions are mostly based on Roassal and List/Tree/Table views. I also have one or two Glamour browsers. Is that all still there in one form or another? > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.feenk.com > > "Every thing has its own flow." > > > > > > > _______________________________________________ > 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.feenk.com "The coherence of a trip is given by the clearness of the goal."

1 0

Re: [Pharo-users] [Moose-dev] glamorous toolkit: v0.4.0
by Tudor Girba Dec. 28, 2018

Dec. 28, 2018

Hi, Thanks for the feedback! I am happy you like the new possibilities and that you see the incentives to move to the new world :). The inspector part is working quite well. The main reason we call it an alpha is because of the missing pieces to get to a full environment. You noticed the issue of Spotter. The existing Spotter is the one that is included in the old GT and it lives in the Morphic world. When the focus is in the new inspector, that means that keybindings are handled by Bloc and this is a separate world from Morphic. At present time, we can embed Bloc in Morphic but not the other way around as we want no binding from Bloc to Morphic. For this reason, unhandled keys are not propagated from Bloc to Morphic and that is why pressing Shift+Enter does not open Spotter. So, we will have a Spotter, but that will be another implementation. Other unfinished tools are the Debugger and Coder, but these are likely less relevant for your use case. A few other missing pieces: - some widgets such as a tree are not yet implemented. So, we do not yet have a tree view in inspector. - the text editor requires a few enhancements for navigation support. - scrollbar The Miller-columns interface can be scrolled with the touchpad left-right. Can you confirm? About clicking vs double-clicking: Indeed, we now distinguish between selecting and spawning. As soon as there is a page to the right, selecting will populate that page. However, if there is no page to the right, simply selecting in a list will not spawn, like in the old inspector. Like this, you can work on a page without the page scrolling from underneath you. Please note that between pages we have triangles which are actually buttons. Selecting in a list shows a triangle. Clicking on the triangle spawns. So, you can either double-click to spawn, or you can select and then click on the triangle. Once spawned, simple selection is enough. Does this clarify the situation? About Roassal: In the new GT we have GtMondrian which is similar to the one from Roassal. We do not yet have support for creating charts (like bar or line charts). About the porting strategy: When you have the new GT loaded, the old Inspector will get a _GT pane that will essentially embed the new views in the old inspector. These also allow for interaction. Like this, you can port at your pace and switch only when you are ready. Cheers, Doru > On Dec 27, 2018, at 11:36 AM, Luke Gorrie <luke(a)snabb.co> wrote: > > ... Some comments and questions if I may: > > The "+" button to quickly maximize a panel is fantastic. I am often looking at complex visualizations that should really be full-screen and it was always too much trouble to "drag" them to full screen and back. > > Is the Spotter still a part of GToolkit? If not then what replaces it? (I can see that it is present in the image but Shift-Return doesn't seem to invoke it when the GTInspector window has focus.) > > Is it still possible to pan left-right between "miller columns"? I see the squares at the top representing panes but clicking and dragging them doesn't seem to do anything. > > How come a double-click is now needed to inspect an object? Is single-click going to have a new function? > > Once more - great work you guys are doing ! > > On Thu, 27 Dec 2018 at 11:06, Luke Gorrie <luke(a)snabb.co> wrote: > Hi Doru, > > Thank you very much for the detailed explanation. > > I have spent some time with the alpha now. I think it is absolutely fantastic! > > I love the new narrative style of the UI. This ties everything together beautifully and makes it easy to explore. That's really what I am lacking in my application. Currently it simply opens to a blank quasi-playground and it is not obvious what to type or how to get started. I started writing a separate HTML manual but I don't think that's the right medium -- much better with something interactive in the image like the Documenter. > > Just clicking around everything seemed to work basically smoothly for me. Maybe it's already time for me to port over to the new GT? Or what do you think the most likely obstacles would be in transitioning to this alpha version? > > Currently my custom inspector extensions are mostly based on Roassal and List/Tree/Table views. I also have one or two Glamour browsers. Is that all still there in one form or another? > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Every thing has its own flow."

1 0

Move methods to other class in P7/Calypso
by Esteban Maringolo Dec. 27, 2018

Dec. 27, 2018

What the canonical way of moving a set of methods from one class to another? I couldn't find it in the contextual menu or in the refactorings. Regards, Esteban A. Maringolo

2 1