- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GTInspector auto refresh hooks?

by Denis Kudriashov

Actually I found trick: composite fastTable title: 'Devices'; display: [ devices ]; wantsAutomaticRefresh: true; *when: GLMPresentationRefreshRequest do: [myModel update].* Event handler can be executed after actual view update because announcer do not ensure delivering order. But in that case new value will be shown at next refresh which should be fine. What you thing? 2017-08-09 13:47 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > Hi Denis, > > The current update mechanism in the inspector is very light, in the sense > that it only updates the visual representation of elements and does not > recompute them, nor offers any hooks into the update process. > Indeed having a way to also recompute the display elements could be > useful. We could change the update mechanism to add different kind of > update strategies. > > Cheers, > Andrei > > On Wed, Aug 9, 2017 at 10:58 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> Hi. >> >> Is there a way in GTInspector presentation to call some special updating >> block before each of auto refresh operation? >> >> I want something like: >> >> composite fastTable >> title: 'Devices'; >> display: [ devices ]; >> wantsAutomaticRefresh: true; >> >> * beforeUpdateDo: ["rows updating code"]* >> >> Imaging my presentation shows database table and I want query updated >> rows. >> >> (I activate updating by GTInspector setEnabledStepRefreshStatus: true). >> >> Best regards, >> Denis >> > >

Aug. 9, 2017

Re: [Pharo-dev] GTInspector auto refresh hooks?

by Andrei Chis

Hi Denis, The current update mechanism in the inspector is very light, in the sense that it only updates the visual representation of elements and does not recompute them, nor offers any hooks into the update process. Indeed having a way to also recompute the display elements could be useful. We could change the update mechanism to add different kind of update strategies. Cheers, Andrei On Wed, Aug 9, 2017 at 10:58 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > Is there a way in GTInspector presentation to call some special updating > block before each of auto refresh operation? > > I want something like: > > composite fastTable > title: 'Devices'; > display: [ devices ]; > wantsAutomaticRefresh: true; > > * beforeUpdateDo: ["rows updating code"]* > > Imaging my presentation shows database table and I want query updated rows. > > (I activate updating by GTInspector setEnabledStepRefreshStatus: true). > > Best regards, > Denis >

Aug. 9, 2017

Re: [Pharo-dev] Pull requests ready to be reviewed

by Alistair Grant

On Wed, Aug 09, 2017 at 12:20:17PM +0200, Guillermo Polito wrote: > On Wed, Aug 9, 2017 at 11:09 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > We have several pull requests validated successfully by the infrastructure. > They need to be reviewed by humans: > > https://github.com/pharo-project/pharo/pull/75 > > > This one has a merge coflict. This is also the subject of a current discussion, see subject "FileSystem fix integration" Cheers, Alistair > https://github.com/pharo-project/pharo/pull/66 > > > I made a little review there :) > > > > > https://github.com/pharo-project/pharo/pull/175 > > https://github.com/pharo-project/pharo/pull/172 > > https://github.com/pharo-project/pharo/pull/169 > > https://github.com/pharo-project/pharo/pull/168 > > https://github.com/pharo-project/pharo/pull/134

Aug. 9, 2017

Re: [Pharo-dev] Pull requests ready to be reviewed

by Guillermo Polito

On Wed, Aug 9, 2017 at 11:09 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > We have several pull requests validated successfully by the > infrastructure. They need to be reviewed by humans: > > https://github.com/pharo-project/pharo/pull/75 > This one has a merge coflict. > > > https://github.com/pharo-project/pharo/pull/66 > I made a little review there :) > > > https://github.com/pharo-project/pharo/pull/175 > > https://github.com/pharo-project/pharo/pull/172 > > https://github.com/pharo-project/pharo/pull/169 > > https://github.com/pharo-project/pharo/pull/168 > > https://github.com/pharo-project/pharo/pull/134 > > Cheers, > -- Pavel > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 9, 2017

Pull requests ready to be reviewed

by Pavel Krivanek

We have several pull requests validated successfully by the infrastructure. They need to be reviewed by humans: https://github.com/pharo-project/pharo/pull/75 https://github.com/pharo-project/pharo/pull/66 https://github.com/pharo-project/pharo/pull/175 https://github.com/pharo-project/pharo/pull/172 https://github.com/pharo-project/pharo/pull/169 https://github.com/pharo-project/pharo/pull/168 https://github.com/pharo-project/pharo/pull/134 Cheers, -- Pavel

Aug. 9, 2017

GTInspector auto refresh hooks?

by Denis Kudriashov

Hi. Is there a way in GTInspector presentation to call some special updating block before each of auto refresh operation? I want something like: composite fastTable title: 'Devices'; display: [ devices ]; wantsAutomaticRefresh: true; * beforeUpdateDo: ["rows updating code"]* Imaging my presentation shows database table and I want query updated rows. (I activate updating by GTInspector setEnabledStepRefreshStatus: true). Best regards, Denis

Aug. 9, 2017

Re: [Pharo-dev] FileSystem fix integration

by Denis Kudriashov

Hi 2017-08-09 8:47 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > Hi Stef, > > On Tue, Aug 08, 2017 at 07:00:04PM +0200, Stephane Ducasse wrote: > > Hi Alistair > > > > I'm going over the green build first. > > > > - Then also https://pharo.fogbugz.com/f/cases/18042/FileSystem-a-file- > doesn-t-exist-but-still-exists > > I read it but do you suggest to drop it and close it? > > I don't think this issue should be dropped, there is a regular stream of > questions to the mailing list from newcomers getting confused by the > current behaviour. > > There are basically two opposing proposals: > > 1. Modify FileReference>>/ to accept a path and parse it correctly > (which is what I proposed). > 2. Modify FileReference>>/ to explicitly reject an argument which > includes the path delimiter (and it should suggest using #resolve:). > > The first proposal is more "practical", and the second is more "pure", > keeping the to original design goals and abstractions. > > Both have had multiple people support them, and both are better than the > current situation, however it is subjective as to which of the two > proposals is better. > I would vote for first solution > > I'm not sure what the normal tie-breaking process is, but I'm happy to > defer to the Pharo Association (Esteban? / Marcus? / yourself?). > > Cheers, > Alistair > >

Aug. 9, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Cyril Ferlicot

On Wed, Aug 9, 2017 at 9:33 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > yes, the keys may be an issue, but the standard rsa generated key should > work. We need to do a pass in security/credentials system (and probably a > revamp of some parts), but I still didnât find the time. > about the 255 limitation, if you execute this in command line: > > git config --system core.longpaths true > I already did it but I still get the problem :( > it should also fix the problem with pharo repo. > > Esteban > > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 9, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Esteban Lorenzano

> On 8 Aug 2017, at 23:47, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 08/08/2017 Ã 23:40, Nicolai Hess a Ã©crit : >> Thanks for the info, cyril. >> >> What do you use for the ssh username in pharo setting and what username >> did you use for creating the ssh-key ? >> I tried both, my github-email and my github-username, I didn't get it to >> work. >> > > I did not use anything special. While creating the ssh key I used all > the default options and in the setting I do not change the username (see > joined screenshot). > > This is the command I probably used since I followed github tutorial[1]: > > ssh-keygen -t rsa -b 4096 -C "cyril.ferlicot(a)gmail.com" > > [1] https://help.github.com/articles/connecting-to-github-with-ssh/ <https://help.github.com/articles/connecting-to-github-with-ssh/> yes, the keys may be an issue, but the standard rsa generated key should work. We need to do a pass in security/credentials system (and probably a revamp of some parts), but I still didnât find the time. about the 255 limitation, if you execute this in command line: git config --system core.longpaths true it should also fix the problem with pharo repo. Esteban > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France > <PharoScreenshot.png>

Aug. 9, 2017

Re: [Pharo-dev] FileSystem fix integration

by Alistair Grant

Hi Stef, On Tue, Aug 08, 2017 at 07:00:04PM +0200, Stephane Ducasse wrote: > Hi Alistair > > I'm going over the green build first. > > - Then also https://pharo.fogbugz.com/f/cases/18042/FileSystem-a-file-doesn-t-exist-but… > I read it but do you suggest to drop it and close it? I don't think this issue should be dropped, there is a regular stream of questions to the mailing list from newcomers getting confused by the current behaviour. There are basically two opposing proposals: 1. Modify FileReference>>/ to accept a path and parse it correctly (which is what I proposed). 2. Modify FileReference>>/ to explicitly reject an argument which includes the path delimiter (and it should suggest using #resolve:). The first proposal is more "practical", and the second is more "pure", keeping the to original design goals and abstractions. Both have had multiple people support them, and both are better than the current situation, however it is subjective as to which of the two proposals is better. I'm not sure what the normal tie-breaking process is, but I'm happy to defer to the Pharo Association (Esteban? / Marcus? / yourself?). Cheers, Alistair

Aug. 9, 2017