Re: [Pharo-dev] [Moose-dev] Re: GanttChartMorph openOn: aCollectionOfActivities ?

You should load the latest Roassal. Alexandre > Le 9 mai 2015 à 19:06, H. Hirzel a écrit : > > Thank you for the examples, Alexandre! > > I have Pharo 4.0 with Roassal 2.0 installed (AlexandreBergel.718) > > I paste the following into a 'Playground' window and 'do it'. > > b := RTTimeLin

Re: [Pharo-dev] Error on loading GToolkit configuration

Thank you! 2015-05-10 12:44 GMT+02:00 Andrei Chis : > Made a small mistake in the configuration. > Should work now. > > Cheers, > Andrei > > On Sun, May 10, 2015 at 11:50 AM, Nicolai Hess wrote: > >> >> 15470 >> Replace Announcer>>#on:send:to:'s send

Re: [Pharo-dev] [Request]: Feed MetaRepoForXyz Configs Back to Projects

It seems very logical to require configs to be save into there own repos. The other locations should just be copies. > On 10 May 2015, at 18:45, Sean P. DeNigris wrote: > > For example, Soup's config was updated to declare a stable version for 4.0. > It was committed to MetaRepoForPharo40, but n

[Pharo-dev] [Request]: Feed MetaRepoForXyz Configs Back to Projects

For example, Soup's config was updated to declare a stable version for 4.0. It was committed to MetaRepoForPharo40, but not to PharoExtras/Soup. It was confusing that loading from the config browser worked, but loading via another config as a dependent project did not (since we use the canonical re

Re: [Pharo-dev] [Review]: Issue 13159: ListDialogWindow - Grow Width to Fit List

Nicolai Hess wrote > Does not work well in all situations... Thanks for the great review! Fix in inbox: SLICE-Issue-13159-ListDialogWindow---Grow-Width-to-Fit-List-SeanDeNigris.2 ### This version - Don't go smaller than the default size - Make sure fits in world, and it not occluded by docking too

Re: [Pharo-dev] Transcript needs your love

2015-05-10 13:23 GMT+02:00 stepharo : > Just so that I understand why Transcript does not support stream api > ThreadSafeTranscript implements the following selectors: > > #(#ensureCr #close #print: #white #openLabel: #characterLimit #'<<' > #initialize #title #printOn: #nextPutAll: #show: #shou

Re: [Pharo-dev] Transcript needs your love

2015-05-10 10:37 GMT+02:00 Esteban Lorenzano : > > On 10 May 2015, at 10:28, Clément Bera wrote: > > > > 2015-05-09 23:21 GMT+02:00 Tudor Girba : > >> I do not think there are many people around here that would think that it >> is irrelevant if the Pharo VM can be developed in Pharo or not. Of co

Re: [Pharo-dev] Transcript needs your love

> not that output is interleaved with a specific policy. Hi Eliot, I guess it was hard to analyse that output dump from your phone, and I should have been more explicit. The problem is not the interleave order, but duplicate and missing output items. I've cut down the example and and manually r

Re: [Pharo-dev] Transcript needs your love

Just so that I understand why Transcript does not support stream api ThreadSafeTranscript implements the following selectors: #(#ensureCr #close #print: #white #openLabel: #characterLimit #'<<' #initialize #title #printOn: #nextPutAll: #show: #shoutAboutToStyle: #cr #tab #black #initialExtent

Re: [Pharo-dev] Transcript needs your love

> On 10 May 2015, at 13:10, stepharo wrote: > > Why we cannot use the of Juan? > > > > Le 10/5/15 10:36, Esteban Lorenzano a écrit : >> +1 >> >> let’s recapitulate: >> >> requirement is >> - fast >> - editable > why do you need to edit it? you can type in it, make do it, etc. (just like

Re: [Pharo-dev] Transcript needs your love

Why we cannot use the of Juan? Le 10/5/15 10:36, Esteban Lorenzano a écrit : +1 let’s recapitulate: requirement is - fast - editable why do you need to edit it? - polymorphic with WriteStream - and immediate to screen from our perspective (pharo), it has to be also - thread safe - well de

Re: [Pharo-dev] Error on loading GToolkit configuration

Made a small mistake in the configuration. Should work now. Cheers, Andrei On Sun, May 10, 2015 at 11:50 AM, Nicolai Hess wrote: > > 15470 > Replace Announcer>>#on:send:to:'s senders in GTSpotter > > > Pharo5.0 > Latest update: #50040 > > > Anyone k

[Pharo-dev] Error on loading GToolkit configuration

15470 Replace Announcer>>#on:send:to:'s senders in GTSpotter Pharo5.0 Latest update: #50040 Anyone knows why this fails: Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; load; configurationOf: 'GTSpotter'; loadVersion:'1.2.4' ->

Re: [Pharo-dev] Transcript needs your love

On 5/10/15, Sven Van Caekenberghe wrote: > >> On 10 May 2015, at 10:36, Esteban Lorenzano wrote: >> >> +1 >> >> let’s recapitulate: >> >> requirement is >> - fast >> - editable >> - polymorphic with WriteStream >> - and immediate to screen >> from our perspective (pharo), it has to be also >> - t

Re: [Pharo-dev] Transcript needs your love

> On 10 May 2015, at 10:36, Esteban Lorenzano wrote: > > +1 > > let’s recapitulate: > > requirement is > - fast > - editable > - polymorphic with WriteStream > - and immediate to screen > from our perspective (pharo), it has to be also > - thread safe > - well designed. > > our constrai

Re: [Pharo-dev] Transcript needs your love

Hi Clément, Thanks for the detailed write up, this is surely helpful. I cannot react to all points, because some are out of my expertise. However, in this whole, very long thread, there is no one who ever said WHICH STREAM API IS MISSING ? It should be quite easy to add something, if only some

Re: [Pharo-dev] Transcript needs your love

> On 10 May 2015, at 10:22, stepharo wrote: > > > > Le 9/5/15 20:51, Sven Van Caekenberghe a écrit : >> Yes, the Cuis implementation is cool. Especially because it implements both >> the limited/circular buffer and timed/batched updating. > > I should finish my circular linkedList. > I will

Re: [Pharo-dev] Transcript needs your love

> On 10 May 2015, at 10:28, Clément Bera wrote: > > > > 2015-05-09 23:21 GMT+02:00 Tudor Girba >: > I do not think there are many people around here that would think that it is > irrelevant if the Pharo VM can be developed in Pharo or not. Of course, it is > imp

Re: [Pharo-dev] Transcript needs your love

+1 let’s recapitulate: requirement is - fast - editable - polymorphic with WriteStream - and immediate to screen from our perspective (pharo), it has to be also - thread safe - well designed. our constraints are: - bad design of transcripts - super naive implementation of text editors (t

Re: [Pharo-dev] Transcript needs your love

2015-05-09 23:21 GMT+02:00 Tudor Girba : > I do not think there are many people around here that would think that it > is irrelevant if the Pharo VM can be developed in Pharo or not. Of course, > it is important. > > So, the discussion should not go to challenge this direction, but rather > in you

Re: [Pharo-dev] Transcript needs your love

i think there is a fundamental difference between 'stream' and 'update on the screen' . Choose one and stick to it. We shall separate such responsibilities and NEVER ever merge them again , even if it was cool, nice, soft and puffy in the past. Yes, sure, we can then build the facade on top of t

Re: [Pharo-dev] Transcript needs your love

Le 9/5/15 20:51, Sven Van Caekenberghe a écrit : Yes, the Cuis implementation is cool. Especially because it implements both the limited/circular buffer and timed/batched updating. I should finish my circular linkedList. I will resume it. It does however mix different things in 1 class (s