- Pharo-dev - lists.pharo.org

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

by Esteban Lorenzano

no, they should be found... no changed by hand. Maybe you need to point yo right framework direction? (xcode-select)? 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>

April 10, 2012

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

by phil＠highoctane.be

I am able to open the Xcode project in Xcode 4.3 now. Next step, build properly. Phil 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

April 10, 2012

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

by phil＠highoctane.be

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

April 10, 2012

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

by Esteban Lorenzano

wow :) On Apr 10, 2012, at 2:48 PM, Pavel Krivanek wrote: > You can see it in action: > http://www.youtube.com/watch?v=pOyvXamn3Y4 > > -- Pavel > > On Tue, Apr 10, 2012 at 12:41 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> 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] Power of Fuel - Pharo-Kernel to Pharo-Core in 15 seconds

by Pavel Krivanek

You can see it in action: http://www.youtube.com/watch?v=pOyvXamn3Y4 -- Pavel On Tue, Apr 10, 2012 at 12:41 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> 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] SmallLint and manifest

by Tudor Girba

Hi, On Sat, Apr 7, 2012 at 9:14 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks > >> Hi, >> >> Thanks. >> >> I gave it a short try, and here are some comments: >> - The Manifest-Core should contain only the core of the manifest engine. For example, I see here some mechanism for traversing Manifest classes and retrieving data from them. Everything else that is specific to SmallLint should be in a Manifest-SmallLint package. >> - All tests should be in the Manifest-Tests package (currently, there are extension tests in Manifest-Core - I actually do not know why) >> - I like it that a Manifest class does not have to inherit from a specific root class. >> - There exists a ManifestManifestCore class, but I do not understand why there are subclasses to it. >> - You are using numbers to identify SmallLint rules. For this, you extended the rules with unique numbers. This is a very brittle scheme, and when people have domain specific rules, you will likely get a mess. Furthermore, I do not see the reason for having a number as a unique identifier, when you already have a unique identifier in the name of the rule class. Also, when looking at a method, we see something like: rule17V1FalsePositive. This is unnecessary cryptic. > > Because we do not want to rely on class refactoring. 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. If you keep the numbering, you will immediately get into numbering issues as soon as people will start writing their own rules. >> - 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. 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"

April 10, 2012

Re: [Pharo-project] SmallLint and manifest

by Tudor Girba

Hi, On Tue, Apr 10, 2012 at 2:18 PM, Simon Allier <simon.allier(a)inria.fr> wrote: > Thanks for this comments > >> Thanks >> >>> Hi, >>> >>> Thanks. >>> >>> I gave it a short try, and here are some comments: >>> - The Manifest-Core should contain only the core of the manifest engine. For example, I see here some mechanism for traversing Manifest classes and retrieving data from them. Everything else that is specific to SmallLint should be in a Manifest-SmallLint package. > > In this case, we also need a specific package for the SmallLint Browser. > >>> - All tests should be in the Manifest-Tests package (currently, there are extension tests in Manifest-Core - I actually do not know why) > > I will check this. > >>> - I like it that a Manifest class does not have to inherit from a specific root class. >>> - There exists a ManifestManifestCore class, but I do not understand why there are subclasses to it. > > ManifestManifestCore is the manifest class of the package Manifest-Core, it does not have the subclasses. Indeed. It was my bad. Doru >>> - You are using numbers to identify SmallLint rules. For this, you extended the rules with unique numbers. This is a very brittle scheme, and when people have domain specific rules, you will likely get a mess. Furthermore, I do not see the reason for having a number as a unique identifier, when you already have a unique identifier in the name of the rule class. Also, when looking at a method, we see something like: rule17V1FalsePositive. This is unnecessary cryptic. >> >> Because we do not want to rely on class refactoring. >> >>> - 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. >> >> 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"

April 10, 2012

[Pharo-project] [update 1.4] #14425

by Esteban Lorenzano

14425 ----- Issue 5445: Broken command-line arguments in 1.4, thanks Pavel http://code.google.com/p/pharo/issues/detail?id=5445

April 10, 2012

Re: [Pharo-project] SmallLint and manifest

by Simon Allier

Thanks for this comments > Thanks > >> Hi, >> >> Thanks. >> >> I gave it a short try, and here are some comments: >> - The Manifest-Core should contain only the core of the manifest engine. For example, I see here some mechanism for traversing Manifest classes and retrieving data from them. Everything else that is specific to SmallLint should be in a Manifest-SmallLint package. In this case, we also need a specific package for the SmallLint Browser. >> - All tests should be in the Manifest-Tests package (currently, there are extension tests in Manifest-Core - I actually do not know why) I will check this. >> - I like it that a Manifest class does not have to inherit from a specific root class. >> - There exists a ManifestManifestCore class, but I do not understand why there are subclasses to it. ManifestManifestCore is the manifest class of the package Manifest-Core, it does not have the subclasses. >> - You are using numbers to identify SmallLint rules. For this, you extended the rules with unique numbers. This is a very brittle scheme, and when people have domain specific rules, you will likely get a mess. Furthermore, I do not see the reason for having a number as a unique identifier, when you already have a unique identifier in the name of the rule class. Also, when looking at a method, we see something like: rule17V1FalsePositive. This is unnecessary cryptic. > > Because we do not want to rely on class refactoring. > >> - 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. > > 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." >> >> > >

April 10, 2012

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

by Esteban Lorenzano

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>

April 10, 2012