October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] 12 issues tagged for the spring Friday

by Benjamin

Cool :P Ben On Oct 16, 2013, at 4:51 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > I tagged 12 issues that should be quite nice to be done Friday: > (tag sprint, non closed): > > https://pharo.fogbugz.com/f/filters/?sColumns=Category-Favorite-Case-TitleC… > > > Marcus

Oct. 16, 2013

Re: [Pharo-dev] Color is strange

by Benjamin

put a halt XD Ben On Oct 16, 2013, at 4:49 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I wonder if this is me that miss something importantâ¦ but here is what I did: > > Color>>printOn: aStream > | name | > Transcript show:'x'. > (name := self name) ifNotNil: > [ ^ aStream > nextPutAll: 'Color '; > nextPutAll: name ]. > self storeOn: aStream > > > then I type > > 1 makeAnError and execute it. > > and in the transcript I get > xxxxxxxxxxxxxxxxxxxxxSmallInteger > > I'm totally puzzled why would we printOn: color ? before even opening a browser. > > stef

Oct. 16, 2013

12 issues tagged for the spring Friday

by Marcus Denker

Hi, I tagged 12 issues that should be quite nice to be done Friday: (tag sprint, non closed): https://pharo.fogbugz.com/f/filters/?sColumns=Category-Favorite-Case-TitleC… Marcus

Oct. 16, 2013

Color is strange

by StÃ©phane Ducasse

Hi guys I wonder if this is me that miss something importantâ¦ but here is what I did: Color>>printOn: aStream | name | Transcript show:'x'. (name := self name) ifNotNil: [ ^ aStream nextPutAll: 'Color '; nextPutAll: name ]. self storeOn: aStream then I type 1 makeAnError and execute it. and in the transcript I get xxxxxxxxxxxxxxxxxxxxxSmallInteger I'm totally puzzled why would we printOn: color ? before even opening a browser. stef

Oct. 16, 2013

Re: [Pharo-dev] Old Compiler is now unload able!

by Sven Van Caekenberghe

+10 On 16 Oct 2013, at 13:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Well said! > > Stef > > On Oct 16, 2013, at 12:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> This is amazing work! Thank you! >> >> I am an outsider in this topic, but I would kindly ask everyone to take a moment and consider the achievement. >> >> This is the first important sign of a long, tedious and highly undervalued work towards a goal set essentially from the very beginning of Pharo. It might not appear glamorous, but it certainly is a cornerstone. >> >> It is precisely this type of work that places Pharo in a land of its own. >> >> Doru >> >> >> >> On Wed, Oct 16, 2013 at 12:05 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> This opens a wide range of improvements. The future will be bright :). >> Thanks clement, camillo and marcus for this effort. >> Opal + slots will be really sexy. >> >> Stef >> >> > Bravo! >> > >> > Thierry >> > >> > Le 16/10/2013 11:15, Marcus Denker a Ã©crit : >> >> Hi, >> >> >> >> You can now do: >> >> >> >> ScriptLoader new unloadPackageNamed: 'CompilerTests'. >> >> ScriptLoader new unloadPackageNamed: 'Compiler'. >> >> >> >> and the system continues to work. >> >> >> >> >> >> Marcus >> >> >> > >> > -- >> > Thierry Goubier >> > CEA list >> > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> > 91191 Gif sur Yvette Cedex >> > France >> > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > >> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >

Oct. 16, 2013

Re: [Pharo-dev] [Moose-dev] Re: [ann] system attraction view

by Alexandre Bergel

Does this make sense to you? I would like to have this as a student project for next semester Alexandre On Oct 16, 2013, at 11:27 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > It would be great to have a domain specific force based layout. > > For example, if you want to connect methods with their defining classes, and have many classes on screen. It is more important to have a strong repulsion between the classes, than having the methods of a class repulsing from methods from another class. > > Alexandre > > > On Oct 16, 2013, at 11:09 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> System Attraction is pretty, but slow due to the complexity of the force based layout. >> >> Doru >> >> >> On Wed, Oct 16, 2013 at 1:34 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> But very slow even on small examples ... >>> Do you use a magic trick to enhance the performance ? >> >> Not really. >> >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 16, 2013

Re: [Pharo-dev] default monospaced code font

by Igor Stasenko

On 16 October 2013 16:31, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 16 October 2013 13:11, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> >> >> Le 16/10/2013 11:50, Sven Van Caekenberghe a Ã©crit : >> >> >>> On 16 Oct 2013, at 10:20, Goubier Thierry <thierry.goubier(a)cea.fr> >>> wrote: >>> >>> Interesting display, Sven. >>>> >>>> My take on that: >>>> >>>> * Aesthetics: the system has two fonts, not one. -1 if I review a >>>> document with more than one font. >>>> >>> >>> In all documents, you have at least two fonts: body and headings, often >>> quotes, examples, listings, etc have an another font to make them stand >>> out. In the new approach, the idea is that monospaced fonts indicate code >>> (in browsers, debuggers, workspaces). It is a useful principle. >>> >> >> You're right. But nobody would dare write headings in a monospaced font >> :) unless for an art project. >> >> >> * Coherence / uniformity: A class name, a method selector has a >>>> different shape in the GUI (proportional) than in the code (monospaced). >>>> Are they different objects? Can I recognize my class name in the code >>>> without reading it? >>>> >>> >>> Syntax highlighting should take care of that I guess. >>> >> >> I don't think so. This is no by making the selector green that it will >> look more like the proportional version in the pane above. >> >> Kind of disrupting the uniformity of the underlying model, when I'm >> pushing for things like smart suggestions where the GUI understands the >> objects written in the code. >> >> >> I think that if the monospaced font is a point size smaller that the >>> main sans font (e.g. 12 and 11) the excessive width problem or visual shock >>> is much more manageable. In any case, I am giving it a try. >>> >> >> Probably. But then individual characters may become harder to read and >> distinguish... sort of compromising character readability to make space for >> the added whitespace inherent to the monospaced font. >> >> I'd be more impressed if the argument was helping me distinguish between >> | and l. >> >> usually, most of sans-serif fonts barely distinguish between following 3: > l I | > (capital i, low-case el, pipe) > > test word: Illiterate :) > I'l let you try, then :) >> >> Thierry >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> >> > > > -- > Best regards, > Igor Stasenko. > -- Best regards, Igor Stasenko.

Oct. 16, 2013

Re: [Pharo-dev] default monospaced code font

by Igor Stasenko

On 16 October 2013 13:11, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 16/10/2013 11:50, Sven Van Caekenberghe a Ã©crit : > > >> On 16 Oct 2013, at 10:20, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >> Interesting display, Sven. >>> >>> My take on that: >>> >>> * Aesthetics: the system has two fonts, not one. -1 if I review a >>> document with more than one font. >>> >> >> In all documents, you have at least two fonts: body and headings, often >> quotes, examples, listings, etc have an another font to make them stand >> out. In the new approach, the idea is that monospaced fonts indicate code >> (in browsers, debuggers, workspaces). It is a useful principle. >> > > You're right. But nobody would dare write headings in a monospaced font :) > unless for an art project. > > > * Coherence / uniformity: A class name, a method selector has a different >>> shape in the GUI (proportional) than in the code (monospaced). Are they >>> different objects? Can I recognize my class name in the code without >>> reading it? >>> >> >> Syntax highlighting should take care of that I guess. >> > > I don't think so. This is no by making the selector green that it will > look more like the proportional version in the pane above. > > Kind of disrupting the uniformity of the underlying model, when I'm > pushing for things like smart suggestions where the GUI understands the > objects written in the code. > > > I think that if the monospaced font is a point size smaller that the main >> sans font (e.g. 12 and 11) the excessive width problem or visual shock is >> much more manageable. In any case, I am giving it a try. >> > > Probably. But then individual characters may become harder to read and > distinguish... sort of compromising character readability to make space for > the added whitespace inherent to the monospaced font. > > I'd be more impressed if the argument was helping me distinguish between | > and l. > > usually, most of sans-serif fonts barely distinguish between following 3: l I | (capital i, low-case el, pipe) I'l let you try, then :) > > Thierry > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- Best regards, Igor Stasenko.

Oct. 16, 2013

Re: [Pharo-dev] [Moose-dev] [ann] system attraction view

by Alexandre Bergel

It would be great to have a domain specific force based layout. For example, if you want to connect methods with their defining classes, and have many classes on screen. It is more important to have a strong repulsion between the classes, than having the methods of a class repulsing from methods from another class. Alexandre On Oct 16, 2013, at 11:09 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > System Attraction is pretty, but slow due to the complexity of the force based layout. > > Doru > > > On Wed, Oct 16, 2013 at 1:34 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > But very slow even on small examples ... > > Do you use a magic trick to enhance the performance ? > > Not really. > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 16, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 16, 2013