Re: [Pharo-users] GTInspect auto-update in raw view?

Hello Esteban, You can enable auto-refresh with: GTInspector enableStepRefresh For performance reasons it is disabled by default. If you are curious why I think Andrei could explain a bit more :) Cheers, Alex On 17 August 2017 at 00:56, Esteban A. Maringolo wrote: > Hi

[Pharo-users] GTInspect auto-update in raw view?

Hi all, Is there a way to enable the auto-update of instance variables display in the GTInspector? There are cases where the instance is nil, I then initialize it somehow, but the variable is still displayed as nil. I know there is an "Update" button, which BTW should be labeled "refresh"

[Pharo-users] Parser failure on FFI pragmas declaration in Pharo 5

Hi, I stumbled upon what seems to me a strange issue in Pharo 5. The RBParser fails to correctly parse the legacy FFI pragmas. This completely breaks down the browser, the inspector and debugger (because as far as I understand all use RBParser to correctly highlight syntax). I had the image

Re: [Pharo-users] How to find where pharo is killing processor power?

Are you using VNC ? > On 16 Aug 2017, at 21:03, sergio ruiz wrote: > > > hey all.. my current pharo implementation is running super serious processor > power, but it shouldn’t be doing much. > > > > how would I go about tracking this inside the pharo image? > >

Re: [Pharo-users] Encoding Login information in your image (safely)

Todd, i think you are right, I can't get around it - I need to pass something from my live environment (where it's kept encrypted) into my image. I can however potentially simplify the setup by passing a single key that I can use to unlock a PasswordVault in my image and it can have multiple

[Pharo-users] How to find where pharo is killing processor power?

hey all.. my current pharo implementation is running super serious processor power, but it shouldn’t be doing much. how would I go about tracking this inside the pharo image? Thanks! peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage 

Re: [Pharo-users] Encoding Login information in your image (safely)

I do a lot of deployments on AWS elastic beanstalks. I put the credentials into environment variables on the beanstalk. When running locally, the credentials are in the environment on my machine. > On Aug 16, 2017, at 9:55 AM, Tim Mackinnon wrote: > > Hi - I’m struggling to

Re: [Pharo-users] Encoding Login information in your image (safely)

Apologies for top quoting; there isn't any single place which seemed appropriate. A colleague of mine who worked for a Swiss bank (they take security seriously) addressed this by NOT keeping the credentials in the image. 1. Set up a distinct user intended solely for running the application. 2.

Re: [Pharo-users] What is proper fix for this?

Am 16.08.17 um 19:33 schrieb Esteban Lorenzano: is asking for, I encourage to keep discussion also here, then solution can hit both platforms. No complains about having the discussion on both groups in parallel ;-) I just don't like the idea of private fixes to Glorp on any of the

Re: [Pharo-users] What is proper fix for this?

> On 16 Aug 2017, at 19:29, "jtuc...@objektfabrik.de" > wrote: > >> Am 16.08.17 um 18:08 schrieb Esteban Lorenzano: >> but if he is using Glorp for Pharo and cincom takes the bug and fixes it, it >> still will not hit Pharo until someone ports it. > > OTOH: if

Re: [Pharo-users] What is proper fix for this? (was: Re: Big Glorp problem w/ type coercion, pls help)

Herby, Please apologize I can't take the time to look into your code. I granted you write access to , could you upload your latter version to it? Regards! Esteban A. Maringolo 2017-08-15 19:07 GMT-03:00 : > BTW I took the latter

Re: [Pharo-users] What is proper fix for this?

Am 16.08.17 um 18:08 schrieb Esteban Lorenzano: but if he is using Glorp for Pharo and cincom takes the bug and fixes it, it still will not hit Pharo until someone ports it. OTOH: if nobody at Cincom reads about it, chances are you do a complete fork of Glorp for Pharo. Not sure I like that

Re: [Pharo-users] Encoding Login information in your image (safely)

2017-08-16 13:55 GMT-03:00 Tim Mackinnon : > ./pharo Pharo.image eval "(ByteString allInstances)” > > I think you would ulimtately find those strings unless the Class encrypts > them in some way right? > > So I’m wondering why we don’t have an EncryptedString object for just this

[Pharo-users] Encoding Login information in your image (safely)

Hi - I’m struggling to find something that I saw that discussed this issue kind of. In my image (its actually a headless one - but this could apply to a fat image too) - I build an application that needs access to a service (in this case an S3 bucket). The AWS library I’m using (but others

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

ok, thanks, is there a difference in the 32 and 64 bit vm behaviour? it seemed to me they both had this error, but I am a byte confused now. Anyway, for the time being it is not a problem to continue with Pharo 5.0. TedvG > On 16. Aug 2017, at 18:25, EstebanLM [via Smalltalk] >

Re: [Pharo-users] What is proper fix for this? (was: Re: Big Glorp problem w/ type coercion, pls help)

Herby Vojčík wrote: Esteban Lorenzano wrote: but if he is using Glorp for Pharo and cincom takes the bug and fixes it, it still will not hit Pharo until someone ports it. So, while I have literally no idea of what Herby is asking for, I encourage to keep discussion also here, then solution can

Re: [Pharo-users] What is proper fix for this? (was: Re: Big Glorp problem w/ type coercion, pls help)

Esteban Lorenzano wrote: but if he is using Glorp for Pharo and cincom takes the bug and fixes it, it still will not hit Pharo until someone ports it. So, while I have literally no idea of what Herby is asking for, I encourage to keep discussion also here, then solution can hit both platforms.

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

> On 16 Aug 2017, at 16:55, Stephan Eggermont wrote: > > Please try starting your Pharo image with a new squeak vm. I remember Tobias > posting something on a full screen bug fix about a year ago, and don't know > what happened with it. It was around the same time as his

Re: [Pharo-users] What is proper fix for this? (was: Re: Big Glorp problem w/ type coercion, pls help)

but if he is using Glorp for Pharo and cincom takes the bug and fixes it, it still will not hit Pharo until someone ports it. So, while I have literally no idea of what Herby is asking for, I encourage to keep discussion also here, then solution can hit both platforms. Esteban > On 16 Aug

Re: [Pharo-users] [Ann] Blog entry about using Pharo / Smalltalk to build a bot

nice! thanks :) > On 15 Aug 2017, at 20:23, sergio ruiz wrote: > > Hey, all.. > > I just released a blog entry entitled: > > "Why I chose Pharo Smalltalk to build my Bot project" > > which can be viewed here: > >

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

Please try starting your Pharo image with a new squeak vm. I remember Tobias posting something on a full screen bug fix about a year ago, and don't know what happened with it. It was around the same time as his hiDPI fix, which triggered some garbage collection issue at the time. Some part of

Re: [Pharo-users] YAML parser (2017)

Are there any news about a YAML parser for Pharo 5 / 6.1? --Hannes On 5/29/17, Peter Uhnak wrote: > Hi, > > do we have a working parser for YAML? > > There's PPYAMLGrammar (in PetitParser), however it doesn't seem to work in > Pharo 6 at all (not even tests pass). > In Pharo

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

Aha! similar here! Didn't do that before: resizing after freezing. So almost sure it has to do with resizing only? 1: after maximizing to full screen parts are not redrawn but still can drag windows around: 2: then after coming back

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

Actually this reminds me of a similar problem I’ve seen on my MacBook Pro (retina) - if I stretch the desktop to try and use the full space of the screen (not maximising it) I have on occasion frozen - however its not actually frozen it seems that drawing on screen has stopped, and if I resize

[Pharo-users] Preference to for not showing hidden files in the FileBrowser?

Hello Is there a preference for not showing hidden files in the FileBrowser? I checked menu 'System' -> 'Settings' searching for 'hidden'. This is on Ubuntu, i.e. hidden files start with a dot. Thank you for the answer in advance Hannes

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

here's a screenshot. notice the white band in the content area after maximizing the window. It freezed, can't move the inner windows anymore and ctrl '.' user interrupt doesn't work and have to force quit Pharo. No idea what happens but Pharo 5.0 runs as stable as ever. Kind Regards TedvG

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

On Wed, Aug 16, 2017 at 11:46 AM, Tim Mackinnon wrote: > Hi, tracing through your changes - it looks like: > > Smalltalk cleanUp: true except: #() confirming: false. > > Takes care of all the non-unicode changes you proposed (and it seems like > its a known cleanup protocol). >

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Hi, tracing through your changes - it looks like: Smalltalk cleanUp: true except: #() confirming: false. Takes care of all the non-unicode changes you proposed (and it seems like its a known cleanup protocol). I wonder if the Unicode change is worth it/risky as many web based services I might

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Yes - that is a fair warning - I guess I’m looking for ways to reset Monticello/metocello artefacts and caching (maybe I should ask Dale for some tips - as I find the Monticello/metacello packages quite big and difficult to follow, and there are no class comments to give you any pointers). I’m

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Be careful because some of those aggressive cleanups may turn some parts of your image unstable. For example: This is dangerous: MCMethodDefinition allInstances do: [:each | each become: String new ]. MCClassDefinition allInstances do: [:each | each become: String new ]. MCVersionInfo

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

This is very encouraging, and also very instructive (your post on snapshot is also one in this area too. I have a queue of things to try for you on Friday). I'll try adding your ideas to my script and see if it squeezes some more. And then I guess we need to to decide which parts go into your

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

This means it would be healthy to do a cleanup (at least the non aggressive one, ChangeSets and MC stuff) on each of the images we produce and not just the latest one. On Wed, Aug 16, 2017 at 8:35 AM, Tim Mackinnon wrote: > Yes you were on to something there (and at the same

Re: [Pharo-users] Glamour: update presenter with new text

Hi Hilaire, Sorry for the late reply. Indeed, it should be possible to do this, but we have to look closer at your concrete code. Here is an example: browser := GLMTabulator new. browser column: #one; column: #two. browser transmit to: #one; andShow: [ :a |

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Yes you were on to something there (and at the same time, by poking around with #pointersTo I noticed some chains of objects too). So I ran the following script (partially borrowed from ImageCleaner) and this has got me down to a 14mb image (instance sizes listed below, which is looking much