April 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Workspace completion with Tab and Ctrl-q gone in Pharo 1.4?

by Levente Uzonyi

On Mon, 9 Apr 2012, StÃ©phane Ducasse wrote: > first load ConfigurationOfNewECompletion (via the configurationBrowser). > > Second we will see if we can clean OCompletion to make it work with ECompletion instead of breaking it. > We could ship the old and ugly version but we will see if we can make both happily work together. > Some people like ECompletion (but could not use it in pharo because OCompletion broke it - I was not aware because I only use Ocompletion), > some Ocompletion (me but I do not like the implementation of OCompletion that just copy everything and break - So I cleaned Ecompletion and > started to make Ocompletion implementation nicer but did not finish. FYI: OCompletion includes ECompletion, there's a setting to change between the two. Levente > > Stef > > On Apr 9, 2012, at 9:35 PM, phil(a)highoctane.be wrote: > >> I tried the 1.4 and there is no completion anymore. >> >> What to do to get it back? >> >> Philippe > > >

April 10, 2012

Re: [Pharo-project] Vm on iOS with Xcode 4.3

by phil＠highoctane.be

Fail: Key #IOSPlugin not found. I have removed the build/ folder before generating anything. See screenshot. Phil 2012/4/10 Esteban Lorenzano <estebanlm(a)gmail.com> > yeah... but you don't need FT2 for iOS... that instructions were for plain > cog vm. > > Run this instead: > > StackIPhoneConfig new > "generateForDebug;" > generateSources; generate. > > btw... you will need to remove CMakeCache.txt before running cmake again. > > On Apr 10, 2012, at 6:09 PM, phil(a)highoctane.be wrote: > > Looks like OSX 10.7 needs a bit of sudo port install automake to have the > right version for FT2 plugin. > > Let's see. > > Phil > > 2012/4/10 Esteban Lorenzano <estebanlm(a)gmail.com> > >> on ./build >> >> execute: >> >> ../codegen-scripts/extract-commit-info.sh >> >> then... you are going to have errors (23, if everything is like my >> installation)... and you are going to be in the same stage as me (I still >> didn't fixed that, is an cmakemaker issue) >> >> On Apr 10, 2012, at 2:58 PM, phil(a)highoctane.be wrote: >> >> Ok, it generates sources. >> >> I used the cmake you told me: >> >> So, on Lion, some frameworks are not found. I guess that I'll have to >> update that by hand. >> >> Philippe >> >> 2012/4/10 Esteban Lorenzano <estebanlm(a)gmail.com> >> >>> sorry, my fault... there is no stable version on cog >>> >>> try: >>> >>> (ConfigurationOfCog project version: '4.4') load. >>> >>> >>> On Apr 10, 2012, at 2:11 PM, phil(a)highoctane.be wrote: >>> >>> Sorry, fails on #stable load. >>> >>> Did you meant #release ? >>> >>> Phil >>> >>> >>> 2012/4/10 Esteban Lorenzano <estebanlm(a)gmail.com> >>> >>>> that's a pretty old version of CMakeMaker... you should: >>>> >>>> 1) download latest pharo 1.4 (and place it in ./image) >>>> 2) install ConfigurationOfCog >>>> >>>> Gofer it >>>> squeaksource: 'MetacelloRepository'; >>>> package: 'ConfigurationOfCog'; >>>> load. >>>> >>>> 3) execute >>>> >>>> (ConfigurationOfCog project version: #stable) load. >>>> >>>> 4) then execute: >>>> >>>> CogCocoaIOSConfig new >>>> "generateForDebug;" >>>> addExternalPlugins: #(FT2Plugin); >>>> generateSources; generate. >>>> >>>> that's the correct way of doing >>>> >>>> best, >>>> Esteban >>>> >>>> On Apr 10, 2012, at 1:51 PM, phil(a)highoctane.be wrote: >>>> >>>> The CocoaIOSJitConfig>>prepareForGeneration >>>> >>>> "force using LF on Macs" >>>> CrLfFileStream defaultToLF. >>>> >>>> ^ self prepareForCogGeneration >>>> >>>> fails on CrLfFileStream defaultToLF. >>>> >>>> The only implementer was MultiByteFileStream defaultToLF. >>>> >>>> The CrLfFileStream occurs in quite a *Config places. >>>> >>>> Phil >>>> >>>> 2012/4/10 Mariano Martinez Peck <marianopeck(a)gmail.com> >>>> >>>>> >>>>> >>>>> On Tue, Apr 10, 2012 at 12:16 AM, phil(a)highoctane.be < >>>>> phil(a)highoctane.be> wrote: >>>>> >>>>>> I do have the cloned repos now. >>>>>> >>>>>> For ConfigurationOfCog where can I pick this one up ? In the supplied >>>>>> image I guess. Right? >>>>>> >>>>>> >>>>> Hi Philip. Just by change did you read my blog posts about building >>>>> the VM? they may be of help: >>>>> >>>>> http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… >>>>> >>>>> http://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/ >>>>> >>>>> Cheers >>>>> >>>>> >>>>>> ... moving (slowly) forward. >>>>>> >>>>>> Thanks! >>>>>> >>>>>> 2012/4/6 phil(a)highoctane.be <phil(a)highoctane.be> >>>>>> >>>>>> Oh great news! >>>>>>> Tomorrow will be Pharo iOS day. >>>>>>> Le 6 avr. 2012 17:54, "Esteban Lorenzano" <estebanlm(a)gmail.com> a >>>>>>> Ã©crit : >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> On Apr 6, 2012, at 10:51 AM, phil(a)highoctane.be wrote: >>>>>>>> >>>>>>>> I am still unable to get this to work. >>>>>>>> >>>>>>>> latest nightly build from cmake is able to build valid xcode >>>>>>>> projects again [1]. >>>>>>>> Some adjusts are needed to actually build, but it is almost there >>>>>>>> (I will take care about that this days) >>>>>>>> >>>>>>>> Also I see a jenkins build for OSX but not for iOS. >>>>>>>> >>>>>>>> Yeah, and I want to have one, but it will take time (and time is >>>>>>>> tyrant, you know). >>>>>>>> >>>>>>>> XCode 4.3 will open old xcode projects so posting a full set of >>>>>>>> files that work out of cmake (ie a fully made build/ folder) would help a >>>>>>>> lot. >>>>>>>> >>>>>>>> Would you be able to ship me such a set of files? >>>>>>>> >>>>>>>> you already have them: clone of my repository [2] or blessed [3] >>>>>>>> and install latest ConfigurationOfCog >>>>>>>> >>>>>>>> best, >>>>>>>> Esteban >>>>>>>> >>>>>>>> [1] >>>>>>>> http://www.cmake.org/files/dev/cmake-2.8.7.20120405-gd2c9c-Darwin64-univers… >>>>>>>> [2] https://gitorious.org/~estebanlm/cogvm/cog-osx >>>>>>>> [3] https://gitorious.org/cogvm/blessed >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Philippe Back >>>>>> "Helping you hit the top 3 outcomes you really want to achieve" >>>>>> >>>>>> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >>>>>> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >>>>>> http://philippeback.be >>>>>> >>>>>> High Octane SPRL >>>>>> rue cour Boisacq 101 >>>>>> 1301 Bierges >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Mariano >>>>> http://marianopeck.wordpress.com >>>>> >>>>> >>>> >>>> >>>> -- >>>> Philippe Back >>>> "Helping you hit the top 3 outcomes you really want to achieve" >>>> >>>> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >>>> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >>>> http://philippeback.be >>>> >>>> High Octane SPRL >>>> rue cour Boisacq 101 >>>> 1301 Bierges >>>> >>>> >>>> >>> >>> >>> -- >>> Philippe Back >>> "Helping you hit the top 3 outcomes you really want to achieve" >>> >>> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >>> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >>> http://philippeback.be >>> >>> High Octane SPRL >>> rue cour Boisacq 101 >>> 1301 Bierges >>> >>> <PharoScreenshot.3.png> >>> >>> >>> >> >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> >> <2012-04-10_14-56-49-cmake.png> >> >> >> > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: > http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges > > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 10, 2012

Re: [Pharo-project] Vm on iOS with Xcode 4.3

by phil＠highoctane.be

I'll write a post on this anyway. 2012/4/10 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > we should update the blog of mariano. > > Stef > > On Apr 10, 2012, at 2:00 PM, Esteban Lorenzano wrote: > > > that's a pretty old version of CMakeMaker... you should: > > > > 1) download latest pharo 1.4 (and place it in ./image) > > 2) install ConfigurationOfCog > > > > Gofer it > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfCog'; > > load. > > > > 3) execute > > > > (ConfigurationOfCog project version: #stable) load. > > > > 4) then execute: > > > > CogCocoaIOSConfig new > > "generateForDebug;" > > addExternalPlugins: #(FT2Plugin); > > generateSources; generate. > > > > that's the correct way of doing > > > > best, > > Esteban > > > > On Apr 10, 2012, at 1:51 PM, phil(a)highoctane.be wrote: > > > >> The CocoaIOSJitConfig>>prepareForGeneration > >> > >> "force using LF on Macs" > >> CrLfFileStream defaultToLF. > >> > >> ^ self prepareForCogGeneration > >> > >> fails on CrLfFileStream defaultToLF. > >> > >> The only implementer was MultiByteFileStream defaultToLF. > >> > >> The CrLfFileStream occurs in quite a *Config places. > >> > >> Phil > >> > >> 2012/4/10 Mariano Martinez Peck <marianopeck(a)gmail.com> > >> > >> > >> On Tue, Apr 10, 2012 at 12:16 AM, phil(a)highoctane.be < > phil(a)highoctane.be> wrote: > >> I do have the cloned repos now. > >> > >> For ConfigurationOfCog where can I pick this one up ? In the supplied > image I guess. Right? > >> > >> > >> Hi Philip. Just by change did you read my blog posts about building the > VM? they may be of help: > >> > http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… > >> > http://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/ > >> > >> Cheers > >> > >> ... moving (slowly) forward. > >> > >> Thanks! > >> > >> 2012/4/6 phil(a)highoctane.be <phil(a)highoctane.be> > >> > >> Oh great news! > >> Tomorrow will be Pharo iOS day. > >> Le 6 avr. 2012 17:54, "Esteban Lorenzano" <estebanlm(a)gmail.com> a > Ã©crit : > >> Hi, > >> > >> On Apr 6, 2012, at 10:51 AM, phil(a)highoctane.be wrote: > >> > >>> I am still unable to get this to work. > >> latest nightly build from cmake is able to build valid xcode projects > again [1]. > >> Some adjusts are needed to actually build, but it is almost there (I > will take care about that this days) > >>> Also I see a jenkins build for OSX but not for iOS. > >>> > >> Yeah, and I want to have one, but it will take time (and time is > tyrant, you know). > >> > >>> XCode 4.3 will open old xcode projects so posting a full set of files > that work out of cmake (ie a fully made build/ folder) would help a lot. > >>> > >>> Would you be able to ship me such a set of files? > >>> > >> you already have them: clone of my repository [2] or blessed [3] and > install latest ConfigurationOfCog > >> > >> best, > >> Esteban > >> > >> [1] > http://www.cmake.org/files/dev/cmake-2.8.7.20120405-gd2c9c-Darwin64-univers… > >> [2] https://gitorious.org/~estebanlm/cogvm/cog-osx > >> [3] https://gitorious.org/cogvm/blessed > >> > >> > >> > >> > >> > >> > >> -- > >> Philippe Back > >> "Helping you hit the top 3 outcomes you really want to achieve" > >> > >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > >> http://philippeback.be > >> > >> High Octane SPRL > >> rue cour Boisacq 101 > >> 1301 Bierges > >> > >> > >> > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > >> > >> > >> > >> -- > >> Philippe Back > >> "Helping you hit the top 3 outcomes you really want to achieve" > >> > >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > >> http://philippeback.be > >> > >> High Octane SPRL > >> rue cour Boisacq 101 > >> 1301 Bierges > >> > > > > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 10, 2012

Re: [Pharo-project] font reading problems

by Alain Plantec

http://code.google.com/p/pharo/issues/detail?id=5591 just send StandardFonts class >>fixSmallDejaVuPunctuationMarks as a postcript Cheers Alain Le 10/04/12 22:07, StÃ©phane Ducasse a Ã©crit : > thanks alain like that we integrate it in 1.4 and release it (we should check at the defaultAction od deprecation). > On Apr 10, 2012, at 9:56 PM, Alain Plantec wrote: > >> y sent because it has to be sent only one time. >> I open an issue. >

April 10, 2012

Re: [Pharo-project] font reading problems

by StÃ©phane Ducasse

thanks alain like that we integrate it in 1.4 and release it (we should check at the defaultAction od deprecation). On Apr 10, 2012, at 9:56 PM, Alain Plantec wrote: > y sent because it has to be sent only one time. > I open an issue.

April 10, 2012

Re: [Pharo-project] SmallLint and manifest

by Tudor Girba

Hi, On 10 Apr 2012, at 21:31, StÃ©phane Ducasse wrote: >> >> I do not get it. You want an identifier. Why is a brittle and >> obfuscated number better than the name of the class, which is already >> a proper identifier? If you do not want to rely directly on a class >> reference, you can store it as a symbol. > > sure this is not the problem numbers solve. We want to have no impact because of class name change. > >> If you keep the numbering, >> you will immediately get into numbering issues as soon as people will >> start writing their own rules. > > Normally not because number should be unique and should never change. But I see your point > After we have a version number when we change a rule > for example rule 1 version 1 is different from rule 1 version 2 > > How you scenario behave in presence of class renaming? > Our is stable but indeed people can add number that clashes with existing ones. Now we should have a rule stating that rule should have unique id. Rules are effective when they are like specific, not when they are generic. So, we should expect (and encourage) people to write their own rules for their own context. There is no way in which you could get a numbering scheme to fit a hundred different projects and still have an understandable situation. In my scenario, if someone renamed a SmallLint rule but the false positives still refer to the old one, the false positives from the manifest would simply get ignored. On top of that, we could add a meta-rule that says that all manifest rules should have a corresponding SamllLint rule. >>>> - In the rule methods, you are storing strings. This means that when someone renames a rule, the code in there will not be updated. Why not store this information as normal code and use symbols that can be queried? >>> >>> I do not get it? It is normal code no? >>> You mean symbols instead of strings. >> >> I mean you are currently storing the following in a rule exception: >> rule24V1FalsePositive >> ^ #(#('(RGMethodDefinition className: ''RGClassDefinitionTest'' >> selector: #testReadFrom isMetaSide: false)' >> #'2012-04-02T11:31:59.933+02:00') ) >> >> This an array of strings, not code. I was wondering why it would not >> be possible to be code directly. > > because we do not want to store information that force us to have ring loaded. Why not: '(RGMethodDefinition className: ''RGClassDefinitionTest'' selector: #testReadFrom isMetaSide: false)' ==> (Smalltalk at: #RGMethodDefinition) className: ''RGClassDefinitionTest'' selector: #testReadFrom isMetaSide: false Cheers, Doru > Cheers, >> Doru >> >> >>> We will the issues. >>> >>> >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>> On 6 Apr 2012, at 09:51, Simon Allier wrote: >>>> >>>>> Hi pharoers >>>>> >>>>> Since a couple of months the Pharo team has been working on improving the support for rules checking and in particular the handling of false positives (there is nothing more boring that to get all the time the same warnings that we know are not adequate). >>>>> We added a manifest mechanism to manage the false/true positive of SmallLint, the rule checker of Pharo. A manifest is a class that contains meta data. In the future we may add package license and package documentation. This data is stored in methods on the meta side of the class. So, manifest can be versioned in Monticello and not lost. There is one manifest per package. >>>>> >>>>> It possible to use SmallLint with Manifest using the Critics Browser (menuWorld > Tool > CriticBrowser). With the Critics browser you can inspect violations of rules and mark them as false positive or true positive (ToDo) and see previous warnings flagged as false positives or toDo. >>>>> In addition all the logic of the browser has been developed so that the manifest can be saved within the package without adding dependencies. >>>>> We will continue to improve the Browser. In addition we will run SmallLint rules to all the Pharo packages and the rules checking will be part of the package validation. We want the community to use rule checking for real so that we all improve. >>>>> >>>>> Simon and Stef >>>>> >>>>> Gofer >>>>> new >>>>> url: 'http://www.squeaksource.com/PharoTaskForces'; >>>>> package: 'ConfigurationOfManifest'; >>>>> load. >>>>> ((Smalltalk at: #ConfigurationOfManifest) project version: #stable) load >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Not knowing how to do something is not an argument for how it cannot be done." >>>> >>>> >>> >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "We are all great at making mistakes."

April 10, 2012

Re: [Pharo-project] font reading problems

by Alain Plantec

Le 10/04/12 21:34, StÃ©phane Ducasse a Ã©crit : > esteban we should add this to 1.4 (as a method so that we can invoke it). so, you should remove the widen:by sent because it has to be sent only one time. I open an issue. Cheers Alain > > Stef > > On Apr 10, 2012, at 1:03 AM, Alain Plantec wrote: > >> Hi, >> >> yes, the default font is not that readable. >> as a workarround try the following (and see before and after screenshots): >> ------- >> | fb | >> StandardFonts setFontsToStyleNamed: #small. >> fb :=StandardFonts defaultFont emphasized: 1. >> #($. $: $; $' $` $,) >> do: [:ch | >> StandardFonts defaultFont characterFormAt: ch put: (fb characterFormAt: ch) deepCopy. >> StandardFonts defaultFont widen: ch by: 1]. >> ------- >> >> this make the punctuation chars much more visible : >> it replace a regular one with the corresponding bold one and make it wider by 1 pixel. >> >> Cheers >> Alain >> >> >> >> Le 08/04/12 21:03, StÃ©phane Ducasse a Ã©crit : >>> Hi guys >>> >>> I do not like the default font because there is not enough space around : >>> so this is difficult to see it for example in >>> >>> := >>> >>> >>> >>> >>> so what can be done? >>> Can we modify this font? >>> >>> Stef >> <before.png><after.png> >

April 10, 2012

Re: [Pharo-project] Vm on iOS with Xcode 4.3

by StÃ©phane Ducasse

we should update the blog of mariano. Stef On Apr 10, 2012, at 2:00 PM, Esteban Lorenzano wrote: > that's a pretty old version of CMakeMaker... you should: > > 1) download latest pharo 1.4 (and place it in ./image) > 2) install ConfigurationOfCog > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfCog'; > load. > > 3) execute > > (ConfigurationOfCog project version: #stable) load. > > 4) then execute: > > CogCocoaIOSConfig new > "generateForDebug;" > addExternalPlugins: #(FT2Plugin); > generateSources; generate. > > that's the correct way of doing > > best, > Esteban > > On Apr 10, 2012, at 1:51 PM, phil(a)highoctane.be wrote: > >> The CocoaIOSJitConfig>>prepareForGeneration >> >> "force using LF on Macs" >> CrLfFileStream defaultToLF. >> >> ^ self prepareForCogGeneration >> >> fails on CrLfFileStream defaultToLF. >> >> The only implementer was MultiByteFileStream defaultToLF. >> >> The CrLfFileStream occurs in quite a *Config places. >> >> Phil >> >> 2012/4/10 Mariano Martinez Peck <marianopeck(a)gmail.com> >> >> >> On Tue, Apr 10, 2012 at 12:16 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> I do have the cloned repos now. >> >> For ConfigurationOfCog where can I pick this one up ? In the supplied image I guess. Right? >> >> >> Hi Philip. Just by change did you read my blog posts about building the VM? they may be of help: >> http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… >> http://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/ >> >> Cheers >> >> ... moving (slowly) forward. >> >> Thanks! >> >> 2012/4/6 phil(a)highoctane.be <phil(a)highoctane.be> >> >> Oh great news! >> Tomorrow will be Pharo iOS day. >> Le 6 avr. 2012 17:54, "Esteban Lorenzano" <estebanlm(a)gmail.com> a Ã©crit : >> Hi, >> >> On Apr 6, 2012, at 10:51 AM, phil(a)highoctane.be wrote: >> >>> I am still unable to get this to work. >> latest nightly build from cmake is able to build valid xcode projects again [1]. >> Some adjusts are needed to actually build, but it is almost there (I will take care about that this days) >>> Also I see a jenkins build for OSX but not for iOS. >>> >> Yeah, and I want to have one, but it will take time (and time is tyrant, you know). >> >>> XCode 4.3 will open old xcode projects so posting a full set of files that work out of cmake (ie a fully made build/ folder) would help a lot. >>> >>> Would you be able to ship me such a set of files? >>> >> you already have them: clone of my repository [2] or blessed [3] and install latest ConfigurationOfCog >> >> best, >> Esteban >> >> [1] http://www.cmake.org/files/dev/cmake-2.8.7.20120405-gd2c9c-Darwin64-univers… >> [2] https://gitorious.org/~estebanlm/cogvm/cog-osx >> [3] https://gitorious.org/cogvm/blessed >> >> >> >> >> >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> >

April 10, 2012

Re: [Pharo-project] Power of Fuel - Pharo-Kernel to Pharo-Core in 15 seconds

by StÃ©phane Ducasse

I love your attitude: a hammer and systematically beating beating beating the same huge nail until we get thereâ¦. I love that. I call that the bull attitude: I'm like that too :). Stef On Apr 10, 2012, at 12:41 PM, Pavel Krivanek wrote: > Hi, > > I tried to load entire Pharo-Core content into Pharo-Kernel with help > of Fuel and I was successful. It was done in 4 steps: > - load and initialize all packages up to Gofer (gofer.fuel) > - load and initialize Ring (ring.fuel) > - load rest of the Paharo-Core packages (pharo-core.fuel) > - do the initialization of Morphic and the rest of the system. > All that takes about 15 seconds on my old laptop. Normally it takes > about 12 minutes. > > Of course there are several issues we have to solve permanently: > - current Fuel cannot load several packages at once but it is very > easy to enhance it. > - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, > sometimes nil category) > - the packages must be clean because Fuel raises error when it uses > unknown global variable > - Fuel must have a way how to disable initialization of loaded classes > - some packages like Morphic have extension methods in categories > named "*Morphic-something". PackageInfo ignores it and expects that > this categories are extending categories of some different package. > - it doesn't store to Changes. > > If anyone will want, I send him an archive with the images and ad-hoc fixes. > > Cheers, > -- Pavel >

April 10, 2012

Re: [Pharo-project] font reading problems

by StÃ©phane Ducasse

esteban we should add this to 1.4 (as a method so that we can invoke it). Stef On Apr 10, 2012, at 1:03 AM, Alain Plantec wrote: > Hi, > > yes, the default font is not that readable. > as a workarround try the following (and see before and after screenshots): > ------- > | fb | > StandardFonts setFontsToStyleNamed: #small. > fb :=StandardFonts defaultFont emphasized: 1. > #($. $: $; $' $` $,) > do: [:ch | > StandardFonts defaultFont characterFormAt: ch put: (fb characterFormAt: ch) deepCopy. > StandardFonts defaultFont widen: ch by: 1]. > ------- > > this make the punctuation chars much more visible : > it replace a regular one with the corresponding bold one and make it wider by 1 pixel. > > Cheers > Alain > > > > Le 08/04/12 21:03, StÃ©phane Ducasse a Ã©crit : >> Hi guys >> >> I do not like the default font because there is not enough space around : >> so this is difficult to see it for example in >> >> := >> >> >> >> >> so what can be done? >> Can we modify this font? >> >> Stef > > <before.png><after.png>

April 10, 2012