- Pharo-dev - lists.pharo.org

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

by Pavel Krivanek

I looked at Feature/Enhancements issues, some unsorted selection: - new code changes manager (Epicea) - GToolkit, GTools update - API for metalinks on AST nodes - improve host platforms management (32-bit/64-bit) - GlobalIdentifier for computer identification - suport Server Name Indication (SNI) in Zodiac/SSLPlugin - NeoUUIDGenerator for UUID generation - STON improvements - STON used by Monticello FileTree - Introductionof FullBlockClosure - Adding a way of storing Announcements while suspended - improved newAnonymousSubclass - improve icons management (#iconNmaed: instead of relying on DNU) - "close all debuggers" in taskbar context menu - rename #Pragma>>#selector to Pragma>>#methodSelector - Fuel improvements - improve working directory directory structure (introduce pharo-local) - filtering and critiques in MessageBrowser - mirror primitives - Sista Encoder - enable <example> methods to be easily executed - Improve MethodClassifier logic - new class ant methods API for tags as replacemnt for categories and protocols - TabMorph improvements - split large variable entries in the Variables menu - introduce Ephemeron Registry - Unify Dictionary APIs - support of standalone Morphic worlds in separate windows - Glamour integration in Spec - Zinc/Zodiac update - imrpoved Dependency Analyzer - "Run To Here" in GTDebugger - two double quotes inside comments - introduction of objects immutability - package manifests improvements - Inheritable process specific variables - Quality Assistant improvements - FuzzyMatcher for approximate string matching - improve RadioButton Group - inlined method const could be implemented by metalinks - support for <sampleInstance> - deprecate Object>>#name - limit use of #asClass - new assert extension to compare floats by closeTo: - 64-bit support - Dark Theme improvements - better themes switching - turn of catalog search in Spotter by default - remove Chroma-CubeHelix, TxWorkspace - Iceberg - ability of the system to be fully bootstrapped - better system modularization - Reflectivity improvements - 2017-04-11 15:58 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hi, > > We have the complete list of changes here: > > https://pharo.fogbugz.com/f/filters/?fClosedBugs=true& > fGlobal=true&fOpenBugs=false&ixFixFor=22&ixPerson=46& > ixPriority=6&priorityRange=-1&sColumns=Category-Favorite- > Case-TitleComment-Status-Priority-LastUpdated&sSorts=Priority > > 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 >

April 12, 2017

Security in the image

by LaeMing

Hi, I am fishing about for an environment to try to develop a simple virtual world system in (yes, I'm aware of croquet/cobolt!). In a smalltalk-like environment, that might conceivably involve inviting multiple people into the 'image' where the world is hosted to interact with objects within it (if I was to use a smalltalk, it would want it to interleave the entire system, not just host it on top.) What sort of security implications might that have and are there any current solutions to a multi-user single-image situation? -- View this message in context: http://forum.world.st/Security-in-the-image-tp4941857.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 12, 2017

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