- Pharo-dev - lists.pharo.org

[ANN] Multiple Desktop support for Pharo 5

by Torsten Bergmann

Julien Delplanque provided this week a goodie to switch between "desktops" - but his initial solution was more or less hiding windows and not really switching between real Pharo worlds/desktops. I gave him some tips what could be done on the pharo-user list. Havent heard from him afterwards. Now I was able to spend a few hours on this topic myself and implemented a full multiple desktop solution myself. This works in Pharo 5 only (currently) and requires latest VM (at least on Windows) from files.pharo.org to get the keyboard shortcuts right. To try: Gofer new smalltalkhubUser: 'TorstenBergmann' project: 'DesktopManager'; configuration; loadDevelopment. The goodie has some nice features like keyboard navigation, world menu integration and even a custom spotter with preview of the desktops. Quick start: =========== - evaluate the above expression in a Pharo 5 image - check the world menu "Desktop" - you can press CTRL + D and then CTRL + A (= Desktop Add) to add a new desktop - you can press CTRL + D and then CTRL + D (= Desktop Desktop) to open the overview - you can press CTRL + D and then CTRL + P (= Desktop Previous) to navigate to the previous desktop - you can press CTRL + D and then CTRL + N (= Desktop Next) to navigate to the next desktop The code is hopefully a good example on how to build a custom spotter, shortcuts, inspector extensions, ... Additionally all this is described in a new article including screenshots and a guide on how to use this new goodie: https://medium.com/@astares/multiple-desktops-for-pharo-5cbc46f3179f Actually the article took more time to write than coding but I hope it helps explaining Pharo and why it is a power tool. Project is on http://www.smalltalkhub.com/#!/~TorstenBergmann/DesktopManager Article and code is still subject to change. Have fun T.

Aug. 27, 2015

Re: [Pharo-dev] Spec - TabManagerModel prevents the right/left keyboard navigation in TextModel

by Glenn CavarlÃ©

Thanks Nicolai, How does the KM framework work ? Pragmas can be used ? What is the roadmap to test with the new TextModel ? There is no rush for me, it's just to know. Regards, Glenn. ----- Glenn CavarlÃ© -- View this message in context: http://forum.world.st/Spec-TabManagerModel-prevents-the-right-left-keyboard… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 27, 2015

Re: [Pharo-dev] Spec - TabManagerModel prevents the right/left keyboard navigation in TextModel

by Nicolai Hess

This will work when we move all shortcut definitions from cmdActions-map to the keymapping framework. (only tested for the old TextModel<->PluggableTextMorph adapter). 2015-08-26 23:33 GMT+02:00 Glenn CavarlÃ© <glenn(a)cavarle.fr>: > Hi all, > When a TextModel is contained in a TabModel, right and left keyboard > navigation doesn't work in the textarea. > Example : > > | ui | > ui := DynamicComposableModel new > title: 'test'; > instantiateModels: #(#tabManager #TabManagerModel); > yourself. > ui tabManager > addTab: > (TabModel new > label: 'Test'; > model: (ui instantiate: TextModel); > yourself). > ui > openWithSpecLayout: > (SpecLayout composed > add: #tabManager; > yourself) > > I don't know what happens exactly, but some key bindings are registered > from > ComposableModel >> #registerKeyStrokesForPreviousFor: and > #registerKeyStrokesForNextFor:. > They handle left and right keyboard inputs. The only solution i found is to > override these methods with a ^self, that avoid all keystrokes handling for > next and previous focus in Spec models... > > Any ideas? > (I tested in a fresh pharo5 image) > > Regards, > Glenn. > > > > > > ----- > Glenn CavarlÃ© > -- > View this message in context: > http://forum.world.st/Spec-TabManagerModel-prevents-the-right-left-keyboard… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Aug. 26, 2015

Spec - TabManagerModel prevents the right/left keyboard navigation in TextModel

by Glenn CavarlÃ©

Hi all, When a TextModel is contained in a TabModel, right and left keyboard navigation doesn't work in the textarea. Example : | ui | ui := DynamicComposableModel new title: 'test'; instantiateModels: #(#tabManager #TabManagerModel); yourself. ui tabManager addTab: (TabModel new label: 'Test'; model: (ui instantiate: TextModel); yourself). ui openWithSpecLayout: (SpecLayout composed add: #tabManager; yourself) I don't know what happens exactly, but some key bindings are registered from ComposableModel >> #registerKeyStrokesForPreviousFor: and #registerKeyStrokesForNextFor:. They handle left and right keyboard inputs. The only solution i found is to override these methods with a ^self, that avoid all keystrokes handling for next and previous focus in Spec models... Any ideas? (I tested in a fresh pharo5 image) Regards, Glenn. ----- Glenn CavarlÃ© -- View this message in context: http://forum.world.st/Spec-TabManagerModel-prevents-the-right-left-keyboard… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 26, 2015

[pharo-project/pharo-core]

by GitHub

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

Aug. 26, 2015

[pharo-project/pharo-core] d42298: 50278

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d42298c9224057c5871d0c15311b6478a7274d87 https://github.com/pharo-project/pharo-core/commit/d42298c9224057c5871d0c15… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-26 (Wed, 26 Aug 2015) Changed paths: M Graphics-Files.package/ImageReadWriter.class/class/image reading%2Fwriting/formFromStream_.st M Refactoring-Critics.package/RBConsistencyCheckRule.class/instance/accessing/name.st M Refactoring-Critics.package/RBConsistencyCheckRule.class/instance/initialization/initialize.st M Refactoring-Critics.package/RBEqualNilRule.class/README.md M Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/running/checkMethod_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50277.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50278.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50277.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50278.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50278 16399 Improve RBSentNotImplementedRule for Traits https://pharo.fogbugz.com/f/cases/16399 16395 remove some duplicated tests in RBConsistencyCheckRule and RBEqualNilRule https://pharo.fogbugz.com/f/cases/16395 16387 remove Cursor read showWhile: from ImageReadWriter>>#formFromStream: https://pharo.fogbugz.com/f/cases/16387 http://files.pharo.org/image/50/50278.zip

Aug. 26, 2015

OSX code signing

by Ben Coman

What are the future plans for dealing with OSX code signing? I read [1] that "With the release of OS X 10.10 DP 5 and 10.9.5, Apple changed the code signing format, especially regarding these resource rules. [...] The main change is that now you cannot exclude resources from being signed. You used to be able to use a file called ResourceRules.plist inside of the signed bundle to specify files which should not be considered when checking if the seal of a bundle was broken. As of the version 2 code signing, this does not work anymore. All code and resources must be signed â no exceptions. " My question arises from reviewing PharoTour chapter in UPBE [2], where downloading the zip and running the app produces the dreaded {youApp} is an application downloaded from the Internet. Are you sure you want to open it?" Sure any aspiring programmer should know their way around this, but still its not very inviting. So if we can no longer store a writable Image under the Resources folder, what are the alternatives? 1. Deliver app with read-only Image under the Resources folder. The INI file can define the location of the writeable Image under ../{user}/Library/. When the VM starts, if the writable Image file does not exist, the VM transparently copies the read-only Image from resources to the writable location. 2. Use a launcher application like PharoLauncher. 3. For a "portable" app (e.g. on USB stick) push the app down one folder, so rather than putting the Win/Lin executables inside the OSX app, the top level folder contains folders Windows, Linux, Common, and the app. cheers -ben [1] https://www.objc.io/issues/17-security/inside-code-signing/ [2] https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSucces…

Aug. 26, 2015

Re: [Pharo-dev] http://pharo.org/download suggestions

by Marcus Denker

Fixed, thanks! Marcus > On 26 Aug 2015, at 15:51, Ben Coman <btc(a)openinworld.com> wrote: > > http://pharo.org/download says... > > "To run Pharo you need an image(1), changes(2), and a sources > file(3), as well as a VM(4) for your platform." > > ...then below links to (1) (3) & (4). > > but (2) seems to be missing. So I suggest the > "Pharo 4.0 image" link be "Pharo 4.0 image & changes" > > And some optional word-smithing on this: "To run Pharo you need > platform independent image, changes & sources files, and a platform > specific VM." > > cheers -ben >

Aug. 26, 2015

[pharo-project/pharo-core]

by GitHub

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

Aug. 26, 2015

[pharo-project/pharo-core] bc1eb4: 40619

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: bc1eb424a6b78a05281f82d1f3a5144f7d1d6c29 https://github.com/pharo-project/pharo-core/commit/bc1eb424a6b78a05281f82d1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-26 (Wed, 26 Aug 2015) Changed paths: R ProfStef-Core.package/PharoSyntaxTutorial.class/instance/-- all --/initialize.st R ProfStef-Core.package/PharoSyntaxTutorial.class/instance/-- all --/prepareDebuggerExample.st R ProfStef-Core.package/PharoSyntaxTutorial.class/instance/initialize-release/initialize.st R ProfStef-Core.package/PharoSyntaxTutorial.class/instance/interactive/prepareDebuggerExample.st M Refactoring-Critics.package/RBImplementedNotSentRule.class/instance/-- all --/literals.st M Refactoring-Critics.package/RBImplementedNotSentRule.class/instance/cache/literals.st M Refactoring-Critics.package/RBModifiesCollectionRule.class/instance/-- all --/modifiesTree_in_.st M Refactoring-Critics.package/RBModifiesCollectionRule.class/instance/private/modifiesTree_in_.st M ScriptLoader40.package/ScriptLoader.class/instance/-- all --/commentForCurrentUpdate.st R ScriptLoader40.package/ScriptLoader.class/instance/-- all --/script618.st A ScriptLoader40.package/ScriptLoader.class/instance/-- all --/script619.st R ScriptLoader40.package/ScriptLoader.class/instance/-- all --/update40618.st A ScriptLoader40.package/ScriptLoader.class/instance/-- all --/update40619.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script618.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script619.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40618.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40619.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40619 16362 Backport Pharo4: 16131 RBModifiesCollectionRule breaks methods AST when checking https://pharo.fogbugz.com/f/cases/16362 16069 backport Pharo4: 16067 remove #prepareDebuggerExample https://pharo.fogbugz.com/f/cases/16069 16081 Backport Pharo: 16080 RBImplementedButNotSent always true https://pharo.fogbugz.com/f/cases/16081 http://files.pharo.org/image/40/40619.zip

Aug. 26, 2015