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

Re: [Pharo-project] split/join

by Oscar Nierstrasz

Here it is: http://www.squeaksource.com/RubyShards.html - on On Mar 1, 2009, at 19:22, StÃ©phane Ducasse wrote: > I think that there was a split/join package somewhere. > Does anybody know where it is? > At one point it was planned to get added to squeak and nothing > happened. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 1, 2009

Re: [Pharo-project] changing default font

by Sebastian Sastre

Actually I was thinking simple :) I had in mind a well writen blog post with that script, talking how cool and fun the environment is with those and maybe mentioning why good UI helps do better software. Just that could be teasing about pharo to an outsider. Of course the a blog should be for branding and well indexed (a nice sitemap could do it). Better branding always help and it means valuable actions that sometimes are beyond the image ;) best, sebastian > -----Mensaje original----- > De: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] En > nombre de Michael Rueger > Enviado el: Sunday, March 01, 2009 15:43 > Para: Pharo-project(a)lists.gforge.inria.fr > Asunto: Re: [Pharo-project] changing default font > > Rob Rothwell wrote: > > And if you get tired of setting your fonts individually, > you can set > > them all at once: > > we should add something like that as font themes to the preferences? > > Michael > > > > > font := LogicalFont familyName: 'Andika Basic' pointSize: 10. > > codeFont := LogicalFont familyName: 'DejaVu Sans Mono' > pointSize: 9. > > Preferences setListFontTo: font. > > Preferences setMenuFontTo: font. > > Preferences setCodeFontTo: codeFont. > > Preferences setButtonFontTo: font. > > Preferences setSystemFontTo: font. > > font := LogicalFont familyName: 'Andika Basic' pointSize: 11. > > Preferences setWindowTitleFontTo: font. > > > > Just replace the font names with those of your choice! > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 1, 2009

Re: [Pharo-project] changing default font

by Rob Rothwell

Oh...I get it! What would be nice about Fonts (unlike window appearances), is that you could EASILY define your own custom themes as well, just by saving your current settings. Then you could save them somehow for re-use when the next version of the image came out! Again, this would be hard for many things, but easy for fonts! Rob On Sun, Mar 1, 2009 at 2:13 PM, Michael Rueger <m.rueger(a)acm.org> wrote: > Rob Rothwell wrote: > > I kind of like the idea, but I'm not sure what the UI would look like? > > Is it the option of choosing the same font for multiple purposes that is > > attractive? > > Not necessarily just the same font name but as with the UI themes a > group of settings that work well together. > You could predefine in some script themes like "large", "small", "fixed > width", "50+" ;-) and then select them from the preference panel just > like you select the UI theme. > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 1, 2009

Re: [Pharo-project] towards pharo 1.0 (from pavel)

by Adrian Lienhard

Thanks for the feedback, Pavel. I tagged these issues with Milestone-1.0 and reopened issue 71 since it seems still open according to the comment below. Cheers, Adrian On Mar 1, 2009, at 18:18 , StÃ©phane Ducasse wrote: > >> >> Hi Stef, >> >> there are some opened issues so we may start with them: >> 310 and 311 - the goal is to be able to unload all tests. As Adrian >> sugested, we may place it the package Tests - at least for now. >> 346 - easy and safe to integrate >> 348 - very important issue. Maybe you should place in one update fix >> for MorphicUIManager>>interactiveParserFor: and in the next the rest >> of the patch to prevent loading problems >> There was one wrong step in the development of Pharo during removing >> of MVC. Pharo deleted all MVC related code however in some cases it >> was the sign to use the UIManager. >> 71, 59 - very critical patch but I will have to check if the patches >> are suitable for the latest pharo >> >> I suggest to remove the unused class variable Current from the >> ColorTheme (issue 467) firstly - that cleans a lot of >> obsoleteClasses. >> >> I think that we need one important step in the development of Pharo - >> the next image that will not contain any code that can be unloaded. >> That should help us to increase the Pharo quality because now most >> packges are on the logical level in contradistiction to KernelImage >> where all packages are standalone unloadable entities. >> The ideal state is when we have the minimal core image with logical >> packages (like Collections) and the rest will be all unloadable >> packages. >> >> Cheers, >> -- Pavel >> >> >> >> On Sun, Mar 1, 2009 at 9:57 AM, stephane ducasse >> <stephane.ducasse(a)free.fr> wrote: >>> >>>> The KernelImage ZOO including the building environment is here: >>>> http://squeak.cz/public/pub/KernelImage/current/ >>>> >>>> Of course it is not perfect - the smallest image works only in >>>> Linux >>>> and MorphicCore needs a lot of fixes so people should start with >>>> MorphicExt and so on but it is usable starting point if someone is >>>> interested... >>>> >>>> -- Pavel >>> >>> Hi pavel >>> >>> do you have some fixes, cs list that we could slowly integrate to >>> pharo? >>> >>> Stef >>> >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 1, 2009

Re: [Pharo-project] changing default font

by Michael Rueger

Rob Rothwell wrote: > I kind of like the idea, but I'm not sure what the UI would look like? > Is it the option of choosing the same font for multiple purposes that is > attractive? Not necessarily just the same font name but as with the UI themes a group of settings that work well together. You could predefine in some script themes like "large", "small", "fixed width", "50+" ;-) and then select them from the preference panel just like you select the UI theme. Michael

March 1, 2009

Re: [Pharo-project] changing default font

by Rob Rothwell

I kind of like the idea, but I'm not sure what the UI would look like? Is it the option of choosing the same font for multiple purposes that is attractive? I also do something like: Preferences addBooleanPreference: #ScanAtStartup categories: #(FreeType) default: false balloonHelp: 'select to rescan the font folder during startup' . Along with: FreeTypeFontProvider>>startUp: resuming Preferences ScanAtStartup ifFalse: [^self]. resuming ifTrue:[ self current updateFromSystem] Just so I don't have to wait for it to scan my font folder during start up each time. So...I guess I managed to figure out SOMETHING about Preferences, but I don't know how to add other UI elements like radio buttons, drop down lists, etc... which would be useful in this case. If it is really something that you think would be useful, I'll give it a shot if anyone can point me towards some Preferences examples that would be similar, otherwise, I'll just keep loading my "Personalization" package that, upon loading, executes "Personalize fonts"! Rob On Sun, Mar 1, 2009 at 1:42 PM, Michael Rueger <m.rueger(a)acm.org> wrote: > Rob Rothwell wrote: > > And if you get tired of setting your fonts individually, you can set > > them all at once: > > we should add something like that as font themes to the preferences? > > Michael > > > > > font := LogicalFont familyName: 'Andika Basic' pointSize: 10. > > codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. > > Preferences setListFontTo: font. > > Preferences setMenuFontTo: font. > > Preferences setCodeFontTo: codeFont. > > Preferences setButtonFontTo: font. > > Preferences setSystemFontTo: font. > > font := LogicalFont familyName: 'Andika Basic' pointSize: 11. > > Preferences setWindowTitleFontTo: font. > > > > Just replace the font names with those of your choice! > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 1, 2009

Re: [Pharo-project] changing default font

by Michael Rueger

Rob Rothwell wrote: > And if you get tired of setting your fonts individually, you can set > them all at once: we should add something like that as font themes to the preferences? Michael > > font := LogicalFont familyName: 'Andika Basic' pointSize: 10. > codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. > Preferences setListFontTo: font. > Preferences setMenuFontTo: font. > Preferences setCodeFontTo: codeFont. > Preferences setButtonFontTo: font. > Preferences setSystemFontTo: font. > font := LogicalFont familyName: 'Andika Basic' pointSize: 11. > Preferences setWindowTitleFontTo: font. > > Just replace the font names with those of your choice!

March 1, 2009

Re: [Pharo-project] from #foo:bar: to foo: arg1 bar: arg2

by Lukas Renggli

The refactoring browser has this: genericPatternForSelector: aSymbol ^ String streamContents: [ :stream | aSymbol keywords keysAndValuesDo: [ :index :value | stream space; nextPutAll: value. aSymbol last = $: ifTrue: [ stream space; nextPutAll: 'arg'; print: index ] ] ] Lukas On Sun, Mar 1, 2009 at 7:18 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > does one of you get to know a method for doing that? > > #foo:bar: > > Â Â Â Â -> Â foo: arg1 bar: arg2 > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

March 1, 2009

Re: [Pharo-project] from #foo:bar: to foo: arg1 bar: arg2

by StÃ©phane Ducasse

may be we should add it somewhere in symbol because this is handy when you want to generate methods on the fly. signatureFromSelector: aSelector "self new signatureFromSelector: #foo:bar: " "self new signatureFromSelector: #foo" "self new signatureFromSelector: #foo:" | count | ^ String streamContents: [:str| count := 1. (ReadStream on: aSelector) do: [:each | each = $: ifTrue: [ str nextPut: each. str nextPutAll: ' arg', count printString, ' '. count := count + 1] ifFalse: [str nextPut: each] ]] On Mar 1, 2009, at 7:18 PM, StÃ©phane Ducasse wrote: > Hi > > does one of you get to know a method for doing that? > > #foo:bar: > > -> foo: arg1 bar: arg2 > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 1, 2009

[Pharo-project] split/join

by StÃ©phane Ducasse

I think that there was a split/join package somewhere. Does anybody know where it is? At one point it was planned to get added to squeak and nothing happened. Stef

March 1, 2009