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

Re: [Pharo-dev] Spotlight Demo

by Tudor Girba

Hi, I am not sure I understand. You tried to load Spotlight? And you got the error in Spotlight, or in any text? Cheers, Doru On Mon, Jan 6, 2014 at 4:47 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > I tried in latest 3.0 the example and I get a DNU > > error: 'Some code is setting text attributes length not matching the > string size']. > > when I remove character. > > stef > > On 06 Jan 2014, at 00:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi again, > > I added a first shot at theming. The idea is simple: > - we have one method in UITheme called spotterThemer that simply returns a > SpotterThemer, and > - all Spotter/Spotlight specific rendering methods are in SpotterThemer > > I think this should be the design to follow for all morphs. I blogged > about it in more details here: > > http://www.humane-assessment.com/blog/a-pharo-refactoring-story-adding-them… > > > You can get the code from here: > Gofer new > smalltalkhubUser: 'girba' project: 'GPlay'; > package: 'Spotlight'; > disablePackageCache; > load > > In summary, something like: > > SpotlightItemMorph>>onSelected > self color: (Color r: 0.2627 g: 0.4588 b: 0.9333). > > becomes: > > SpotlightItemMorph>>onSelected > self theme spotterThemer configureSelectedItemMorph: self > > And the default SpotterThemer says: > > SpotterThemer>>configureSelectedItemMorph: aMorph > aMorph color: (Color r: 0.2627 g: 0.4588 b: 0.9333) > > > What do you think? > > Cheers, > Doru > > > > > On Sun, Jan 5, 2014 at 9:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi Sean, >> >> I just tested it. It works just great. >> >> First, would it be Ok with you to move the project to a more public place >> (like http://www.smalltalkhub.com/#!/~PharoExtras) so that others can >> contribute easier? >> >> Second, I created a configuration with a development and stable version. >> You can find it here: >> Gofer new >> smalltalkhubUser: 'girba' project: 'GPlay'; >> package: 'ConfigurationOfSpotter'; >> load. >> (Smalltalk globals at: #ConfigurationOfSpotter) >> loadStable >> >> And in the MetaRepoForPharo30 so that you can load it from the >> Configuration Browser. Please note that I named the configuration Spotter, >> because there already exists a ConfigurationOfSpotlight for the widget of >> Esteban. Would it be Ok to change the name of the classes, too, to avoid >> confusion? >> >> Third, I think we should not mix the morph with the global shortcut. I >> understand this is convenient, but these should pretty much be different >> projects. Is that Ok with you? >> >> Fourth, I would like to theme this morph, too :). With this occasion, I >> would like to try a slightly different design for handling the theme code. >> I will follow up on this in another mail. >> >> Doru >> >> >> On Sat, Jan 4, 2014 at 5:42 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: >> >>> I'm happy for now. As a general purpose completion option, I'd say we're >>> officially at version 1.0. No obvious bugs, and provides the basic >>> features >>> I'd want. >>> >>> As for replacing the existing Spotlight, I've decided to eat my own dog >>> food >>> and use the new tool in my images: >>> *** n.b., if you load the Spotlight package now, it will override the >>> global Spotlight shortcut >>> >>> p.s. Steph, I added packages to the example for you ;) â¦ >>> < >>> http://forum.world.st/file/n4734153/Screen_Shot_2014-01-04_at_11.18.57_AM.p… >>> > >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: >>> http://forum.world.st/Spotlight-Demo-tp4733076p4734153.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 6, 2014

Re: [Pharo-dev] Browser focus issue?

by Benjamin

strange :) Ben On 06 Jan 2014, at 13:16, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > yeah, with the same result > > sounds like the keyboard events aren't observed so it won't react (mouse is ok) > > > > > > On Jan 6, 2014, at 1:41 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> did you try cmd+x, cmd+m >> >> Ben >> >> On 06 Jan 2014, at 08:39, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >> >>> Hi guys, >>> >>> I'm using the code browser and selecting methods and often I click select a method, lets say for refactoring, and press cmd-x and nothing happens. >>> >>> Sounds like a key events focus issue >>> >>> sebastian >>> >>> o/ >>> >>> >>> Pharo #30668 >>> >>> >> >

Jan. 6, 2014

Re: [Pharo-dev] Browser focus issue?

by Sebastian Sastre

yeah, with the same result sounds like the keyboard events aren't observed so it won't react (mouse is ok) On Jan 6, 2014, at 1:41 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > did you try cmd+x, cmd+m > > Ben > > On 06 Jan 2014, at 08:39, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> Hi guys, >> >> I'm using the code browser and selecting methods and often I click select a method, lets say for refactoring, and press cmd-x and nothing happens. >> >> Sounds like a key events focus issue >> >> sebastian >> >> o/ >> >> >> Pharo #30668 >> >> >

Jan. 6, 2014

Re: [Pharo-dev] Spotlight Demo

by StÃ©phane Ducasse

I tried in latest 3.0 the example and I get a DNU error: 'Some code is setting text attributes length not matching the string size']. when I remove character. stef On 06 Jan 2014, at 00:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi again, > > I added a first shot at theming. The idea is simple: > - we have one method in UITheme called spotterThemer that simply returns a SpotterThemer, and > - all Spotter/Spotlight specific rendering methods are in SpotterThemer > > I think this should be the design to follow for all morphs. I blogged about it in more details here: > http://www.humane-assessment.com/blog/a-pharo-refactoring-story-adding-them… > > > You can get the code from here: > Gofer new > smalltalkhubUser: 'girba' project: 'GPlay'; > package: 'Spotlight'; > disablePackageCache; > load > > In summary, something like: > > SpotlightItemMorph>>onSelected > self color: (Color r: 0.2627 g: 0.4588 b: 0.9333). > > becomes: > > SpotlightItemMorph>>onSelected > self theme spotterThemer configureSelectedItemMorph: self > > And the default SpotterThemer says: > > SpotterThemer>>configureSelectedItemMorph: aMorph > aMorph color: (Color r: 0.2627 g: 0.4588 b: 0.9333) > > > What do you think? > > Cheers, > Doru > > > > > On Sun, Jan 5, 2014 at 9:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Sean, > > I just tested it. It works just great. > > First, would it be Ok with you to move the project to a more public place (like http://www.smalltalkhub.com/#!/~PharoExtras) so that others can contribute easier? > > Second, I created a configuration with a development and stable version. You can find it here: > Gofer new > smalltalkhubUser: 'girba' project: 'GPlay'; > package: 'ConfigurationOfSpotter'; > load. > (Smalltalk globals at: #ConfigurationOfSpotter) > loadStable > > And in the MetaRepoForPharo30 so that you can load it from the Configuration Browser. Please note that I named the configuration Spotter, because there already exists a ConfigurationOfSpotlight for the widget of Esteban. Would it be Ok to change the name of the classes, too, to avoid confusion? > > Third, I think we should not mix the morph with the global shortcut. I understand this is convenient, but these should pretty much be different projects. Is that Ok with you? > > Fourth, I would like to theme this morph, too :). With this occasion, I would like to try a slightly different design for handling the theme code. I will follow up on this in another mail. > > Doru > > > On Sat, Jan 4, 2014 at 5:42 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I'm happy for now. As a general purpose completion option, I'd say we're > officially at version 1.0. No obvious bugs, and provides the basic features > I'd want. > > As for replacing the existing Spotlight, I've decided to eat my own dog food > and use the new tool in my images: > *** n.b., if you load the Spotlight package now, it will override the > global Spotlight shortcut > > p.s. Steph, I added packages to the example for you ;) â¦ > <http://forum.world.st/file/n4734153/Screen_Shot_2014-01-04_at_11.18.57_AM.p…> > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Spotlight-Demo-tp4733076p4734153.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Jan. 6, 2014

Re: [Pharo-dev] slice maker and dirty packages

by Marcus Denker

On 06 Jan 2014, at 16:42, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Take a fresh image, > Spec-Debugger is flagged as dirty. > > Select it and select Pharo-repo. > Ask for the changes, itâs not dirty anymore :P > The reason is a workaround that I integrated that made the package dirtyâ¦. (one of the two issues in the last update) This is known and needs a next update to re-load that package. (yes, ugly) Sadly I am busy today and will only have time tomorrow. > Ben > > On 06 Jan 2014, at 12:20, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> I have a freshly 30673 image. >> Made a change in package Nautilus. >> Create a new slice and Slice Maker marks package Spec-Debugger as dirty. >> But I don't have any changes in Spec-Debugger. >> >> >> >> >

Jan. 6, 2014

Re: [Pharo-dev] slice maker and dirty packages

by Benjamin

Take a fresh image, Spec-Debugger is flagged as dirty. Select it and select Pharo-repo. Ask for the changes, itâs not dirty anymore :P Ben On 06 Jan 2014, at 12:20, Nicolai Hess <nicolaihess(a)web.de> wrote: > I have a freshly 30673 image. > Made a change in package Nautilus. > Create a new slice and Slice Maker marks package Spec-Debugger as dirty. > But I don't have any changes in Spec-Debugger. > > > >

Jan. 6, 2014

Re: [Pharo-dev] Browser focus issue?

by Benjamin

did you try cmd+x, cmd+m Ben On 06 Jan 2014, at 08:39, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hi guys, > > I'm using the code browser and selecting methods and often I click select a method, lets say for refactoring, and press cmd-x and nothing happens. > > Sounds like a key events focus issue > > sebastian > > o/ > > > Pharo #30668 > >

Jan. 6, 2014

slice maker and dirty packages

by Nicolai Hess

I have a freshly 30673 image. Made a change in package Nautilus. Create a new slice and Slice Maker marks package Spec-Debugger as dirty. But I don't have any changes in Spec-Debugger.

Jan. 6, 2014

Re: [Pharo-dev] [Glass] printString and asString

by StÃ©phane Ducasse

+ 1 >>>> I need for example a string representation of objects generally to >>>> display in anchors in our seaside application. We have a class >>>> DomainObject from which most of our classes inherit, so this is >>>> probably the place to add a 'displayString' for something like this. >>> >>> Not necessarily domain objects only. >>> >>> Some core objects (Blocks, CompiledMethods, etc.) could benefit from >>> having a developer string representation (#printString) and a UI >>> string representation (#displayString). >> >> I don't really understand why. How would you distinguish between which >> (kinds of) core objects and which not? Will you not end up with a >> displayString on Object again? > > Yes, I want displayString on Object. > > What I don't like is #asString in Object. > > I want to be able to do: > Transcript show: anyObject displayString. > > Without getting a single quoted output if anyObject was a String. > > Regards.

Jan. 6, 2014

Two videos to explain what we do when integrating a fix.

by StÃ©phane Ducasse

Hi guys I produced two videos to show how simple is an integration now (It could be better see below). This can influence some of you to help us: sven, ben, igor :)? First one: install some scripts http://stephane.ducasse.free.fr/Videos/PharoIntegration/DownloadingScripts.… Second one http://stephane.ducasse.free.fr/Videos/PharoIntegration/integratingAChange.… ./prepare start menu merge 9look at the fixâ¦.) freeze menu publish menu ./publish I do not think that Monticello is the best tool for managing our changes and code (and I asked money in the past to get an engineer but it was refused and I spent the holiday building a new case to ask money to pay an engineer to get a real integration with Git) but for now this is what we have and it is working. I do not want that end users to get expose to git on the command-line with different platforms. We should keep the simplicity of Pharo. Stef

Jan. 6, 2014