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

Re: [Pharo-dev] [Ann] Commander. Command pattern library

by Ben Coman

On Wed, Apr 12, 2017 at 6:28 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > Was is really necessary to introduce pragmas here? > > > > In short: Commander needs pragma to query methods for command lookup. > What alternative you could suggest? > > I would imagine that your activatorClass can lookup the command simply as: > > PackageCommand allSubclasses select: [ :c | c isEnabledFor: â¦ ] > > Would this not work? > I am personally not keen of using pragma. The worth is when you have no > idea what a pragma does and looking for implementors or sender does not > help. The other way to look at it is we need to improve implementor/sender lookups around pragmas (speaking very generically. I don't know what the gaps are.) cheers -ben > Here is an example: > -=-=-=-=-=-=-=-=-=-=-=-= > RadioButtonModel>>canDeselectByClick > <api: #inspect> > "Return true clicking on a selected radio button deselects it" > > ^ canDeselectByClick value > -=-=-=-=-=-=-=-=-=-=-=-= > > No idea what is the effect of the #api: pragma. There is no implementor of > it. I could also the example of the Fame metamodel. > Anyway, the fact that I am kind of complaining should not prevent you from > moving ahead. I would be happy having Calypso in the image, even if pragmas. > > Go go go! > > Cheers, > Alexandre > > > > > > In details: > > > > Commander caches all activators for each command class. It searches all > methods which supply them using pragma and store all retrieved instances in > class variable. > > > > To lookup required commands users enumerate cached activators declared > for given context: > > activatorClass allDeclaredFor: aToolContext do: blockWithActivator > > This process is fast and not produces any garbage. > > > > Also activation methods are supposed to be packaged together with > application which provide context for them. They can be in different > package than commands. > > Commands are reusable and can be extended by multiple applications with > different set of activation methods. > > For example in Calypso I will extract separate SystemCommands package > which can be reused by other tools like inspector and debugger. And Calypso > will "attach" these commands by own set of extension methods. > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

April 12, 2017

Re: [Pharo-dev] [Pharo6] Wanted: Human Readable ChangeLog

by Ben Coman

On Tue, Apr 11, 2017 at 9:58 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > We have the complete list of changes here: > > https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&fGlobal=true&fOpenBug… > > all 1386 closed issues with MileStone Pharo6. > > For the release announcement, it would be nice to have a shorter, more > digestible list. > > I think we need 2 kind: > > 1) some 5-8 âmost importantâ ones > 2) a list of maybe 20 issues that are interesting > > I think the easiest is to do it together.. so if you have points for the 2 > kinds of changes, I would be interested. > > I will then create one merged version of everything people send me (or to > the list). > > Marcus Just to try a crowdsource experiment, I've uploaded the issue list for review and rating here... https://docs.google.com/spreadsheets/d/1NrCnkIJl9Ezk35B1IfpN9BC4wkhHG26C7DI… It would be great if a few people could jump in to grab a block of 50 items to rate. Should only take a few minutes. cheers -ben

April 12, 2017

Re: [Pharo-dev] [SPAM] [ann] steering agile architecture video published by o'reilly

by Graham McLeod

This is great news. I am actively trying to promote these concepts / tools within my clients. This will help. Best Graham Tudor Girba wrote: > Hi, > > I am happy to announce that OâReilly has published my Steering Agile Architecture video training: > http://www.humane-assessment.com/blog/steering-agile-architecture-video-tra… > > This video is based on my work on humane assessment, and it features Moose prominently. It also shows Pharo, GT and Roassal (in the last part). > > The video is indeed paid and it is mainly targeted to people that have a Safari Books Online subscription. But, the interesting thing about it is that it opens Pharo and Moose to a new kind of an audience, OâReilly being the most prominent publishing company in the software area. > > Agile architecture is considered a prominent topic but the literature (until now) was rather loose at how to make it really work in practice. This course offers both a concrete approach based on humane assessment. As you might know, humane assessment centers around the idea of building tools cheaply as a way to figure the system out, and this is right now pretty much only practicable in Moose and Pharo. > > One thing that I ask people when I go to conferences, the last one being the Software Architecture Conference organized by OâReilly, is if they like working with legacy systems. They actively dislike it. Then I show them demos of how it can be like and then I ask them if they think these demos are cool. And I never encountered one that did not find it cool. So, in a way, we can now be quite confident in saying that we work on the single platform that makes working with an existing system cool. Not a small feat. > > So, if you do get the chance to look at these things, you might also get a concrete inspiration of how to leverage Pharo skills within companies that do not yet work with Pharo. > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "Presenting is storytelling." > > >

April 11, 2017

Re: [Pharo-dev] [Moose-dev] [ann] steering agile architecture video published by o'reilly

by Alexandre Bergel

This is a fantastic experience! Alexandre > On Apr 11, 2017, at 8:04 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I am happy to announce that OâReilly has published my Steering Agile Architecture video training: > http://www.humane-assessment.com/blog/steering-agile-architecture-video-tra… > > This video is based on my work on humane assessment, and it features Moose prominently. It also shows Pharo, GT and Roassal (in the last part). > > The video is indeed paid and it is mainly targeted to people that have a Safari Books Online subscription. But, the interesting thing about it is that it opens Pharo and Moose to a new kind of an audience, OâReilly being the most prominent publishing company in the software area. > > Agile architecture is considered a prominent topic but the literature (until now) was rather loose at how to make it really work in practice. This course offers both a concrete approach based on humane assessment. As you might know, humane assessment centers around the idea of building tools cheaply as a way to figure the system out, and this is right now pretty much only practicable in Moose and Pharo. > > One thing that I ask people when I go to conferences, the last one being the Software Architecture Conference organized by OâReilly, is if they like working with legacy systems. They actively dislike it. Then I show them demos of how it can be like and then I ask them if they think these demos are cool. And I never encountered one that did not find it cool. So, in a way, we can now be quite confident in saying that we work on the single platform that makes working with an existing system cool. Not a small feat. > > So, if you do get the chance to look at these things, you might also get a concrete inspiration of how to leverage Pharo skills within companies that do not yet work with Pharo. > > Cheers, > Doru > > > -- > 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 11, 2017

[ann] steering agile architecture video published by o'reilly

by Tudor Girba

Hi, I am happy to announce that OâReilly has published my Steering Agile Architecture video training: http://www.humane-assessment.com/blog/steering-agile-architecture-video-tra… This video is based on my work on humane assessment, and it features Moose prominently. It also shows Pharo, GT and Roassal (in the last part). The video is indeed paid and it is mainly targeted to people that have a Safari Books Online subscription. But, the interesting thing about it is that it opens Pharo and Moose to a new kind of an audience, OâReilly being the most prominent publishing company in the software area. Agile architecture is considered a prominent topic but the literature (until now) was rather loose at how to make it really work in practice. This course offers both a concrete approach based on humane assessment. As you might know, humane assessment centers around the idea of building tools cheaply as a way to figure the system out, and this is right now pretty much only practicable in Moose and Pharo. One thing that I ask people when I go to conferences, the last one being the Software Architecture Conference organized by OâReilly, is if they like working with legacy systems. They actively dislike it. Then I show them demos of how it can be like and then I ask them if they think these demos are cool. And I never encountered one that did not find it cool. So, in a way, we can now be quite confident in saying that we work on the single platform that makes working with an existing system cool. Not a small feat. So, if you do get the chance to look at these things, you might also get a concrete inspiration of how to leverage Pharo skills within companies that do not yet work with Pharo. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

April 11, 2017

Re: [Pharo-dev] [Ann] Commander. Command pattern library

by Alexandre Bergel

> Was is really necessary to introduce pragmas here? > > In short: Commander needs pragma to query methods for command lookup. What alternative you could suggest? I would imagine that your activatorClass can lookup the command simply as: PackageCommand allSubclasses select: [ :c | c isEnabledFor: â¦ ] Would this not work? I am personally not keen of using pragma. The worth is when you have no idea what a pragma does and looking for implementors or sender does not help. Here is an example: -=-=-=-=-=-=-=-=-=-=-=-= RadioButtonModel>>canDeselectByClick <api: #inspect> "Return true clicking on a selected radio button deselects it" ^ canDeselectByClick value -=-=-=-=-=-=-=-=-=-=-=-= No idea what is the effect of the #api: pragma. There is no implementor of it. I could also the example of the Fame metamodel. Anyway, the fact that I am kind of complaining should not prevent you from moving ahead. I would be happy having Calypso in the image, even if pragmas. Go go go! Cheers, Alexandre > > In details: > > Commander caches all activators for each command class. It searches all methods which supply them using pragma and store all retrieved instances in class variable. > > To lookup required commands users enumerate cached activators declared for given context: > activatorClass allDeclaredFor: aToolContext do: blockWithActivator > This process is fast and not produces any garbage. > > Also activation methods are supposed to be packaged together with application which provide context for them. They can be in different package than commands. > Commands are reusable and can be extended by multiple applications with different set of activation methods. > For example in Calypso I will extract separate SystemCommands package which can be reused by other tools like inspector and debugger. And Calypso will "attach" these commands by own set of extension methods. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 11, 2017

Re: [Pharo-dev] [Ann] Commander. Command pattern library

by Denis Kudriashov

2017-04-11 17:34 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Was is really necessary to introduce pragmas here? > In short: Commander needs pragma to query methods for command lookup. What alternative you could suggest? In details: Commander caches all activators for each command class. It searches all methods which supply them using pragma and store all retrieved instances in class variable. To lookup required commands users enumerate cached activators declared for given context: activatorClass allDeclaredFor: aToolContext do: blockWithActivator This process is fast and not produces any garbage. Also activation methods are supposed to be packaged together with application which provide context for them. They can be in different package than commands. Commands are reusable and can be extended by multiple applications with different set of activation methods. For example in Calypso I will extract separate SystemCommands package which can be reused by other tools like inspector and debugger. And Calypso will "attach" these commands by own set of extension methods.

April 11, 2017

Re: [Pharo-dev] [Ann] Commander. Command pattern library

by Denis Kudriashov

2017-04-11 19:38 GMT+02:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > Nice work, I like the approach. > Thank's. > > Did you inspire your work in how Dolphin and VAST implements menu > creation, command execution, and so on? > No. I actually not remember that there were first class commands in Dolphin. I remember kind of CommandDescription with selector/block inside. No hierarchy of commands. But I could be wrong. I was more inspired by OmniBrowser and AltBrowser commands. But there were no activators idea inside. (I never worked with VAST) > I find your solution similar to how Dolphin implements it, where even > each Presenter is even queried about each command by using a command > query and routing solution. > > Will you use this in the context of Calypso and friends? > Yes. And Calypso extends it with specific activators: - ClyToolbarCommandActivator to build middle bar of browser (switch browser to instance/class side are commands) - ClyTableIconCommandActivator to decorate table rows with iconic buttons (to provide method icons like in Nautilus)

April 11, 2017

Re: [Pharo-dev] discord channel request

by Dimitris Chloupis

+1 On Tue, Apr 11, 2017 at 9:50 PM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > About the mooc and the social barrier I agree. > We should make sure that shy people ask questions. > > On Sun, Apr 9, 2017 at 7:45 PM, Ben Coman <btc(a)openinworld.com> wrote: > > On Sun, Apr 9, 2017 at 8:09 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > #welcome is not necessary there is already a bot in place that provides a > > welcome message and displays a command for help for newcomers > > There have been some requests to remove the bot. > But I see that you've responded to feedback to tune its behaviour, > so I'm happy to wait to see how that panes out. > But oh! the irony... > > jecisc-Yesterday at 8:16 PM > Can you delete this level thing with the bot please?(edited) > > Mee6BOT-Yesterday at 8:16 PM > GG @jecisc, you just advanced to level 3 ! > > > btw, where is the bot hosted? > > > > #help is not necessary too, Discord has a search capability which could > be > > potentially used from inside a Pharo image but again the question is who > is > > going to do this > > Its not just about searchability. Its a social barrier thing. > If the regulars are rolling through some deep discussion, > a newcomer may hesitate to jump in with a side topic. > > If you want to condense channels, then probably the #mooc and #help > could be rolled into one. > > cheers -ben > > > > > #mooc , I am not against this idea but again we had a student yesterday > > asking for help that is following Mooc , I had no problem providing it > and > > he had not issues with the process of getting his question aswered in > > #general channel. If he asked at #mooc I would have missed it because I > am > > not going to keep a mind in all channels. > > > > For general questions I would prefer , even if they are mooc related , > to be > > at #general channel, lets not fragment our discussions for little > > justification, > > but for very mooc discusions, like where to find a specific > > teach or reports of errors in mooc it makes sense to have a mooc channel. > > > > My policy is to point an admin for each channel , channel admis are > > different than us general admins, we have full power they can only > > > > 1)manage message in a specific channel > > 2) manage webhooks (for example github commits or rss feeds) > > 3) create instant invites > > > > so if there is one person that is willing to become a mooc admin i will > > create the channel and add his as admin > > > > On Sun, Apr 9, 2017 at 5:33 AM Ben Coman <btc(a)openinworld.com> wrote: > >> > >> Could we have additional channels: > >> > >> #welcome - which would be the generally advertised invite URL. A > >> read-only channel that informs about community rules and summaries > available > >> channels etc (maybe including hidden channels and who to ask for invite) > >> > >> #help - To be referenced from in-Image Help Browser. Maybe later have > an > >> in-Image chat tool that connects to this channel. How cool would it be > to > >> have live help from within the IDE? > >> > >> #mooc - So people can maybe look back through history before asking > >> questions, and also people further along might help others less > advanced ==> > >> more participation > >> > >> cheers -ben > > >

April 11, 2017

Re: [Pharo-dev] stepping off the end of the debug stack

by Eliot Miranda

Hi Ben, On Fri, Apr 7, 2017 at 9:32 PM, Ben Coman <btc(a)openinworld.com> wrote: > > I imagine a newcomer exploring the system could easily step off the end of > the debug stack like this... > > (1 printString) "debugIt" > then StepOver six times where the image hangs at "Processor > terminateActive" > > This could have a strong impact against first impressions. > What would it take to guard against this? > I just took a look at this in Squeak and fixed it there. All I had to do was fix Process>>completeStep: and arrange that the Debugger wasn't confused when it got back the nil suspendedContext of a terminated process and that it disabled its into/over/through buttons on process termination. You can see the Squeak changes in these two commits: The Trunk: Kernel-eem.1093.mcz <http://forum.world.st/The-Trunk-Kernel-eem-1093-mcz-tp4941815.html> The Trunk: Tools-eem.756.mcz <http://forum.world.st/The-Trunk-Tools-eem-756-mcz-tp4941816.html> cheers -ben > HTH _,,,^..^,,,_ best, Eliot

April 11, 2017