May 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] can you give feedabck to alain on preference cleaning

by StÃ©phane Ducasse

fun this is the first thing I remove. Stef On May 21, 2009, at 8:55 PM, Igor Stasenko wrote: > annotation pane is very useful thing. This is first thing i turning > on, when start using new image. > > 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> http://code.google.com/p/pharo/issues/detail?id=810 >> Especially for the annotation panes in the old browser. >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 21, 2009

Re: [Pharo-project] call for hypercool fonts configuration

by Adrian Lienhard

On Mac, I like the following "special" configuration with Lucida Grande and Monaco: font := LogicalFont familyName: 'Lucida Grande' pointSize: 10. codeFont := LogicalFont familyName: 'Monaco' pointSize: 9. codeFont realFont instVarNamed: 'cachedAscent' put: 12. codeFont realFont instVarNamed: 'cachedHeight' put: 15. titleFont := LogicalFont familyName: 'Lucida Grande' pointSize: 10. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. Preferences setWindowTitleFontTo: titleFont. Note, I manually tweak the font description of Monaco to decrease the line height (don't know why it is that high by default). With the above, it looks more like in TextMate for example. Adrian On May 21, 2009, at 10:55 , Hilaire Fernandes wrote: > Yes, anythinks related to look'nd feel and overal design in Pharo > could help a lot to make people to LOVE Pharo or to RUN AWAY. > > Regarding fonts, I found myself sharing the point previously > expressed there: > -Dejavu Sans for all but code > -Code with Dedavu mono > > The issue about Freetype efficiency, related to submorph damage code > related previsouly, is of equal importance. > > If the user experience is ungood -- slowness -- people will RUN AWAY. > > > > > 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Hi guys >> >> on one hand we should have a good default for fonts - default means >> ok >> for license and >> work on platforms.... >> >> Now I would LOVE to get a list of cool combination of fonts even if >> they are proprietary. >> >> So I hope that I woke the designer in you :) >> Send snippets in the following forms that we can impress girls :) >> >> >> font := LogicalFont familyName: 'DejaVu Sans' pointSize: 10. >> codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. >> titleFont := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. >> >> Preferences setListFontTo: font. >> Preferences setMenuFontTo: font. >> Preferences setCodeFontTo: codeFont. >> Preferences setButtonFontTo: font. >> Preferences setSystemFontTo: font. >> Preferences setWindowTitleFontTo: titleFont. >> >> >> Stef >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 21, 2009

Re: [Pharo-project] About "external" pharo code

by Mariano Martinez Peck

On Thu, May 21, 2009 at 7:16 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > In this package would go stuff like the Morph classes you find in the > class categories MorphicExtras-* in the current Pharo-core image > (e.g., StarMorph). But is only Morphic related ? If so, we should use another name like PharoMorphicAddOns. If not, any other example ? Thanks! Mariano > > > Projects like OCompletion are not related to this. > > Adrian > > On May 21, 2009, at 22:02 , Mariano Martinez Peck wrote: > > > For me, the difficult thing is to differentiate between a Pharo > > addon or a > > project. What is a Pharo addon or what is a project? Most of this, > > no matter > > what they are, have their own squeaksource repository. > > > > Suppose OCompletion will be in Pharo image, is an addon or a project? > > > > In summary, it is not clear for me what should be in that package > > you are > > talking about and what is just a package that works on pharo. > > > > Best, > > > > Mariano > > > > On Thu, May 21, 2009 at 6:56 PM, Adrian Lienhard <adi(a)netstyle.ch> > > wrote: > > > >> Yes, an external package in a separate SqueakSource repository. > >> I would not call it "orphans" as it should contain nice demos of > >> Morphic to learn from (rather than the stuff we don't care about. > >> This > >> one can be deleted right away). Maybe PharoMorphicExamples or > >> PharoMorphicExtras. > >> > >> By extracting these from the image we also simplify the process of > >> evolving them as changes don't have to be integrated in the image. > >> > >> Adrian > >> > >> > >> On May 21, 2009, at 10:38 , StÃ©phane Ducasse wrote: > >> > >>> Hi guys > >>> > >>> I would like to have a discussion with you. > >>> What do we do with the code like the excellent PlotMorph that do not > >>> have its own > >>> package. > >>> > >>> Do we create a package for it? > >>> Do we create a PharoAddOnsOrphans? > >>> Ideally I would like that people can maintain improve such packages > >>> as well as the ones we may remove (ledMorph and others). > >>> > >>> Stef > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 21, 2009

Re: [Pharo-project] About "external" pharo code

by Adrian Lienhard

In this package would go stuff like the Morph classes you find in the class categories MorphicExtras-* in the current Pharo-core image (e.g., StarMorph). Projects like OCompletion are not related to this. Adrian On May 21, 2009, at 22:02 , Mariano Martinez Peck wrote: > For me, the difficult thing is to differentiate between a Pharo > addon or a > project. What is a Pharo addon or what is a project? Most of this, > no matter > what they are, have their own squeaksource repository. > > Suppose OCompletion will be in Pharo image, is an addon or a project? > > In summary, it is not clear for me what should be in that package > you are > talking about and what is just a package that works on pharo. > > Best, > > Mariano > > On Thu, May 21, 2009 at 6:56 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > >> Yes, an external package in a separate SqueakSource repository. >> I would not call it "orphans" as it should contain nice demos of >> Morphic to learn from (rather than the stuff we don't care about. >> This >> one can be deleted right away). Maybe PharoMorphicExamples or >> PharoMorphicExtras. >> >> By extracting these from the image we also simplify the process of >> evolving them as changes don't have to be integrated in the image. >> >> Adrian >> >> >> On May 21, 2009, at 10:38 , StÃ©phane Ducasse wrote: >> >>> Hi guys >>> >>> I would like to have a discussion with you. >>> What do we do with the code like the excellent PlotMorph that do not >>> have its own >>> package. >>> >>> Do we create a package for it? >>> Do we create a PharoAddOnsOrphans? >>> Ideally I would like that people can maintain improve such packages >>> as well as the ones we may remove (ledMorph and others). >>> >>> Stef >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 21, 2009

Re: [Pharo-project] About "external" pharo code

by Mariano Martinez Peck

For me, the difficult thing is to differentiate between a Pharo addon or a project. What is a Pharo addon or what is a project? Most of this, no matter what they are, have their own squeaksource repository. Suppose OCompletion will be in Pharo image, is an addon or a project? In summary, it is not clear for me what should be in that package you are talking about and what is just a package that works on pharo. Best, Mariano On Thu, May 21, 2009 at 6:56 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Yes, an external package in a separate SqueakSource repository. > I would not call it "orphans" as it should contain nice demos of > Morphic to learn from (rather than the stuff we don't care about. This > one can be deleted right away). Maybe PharoMorphicExamples or > PharoMorphicExtras. > > By extracting these from the image we also simplify the process of > evolving them as changes don't have to be integrated in the image. > > Adrian > > > On May 21, 2009, at 10:38 , StÃ©phane Ducasse wrote: > > > Hi guys > > > > I would like to have a discussion with you. > > What do we do with the code like the excellent PlotMorph that do not > > have its own > > package. > > > > Do we create a package for it? > > Do we create a PharoAddOnsOrphans? > > Ideally I would like that people can maintain improve such packages > > as well as the ones we may remove (ledMorph and others). > > > > Stef > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 21, 2009

Re: [Pharo-project] About "external" pharo code

by Adrian Lienhard

Yes, an external package in a separate SqueakSource repository. I would not call it "orphans" as it should contain nice demos of Morphic to learn from (rather than the stuff we don't care about. This one can be deleted right away). Maybe PharoMorphicExamples or PharoMorphicExtras. By extracting these from the image we also simplify the process of evolving them as changes don't have to be integrated in the image. Adrian On May 21, 2009, at 10:38 , StÃ©phane Ducasse wrote: > Hi guys > > I would like to have a discussion with you. > What do we do with the code like the excellent PlotMorph that do not > have its own > package. > > Do we create a package for it? > Do we create a PharoAddOnsOrphans? > Ideally I would like that people can maintain improve such packages > as well as the ones we may remove (ledMorph and others). > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 21, 2009

Re: [Pharo-project] can you give feedabck to alain on preference cleaning

by Igor Stasenko

annotation pane is very useful thing. This is first thing i turning on, when start using new image. 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > http://code.google.com/p/pharo/issues/detail?id=810 > Especially for the annotation panes in the old browser. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

May 21, 2009

Re: [Pharo-project] question for nicolas

by Nicolas Cellier

Yes please, just merge. The slice replaces ugly tests in Compiler by proper delegation using literalEqual: #literalEqual: is coming from NewCompiler and is already in Pharo, and already in new ScaledDecimal. We just have to plug this neat message in the Compiler. 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > hi nicolas > > is the slice in the pharo inbox still to be integrated? > Mantis6797- issue 803? > issue with scale decimal? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 21, 2009

Re: [Pharo-project] Pharo Software Distribution Agreement fax number

by Mariano Martinez Peck

Thanks! I think that adding this information into the pdf will be a good idea. People far away from Europe (as me) can be a bit lazy to send it by mail (not email) or by fax. Sending it by email is far much easy. Cheers, Mariano On Thu, May 21, 2009 at 4:14 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > sure > > Stef > > On May 21, 2009, at 4:24 PM, Mariano Martinez Peck wrote: > > > Can this be scanned and send it by email? > > > > On Thu, May 21, 2009 at 12:06 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr > > > wrote: > > 00 33 > > > > is international + france then 3.... > > > > stef > > On May 21, 2009, at 2:49 PM, Mariano Martinez Peck wrote: > > > > > Hi folks, > > > > > > simple question: the fax number it says in the > > > PharoSoftwareDistributionAgreement.pdf has included the country > > > code? I mean, I can call to it just as it is from any where in the > > > world ? > > > > > > Thanks! > > > > > > Mariano > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 21, 2009

Re: [Pharo-project] ThirtyTwoBitRegister methods removed

by StÃ©phane Ducasse

On May 21, 2009, at 3:10 PM, Mariano Martinez Peck wrote: > > > On Thu, May 21, 2009 at 6:51 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > If you need them for glorp copy them from Squeak and publish a new > package version working for Glorp in PharoInbox > I will push it in pharo > > Ok, I will do that. I am trying to see how the fax the license signed. > > However, it is not that I NEED it for Glorp. I mean, I can put it in > Glorp as an method extension with *Glorp and will work. But for me, > these two methods are ok to be in Pharo. sounds like so push them > > > Cheers, > > Mariano > > > On May 21, 2009, at 3:07 AM, Mariano Martinez Peck wrote: > > > I searched in Monticello for the package System-Digital Signatures > > and in the Pharo repository I only see two commits and even in the > > first one, these two methods are not there. But, they are in Squeak. > > So, know I guess where this commit should be? where I can search ? > > > > Thanks! > > > > Mariano > > > > On Mon, May 18, 2009 at 9:27 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > > > wrote: > > Hi folks. I noticed that this two methods were removed from > > ThirtyTwoBitRegister: > > > > asByteArray > > ^ ByteArray with: (low bitAnd: 16rFF) with: (low bitShift: > > -8) with: (hi bitAnd: 16rFF) with: (hi bitShift: -8) > > > > > > > > reverseLoadFrom: aByteArray at: index > > "Load my 32-bit value from the four bytes of the given > > ByteArraystarting at the given index. Consider the first byte to > > contain the mostsignificant bits of the word (i.e., use big-endian > > byte ordering)." > > > > hi := ((aByteArray at: index + 3) bitShift: 8) + > > ( aByteArray at: index + 2). > > low := ((aByteArray at: index + 1) bitShift: 8) + > > ( aByteArray at: index). > > > > > > > > I need them for Glorp. I looked but I didn't found a similar message > > for them. I don't think adding them as an extension is a good > > solution here since this seems to be very "internal". is there a > > reason of the removing? If not, could them be added again? If there > > are reason, which should be the best approach to fix this in mi > case? > > > > I have no problem in commit them if you want. > > > > Thanks! > > > > Mariano > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 21, 2009