- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Suggestion: introducing a fixme/issue/todo pragma

by StÃ©phane Ducasse

On Apr 22, 2012, at 2:24 PM, phil(a)highoctane.be wrote: > Stef, > > Thanks. > > How are flags working? just like a simple method. after you can do "senders" to identify them. > > Looks like this is at the class level. I am interested in a method level ting. no this is like any send in the system so this is a method level identification. Try senders of flag: > > KR > Phil > > 2012/4/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > we use self flag: #fixMe > you can then query either #fixMe or flag: > > and yes this is a good idea to mark things and create bug entries. > > Stef > > > On Apr 22, 2012, at 11:18 AM, phil(a)highoctane.be wrote: > > > While looking around in the image, I am in need of knowing where I found thngs that either puzzle me or are "wrong" (well, a code smell). > > > > What I do is that I put pragmas in there like this (not that this sample is meant to be representative) > > > > privCleanTextConstants > > <fixme> > > TextConstants TextSharedInformation removeKey: #DefaultTextStyle. > > TextConstants TextSharedInformation removeKey: #DefaultMultiStyle. > > TextConstants TextSharedInformation removeKey: #DefaultFixedTextStyle. > > TextConstants TextSharedInformation removeKey: StrikeFont defaultFontKey. > > > > Smalltalk allClasses select: [:c | c sharedPools includes: TextConstants] thenDo: [:c | c compileAll ]. > > > > And I can then find back the things with: > > > > pc := (PragmaCollector filter: [:prg | prg keyword = 'fixme']) reset. > > pc collected size. "(Print It: 1)" > > pc collected explore. > > > > And then finding back the Class and Method Name > > > > Building upon that, why not do what is done in other environments (well, I've got that in PHP, Java, ...) and use: > > > > <todo:do this and that> or plain <todo> > > <fixme: this and that> or plain <fixme> > > <issue:issue#> > > > > And have a specific tool to help the navigation (explore is fine for a moment but...) > > > > This would allow us to have an idea on the technical debt inside the system, broken down by areas if we start leveraging Packages. > > > > What I do not know is how much stress this would put on the system. Are pragmas eating a lot or a just markers? > > > > Phil > > > > > > > > -- > 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 22, 2012

Re: [Pharo-project] Suggestion: introducing a fixme/issue/todo pragma

by phil＠highoctane.be

Stef, Thanks. How are flags working? Looks like this is at the class level. I am interested in a method level ting. KR Phil 2012/4/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > we use self flag: #fixMe > you can then query either #fixMe or flag: > > and yes this is a good idea to mark things and create bug entries. > > Stef > > > On Apr 22, 2012, at 11:18 AM, phil(a)highoctane.be wrote: > > > While looking around in the image, I am in need of knowing where I found > thngs that either puzzle me or are "wrong" (well, a code smell). > > > > What I do is that I put pragmas in there like this (not that this sample > is meant to be representative) > > > > privCleanTextConstants > > <fixme> > > TextConstants TextSharedInformation removeKey: #DefaultTextStyle. > > TextConstants TextSharedInformation removeKey: #DefaultMultiStyle. > > TextConstants TextSharedInformation removeKey: > #DefaultFixedTextStyle. > > TextConstants TextSharedInformation removeKey: StrikeFont > defaultFontKey. > > > > Smalltalk allClasses select: [:c | c sharedPools includes: > TextConstants] thenDo: [:c | c compileAll ]. > > > > And I can then find back the things with: > > > > pc := (PragmaCollector filter: [:prg | prg keyword = 'fixme']) reset. > > pc collected size. "(Print It: 1)" > > pc collected explore. > > > > And then finding back the Class and Method Name > > > > Building upon that, why not do what is done in other environments (well, > I've got that in PHP, Java, ...) and use: > > > > <todo:do this and that> or plain <todo> > > <fixme: this and that> or plain <fixme> > > <issue:issue#> > > > > And have a specific tool to help the navigation (explore is fine for a > moment but...) > > > > This would allow us to have an idea on the technical debt inside the > system, broken down by areas if we start leveraging Packages. > > > > What I do not know is how much stress this would put on the system. Are > pragmas eating a lot or a just markers? > > > > Phil > > > > > -- 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 22, 2012

Re: [Pharo-project] Kernel jobs for 2.0

by Mariano Martinez Peck

On Sun, Apr 22, 2012 at 2:15 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Apr 22, 2012, at 12:47 PM, Pavel Krivanek wrote: > > > Hi, > > > > I created Kernel jobs for the version 2.0. It uses separate set of > > scripts so new big changes will not break 1.4. > > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel%202.0/ > > > > Now is pointless to run them because 2.0 repository doesn't include > > all packages. Some things that should be done: > > - start Trello board for 2.0 ;-) > > Done: https://trello.com/board/pharo-2-0/4f7ae7371d239ca86263c96f > > > - the package Deprecated 14 should be replaced by Deprecated20. > > - integrate basic Fuel packages (Fuel, FuelMetalevel, FuelPackageLoader > + tests) > > > GIve us one or two weeks that we want to release Fuel 1.8. Martin is giving his last exam on Thuesday so hopefully we will release 1.8 soon. Then we can integrate such release in Pharo 2.0. > > -- Pavel > > > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Mariano http://marianopeck.wordpress.com

April 22, 2012

Re: [Pharo-project] Suggestion: introducing a fixme/issue/todo pragma

by Mariano Martinez Peck

On Sun, Apr 22, 2012 at 11:55 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > we use self flag: #fixMe > you can then query either #fixMe or flag: > > and yes this is a good idea to mark things and create bug entries. > > Stef > > > On Apr 22, 2012, at 11:18 AM, phil(a)highoctane.be wrote: > > > While looking around in the image, I am in need of knowing where I found > thngs that either puzzle me or are "wrong" (well, a code smell). > > > > What I do is that I put pragmas in there like this (not that this sample > is meant to be representative) > > > > privCleanTextConstants > > <fixme> > > TextConstants TextSharedInformation removeKey: #DefaultTextStyle. > > TextConstants TextSharedInformation removeKey: #DefaultMultiStyle. > > TextConstants TextSharedInformation removeKey: > #DefaultFixedTextStyle. > > TextConstants TextSharedInformation removeKey: StrikeFont > defaultFontKey. > > > > Smalltalk allClasses select: [:c | c sharedPools includes: > TextConstants] thenDo: [:c | c compileAll ]. > > > > And I can then find back the things with: > > > > pc := (PragmaCollector filter: [:prg | prg keyword = 'fixme']) reset. > > pc collected size. "(Print It: 1)" > > pc collected explore. > > > > And then finding back the Class and Method Name > > > > Building upon that, why not do what is done in other environments (well, > I've got that in PHP, Java, ...) and use: > > > > <todo:do this and that> or plain <todo> > > <fixme: this and that> or plain <fixme> > > <issue:issue#> > > > As Stef said, we usually use #flag: Normal cases are #flag:todo, #flag:fixMe, etc .. and the browser is aware of that and shows you a flag in the icon of the method. > > And have a specific tool to help the navigation (explore is fine for a > moment but...) > > > > This would allow us to have an idea on the technical debt inside the > system, broken down by areas if we start leveraging Packages. > > > > What I do not know is how much stress this would put on the system. Are > pragmas eating a lot or a just markers? > > > > Phil > > > > > -- Mariano http://marianopeck.wordpress.com

April 22, 2012

Re: [Pharo-project] Kernel jobs for 2.0

by Marcus Denker

On Apr 22, 2012, at 12:47 PM, Pavel Krivanek wrote: > Hi, > > I created Kernel jobs for the version 2.0. It uses separate set of > scripts so new big changes will not break 1.4. > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel%202.0/ > > Now is pointless to run them because 2.0 repository doesn't include > all packages. Some things that should be done: > - start Trello board for 2.0 ;-) Done: https://trello.com/board/pharo-2-0/4f7ae7371d239ca86263c96f > - the package Deprecated 14 should be replaced by Deprecated20. > - integrate basic Fuel packages (Fuel, FuelMetalevel, FuelPackageLoader + tests) > > -- Pavel > -- Marcus Denker -- http://marcusdenker.de

April 22, 2012

Re: [Pharo-project] How can I do literate programming?

by Tudor Girba

Excellent recipe :) Doru On 21 Apr 2012, at 15:30, Stephan Eggermont wrote: > You should probably use a MOOSE image if you want to do the modern equivalent > of literate programming. Instead of comments, drive your code from (behavioural) > tests, create glamour & mondrian browsers to visualize the design and quality > attributes of the code and use magritte style descriptions to declaratively describe > your domain. Then generate LaTeX & pictures from this for the paper trail. > > Stephan Eggermont -- www.tudorgirba.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

April 22, 2012

Re: [Pharo-project] The video about Athens

by Sean P. DeNigris

Igor Stasenko wrote > > this is strange. calling this function should simply work, since it > belongs to VM plugin. > Can you send me a stack trace? > Even stranger... now it's working! Maybe I just needed to restart after loading cairo... Looks *really* coooool!! Thanks. Sean -- View this message in context: http://forum.world.st/The-video-about-Athens-tp4571100p4578012.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 22, 2012

Re: [Pharo-project] Unresponsive 1.4 image

by Sean P. DeNigris

Sean P. DeNigris wrote > > Opening a browser got much slower the bigger I made my fonts, esp. the > code font it seemed... Opened issue http://code.google.com/p/pharo/issues/detail?id=5656 ... this seems like a different problem than the freezing... Sean -- View this message in context: http://forum.world.st/Unresponsive-1-4-image-tp4574693p4577994.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 22, 2012

Re: [Pharo-project] The video about Athens

by Igor Stasenko

On 21 April 2012 14:03, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote >> >> I get Generic failure >> Â Â fnSpec: #(#bool #ioRegisterSurface #(#ulong #aCairoSurfaceHandle #, >> #void #* #sqSurfaceDispatchPtr #, #int #* #idHolder)) >> Â Â module: #SurfacePlugin >> Â Â errorCode: 1 >> > > Igor, I guess you didn't run into this on Mac... any ideas why it's still > not working? > this is strange. calling this function should simply work, since it belongs to VM plugin. Can you send me a stack trace? > Sean > > -- > View this message in context: http://forum.world.st/The-video-about-Athens-tp4571100p4576317.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

April 22, 2012

[Pharo-project] Kernel jobs for 2.0

by Pavel Krivanek

Hi, I created Kernel jobs for the version 2.0. It uses separate set of scripts so new big changes will not break 1.4. https://ci.lille.inria.fr/pharo/view/Pharo-Kernel%202.0/ Now is pointless to run them because 2.0 repository doesn't include all packages. Some things that should be done: - start Trello board for 2.0 ;-) - the package Deprecated 14 should be replaced by Deprecated20. - integrate basic Fuel packages (Fuel, FuelMetalevel, FuelPackageLoader + tests) -- Pavel

April 22, 2012