Re: [Pharo-dev] [ANN] Multiple Desktop support for Pharo 5
uuhhh I just quickly watched your amazing post. I WANT THIS! Even if shortcuts don't work could it work in 4.0? please! On Thu, Aug 27, 2015 at 11:23 AM, Mariano Martinez Peck marianop...@gmail.com wrote: Hi Torsten, There is no way to make it work in Pharo 4.0? On Wed, Aug 26, 2015 at 10:19 PM, Torsten Bergmann asta...@gmx.de wrote: 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. -- Mariano http://marianopeck.wordpress.com -- Mariano http://marianopeck.wordpress.com
[Pharo-dev] translucent windows
Hi all-- I'd like to have windows that use translucent colors, so I can see other windows and the app background beneath. I've been doing this in various versions of Squeak and like it a lot. In Pharo, when I use the titlebar menu of window to change the window's color, the window color doesn't change. What must I do? I'm using the tODE memory from Dale Henrich's GSDevKit project for Gemstone, built from Pharo 3.0.30864. thanks! -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)
Re: [Pharo-dev] [ANN] Multiple Desktop support for Pharo 5
Hi Torsten, There is no way to make it work in Pharo 4.0? On Wed, Aug 26, 2015 at 10:19 PM, Torsten Bergmann asta...@gmx.de wrote: 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. -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-dev] [Pharo-users] [ANN] Multiple Desktop support for Pharo 5
Indeed, tell us since maybe someone can find a workaround :) On Thu, Aug 27, 2015 at 1:52 PM, H. Hirzel hannes.hir...@gmail.com wrote: Julien, could you please describe the problem you had in Pharo 4.0 with more details? --Hannes On 8/27/15, Julien Delplanque jul...@tamere.eu wrote: On 27/08/15 11:42, H. Hirzel wrote: On 8/27/15, Torsten Bergmann asta...@gmx.de wrote: Hi Julien, sorry for hijacking the topic. But I got some time left while traveling allowing me to put my recommended puzzle pieces together myself and as I wrote the code was less time consuming compared to the article. The article should help others to investigate in the goodies code and learn how to do own inspector extensions, spotter models, ... in recent Pharo now. If there is something wrong with the implementation feel free to send me comments/corrections. Also note that the project on STHub is open for commits, so if you find something missing please add it. I would like to keep the multiple desktops metaphor instead of multiple worlds as it better fits what people know and expect. +1 Additional info: Meanwhile the job run that checks the configurations for the Catalog Browser. So in a fresh and updated Pharo 5 image you can just: - hit SHIFT + ENTER to open the default Spotter - enter DesktopManager as a search term to find the project automagically - hit enter to load it So there is no need to rember cumbersome Gofer scripts anymore. Just type and go. After loading you can use the tool as written before: - 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 (custom spotter for desktop selection) - 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 You can also use the world menu (see another screenshot attached). Hope it will become useful to others as well. We should have cared already back in 2010/2011 when Jochen and Sean raised the issue. On the other side with the nice moldable GT tools introduced now in Pharo 4/5 it was really easy to implement. Does this mean that it is available in Pharo 4 as well? I tried it on pharo 4 and it doesn't works, it has the same problem as the one I had when implementing my version. Julien -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-dev] [ANN] Multiple Desktop support for Pharo 5
When changing the desktop, windows opened before where not clickable anymore like if they where a part of the wallpaper. Julien On 27/08/15 18:52, H. Hirzel wrote: Julien, could you please describe the problem you had in Pharo 4.0 with more details? --Hannes On 8/27/15, Julien Delplanque jul...@tamere.eu wrote: On 27/08/15 11:42, H. Hirzel wrote: On 8/27/15, Torsten Bergmann asta...@gmx.de wrote: Hi Julien, sorry for hijacking the topic. But I got some time left while traveling allowing me to put my recommended puzzle pieces together myself and as I wrote the code was less time consuming compared to the article. The article should help others to investigate in the goodies code and learn how to do own inspector extensions, spotter models, ... in recent Pharo now. If there is something wrong with the implementation feel free to send me comments/corrections. Also note that the project on STHub is open for commits, so if you find something missing please add it. I would like to keep the multiple desktops metaphor instead of multiple worlds as it better fits what people know and expect. +1 Additional info: Meanwhile the job run that checks the configurations for the Catalog Browser. So in a fresh and updated Pharo 5 image you can just: - hit SHIFT + ENTER to open the default Spotter - enter DesktopManager as a search term to find the project automagically - hit enter to load it So there is no need to rember cumbersome Gofer scripts anymore. Just type and go. After loading you can use the tool as written before: - 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 (custom spotter for desktop selection) - 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 You can also use the world menu (see another screenshot attached). Hope it will become useful to others as well. We should have cared already back in 2010/2011 when Jochen and Sean raised the issue. On the other side with the nice moldable GT tools introduced now in Pharo 4/5 it was really easy to implement. Does this mean that it is available in Pharo 4 as well? I tried it on pharo 4 and it doesn't works, it has the same problem as the one I had when implementing my version. Julien
Re: [Pharo-dev] [ANN] Multiple Desktop support for Pharo 5
Julien, could you please describe the problem you had in Pharo 4.0 with more details? --Hannes On 8/27/15, Julien Delplanque jul...@tamere.eu wrote: On 27/08/15 11:42, H. Hirzel wrote: On 8/27/15, Torsten Bergmann asta...@gmx.de wrote: Hi Julien, sorry for hijacking the topic. But I got some time left while traveling allowing me to put my recommended puzzle pieces together myself and as I wrote the code was less time consuming compared to the article. The article should help others to investigate in the goodies code and learn how to do own inspector extensions, spotter models, ... in recent Pharo now. If there is something wrong with the implementation feel free to send me comments/corrections. Also note that the project on STHub is open for commits, so if you find something missing please add it. I would like to keep the multiple desktops metaphor instead of multiple worlds as it better fits what people know and expect. +1 Additional info: Meanwhile the job run that checks the configurations for the Catalog Browser. So in a fresh and updated Pharo 5 image you can just: - hit SHIFT + ENTER to open the default Spotter - enter DesktopManager as a search term to find the project automagically - hit enter to load it So there is no need to rember cumbersome Gofer scripts anymore. Just type and go. After loading you can use the tool as written before: - 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 (custom spotter for desktop selection) - 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 You can also use the world menu (see another screenshot attached). Hope it will become useful to others as well. We should have cared already back in 2010/2011 when Jochen and Sean raised the issue. On the other side with the nice moldable GT tools introduced now in Pharo 4/5 it was really easy to implement. Does this mean that it is available in Pharo 4 as well? I tried it on pharo 4 and it doesn't works, it has the same problem as the one I had when implementing my version. Julien
[Pharo-dev] [pharo-project/pharo-core]
Branch: refs/tags/50282 Home: https://github.com/pharo-project/pharo-core
Re: [Pharo-dev] [ANN] Multiple Desktop support for Pharo 5
On 27/08/15 11:42, H. Hirzel wrote: On 8/27/15, Torsten Bergmann asta...@gmx.de wrote: Hi Julien, sorry for hijacking the topic. But I got some time left while traveling allowing me to put my recommended puzzle pieces together myself and as I wrote the code was less time consuming compared to the article. The article should help others to investigate in the goodies code and learn how to do own inspector extensions, spotter models, ... in recent Pharo now. If there is something wrong with the implementation feel free to send me comments/corrections. Also note that the project on STHub is open for commits, so if you find something missing please add it. I would like to keep the multiple desktops metaphor instead of multiple worlds as it better fits what people know and expect. +1 Additional info: Meanwhile the job run that checks the configurations for the Catalog Browser. So in a fresh and updated Pharo 5 image you can just: - hit SHIFT + ENTER to open the default Spotter - enter DesktopManager as a search term to find the project automagically - hit enter to load it So there is no need to rember cumbersome Gofer scripts anymore. Just type and go. After loading you can use the tool as written before: - 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 (custom spotter for desktop selection) - 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 You can also use the world menu (see another screenshot attached). Hope it will become useful to others as well. We should have cared already back in 2010/2011 when Jochen and Sean raised the issue. On the other side with the nice moldable GT tools introduced now in Pharo 4/5 it was really easy to implement. Does this mean that it is available in Pharo 4 as well? I tried it on pharo 4 and it doesn't works, it has the same problem as the one I had when implementing my version. Julien
[Pharo-dev] [pharo-project/pharo-core] 0b7375: 50282
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0b7375bcc5cc35590a10b4d9fc26d1436b237d66 https://github.com/pharo-project/pharo-core/commit/0b7375bcc5cc35590a10b4d9fc26d1436b237d66 Author: Jenkins Build Server bo...@pharo-project.org Date: 2015-08-27 (Thu, 27 Aug 2015) Changed paths: M Morphic-Base.package/extension/WorldState/instance/menuBuilder.st M OSWindow-Core.package/OSWindow.class/instance/private/destroy.st M OSWindow-Core.package/OSWindowAttributes.class/class/class initialization/initialize.st M OSWindow-Core.package/OSWindowTest.class/instance/tests/testSettingUpWindow.st M OSWindow-SDL2.package/OSSDL2Driver.class/instance/window creation and deletion/createWindowWithAttributes_osWindow_.st A OSWindow-SDL2.package/OSSDL2Driver.class/instance/window creation and deletion/registerWindow_.st A OSWindow-SDL2.package/OSSDL2Driver.class/instance/window creation and deletion/unregisterWindowWithId_.st R OSWindow-SDL2.package/OSSDL2Driver.class/instance/window creation and deletion/unregisterWindow_.st M OSWindow-SDL2.package/OSSDL2WindowHandle.class/instance/initialize/destroy.st R Refactoring-Tests-Core.package/RBRefactoryTestDataApp.class/instance/lint/noIsNil_.st R Refactoring-Tests-Critics.package/RBSmalllintTest.class/instance/tests/testConsistencyCheck.st R Refactoring-Tests-Critics.package/RBSmalllintTestObject.class/instance/methods/noIsNil_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50281.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50282.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50281.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50282.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: --- 50282 16372 undeclared reference to searchList in FileList https://pharo.fogbugz.com/f/cases/16372 15102 lost worldmenu https://pharo.fogbugz.com/f/cases/15102 16405 Failign test: RBSmalllintTest.testConsistencyCheck https://pharo.fogbugz.com/f/cases/16405 16404 Two tests failing OSWindowTest https://pharo.fogbugz.com/f/cases/16404 http://files.pharo.org/image/50/50282.zip
Re: [Pharo-dev] [Pharo-users] [ann] brick on top of bloc - preview
Hi, We prepared a working image with Brick preview :) Just open it with the latest Pharo VM and you will instantly see an example browser Pharo-Brick.zip https://drive.google.com/file/d/0B-bMBVDOi3oTdll3dGJValVIenc/view?usp=drive_web Cheers, Alex On Tue, Aug 25, 2015 at 10:13 PM, Tudor Girba tu...@tudorgirba.com wrote: Hi, We are happy to announce the first preview version of Brick, a new widget set created from scratch on top of Bloc. Brick is being developed primarily by Alex Syrel (together with Alain Plantec, Andrei Chis and myself), and the work is sponsored by ESUG. Brick is part of the Glamorous Toolkit effort and will provide the basis for the new versions of the development tools. Brick's goal is to provide a beautiful looking widget set, and the default look is based on material design. The widgets are theme-able. Right now, there exists: - Label - Simple button - Toggle button - Checkbox - Radio button - Window with or without an active title bar that can include various visual actions and info - Menu - Beautiful scrollbars that are thin by default and enlarge when the mouse hovers over it - Scalable list for huge amounts of items with various heights (The list also allows one for embedding text widgets with in place editing) The next immediate target is the creation of a new Pager widget (the widget that is behind the current GTInspector). You can see some screenshots on the official site: http://gt.moosetechnology.org/brick To play with it, you can download a ready-made image: https://ci.inria.fr/moose/job/gtoolkit5/lastSuccessfulBuild/artifact/gtoolkit5.zip and, in a Bloc space, you can browse the examples: BrExampleBrowser exampleOpen We would be happy to hear your feedback. Cheers, Doru -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] brick on top of bloc - preview
Works well! Splendide! Cheers, Alexandre On Aug 27, 2015, at 5:00 PM, Aliaksei Syrel alex.sy...@gmail.com wrote: Hi, We prepared a working image with Brick preview :) Just open it with the latest Pharo VM and you will instantly see an example browser Pharo-Brick.zip Cheers, Alex On Tue, Aug 25, 2015 at 10:13 PM, Tudor Girba tu...@tudorgirba.com wrote: Hi, We are happy to announce the first preview version of Brick, a new widget set created from scratch on top of Bloc. Brick is being developed primarily by Alex Syrel (together with Alain Plantec, Andrei Chis and myself), and the work is sponsored by ESUG. Brick is part of the Glamorous Toolkit effort and will provide the basis for the new versions of the development tools. Brick's goal is to provide a beautiful looking widget set, and the default look is based on material design. The widgets are theme-able. Right now, there exists: - Label - Simple button - Toggle button - Checkbox - Radio button - Window with or without an active title bar that can include various visual actions and info - Menu - Beautiful scrollbars that are thin by default and enlarge when the mouse hovers over it - Scalable list for huge amounts of items with various heights (The list also allows one for embedding text widgets with in place editing) The next immediate target is the creation of a new Pager widget (the widget that is behind the current GTInspector). You can see some screenshots on the official site: http://gt.moosetechnology.org/brick To play with it, you can download a ready-made image: https://ci.inria.fr/moose/job/gtoolkit5/lastSuccessfulBuild/artifact/gtoolkit5.zip and, in a Bloc space, you can browse the examples: BrExampleBrowser exampleOpen We would be happy to hear your feedback. Cheers, Doru -- www.tudorgirba.com Every thing has its own flow ___ Moose-dev mailing list moose-...@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-dev] [Pharo-users] [ann] brick on top of bloc - preview
impressive work and it looks very nice indeed , great work guys :) On Thu, Aug 27, 2015 at 11:01 PM Aliaksei Syrel alex.sy...@gmail.com wrote: Hi, We prepared a working image with Brick preview :) Just open it with the latest Pharo VM and you will instantly see an example browser Pharo-Brick.zip https://drive.google.com/file/d/0B-bMBVDOi3oTdll3dGJValVIenc/view?usp=drive_web Cheers, Alex On Tue, Aug 25, 2015 at 10:13 PM, Tudor Girba tu...@tudorgirba.com wrote: Hi, We are happy to announce the first preview version of Brick, a new widget set created from scratch on top of Bloc. Brick is being developed primarily by Alex Syrel (together with Alain Plantec, Andrei Chis and myself), and the work is sponsored by ESUG. Brick is part of the Glamorous Toolkit effort and will provide the basis for the new versions of the development tools. Brick's goal is to provide a beautiful looking widget set, and the default look is based on material design. The widgets are theme-able. Right now, there exists: - Label - Simple button - Toggle button - Checkbox - Radio button - Window with or without an active title bar that can include various visual actions and info - Menu - Beautiful scrollbars that are thin by default and enlarge when the mouse hovers over it - Scalable list for huge amounts of items with various heights (The list also allows one for embedding text widgets with in place editing) The next immediate target is the creation of a new Pager widget (the widget that is behind the current GTInspector). You can see some screenshots on the official site: http://gt.moosetechnology.org/brick To play with it, you can download a ready-made image: https://ci.inria.fr/moose/job/gtoolkit5/lastSuccessfulBuild/artifact/gtoolkit5.zip and, in a Bloc space, you can browse the examples: BrExampleBrowser exampleOpen We would be happy to hear your feedback. Cheers, Doru -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Fwd: [Pharo-users] [ann] brick on top of bloc - preview
On Fri, Aug 28, 2015 at 8:34 AM, J.F. Rick s...@je77.com wrote: On Wed, Aug 26, 2015 at 11:45 PM Ben Coman b...@openinworld.com wrote: So morphic has a Z-order but I think not a Z-depth. Is that be something we should be aiming for? In HTML5, Z-depth is pretty exclusively used as a mechanism to determine Z-order in the HTML / CSS separation. Normally, the order of HTML determines the Z-order. But, Z-order is really a style thing, rather than a composition thing. So, specifying the Z-depth allows you to override standard behavior in the style sheet. This is not necessary in a true object-based GUI where graphical objects are more self contained and can easily determine their own Z-order. I doubt we will see general purpose adoption of any 2D interface that will rely on Z-depth for anything besides determining Z-order. For instance, the example of shadow size seems interesting but runs into usability problems quickly. Let's say that you have element A with a larger shadow to indicate that it is above element B with a smaller shadow. That seems great. What happens if element B is selected and brought to the forefront? Does A's shadow go down in size? If so, that breaks the normal shadow analogy. If not, it would seem that the shadows would just keep growing bigger each time a new element is brought to the front. For limited general-purpose applications (e.g., a larger shadow for an object currently being dragged), you don't need Z-depth info. For specialized applications where a Z-depth might make sense (I can't even think of one), there's little problem adding such functionality to custom widgets. So, my recommendations is to stay away from trying to implement Z-depth as a fundamental component of a 2D interface. The benefit is minimal and largely theoretical. Cheers, Jeff Thats a fair argument, thanks Jeff. I guess if someone wanted different size shadows for different z-order, a fixed distance between levels could be simulated with all windows shuffling down when a window is brought to the top. cheers -ben
[Pharo-dev] [pharo-project/pharo-core] 4e74d9: 50281
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4e74d9d60663c7cc914991385e60493e9c7b921c https://github.com/pharo-project/pharo-core/commit/4e74d9d60663c7cc914991385e60493e9c7b921c Author: Jenkins Build Server bo...@pharo-project.org Date: 2015-08-27 (Thu, 27 Aug 2015) Changed paths: M Graphics-Resources.package/extension/ThemeIcons/instance/blankIconOfWidth_.st R Kernel.package/Context.class/class/examples/trace_on_.st R Kernel.package/Exit.class/README.md R Kernel.package/Exit.class/class/instance creation/failure.st R Kernel.package/Exit.class/class/instance creation/status_.st R Kernel.package/Exit.class/class/instance creation/success.st R Kernel.package/Exit.class/class/signalling/signalFailure.st R Kernel.package/Exit.class/class/signalling/signalFailure_.st R Kernel.package/Exit.class/class/signalling/signalSuccess.st R Kernel.package/Exit.class/class/signalling/signalSuccess_.st R Kernel.package/Exit.class/definition.st R Kernel.package/Exit.class/instance/accessing/defaultAction.st R Kernel.package/Exit.class/instance/accessing/printMessage.st R Kernel.package/Exit.class/instance/accessing/status.st R Kernel.package/Exit.class/instance/accessing/status_.st R Kernel.package/Exit.class/instance/printing/printOn_.st R Kernel.package/Exit.class/instance/testing/isSuccess.st A Kernel.package/ManifestKernel.class/class/meta-data - dependency analyser/ignoredDependencies.st M Kernel.package/ManifestKernel.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st A Kernel.package/PackageManifest.class/class/meta-data - dependency analyser/ignoredDependencies.st A Kernel.package/PackageManifest.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M Komitter.package/KomitMethod.class/class/instance creation/method_.st M Polymorph-Widgets.package/EclipseUIThemeIcons.class/instance/nautilus/smallProfileIcon.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50280.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50281.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50280.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50281.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-CommandLine.package/Exit.class/README.md A System-CommandLine.package/Exit.class/class/instance creation/failure.st A System-CommandLine.package/Exit.class/class/instance creation/status_.st A System-CommandLine.package/Exit.class/class/instance creation/success.st A System-CommandLine.package/Exit.class/class/signalling/signalFailure.st A System-CommandLine.package/Exit.class/class/signalling/signalFailure_.st A System-CommandLine.package/Exit.class/class/signalling/signalSuccess.st A System-CommandLine.package/Exit.class/class/signalling/signalSuccess_.st A System-CommandLine.package/Exit.class/definition.st A System-CommandLine.package/Exit.class/instance/accessing/defaultAction.st A System-CommandLine.package/Exit.class/instance/accessing/printMessage.st A System-CommandLine.package/Exit.class/instance/accessing/status.st A System-CommandLine.package/Exit.class/instance/accessing/status_.st A System-CommandLine.package/Exit.class/instance/printing/printOn_.st A System-CommandLine.package/Exit.class/instance/testing/isSuccess.st M System-CommandLine.package/ManifestSystemCommandLine.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st Log Message: --- 50281 16294 get rid of System-VMEvents dependency in the bootstrap https://pharo.fogbugz.com/f/cases/16294 16203 Wrong diff when changing the package of an extension method https://pharo.fogbugz.com/f/cases/16203 16394 Kernel should not depend on System-CommandLine. Check the Exit class https://pharo.fogbugz.com/f/cases/16394 16403 make two icon names more uniform https://pharo.fogbugz.com/f/cases/16403 http://files.pharo.org/image/50/50281.zip
[Pharo-dev] [pharo-project/pharo-core] 2395d5: 50280
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 2395d50aee1cc812e17c87af7e782ddaf5926703 https://github.com/pharo-project/pharo-core/commit/2395d50aee1cc812e17c87af7e782ddaf5926703 Author: Jenkins Build Server bo...@pharo-project.org Date: 2015-08-27 (Thu, 27 Aug 2015) Changed paths: M Kernel.package/TimeZone.class/class/accessing/local.st M Morphic-Widgets-Windows.package/SystemWindow.class/instance/open%2Fclose/openInWorld_extent_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50279.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50280.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50279.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50280.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Shout.package/SHRBTextStyler.class/instance/private/currentClosedBracketStyleName.st A Shout.package/SHRBTextStyler.class/instance/private/currentClosedParenthesisStyleName.st A Shout.package/SHRBTextStyler.class/instance/private/currentOpenedBracketStyleName.st A Shout.package/SHRBTextStyler.class/instance/private/currentOpenedParenthesisStyleName.st M Shout.package/SHRBTextStyler.class/instance/private/styleCloseBracket_.st M Shout.package/SHRBTextStyler.class/instance/private/styleCloseParenthese_.st M Shout.package/SHRBTextStyler.class/instance/private/styleOpenBracket_.st M Shout.package/SHRBTextStyler.class/instance/private/styleOpenParenthese_.st R System-FileRegistry.package/SimpleServiceEntry.class/instance/services menu/addServiceFor_toMenu_.st A Tool-FileList.package/extension/SimpleServiceEntry/instance/addServiceFor_toMenu_.st M UIManager.package/DummyUIManager.class/instance/display/restoreDisplayAfter_.st Log Message: --- 50280 16377 Formater bug on FileReference with cascade https://pharo.fogbugz.com/f/cases/16377 16398 System-FileRegistry depends on Morphic https://pharo.fogbugz.com/f/cases/16398 16401 opening monticello window does not respect world size https://pharo.fogbugz.com/f/cases/16401 16397 DummyUIManager depends on System-VMEvents https://pharo.fogbugz.com/f/cases/16397 16396 Timezonelocal should use LocalTimeZone https://pharo.fogbugz.com/f/cases/16396 http://files.pharo.org/image/50/50280.zip
[Pharo-dev] [pharo-project/pharo-core]
Branch: refs/tags/50280 Home: https://github.com/pharo-project/pharo-core
[Pharo-dev] [pharo-project/pharo-core] c15b5e: 50279
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c15b5ec45863345ff16be6dff19bcc984f39ce4f https://github.com/pharo-project/pharo-core/commit/c15b5ec45863345ff16be6dff19bcc984f39ce4f Author: Jenkins Build Server bo...@pharo-project.org Date: 2015-08-27 (Thu, 27 Aug 2015) Changed paths: A ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/baselines/baseline04_.st A ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/baselines/baseline05_.st A ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/baselines/baseline06_.st M ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/symbolic versions/development_.st M ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/symbolic versions/stable_.st A ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/versions/version122_.st A ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/versions/version123_.st A ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/versions/version124_.st A ConfigurationOfOSWindow.package/ConfigurationOfOSWindow.class/instance/versions/version125_.st R Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/private/privateColor_.st A OSWindow-Core.package/OSEvent.class/instance/accessing/window.st R OSWindow-Core.package/OSKeyboardEvent.class/instance/accessing/printOn_.st A OSWindow-Core.package/OSKeyboardEvent.class/instance/printing/printOn_.st A OSWindow-Core.package/OSMouseEvent.class/instance/initialization/initialize.st R OSWindow-Core.package/OSMouseEvent.class/instance/initialize/initialize.st R OSWindow-Core.package/OSMouseWheelEvent.class/instance/as yet unclassified/accept_.st A OSWindow-Core.package/OSMouseWheelEvent.class/instance/visitor/accept_.st R OSWindow-Core.package/OSNullWindowDriver.class/instance/as yet unclassified/createWindowWithAttributes_osWindow_.st R OSWindow-Core.package/OSNullWindowDriver.class/instance/as yet unclassified/isNullDriver.st A OSWindow-Core.package/OSNullWindowDriver.class/instance/testing/isNullDriver.st A OSWindow-Core.package/OSNullWindowDriver.class/instance/window creation/createWindowWithAttributes_osWindow_.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/attributes_.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/bounds_.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/clipboardText.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/clipboardText_.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/extent.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/extent_.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/hide.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/isValid.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/position.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/position_.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/show.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/title.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/accessing/title_.st R OSWindow-Core.package/OSNullWindowHandle.class/instance/as yet unclassified/attributes_.st R OSWindow-Core.package/OSNullWindowHandle.class/instance/as yet unclassified/destroy.st R OSWindow-Core.package/OSNullWindowHandle.class/instance/as yet unclassified/extent.st R OSWindow-Core.package/OSNullWindowHandle.class/instance/as yet unclassified/extent_.st R OSWindow-Core.package/OSNullWindowHandle.class/instance/as yet unclassified/isValid.st R OSWindow-Core.package/OSNullWindowHandle.class/instance/as yet unclassified/newFormRenderer_.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/initialize/destroy.st A OSWindow-Core.package/OSNullWindowHandle.class/instance/instance creation/newFormRenderer_.st A OSWindow-Core.package/OSTextInputEvent.class/instance/initialization/initialize.st R OSWindow-Core.package/OSTextInputEvent.class/instance/initialize/initialize.st R OSWindow-Core.package/OSTouchActionCancelEvent.class/README.md R OSWindow-Core.package/OSTouchActionCancelEvent.class/definition.st R OSWindow-Core.package/OSTouchActionHoverEnterEvent.class/README.md R OSWindow-Core.package/OSTouchActionHoverEnterEvent.class/definition.st R OSWindow-Core.package/OSTouchActionHoverEvent.class/README.md R OSWindow-Core.package/OSTouchActionHoverEvent.class/definition.st R OSWindow-Core.package/OSTouchActionHoverExitEvent.class/README.md R OSWindow-Core.package/OSTouchActionHoverExitEvent.class/definition.st
[Pharo-dev] [pharo-project/pharo-core]
Branch: refs/tags/50279 Home: https://github.com/pharo-project/pharo-core
[Pharo-dev] Open Postdoc/PhD positions at the Software Composition Group - University of Bern
Applications are invited for a Postdoc and PhD candidates to participate in a research project on Agile Software Analysis at the Software Composition Group, University of Bern, Switzerland. The Software Composition Group carries out research in software analysis and programming language design and implementation, with a view to enabling software evolution. The SCG is led by Prof. Oscar Nierstrasz and is part of the Institute of Computer Science and Applied Mathematics (IAM) at the University of Berne. Details about the research topics can be found online: http://scg.unibe.ch/research/snf16 The PhD candidates must have a MSc in Computer Science (equivalent to a Swiss MSc), should demonstrate strong programming skills, and have research interests in several of the following areas: - software evolution - program understanding - mining software repositories - software modeling - model-driven engineering - domain specific languages - dynamic analysis - software ecosystems - integrated development environments - software tools The Postdoc should have completed a recent PhD on a topic closely related to the themes listed above. To apply, please send an email including your CV to Prof. Oscar Nierstrasz (os...@inf.unibe.ch). Oscar Nierstrasz --- Prof. Dr. O. Nierstrasz-- os...@inf.unibe.ch Software Composition Group -- http://scg.unibe.ch University of Bern -- Tel +41 31 631 4618
[Pharo-dev] GLMPresentation and actions
Hi Glamour experts, There are methods in GLMPresentation like #act:icon:entitled: #act:icon:on:entitled: adding an action but (unfortunately) these methods do not return the action itself but the presentation instead. But the presentation itself is the receiver of the message so the sender already has access to it anyway. Not returning the created action makes it hard to access the action afterwards to send additional messages to it (like #condition: or other). One would have to implement a #act:icon:entitled:condition: and other flavours - ending up in a lot of method variations. Example: in CatalogBrowserdefineAllRepositoriesInMCBrowserButton: I have access to the list (a presentation) and I can use #act:icon:entitled: to add an action button but have no access to the action added afterwards. Should we change these methods to return the action and also GLMPresentation#addAction: to return the action: addAction: anAction ^self actions addLast: anAction This way it would be similar to a collection: if you add an element you get it in return. IMHO this would prevent adding more and more flavour messages in the future. What do you think. Also: I would like the action buttons in CatalogBrowser to be only enabled when an item in the list (presentation) is selected. How can I do that? There is a #condition: for an action but that is the condition for the button to be there. There is no updating #enabledWhen: or other. Thanks T.
Re: [Pharo-dev] Fwd: [Pharo-users] [ann] brick on top of bloc - preview
On Wed, Aug 26, 2015 at 11:45 PM Ben Coman b...@openinworld.com wrote: So morphic has a Z-order but I think not a Z-depth. Is that be something we should be aiming for? In HTML5, Z-depth is pretty exclusively used as a mechanism to determine Z-order in the HTML / CSS separation. Normally, the order of HTML determines the Z-order. But, Z-order is really a style thing, rather than a composition thing. So, specifying the Z-depth allows you to override standard behavior in the style sheet. This is not necessary in a true object-based GUI where graphical objects are more self contained and can easily determine their own Z-order. I doubt we will see general purpose adoption of any 2D interface that will rely on Z-depth for anything besides determining Z-order. For instance, the example of shadow size seems interesting but runs into usability problems quickly. Let's say that you have element A with a larger shadow to indicate that it is above element B with a smaller shadow. That seems great. What happens if element B is selected and brought to the forefront? Does A's shadow go down in size? If so, that breaks the normal shadow analogy. If not, it would seem that the shadows would just keep growing bigger each time a new element is brought to the front. For limited general-purpose applications (e.g., a larger shadow for an object currently being dragged), you don't need Z-depth info. For specialized applications where a Z-depth might make sense (I can't even think of one), there's little problem adding such functionality to custom widgets. So, my recommendations is to stay away from trying to implement Z-depth as a fundamental component of a 2D interface. The benefit is minimal and largely theoretical. Cheers, Jeff
Re: [Pharo-dev] [squeak-dev] #instSize in Squeak 5 seems to be broken for Traits
Hi Max, fixed in Squeak via a preamble in a new version of Traits. I must remember to fix this in the bootstrap so that it doesn't afflict Pharo Spur. On Sun, Aug 23, 2015 at 4:34 AM, Max Leske maxle...@gmail.com wrote: On 22 Aug 2015, at 19:21, Eliot Miranda eliot.mira...@gmail.com wrote: Hi Max, On Fri, Aug 21, 2015 at 2:11 PM, Max Leske maxle...@gmail.com wrote: On 21 Aug 2015, at 19:31, Eliot Miranda eliot.mira...@gmail.com wrote: Hi Max, On Fri, Aug 21, 2015 at 8:57 AM, Max Leske maxle...@gmail.com wrote: Hi folks I’ve been trying to load Fuel into Squeak 5 but can’t because I get errors when loading Traits (they have not instance variables). The reason for this error seems to be that #instSize answers 2 for Traits when it should answer 0. The current implementation is: ^format bitAnd: 16r The comment in the 4.6 version says: NOTE: This code supports the backward-compatible extension to 8 bits of instSize. When we revise the image format, it should become... ^ ((format bitShift: -1) bitAnd: 16rFF) - 1 Note also that every other method in this category will require 2 bits more of right shift after the change. “ When I use that version in TraitBehaviourinstSize in Squeak 5 I get 0 as expected and I can load Fuel without problems. So Spur has a different layout for format than V3. The above implementation (format bitAnd: 16r) is correct for Spur. In loading classes or traits via Fuel from 4.6 to 5.0 you're going to have to convert the format inst var to reflect its usage in Spur. So we need to be clear here. Is the issue that you're trying to load classes and/or traits from a Fuel file written by 4.6 or is it that as part of the Fuel load a new Trait gets created which has a format of 2? The latter. This is reproducible by simply creating a new Trait: Trait named: #NewTrait uses: #() category: ‘new cat’. NewTrait instSize “— 2” I just took a look at this and it doesn't reproduce. I'm using a trunk Squeak 5 image and I get 0 and required. ? Thanks Eliot. You’re right. The problem is not with #instSize, I don’t know how I managed to get the above… The problem is actually, that TApplyingOnClassSide (which is already present) has a format of 2: TApplyingOnClassSide instSize “— 2” Also, all Traits in the image have format 2, while new Traits have format 0: format2 := Smalltalk allTraits select: [ :e | e format = 2 ]. Smalltalk allTraits size = format2 size “— true Trait named: #NewTrait uses: #() category: 'new cat’. NewTrait instSize “— 0 format2 := Smalltalk allTraits select: [ :e | e format = 2 ]. Smalltalk allTraits size = format2 size “— false” This is with build 15113 (which is trunk I suppose). Cheers, Max Cheers, Max Cheers, Max -- _,,,^..^,,,_ best, Eliot -- _,,,^..^,,,_ best, Eliot -- _,,,^..^,,,_ best, Eliot
