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

Re: [Pharo-dev] GTInspector and huge arrays issue

by Tudor Girba

Because we wanted to be both fast and flexible. Doru On Thu, Dec 11, 2014 at 12:03 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > curious how come you guys did not use Spec ? > > On Thu, Dec 11, 2014 at 12:12 AM, Aliaksei Syrel <alex.syrel(a)gmail.com> > wrote: > >> Hi, >> >> Why the class you use is not available in Moose 5.0 ? >> >> There were some failing tests, so maybe new classes were not in the build >> (The latest is Glamour-Morphic-Brick.88) >> >> Brick more or less is nothing special. The main idea was to kill morphic >> layouting mechanism and reimplement it from scratch. Also drawing logic was >> changed, such that there is no way to draw outside of the parent Brick and >> to support z-index. But one of the most important feature for us was to >> have a normal support of paddings and margins (like in css). And all bounds >> are relative to the parent. >> >> Cheers, >> Alex >> >> On Wed, Dec 10, 2014 at 10:31 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> >>> I am very interested into Brick, because I am very interesting into >>> anything GUI and graphic wise and I want to push pharo forward in that >>> field with my own efforts as best I can. >>> >>> The scrolling of your examples is actually very smooth. >>> >>> Why the class you use is not available in Moose 5.0 ? Because a moose >>> 5.0 image I have downloaded recently with pharolauncher that it contains >>> GTSpotter yet it does not have the class you use here. >>> >>> On Wed, Dec 10, 2014 at 9:31 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> in case someone is still interested, a Glamour-Morphic-Brick (extension >>>> of morph, that was used to build a Spotter) >>>> supports a very large lists. You can try in the latest version: >>>> >>>> GLMScrollListBrick exampleCollection - to open a list of all classes >>>> in the image (each element in the list is a morph). >>>> GLMScrollListBrick example - list of 2000 elements >>>> GLMScrollListBrick exampleInfinity - list of Float infinity number of >>>> elements. >>>> >>>> if your pharo image is old: >>>> >>>>> Gofer new >>>>> smalltalkhubUser: 'Moose' project: 'Glamour'; >>>>> package: 'Glamour-Morphic-Brick'; load. >>>> >>>> >>>> Maybe we will use it instead of default lists in Inspector. >>>> >>>> Cheers, >>>> Alex >>>> >>>> >>>> On Thu, Dec 4, 2014 at 4:04 PM, Ben Coman <btc(a)openinworld.com> wrote: >>>> >>>>> Sven Van Caekenberghe wrote: >>>>> >>>>>> On 04 Dec 2014, at 11:45, phil(a)highoctane.be wrote: >>>>>>> >>>>>>> But further than that I want to edit values in inspectors. >>>>>>> >>>>>> >>>>>> Yes ! >>>>>> >>>>>> And auto refresh ! >>>>>> >>>>>> Both of these could be depending on presentation, so that heavy >>>>>> presentations can opt out. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> It would be good if there was some visual indication of which >>>>> presentations auto-refreshed - like a drop pin looking like its "stuck-in" >>>>> when not-auto-refreshing. A user might even be able to change the state of >>>>> the pin, with the just the default dependent on type of presentation. >>>>> cheers -ben >>>>> >>>>> >>>> >>> >> > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 11, 2014

Re: [Pharo-dev] GTInspector and huge arrays issue

by kilon alios

curious how come you guys did not use Spec ? On Thu, Dec 11, 2014 at 12:12 AM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi, > > Why the class you use is not available in Moose 5.0 ? > > There were some failing tests, so maybe new classes were not in the build > (The latest is Glamour-Morphic-Brick.88) > > Brick more or less is nothing special. The main idea was to kill morphic > layouting mechanism and reimplement it from scratch. Also drawing logic was > changed, such that there is no way to draw outside of the parent Brick and > to support z-index. But one of the most important feature for us was to > have a normal support of paddings and margins (like in css). And all bounds > are relative to the parent. > > Cheers, > Alex > > On Wed, Dec 10, 2014 at 10:31 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > >> I am very interested into Brick, because I am very interesting into >> anything GUI and graphic wise and I want to push pharo forward in that >> field with my own efforts as best I can. >> >> The scrolling of your examples is actually very smooth. >> >> Why the class you use is not available in Moose 5.0 ? Because a moose 5.0 >> image I have downloaded recently with pharolauncher that it contains >> GTSpotter yet it does not have the class you use here. >> >> On Wed, Dec 10, 2014 at 9:31 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> >> wrote: >> >>> Hi, >>> >>> in case someone is still interested, a Glamour-Morphic-Brick (extension >>> of morph, that was used to build a Spotter) >>> supports a very large lists. You can try in the latest version: >>> >>> GLMScrollListBrick exampleCollection - to open a list of all classes in >>> the image (each element in the list is a morph). >>> GLMScrollListBrick example - list of 2000 elements >>> GLMScrollListBrick exampleInfinity - list of Float infinity number of >>> elements. >>> >>> if your pharo image is old: >>> >>>> Gofer new >>>> smalltalkhubUser: 'Moose' project: 'Glamour'; >>>> package: 'Glamour-Morphic-Brick'; load. >>> >>> >>> Maybe we will use it instead of default lists in Inspector. >>> >>> Cheers, >>> Alex >>> >>> >>> On Thu, Dec 4, 2014 at 4:04 PM, Ben Coman <btc(a)openinworld.com> wrote: >>> >>>> Sven Van Caekenberghe wrote: >>>> >>>>> On 04 Dec 2014, at 11:45, phil(a)highoctane.be wrote: >>>>>> >>>>>> But further than that I want to edit values in inspectors. >>>>>> >>>>> >>>>> Yes ! >>>>> >>>>> And auto refresh ! >>>>> >>>>> Both of these could be depending on presentation, so that heavy >>>>> presentations can opt out. >>>>> >>>>> >>>>> >>>>> >>>>> >>>> It would be good if there was some visual indication of which >>>> presentations auto-refreshed - like a drop pin looking like its "stuck-in" >>>> when not-auto-refreshing. A user might even be able to change the state of >>>> the pin, with the just the default dependent on type of presentation. >>>> cheers -ben >>>> >>>> >>> >> >

Dec. 11, 2014

Re: [Pharo-dev] Spotter searching for do:separatedBy:

by Sven Van Caekenberghe

hmm, I just updated to 40410 (just one more) and now it works, sorry for the noise. > On 11 Dec 2014, at 11:05, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > I'm just pressing âdo:sâ and I have the resultsâ¦ > > > <Screen Shot 2014-12-11 at 11.05.30.png> > > Esteban > >> On 11 Dec 2014, at 10:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> I can't search for do:separatedBy: using Spotter, with or without a space. >> This seems to be the case for all keyword message with more than 1 argument. >> The previous search tool (shift+Enter) had no problem with this. >> Or maybe I am doing something wrong. >> >

Dec. 11, 2014

Re: [Pharo-dev] Spotter searching for do:separatedBy:

by Esteban Lorenzano

I'm just pressing âdo:sâ and I have the resultsâ¦ Esteban > On 11 Dec 2014, at 10:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I can't search for do:separatedBy: using Spotter, with or without a space. > This seems to be the case for all keyword message with more than 1 argument. > The previous search tool (shift+Enter) had no problem with this. > Or maybe I am doing something wrong. >

Dec. 11, 2014

Spotter searching for do:separatedBy:

by Sven Van Caekenberghe

I can't search for do:separatedBy: using Spotter, with or without a space. This seems to be the case for all keyword message with more than 1 argument. The previous search tool (shift+Enter) had no problem with this. Or maybe I am doing something wrong.

Dec. 11, 2014

servers maintenance

by Christophe Demarey

Hi, We will need to do some maintenance to Pharo servers this afternoon. It includes smalltalkhub, and all pharo-related web sites. That is likely that you may observe short downtimes. Regards, Esteban and Christophe.

Dec. 11, 2014

Re: [Pharo-dev] GTInspector and huge arrays issue

by Torsten Bergmann

Spotter is cool! I guess the days of Spotlight will now be count. I especially like the search for pragmas, one can easily find the #spotterOrder: examples. When spotting directories is it possible to dive into the contents? Aliaksei Syrel wrote: >and all bounds are relative to the parent. Mmmhh...would like to see this for all Morphic. If I understood correctly Cuis changed this already for existing Morphic - still dont know how much effort it would mean for Pharo. BTW: the brick list does not react to PAGE-DOWN, PAGE-UP like the regular lists Bye T.

Dec. 11, 2014

Re: [Pharo-dev] spotter and exact matches

by Aliaksei Syrel

Hi Norbert, right now it's only possible to find it like: - type on: - then dive in category implementors CMD+Shift+Right - search for #on: btw, for "do:" it finds instantly you are right it would be nice to have weighted results Cheers, Alex On Wed, Dec 10, 2014 at 11:46 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Is it possible to show exact matches in spotter first? Typing something > like "on:" does not bring up a single on: selector and there is no way to > specialize more by typing more. So I think it would be good if they would > come first. > > Norbert > > >

Dec. 10, 2014

spotter and exact matches

by Norbert Hartl

Is it possible to show exact matches in spotter first? Typing something like "on:" does not bring up a single on: selector and there is no way to specialize more by typing more. So I think it would be good if they would come first. Norbert

Dec. 10, 2014

Re: [Pharo-dev] Short AltBrowser end-user test

by kilon alios

I used Eclipse when I was coding python a lot, never missed it . Kinda strange that Pharo (and Squeak) being so unfamiliar to me felt like home right from the start. Its not what you are used to but what you want to use ;) On Wed, Dec 10, 2014 at 6:12 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2014-12-10 16:17 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> > On 10 Dec 2014, at 10:57, Thierry Goubier <thierry.goubier(a)gmail.com> >> wrote: >> > >> > Hi All, >> > >> > I setup a small experiment for a group of students, when teaching them >> a lab about process networks programming with Pharo and Roassal. Students >> were some used to Smalltalk (VisualWorks), some with no knowledge of >> Smalltalk, level is M2. >> > >> > I changed the default Browser to AltBrowser instead of >> PackageTreeNautilus. I gave no explanation about how to use it. Students >> had a four hours lab, and are supposed to hand out a package with a few >> methods containing scripts. I showed them how to save a pre-existing >> package. >> > >> > - There was no question at all about the browser. And when asked, they >> felt there was no need for explanations on it. >> > >> > - They are not using it the way I expected (and the way I designed it >> for). They were using it like an 'eclipse' type of IDE (a single, very >> large window showing both the list of examples and the place they were >> working on). >> >> I donât know why are you so surprisedâ¦ eclipse is what they know, so >> obviously they will use it like it :P >> > > In hindsight, it is obvious. But I haven't used Eclipse for ages :) Never, > really. > > It got me thinking, still. I'm not sure they understood that it behaved > like one method / one file. And not a single file contains many methods and > you can edit in multiple places before saving the whole. > > Thierry > >

Dec. 10, 2014