- Pharo-dev - lists.pharo.org

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

by Alexandre Bergel

Was is really necessary to introduce pragmas here? Alexandre > On Apr 11, 2017, at 11:49 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi. > > I am glad to announce Commander library which implements command pattern based on first class objects. > In Commander every application action is implemented as separate class with #execute method and all state required for execution. > > Commands are reusable objects and applications provide various ways to access them: shortcuts, context menu, buttons, etc.. This information is attached to command classes as activator objects. Currently there are three types of activators: > > - CmdShortcutCommandActivator > - CmdContextMenuCommandActivator > - CmdDragAndDropCommandActivator > > Activators are declared in command class side methods marked with pragma #commandActivator. For example following method will allow RenamePackageCommand to be executed by shortcut in possible system browser: > > RenamePackageCommand class>>packageBrowserShortcutActivator > <commandActivator> > ^CmdShortcutCommandActivator by: $r meta for: PackageBrowserContext > > And for context menu it will be: > > RenamePackageCommand class>>packageBrowserMenuActivator > <commandActivator> > ^CmdContextMenuCommandActivator byRootGroupItemFor: PackageBrowserContext > > Activators are always declared with application context where they can be applied (PackageBrowserContext in example). Application should provide such contexts with information about application state. Every widget can bring own context to interact with application as separate tool. For example system browser shows multiple panes which provide package context, class context and method context. And depending on context browser shows different menu and provides different shortcuts. > > For more details look at my blog http://dionisiydk.blogspot.fr/2017/04/commander-command-pattern-library.html and read docs here. > > Best regards, > Denis > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 11, 2017

[Ann] Commander. Command pattern library

by Denis Kudriashov

Hi. I am glad to announce Commander library which implements command pattern based on first class objects. In Commander every application action is implemented as separate class with #execute method and all state required for execution. Commands are reusable objects and applications provide various ways to access them: shortcuts, context menu, buttons, etc.. This information is attached to command classes as activator objects. Currently there are three types of activators: - CmdShortcutCommandActivator - CmdContextMenuCommandActivator - CmdDragAndDropCommandActivator Activators are declared in command class side methods marked with pragma #commandActivator. For example following method will allow RenamePackageCommand to be executed by shortcut in possible system browser: RenamePackageCommand class>>packageBrowserShortcutActivator <commandActivator> ^CmdShortcutCommandActivator by: $r meta for: PackageBrowserContext And for context menu it will be: RenamePackageCommand class>>packageBrowserMenuActivator <commandActivator> ^CmdContextMenuCommandActivator byRootGroupItemFor: PackageBrowserContext Activators are always declared with application context where they can be applied (PackageBrowserContext in example). Application should provide such contexts with information about application state. Every widget can bring own context to interact with application as separate tool. For example system browser shows multiple panes which provide package context, class context and method context. And depending on context browser shows different menu and provides different shortcuts. For more details look at my blog http://dionisiydk.blogspot.fr/2017/04/commander-command-pattern-library.html and read docs here <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> . Best regards, Denis

April 11, 2017

[Pharo6] Wanted: Human Readable ChangeLog

by Marcus Denker

Hi, We have the complete list of changes here: https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&fGlobal=true&fOpenBug… <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

April 11, 2017

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

by Denis Kudriashov

2017-04-08 6:46 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > As an immediate stop-gap I'm adding the following comment to > BlockClosure>>newProcess > > "IMPORTANT! Debug stepping this deep infrastructure may lock your Image" > "If you are not sure what you are doing, close the debugger now." > And issue for this part 19929 <https://pharo.fogbugz.com/f/cases/19929/Comment-guard-to-warn-debugging-top…>

April 11, 2017

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

by Denis Kudriashov

Hi Ben, 2017-04-08 6:32 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > 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 opened issue 19928 <https://pharo.fogbugz.com/f/cases/19928/Debugger-step-over-through-last-doI…>. (I not found yours, right?)

April 11, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60464 Home: https://github.com/pharo-project/pharo-core

April 11, 2017

[pharo-project/pharo-core] 7282e7: 60464

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 7282e70f15433ab97e70d14b0e0868e345dd4c15 https://github.com/pharo-project/pharo-core/commit/7282e70f15433ab97e70d14b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-04-11 (Tue, 11 Apr 2017) Changed paths: A Rubric.package/RubAbstractTextArea.class/class/settings/defaultMaxExtent.st M Rubric.package/RubAbstractTextArea.class/instance/drawing/drawingBounds.st M Rubric.package/RubParagraph.class/instance/composition/compositionExtent.st M Rubric.package/RubParagraph.class/instance/geometry/width.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60463.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60464.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60463.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60464.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60464 19884 Rubric should not use SmallInteger maxVal https://pharo.fogbugz.com/f/cases/19884 http://files.pharo.org/image/60/60464.zip

April 11, 2017

Re: [Pharo-dev] Estebanâs list of blocking issues for release Pharo 6.0 (updated to April 10)

by Esteban Lorenzano

> On 10 Apr 2017, at 11:39, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi Esteban, > > Is there a chance to have a fully working SDL2? (remember that conflicting issue with main window) > I am just curious :) Sorry, no. Last time that was made by replacing the complete Cocoa backend (from OpenGL to CoreGraphics). While that can be done, it is not realist it will arrive for Pharo 6.0 at all. Esteban > > Cheers, > Alex > > On 10 April 2017 at 09:20, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hello, > > This are the pending issues for release Pharo 6.0: > > VM: > === > - NEW: there is a problem with latest VM and primitiveFindSubstring that needs to be fixed. > - make all tests pass (there are still some failing tests when compiling a new VM). > - libgit2: Still not there, Jan and Ben were trying and sent some suggestions but I still didnât had the time to test it. > > Image: > ===== > - iceberg hit the image > > Fixed last week: > --------------------- > > - win32, cairo fonts problem > - leak revision by Pavel > (and of course several issues not mentioned in the list). > > Next: > - Make the release! > - Test the new process and tape some videos explaining how we will contribute with a bootstrapped process using github :) > > By the wayâ¦ this is a list we have to accomplish in order to make a release (so you know our pain): > > - Prepare release notes > Image: > - add welcome browser > - generate PharoV60.sources > - move SystemVersion > - prepare new ScriptLoader70 package (in theory, this will not needed anymore but better to have it as a backup :P) > VM: > - stable for 6.0 release > WebSite: > - Update index > - Update download page > Infrastructure: > - ZeroConf: Open new 7.0 development > - SmalltalkCI: Open new 7.0 development > - Create platform stable versions > - Jenkins: move all CI projects to Pharo 7.0 (again some will not needed anymore, notable those moved to travis, but still) > - And talking about travis: prepare all new process on github/travis/appveyor > Pub: > - announce post > - announce mail > - post to YC, Reddit > > â¦ and Iâm sure Iâm forgetting a lot more I will remember in the process of making the release. > > (which is one of the reasons why we do not have âmore releases in a yearâ) > > Anyway, do not despairâ¦ we are almost there! > > cheers! > Esteban > > > >

April 10, 2017

Re: [Pharo-dev] Estebanâs list of blocking issues for release Pharo 6.0 (updated to April 10)

by Aliaksei Syrel

Hi Esteban, Is there a chance to have a fully working SDL2? (remember that conflicting issue with main window) I am just curious :) Cheers, Alex On 10 April 2017 at 09:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hello, > > This are the pending issues for release Pharo 6.0: > > VM: > === > - NEW: there is a problem with latest VM and primitiveFindSubstring that > needs to be fixed. > - make all tests pass (there are still some failing tests when compiling a > new VM). > - libgit2: Still not there, Jan and Ben were trying and sent some > suggestions but I still didnât had the time to test it. > > Image: > ===== > - iceberg hit the image > > Fixed last week: > --------------------- > > - win32, cairo fonts problem > - leak revision by Pavel > (and of course several issues not mentioned in the list). > > Next: > - Make the release! > - Test the new process and tape some videos explaining how we will > contribute with a bootstrapped process using github :) > > By the wayâ¦ this is a list we have to accomplish in order to make a > release (so you know our pain): > > - Prepare release notes > Image: > - add welcome browser > - generate PharoV60.sources > - move SystemVersion > - prepare new ScriptLoader70 package (in theory, this will not needed > anymore but better to have it as a backup :P) > VM: > - stable for 6.0 release > WebSite: > - Update index > - Update download page > Infrastructure: > - ZeroConf: Open new 7.0 development > - SmalltalkCI: Open new 7.0 development > - Create platform stable versions > - Jenkins: move all CI projects to Pharo 7.0 (again some will not needed > anymore, notable those moved to travis, but still) > - And talking about travis: prepare all new process on > github/travis/appveyor > Pub: > - announce post > - announce mail > - post to YC, Reddit > > â¦ and Iâm sure Iâm forgetting a lot more I will remember in the process of > making the release. > > (which is one of the reasons why we do not have âmore releases in a yearâ) > > Anyway, do not despairâ¦ we are almost there! > > cheers! > Esteban > > > >

April 10, 2017

Estebanâs list of blocking issues for release Pharo 6.0 (updated to April 10)

by Esteban Lorenzano

Hello, This are the pending issues for release Pharo 6.0: VM: === - NEW: there is a problem with latest VM and primitiveFindSubstring that needs to be fixed. - make all tests pass (there are still some failing tests when compiling a new VM). - libgit2: Still not there, Jan and Ben were trying and sent some suggestions but I still didnât had the time to test it. Image: ===== - iceberg hit the image Fixed last week: --------------------- - win32, cairo fonts problem - leak revision by Pavel (and of course several issues not mentioned in the list). Next: - Make the release! - Test the new process and tape some videos explaining how we will contribute with a bootstrapped process using github :) By the wayâ¦ this is a list we have to accomplish in order to make a release (so you know our pain): - Prepare release notes Image: - add welcome browser - generate PharoV60.sources - move SystemVersion - prepare new ScriptLoader70 package (in theory, this will not needed anymore but better to have it as a backup :P) VM: - stable for 6.0 release WebSite: - Update index - Update download page Infrastructure: - ZeroConf: Open new 7.0 development - SmalltalkCI: Open new 7.0 development - Create platform stable versions - Jenkins: move all CI projects to Pharo 7.0 (again some will not needed anymore, notable those moved to travis, but still) - And talking about travis: prepare all new process on github/travis/appveyor Pub: - announce post - announce mail - post to YC, Reddit â¦ and Iâm sure Iâm forgetting a lot more I will remember in the process of making the release. (which is one of the reasons why we do not have âmore releases in a yearâ) Anyway, do not despairâ¦ we are almost there! cheers! Esteban

April 10, 2017