March 2014 - Pharo-dev - lists.pharo.org

Broken Form>>dominantColor in 3.0

by Hilaire Fernandes

Hello, Problem described there, https://pharo.fogbugz.com/f/cases/13057/DominantColor-brokem It seems to be related to BitBlt, combinationRule #33 Any idea? Thanks Hilaire -- Dr. Geo http://drgeo.eu

March 8, 2014

Re: [Pharo-dev] About inspectors

by Alexandre Bergel

Indeed having particular views is only one (minor) aspect. The coding and navigation flow GTTools offers is fantastic. I am not a big fan of Glamour scripting language, but what is built on top of it is remarkable. It may even be a killing app for Pharo. Alexandre > Le 08-03-2014 Ã 4:16, Tudor Girba <tudor(a)tudorgirba.com> a Ã©crit : > > I hope not. What are we trying to optimize? > > If you look closely at the GT work, you might notice that it is not just a tool, it's a whole new philosophy for coding. The EyeInspector picked only one aspect out of a whole. > > One high goal is to change programming such that the inspector + debugger to capture most of the coding experience. This is what live means. Right now, in the default Pharo we only code small things in the debugger and nothing in the inspector. We work on the idea of a moldable IDE that will change all that. > > Let's look at some facts. Right now, in my image I have 75 different extensions for GTInspector. And the total amount of lines of code has barely passed 1000 LOC (including all utility code). These are not just independent views, but they are combinable. The amount of use cases supported span a wide range: querying source code, visualizing performance, navigating file system, querying DB, and more (read the posts from humane-assessment.com for hints in this direction). > > We programmed most of these extensions from within the inspector both because it's fun and because it's significantly more productive. And I am not the only one. This power is not serendipity, it's by design. And we only started to untap this potential. > > There is still a long way for the concept of inspector and I believe there is a large payoff in it, too. > > Optimizing for a small thing now should not be the way to go :) > > Cheers, > Doru > > > > >> On Fri, Mar 7, 2014 at 11:23 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Well I would hope that some kind of convergence would be possible in the future. Maybe some kind of abstract meta description like magritte, that different tools can use. >> >> On 07 Mar 2014, at 16:43, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> > Hi everyone. >> > >> > This day Iâve attended Moose dojo and Iâm pretty impressed with the possibilities of GTInspector. The one thing that Iâve noticed is that both GTInspactor and EyeInspector support custom inspections for objects. Iâm wandering if we can come up with a common protocol to give an object specific infector view, and not develop a separate thing for each inspector. >> > >> > Uko > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 8, 2014

Re: [Pharo-dev] Tiling Window Manager in 3.0: working but still issues with WorldMorph

by phil＠highoctane.be

And the keybindings are also kind of not working either. Help welcome. Phil On Sat, Mar 8, 2014 at 11:57 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > TWM works in 3.0 after some work on icons and updating menus. > > Gofer new > smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; > configuration; > load. > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > '3.0') load > > You can also use > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > #development) load > > but this will for sure change over time. > > There is the World management icon which is still there and it looks like > it can create worlds but switching between them just breaks havoc. > > Maybe should we just remove that feature from TWM as 3.0 doesn't seem to > be multiworld friendly. > > Nothing done on tests nor themeing (which appears to be not that working > well in 3.0 either due to theming changes); > > At least the thing is back :-) [I missed it...] > > Phil >

March 8, 2014

Tiling Window Manager in 3.0: working but still issues with WorldMorph

by phil＠highoctane.be

TWM works in 3.0 after some work on icons and updating menus. Gofer new smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; configuration; load. ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: '3.0') load You can also use ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: #development) load but this will for sure change over time. There is the World management icon which is still there and it looks like it can create worlds but switching between them just breaks havoc. Maybe should we just remove that feature from TWM as 3.0 doesn't seem to be multiworld friendly. Nothing done on tests nor themeing (which appears to be not that working well in 3.0 either due to theming changes); At least the thing is back :-) [I missed it...] Phil

March 8, 2014

Re: [Pharo-dev] Coral (again)

by Pharo4Stef

We restarted to work on Coral again with Damien C, Damien P and the code is on Smaltalkhub. We will continue. We got distracted because of glitches in pillar. I will take us probably some time but we really want it to become true this year. On 07 Mar 2014, at 21:59, phil(a)highoctane.be wrote: > I would like to know where to look to get a "valid"/"best" version of Coral to use/work on. > > I am going to need to work in an assignment where there are a number of scripting things to do and I'd like to give Pharo a shot. > > I'd like to be able to use Coral, as I liked the video about it and how it worked. > > I saw that Camillo has it on GitHub. > > TIA for the pointers. > > Phil

March 8, 2014

Re: [Pharo-dev] Smalltalk tools: explore failing in 3.0

by Pharo4Stef

On 08 Mar 2014, at 08:33, phil(a)highoctane.be wrote: > If I do inspect > > Smalltalk tools > > it works. > > But explore crashes. > > How is that? not tested :) We will fix that. Probably nothing > > Phil

March 8, 2014

Re: [Pharo-dev] About inspectors

by phil＠highoctane.be

Doru, Where to look on your blog for a view on the essentials of this? I see http://www.humane-assessment.com/blog/making-the-pharo-settings-browser-ope… example. A video? I look at the blog and vids but it is a bit hard to find a basic demo to grasp things. TIA Phil On Sat, Mar 8, 2014 at 8:16 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I hope not. What are we trying to optimize? > > If you look closely at the GT work, you might notice that it is not just a > tool, it's a whole new philosophy for coding. The EyeInspector picked only > one aspect out of a whole. > > One high goal is to change programming such that the inspector + debugger > to capture most of the coding experience. This is what live means. Right > now, in the default Pharo we only code small things in the debugger and > nothing in the inspector. We work on the idea of a moldable IDE that will > change all that. > > Let's look at some facts. Right now, in my image I have 75 different > extensions for GTInspector. And the total amount of lines of code has > barely passed 1000 LOC (including all utility code). These are not just > independent views, but they are combinable. The amount of use cases > supported span a wide range: querying source code, visualizing performance, > navigating file system, querying DB, and more (read the posts from > humane-assessment.com for hints in this direction). > > We programmed most of these extensions from within the inspector both > because it's fun and because it's significantly more productive. And I am > not the only one. This power is not serendipity, it's by design. And we > only started to untap this potential. > > There is still a long way for the concept of inspector and I believe there > is a large payoff in it, too. > > Optimizing for a small thing now should not be the way to go :) > > Cheers, > Doru > > > > > On Fri, Mar 7, 2014 at 11:23 PM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > >> Well I would hope that some kind of convergence would be possible in the >> future. Maybe some kind of abstract meta description like magritte, that >> different tools can use. >> >> On 07 Mar 2014, at 16:43, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> > Hi everyone. >> > >> > This day I've attended Moose dojo and I'm pretty impressed with the >> possibilities of GTInspector. The one thing that I've noticed is that both >> GTInspactor and EyeInspector support custom inspections for objects. I'm >> wandering if we can come up with a common protocol to give an object >> specific infector view, and not develop a separate thing for each inspector. >> > >> > Uko >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

March 8, 2014

Smalltalk tools: explore failing in 3.0

by phil＠highoctane.be

If I do inspect Smalltalk tools it works. But explore crashes. How is that? Phil

March 8, 2014

Re: [Pharo-dev] About inspectors

by Tudor Girba

I hope not. What are we trying to optimize? If you look closely at the GT work, you might notice that it is not just a tool, it's a whole new philosophy for coding. The EyeInspector picked only one aspect out of a whole. One high goal is to change programming such that the inspector + debugger to capture most of the coding experience. This is what live means. Right now, in the default Pharo we only code small things in the debugger and nothing in the inspector. We work on the idea of a moldable IDE that will change all that. Let's look at some facts. Right now, in my image I have 75 different extensions for GTInspector. And the total amount of lines of code has barely passed 1000 LOC (including all utility code). These are not just independent views, but they are combinable. The amount of use cases supported span a wide range: querying source code, visualizing performance, navigating file system, querying DB, and more (read the posts from humane-assessment.com for hints in this direction). We programmed most of these extensions from within the inspector both because it's fun and because it's significantly more productive. And I am not the only one. This power is not serendipity, it's by design. And we only started to untap this potential. There is still a long way for the concept of inspector and I believe there is a large payoff in it, too. Optimizing for a small thing now should not be the way to go :) Cheers, Doru On Fri, Mar 7, 2014 at 11:23 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Well I would hope that some kind of convergence would be possible in the > future. Maybe some kind of abstract meta description like magritte, that > different tools can use. > > On 07 Mar 2014, at 16:43, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > Hi everyone. > > > > This day I've attended Moose dojo and I'm pretty impressed with the > possibilities of GTInspector. The one thing that I've noticed is that both > GTInspactor and EyeInspector support custom inspections for objects. I'm > wandering if we can come up with a common protocol to give an object > specific infector view, and not develop a separate thing for each inspector. > > > > Uko > > > -- www.tudorgirba.com "Every thing has its own flow"

March 8, 2014

Pharo3.0 and Halos: very annoying to work with

by phil＠highoctane.be

I am working on moving TWM to 3.0 and the way morphs are controlled now is really annoying. Now, we get the new menu when doing the special clicking (e.g. Shift-Alt-Click in Windows, Cmd-Shift Click in OSX). How is one now supposed to be accessing the internal morphs by clicking multiple times and having the halo follow suit? The menu prevents that as it gets in the way. Thanks. Phil

March 8, 2014