Re: [Pharo-dev] Epicea user experience report

I don't like the extra menu. I think going three levels in a menu should only be done for thing used rarely. Feels awkward very time. Do we have three cases wirh epicea? - this session meaning all changed since start of the image? - last session/aborted session the last session that did not

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Am 21.12.2016 8:10 vorm. schrieb "Alexandre Bergel" : I had plenty of elements in my Roassal visualization, and on some point it just crashed. I have the impression that having many elements and / or animations (as in the case of Johan Fabry) triggers the crash. One

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Just to make clear, I am using the latest VM on Mac OS X, El capitan, latest Pharo. The crashes I experienced are not new. My original email was not a complain (even if it may be perceived as one), but more to trigger a discussion. Peter did an excellent report of the current state of this

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

I had plenty of elements in my Roassal visualization, and on some point it just crashed. I have the impression that having many elements and / or animations (as in the case of Johan Fabry) triggers the crash. Alexandre > On Dec 20, 2016, at 9:12 AM, Stephane Ducasse

Re: [Pharo-dev] Epicea user experience report

Hi, I think I would prefer to not have to think about this choice at all when in the world menu level. The user interface from the Epicea window already allows me to switch between current session and all sessions, and usually the decision of what to look at is based on whether I find what I

Re: [Pharo-dev] a request to change the meaning of pragma

Stephane Ducasse-3 wrote > In nautilus in Pharo 60 when you use > > > you can get an inspector on the object returned by the > method Cool! Great feature :) - Cheers, Sean -- View this message in context:

Re: [Pharo-dev] About Fraction and parentheses

On Tue, 20 Dec 2016 09:24:57 +0100, Sven Van Caekenberghe wrote: Ah, OK, sorry about the misunderstanding. you are welcome :) Now I do not get why there would be ((1/3)) I have to check On 20 Dec 2016, at 09:21, Stephane Ducasse wrote: I think

Re: [Pharo-dev] Epicea user experience report

I like the second because it associates the name with the function. Stef Hi all, One point of Ben's feedback is how Epicea code changes tool is presented in the World Menu. Below you can see the current state + 3 options to discuss it. 1. "Epicea" main entry > "Session Changes" + "All

Re: [Pharo-dev] Epicea user experience report

Marcus Denker-4 wrote >> 3. Just "Code Changes" + rephrase children: > I like that most. It is the easiest to understand for newcomers. +1 - Cheers, Sean -- View this message in context: http://forum.world.st/Epicea-user-experience-report-tp4920653p4927604.html Sent from the Pharo

Re: [Pharo-dev] all black pharo 6.0 window on startup - unresponsive

#60332 is indeed working, thanks again! On 12/20/2016 10:19 AM, Dale Henrichs wrote: Thanks Marcus, I will download and try again... On 12/20/2016 10:17 AM, Marcus Denker wrote: Hi, This happend for 60330, but we have reverted and it should be working now again (e.g. with 60332) On 20 Dec

Re: [Pharo-dev] all black pharo 6.0 window on startup - unresponsive

Thanks Marcus, I will download and try again... On 12/20/2016 10:17 AM, Marcus Denker wrote: Hi, This happend for 60330, but we have reverted and it should be working now again (e.g. with 60332) On 20 Dec 2016, at 15:09, Dale Henrichs wrote: Running

Re: [Pharo-dev] all black pharo 6.0 window on startup - unresponsive

Hi, This happend for 60330, but we have reverted and it should be working now again (e.g. with 60332) > On 20 Dec 2016, at 15:09, Dale Henrichs > wrote: > > Running Ubuntu 14.04 and a fresh download (as of yesterday) when pharo comes > up I get an

[Pharo-dev] all black pharo 6.0 window on startup - unresponsive

Running Ubuntu 14.04 and a fresh download (as of yesterday) when pharo comes up I get an unresponsive and all black window -- I have to kill the process. I have an older download of pharo6.0 that works fine ... Both vms are the same version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3

Re: [Pharo-dev] Epicea user experience report

> > > 3. Just "Code Changes" + rephrase children: > > ​ > ​ > I like that most. It is the easiest to understand for newcomers. Marcus

Re: [Pharo-dev] Epicea user experience report

Hi all, One point of Ben's feedback is how Epicea code changes tool is presented in the World Menu. Below you can see the current state + 3 options to discuss it. 1. "Epicea" main entry > "Session Changes" + "All Changes" children [current state] 2. Attach purpose to the name: "Epicea Code

[Pharo-dev] [pharo-project/pharo-core] 86be50: 60332

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 86be50c96618776323023836fb3a36754b632cdd https://github.com/pharo-project/pharo-core/commit/86be50c96618776323023836fb3a36754b632cdd Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60332 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

FreeType crashes are different, and I do experience them ocassionally (unlike Roassal ones), but they should be discussed in another thread. Peter On Tue, Dec 20, 2016 at 12:46:30PM +0100, p...@highoctane.be wrote: > Clement told me that a number of these crashes have been solved eons ago in >

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

Clement told me that a number of these crashes have been solved eons ago in the opensmalltalkvm and that we are lagging behind with the integration of these things. I am a clueless n00b on what this was about, so, what is the exact status? I possibly face the same kind of issues in other areas

[Pharo-dev] [pharo-project/pharo-core] 37f27a: 60331

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 37f27a06b50b8c74abc810d24e3cf9d838dbc413 https://github.com/pharo-project/pharo-core/commit/37f27a06b50b8c74abc810d24e3cf9d838dbc413 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60331 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] About Fraction and parentheses

Ah, OK, sorry about the misunderstanding. > On 20 Dec 2016, at 09:21, Stephane Ducasse wrote: > > I think that I know that :) > And this is why I mentioned that if you print 1/3 it prints (1/3) so that we > can continue typing + (2/3) > > On Mon, Dec 19, 2016 at 11:02

Re: [Pharo-dev] About Fraction and parentheses

I think that I know that :) And this is why I mentioned that if you print 1/3 it prints (1/3) so that we can continue typing + (2/3) On Mon, Dec 19, 2016 at 11:02 PM, Sven Van Caekenberghe wrote: > > > On 19 Dec 2016, at 22:00, Stephane Ducasse > wrote: >

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

So what was your crash problem? On Tue, Dec 20, 2016 at 8:43 AM, Alexandre Bergel wrote: > > so did it work? > > Is there something that we should do? > > I had no problem, but as Henrik and Peter said, the problem is likely to > be more complex > > Alexandre > > > > >