November 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Some menu entries should not be in spotter

by Andrei Chis

We added all entries from the world menu to spotter. But indeed without a better ordering of results this can cause some issues. We can revert to a previous solution where we just show the items from the main and the tools menu. On Wed, Nov 11, 2015 at 1:03 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > I managed to start 'Software update' by typing Date in spotter. > There are probably a few more menu entries that should > not be so easily accessible? > > Stephan > > >

Nov. 11, 2015

Re: [Pharo-dev] Does anybody know if Sport is available in Pharo?

by stepharo

I would like to see what is needed and if we can improve Pharo libraries :) Le 10/11/15 21:39, Sven Van Caekenberghe a Ã©crit : > << Sport is a Smalltalk portability layer. Sport presents a consistent interface and implemented in a number of Smalltalk dialects. Smalltalk code written to the Sport interfaces can be run in any Smalltalk dialect without alteration. >> > > Anyway, that was the idea some years ago. It is somewhat comparable to Grease (used by Seaside). > >> On 10 Nov 2015, at 21:27, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >> >> anyone care to explain what Sport is , the project description does not help. >> >> On Tue, Nov 10, 2015 at 8:33 PM stepharo <stepharo(a)free.fr> wrote: >> thanks! >> >> >> Le 10/11/15 10:03, Stephan Eggermont a Ã©crit : >>> On 10-11-15 08:00, stepharo wrote: >>>> Thanks >>> I assume you want it working in Pharo5? >>> There was no #'pharo5.x' >>> >>> Name: ConfigurationOfSPort2-StephanEggermont.16 >>> Author: StephanEggermont >>> Time: 10 November 2015, 10:01:56.039515 am >>> UUID: 0c712020-3d22-405b-9842-3106b6b9721f >>> Ancestors: ConfigurationOfSPort2-StephanEggermont.15 >>> >>> In-place pharo5 version added >>> >>> >>> >>> >> > >

Nov. 11, 2015

I love to see all the enhancements

by stepharo

Hi Pharoers I really love to see all the enhancements being pushed to Pharo. This is a great feeling. Thanks for all your contributions. We are building a really nice system. Stef

Nov. 11, 2015

[pharo-project/pharo-core] 9109c4: 50432

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 9109c40f8bfc8f6e4fee22dde9f419bc2449e4ee https://github.com/pharo-project/pharo-core/commit/9109c40f8bfc8f6e4fee22dd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-11-11 (Wed, 11 Nov 2015) Changed paths: M ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/symbolic versions/stable_.st A ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/versions/version%5F0%5F10_.st R Nautilus.package/AbstractCategoryWidget.class/README.md R Nautilus.package/AbstractCategoryWidget.class/definition.st R Nautilus.package/AbstractCategoryWidget.class/instance/drag and drop/dragPassengersFor_inMorph_.st R Nautilus.package/AbstractCategoryWidget.class/instance/drag and drop/dropMethod_inARow_.st R Nautilus.package/AbstractCategoryWidget.class/instance/drag and drop/wantsDroppedMorph_event_inMorph_.st R Nautilus.package/AbstractCategoryWidget.class/instance/icon/categoryIconFor_.st R Nautilus.package/AbstractCategoryWidget.class/instance/item creation/buildCategoriesList.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/categoriesMenu_shifted_.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/categoriesSelection.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/keyPressedOnCategory_.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/label_.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/resetCategoryList.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/resetCategorySelection.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/searchedElement_.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/selectedCategories.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/selectedCategory.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/showInstance.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/takeKeyboardFocus.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/updateCategoryList.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/vScrollValue.st R Nautilus.package/AbstractCategoryWidget.class/instance/protocol/vScrollValue_.st R Nautilus.package/AbstractCategoryWidget.class/instance/updating/okToChange.st M Nautilus.package/CategoryWidget.class/README.md R Nautilus.package/CategoryWidget.class/class/menu/categoriesMenu_.st R Nautilus.package/CategoryWidget.class/class/shortcuts/buildProtocolShortcutsOn_.st M Nautilus.package/CategoryWidget.class/definition.st A Nautilus.package/CategoryWidget.class/instance/drag and drop/dragPassengersFor_inMorph_.st A Nautilus.package/CategoryWidget.class/instance/drag and drop/dropMethod_inARow_.st A Nautilus.package/CategoryWidget.class/instance/drag and drop/wantsDroppedMorph_event_inMorph_.st A Nautilus.package/CategoryWidget.class/instance/icon/categoryIconFor_.st A Nautilus.package/CategoryWidget.class/instance/protocol/categoriesMenu_shifted_.st A Nautilus.package/CategoryWidget.class/instance/protocol/selectedCategory.st A Nautilus.package/CategoryWidget.class/instance/protocol/showInstance.st A Nautilus.package/CategoryWidget.class/instance/protocol/updateCategoryList.st A Nautilus.package/CategoryWidget.class/instance/updating/okToChange.st M Nautilus.package/MethodWidget.class/instance/initialization/initialize.st M Nautilus.package/MethodWidget.class/instance/protocol/resetMethodSelection.st M Nautilus.package/MethodWidget.class/instance/protocol/selectMethod_.st M Nautilus.package/MethodWidget.class/instance/protocol/selectedMethods.st M Nautilus.package/MethodWidget.class/instance/selection/methodSelectionAt_.st M Nautilus.package/MethodWidget.class/instance/selection/methodSelectionAt_put_.st A Nautilus.package/MethodWidget.class/instance/selection/removeSelectionOf_.st M NautilusCommon.package/PackageTasksPlugin.class/instance/display/updateMethodSelection_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50431.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50432.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50431.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50432.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Catalog.package/extension/GTSpotter/instance/spotterCatalogProjectsFor_.st Log Message: ----------- 50432 16891 MethodWidget should use a dictionary to store selected methods (Was: FT: Multi selection can happen when it should not) https://pharo.fogbugz.com/f/cases/16891 16980 Folding CategoryWidget into superclass https://pharo.fogbugz.com/f/cases/16980 16979 Integrate latest version of Catalog browser 12.11.2015 https://pharo.fogbugz.com/f/cases/16979 http://files.pharo.org/image/50/50432.zip

Nov. 11, 2015

[pharo-project/pharo-core]

by GitHub

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

Nov. 11, 2015

Some menu entries should not be in spotter

by Stephan Eggermont

I managed to start 'Software update' by typing Date in spotter. There are probably a few more menu entries that should not be so easily accessible? Stephan

Nov. 11, 2015

Re: [Pharo-dev] [Pharo-users] Changing playground and monticello shortcuts

by Peter UhnÃ¡k

On Wed, Nov 11, 2015 at 11:46 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I actually think we should disable those shortcuts. > > The reason is that they âpollute" the global shortcut space: Well they are global shortcuts, so that's to be expected. > for example, you can now not use Cmd+o for any custom action in your own > window, and that is less than ideal. > as far as I know events bubble up, so morphs can intercept them (which will break the global shortcut, but if the programmer sees it as appropriate...) > > The alternative is to use Spotter to spawn windows. The interesting thing > there is that you do not need shortcuts for every specific windows because > you can use regular search. For example, opening Playground is: > Shift+Enter, p, Enter > This takes significantly more time, and on top of that doesn't actually work, because the first group is History and not Menu... so this would open PetitParser browser for me. I don't see a problem in having global shortcuts for the most important tools, if the current key combinations are problem, then we should come up with different combinations. Peter

Nov. 11, 2015

Re: [Pharo-dev] [Pharo-users] Changing playground and monticello shortcuts

by Henrik Johansen

Ehm, or maybe fix event dispatch so it works properly? It should always end up testing for event handling By the leaf morph at the given event position and work its way up if unhandled, not check top-down like the change to dispatchEvent:with: has ended up doing... Cheers, Henry > On 11 Nov 2015, at 11:46 , Tudor Girba <tudor(a)tudorgirba.com> wrote: > > I actually think we should disable those shortcuts. > > The reason is that they âpollute" the global shortcut space: for example, you can now not use Cmd+o for any custom action in your own window, and that is less than ideal. > > The alternative is to use Spotter to spawn windows. The interesting thing there is that you do not need shortcuts for every specific windows because you can use regular search. For example, opening Playground is: Shift+Enter, p, Enter > > Cheers, > Doru > > >> On Nov 11, 2015, at 10:49 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> >> >> >> 2015-11-11 10:45 GMT+01:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >> Hi, >> >> currently to open a Playground via shortcut one has to type <cmd>+o+w, that's because it used to open Workspace. >> However since it now opens Playground the shortcut is no longer appropriate. >> >> So can we change it to <cmd>+o+p? >> (This shortcut is currently occupied by Monticello Browser, but that can be movd to <cmd>+o+m which is free.) >> >> cmd+o+m would be >> ctrl+o ctrl+m on windows, but ctrl+m does not work yet on windows. >> >> >> You could argue that people are used to this shortcut, however that will not be true for newcommers, who will just see it as random naming (which it currently is). >> >> Peter >> > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > >

Nov. 11, 2015

Re: [Pharo-dev] Raspberry Pi 2 - NativeBoost?

by Esteban Lorenzano

> On 10 Nov 2015, at 23:08, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > In short NativeBoost has in production no support for ARM assembler. At some point a DSL was built to generate assembly code in an abstract way over ARM and x86 (it was called VirtualCPU) but it has never been released. To solve this issue you need to have NativeBoost generate ARM assembly code. This should be solved mainly inside the image. > > Alternatively Esteban is working (and has almost finished) on a FFI backend for Cairo and FFI already supports ARM and works fine on the Pie. what Iâm working on is a FFI backend for NativeBoost (the FFI part which is what everybody uses)â¦ and is almost finish, not just for Cairo :) Esteban > > Best, > > Clement > > 2015-11-10 21:38 GMT-03:00 Eagle Offshore <eagleoffshore(a)mac.com <mailto:eagleoffshore@mac.com>>: > I've got a nifty raspberry pi 2 - which is a pretty cool lil computer. I am amazed at how powerful it is. > > I got the build from the ci server and wanted to play with open street map stuff but, while I have the cairo2 library installed on raspbian, the NativeBoost class cannot load it. > > Is this a Smalltalk issue or a VM level issue? I saw some messages from early October - please keep me in mind if you need testing help. > > Thanks, > -Todd Blanchard >

Nov. 11, 2015

Re: [Pharo-dev] [Pharo-users] Changing playground and monticello shortcuts

by Tudor Girba

I actually think we should disable those shortcuts. The reason is that they âpollute" the global shortcut space: for example, you can now not use Cmd+o for any custom action in your own window, and that is less than ideal. The alternative is to use Spotter to spawn windows. The interesting thing there is that you do not need shortcuts for every specific windows because you can use regular search. For example, opening Playground is: Shift+Enter, p, Enter Cheers, Doru > On Nov 11, 2015, at 10:49 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2015-11-11 10:45 GMT+01:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > Hi, > > currently to open a Playground via shortcut one has to type <cmd>+o+w, that's because it used to open Workspace. > However since it now opens Playground the shortcut is no longer appropriate. > > So can we change it to <cmd>+o+p? > (This shortcut is currently occupied by Monticello Browser, but that can be movd to <cmd>+o+m which is free.) > > cmd+o+m would be > ctrl+o ctrl+m on windows, but ctrl+m does not work yet on windows. > > > You could argue that people are used to this shortcut, however that will not be true for newcommers, who will just see it as random naming (which it currently is). > > Peter > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

Nov. 11, 2015