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

Re: [Pharo-dev] RPackage: 'accessing' vs 'all accessing' Protocol

by stepharo

a mistake to me. I will resume my work on the automatic classifier and we should classify the complete image. Le 23/4/15 18:31, Sean P. DeNigris a Ã©crit : > What is the distinction of 'all accessing'? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/RPackage-accessing-vs-all-accessing-Protocol-tp482146… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 24, 2015

Re: [Pharo-dev] Updated WebDoc

by stepharo

Ok I saw with the version 30 it is much better :) Because I was surprised that someone could do anything with the 40. Now in that case we should not just put in it in the obscure file server but promoted to the website. Stef Le 24/4/15 09:41, Esteban Lorenzano a Ã©crit : > no, docs for pharo 4.0 are broken. > I will regenerate it next week (it takes hours). > > and about if it is useful: no experienced smalltalker will ever use it. > But newbies and google indexer will. > > So is good to have it and not much effort, I think. > > Esteban > >> On 24 Apr 2015, at 08:37, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Is it used? Is it useful? >> I tried to browse a method during 5 min and the result was really >> strange >> May be my browser is broken (safari) >> >> <jcdfgjeg..png> >> Le 23/4/15 17:15, Guillermo Polito a Ã©crit :<cbeahccf..png> >>> Quick answer, no. >>> >>> More elaborate one: >>> >>> The exports of the full pharo release (versions 3.0 and 4.0) exist >>> and were created by Esteban manually before each release. These, are >>> hosted here >>> >>> http://file-pharo.inria.fr/doc/4.0 >>> http://file-pharo.inria.fr/doc/3.0 >>> >>> We could run it automatically every day with latest pharo to avoid >>> the manual steps. I'll add that into my todo and check it later ^^. >>> >>> >>> El jue., 23 de abr. de 2015 a la(s) 4:09 p. m., Sven Van >>> Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> escribiÃ³: >>> >>> Great! Thank you. >>> >>> And the full image export, is that somewhere (done automatically) ? >>> >>> > On 23 Apr 2015, at 15:56, Guillermo Polito >>> <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> >>> wrote: >>> > >>> > Hi guys, >>> > >>> > I started yesterday to update WebDoc to work on latest Pharo. >>> I share with you my progress since yesterday: >>> > >>> > - Now it loads in latest pharo4 :) >>> > - fixed javascript errors and render issues >>> > - a little of love to the css styles >>> > - removed unused/not working features >>> > - made it work well when exporting not the full image >>> > - ci job is again green [1] >>> > >>> > you can see the result of applying webdoc to webdoc as the >>> result of the ci job here [2]. If you use it further, you'll see >>> there are still of course some problems, but I feel it is better >>> than before :). >>> > >>> > If you want to check it out, instructions in [3]. >>> > Download: >>> > >>> > Gofer it >>> > smalltalkhubUser: 'PharoExtras' project: 'WebDoc'; >>> > package:'ConfigurationOfWebDoc'; >>> > load. >>> > >>> > (#ConfigurationOfWebDoc asClass project version: >>> #development) load. >>> > >>> > Export: >>> > (WebDocExporter packages: {RPackageOrganizer default >>> packageNamed: 'YourProject'}) >>> > title: 'YourProject'; >>> > exportTo: './doc' asFileReference. >>> > >>> > >>> > Guille >>> > >>> > [1] https://ci.inria.fr/pharo-contribution/job/WebDoc/ >>> > [2] >>> https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm… >>> > [3]http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc >>> <http://www.smalltalkhub.com/#%21/%7EPharoExtras/WebDoc> >>> >>> >> >

April 24, 2015

Re: [Pharo-dev] Updated WebDoc

by Esteban Lorenzano

no, docs for pharo 4.0 are broken. I will regenerate it next week (it takes hours). and about if it is useful: no experienced smalltalker will ever use it. But newbies and google indexer will. So is good to have it and not much effort, I think. Esteban > On 24 Apr 2015, at 08:37, stepharo <stepharo(a)free.fr> wrote: > > Is it used? Is it useful? > I tried to browse a method during 5 min and the result was really strange > May be my browser is broken (safari) > > <jcdfgjeg..png> > Le 23/4/15 17:15, Guillermo Polito a Ã©crit :<cbeahccf..png> >> Quick answer, no. >> >> More elaborate one: >> >> The exports of the full pharo release (versions 3.0 and 4.0) exist and were created by Esteban manually before each release. These, are hosted here >> >> http://file-pharo.inria.fr/doc/4.0 <http://file-pharo.inria.fr/doc/4.0> >> http://file-pharo.inria.fr/doc/3.0 <http://file-pharo.inria.fr/doc/3.0> >> >> We could run it automatically every day with latest pharo to avoid the manual steps. I'll add that into my todo and check it later ^^. >> >> >> El jue., 23 de abr. de 2015 a la(s) 4:09 p. m., Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> escribiÃ³: >> Great! Thank you. >> >> And the full image export, is that somewhere (done automatically) ? >> >> > On 23 Apr 2015, at 15:56, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >> > >> > Hi guys, >> > >> > I started yesterday to update WebDoc to work on latest Pharo. I share with you my progress since yesterday: >> > >> > - Now it loads in latest pharo4 :) >> > - fixed javascript errors and render issues >> > - a little of love to the css styles >> > - removed unused/not working features >> > - made it work well when exporting not the full image >> > - ci job is again green [1] >> > >> > you can see the result of applying webdoc to webdoc as the result of the ci job here [2]. If you use it further, you'll see there are still of course some problems, but I feel it is better than before :). >> > >> > If you want to check it out, instructions in [3]. >> > Download: >> > >> > Gofer it >> > smalltalkhubUser: 'PharoExtras' project: 'WebDoc'; >> > package:'ConfigurationOfWebDoc'; >> > load. >> > >> > (#ConfigurationOfWebDoc asClass project version: #development) load. >> > >> > Export: >> > (WebDocExporter packages: {RPackageOrganizer default packageNamed: 'YourProject'}) >> > title: 'YourProject'; >> > exportTo: './doc' asFileReference. >> > >> > >> > Guille >> > >> > [1] https://ci.inria.fr/pharo-contribution/job/WebDoc/ <https://ci.inria.fr/pharo-contribution/job/WebDoc/> >> > [2] https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm… <https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm…> >> > [3]http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc <http://www.smalltalkhub.com/#%21/%7EPharoExtras/WebDoc> >> >> >

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by Esteban Lorenzano

I disagreeâ¦ DarkTheme is just for certain tastes, while regular one, while probably dated, is more âstandardâ. Also, DarkTheme is not ready. yeah, yeahâ¦ it works and works fine most of the timeâ¦ but not *all* the time (take for example find string dialogâ¦ I never found the time to fix it, and nobody complained soâ¦ :P). Finally. we need to adopt SVG icons (in my TODO list since a couple of months, I will deliver soon, I hope), otherwise they do not look good (this is a problem eclipse itself had itâ¦ we are just inheriting it :) ) But a good question would be: How can we push forward our UI, besides using a darker or clearer theme? I would like to hear some opinions here :) Esteban > On 24 Apr 2015, at 08:33, stepharo <stepharo(a)free.fr> wrote: > > comments about color is to be taken with care. > > > Le 24/4/15 02:48, Sean P. DeNigris a Ã©crit : >> Why didn't/don't we make it the default for 4.0? Everyone seems to love it, >> and people are commenting that the UI looks dated. >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Release-with-Dark-Theme-tp4821496.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> > >

April 24, 2015

Re: [Pharo-dev] Updated WebDoc

by stepharo

Is it used? Is it useful? I tried to browse a method during 5 min and the result was really strange May be my browser is broken (safari) Le 23/4/15 17:15, Guillermo Polito a Ã©crit : > Quick answer, no. > > More elaborate one: > > The exports of the full pharo release (versions 3.0 and 4.0) exist and > were created by Esteban manually before each release. These, are > hosted here > > http://file-pharo.inria.fr/doc/4.0 > http://file-pharo.inria.fr/doc/3.0 > > We could run it automatically every day with latest pharo to avoid the > manual steps. I'll add that into my todo and check it later ^^. > > > El jue., 23 de abr. de 2015 a la(s) 4:09 p. m., Sven Van Caekenberghe > <sven(a)stfx.eu <mailto:sven@stfx.eu>> escribiÃ³: > > Great! Thank you. > > And the full image export, is that somewhere (done automatically) ? > > > On 23 Apr 2015, at 15:56, Guillermo Polito > <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > > > > Hi guys, > > > > I started yesterday to update WebDoc to work on latest Pharo. I > share with you my progress since yesterday: > > > > - Now it loads in latest pharo4 :) > > - fixed javascript errors and render issues > > - a little of love to the css styles > > - removed unused/not working features > > - made it work well when exporting not the full image > > - ci job is again green [1] > > > > you can see the result of applying webdoc to webdoc as the > result of the ci job here [2]. If you use it further, you'll see > there are still of course some problems, but I feel it is better > than before :). > > > > If you want to check it out, instructions in [3]. > > Download: > > > > Gofer it > > smalltalkhubUser: 'PharoExtras' project: 'WebDoc'; > > package:'ConfigurationOfWebDoc'; > > load. > > > > (#ConfigurationOfWebDoc asClass project version: #development) > load. > > > > Export: > > (WebDocExporter packages: {RPackageOrganizer default > packageNamed: 'YourProject'}) > > title: 'YourProject'; > > exportTo: './doc' asFileReference. > > > > > > Guille > > > > [1] https://ci.inria.fr/pharo-contribution/job/WebDoc/ > > [2] > https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm… > > [3]http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc > <http://www.smalltalkhub.com/#%21/%7EPharoExtras/WebDoc> > >

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by stepharo

comments about color is to be taken with care. Le 24/4/15 02:48, Sean P. DeNigris a Ã©crit : > Why didn't/don't we make it the default for 4.0? Everyone seems to love it, > and people are commenting that the UI looks dated. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Release-with-Dark-Theme-tp4821496.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 24, 2015

Re: [Pharo-dev] [Pharo-users] QualityAssistant v0.4

by stepharo

Le 23/4/15 19:57, Ben Coman a Ã©crit : > Making code critics more visible --> expect a flood of opinions about > the usefulness of rules and what they mean, and Uko should not be > responsible for all of them :) This is an area where gathering usage > statistics (similar to Spotter) might be very useful - if there was > some way to record which rules people have issues with. This was planned :) I envisioned that and we brainstorm with Yko around 8 months ago :). Stef > cheers -ben > > On Thu, Apr 23, 2015 at 12:06 AM, Cyril Ferlicot > <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: > > Hi ! > Your quality assistant say to me "repeated method in the superclass" > (If a class is overriding a method, it should use a different code. Is > meaningless to have a method in a class and in its superclass) but > i've 3 methods into my class and all overrides a method with "^ > shouldBeImplemented" in the superclass. > I think something is wrong with this warning :) > > > On 22 April 2015 at 16:45, Yuriy Tymchuk <yuriy.tymchuk(a)me.com > <mailto:yuriy.tymchuk@me.com>> wrote: > > Good point, this brings up two problems. > > > > 1) The rule can improve detection by checking the type is the > message is > > sent to self > > 2) Automatic fixing should display the changes and letting you > decide > > whether you want to apply them. > > > > 1st will take some time. 2nd will be soon in QA :) > > > > Uko > > > > > > On 22 Apr 2015, at 16:33, Johan Fabry <jfabry(a)dcc.uchile.cl > <mailto:jfabry@dcc.uchile.cl>> wrote: > > > > Some weird behavior in quality assistant. Have a look at this > method: > > > > duplicateVar: aVarName > > > > self show: 'Var: ', aVarName, ' redefinition ignored'. > > > > This raises the issue: âUse cascaded nextPutAll:âs instead of #, in > > nextPutAll:â It also pops up the automatic rewrite icon, so I > clicked on it > > to see how it would transform the code. Result: > > > > duplicateVar: aVarName > > self > > show: 'Var: ' , aVarName; > > show: ' redefinition ignored' > > > > Needless to say, thatâs not a behavior preserving transformation. > > > > > > On Apr 22, 2015, at 03:58, Yuriy Tymchuk <yuriy.tymchuk(a)me.com > <mailto:yuriy.tymchuk@me.com>> wrote: > > > > Please give me a feedback about your experience, as I want to > make it even > > more useful. Either write me an email, or open an entry at: > > https://github.com/Uko/QualityAssistant/issues > > > > > > > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > > > Johan Fabry - http://pleiad.cl/~jfabry > <http://pleiad.cl/%7Ejfabry> > > PLEIAD lab - Computer Science Department (DCC) - University > of Chile > > > > > > > > -- > Cheers > Cyril Ferlicot > >

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by Ben Coman

Its a bit late to make such a prominent change. Maybe in the Welcome info just note how to activate it. cheers -ben On Fri, Apr 24, 2015 at 7:48 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Why didn't/don't we make it the default for 4.0? Everyone seems to love it, > and people are commenting that the UI looks dated. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Release-with-Dark-Theme-tp4821496.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 24, 2015

Release with Dark Theme

by Sean P. DeNigris

Why didn't/don't we make it the default for 4.0? Everyone seems to love it, and people are commenting that the UI looks dated. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Release-with-Dark-Theme-tp4821496.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 23, 2015

Re: [Pharo-dev] [Pharo-users] QualityAssistant v0.4

by Mariano Martinez Peck

Thank you Yuiry. Super cool. I have just start migrating my client app to 4.0 and start using it full day long. And the first thing I did (after setting dark theme) is to load this tool. I also agree with the rest that I don't see much of a difference regarding modularity whether this tool is loaded in the image by default or not. On the contrary, whether it can be cleanly unloaded or not, which are and how managed are the dependencies etc, does refer to modularity. But that's my opinion only. Cheers, On Thu, Apr 23, 2015 at 2:51 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > It is coming ;) > > On 23 Apr 2015, at 18:57, Ben Coman <btc(a)openinworld.com> wrote: > > Making code critics more visible --> expect a flood of opinions about the > usefulness of rules and what they mean, and Uko should not be responsible > for all of them :) This is an area where gathering usage statistics > (similar to Spotter) might be very useful - if there was some way to record > which rules people have issues with. > cheers -ben > > On Thu, Apr 23, 2015 at 12:06 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com > > wrote: > >> Hi ! >> Your quality assistant say to me "repeated method in the superclass" >> (If a class is overriding a method, it should use a different code. Is >> meaningless to have a method in a class and in its superclass) but >> i've 3 methods into my class and all overrides a method with "^ >> shouldBeImplemented" in the superclass. >> I think something is wrong with this warning :) >> >> >> On 22 April 2015 at 16:45, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> > Good point, this brings up two problems. >> > >> > 1) The rule can improve detection by checking the type is the message is >> > sent to self >> > 2) Automatic fixing should display the changes and letting you decide >> > whether you want to apply them. >> > >> > 1st will take some time. 2nd will be soon in QA :) >> > >> > Uko >> > >> > >> > On 22 Apr 2015, at 16:33, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: >> > >> > Some weird behavior in quality assistant. Have a look at this method: >> > >> > duplicateVar: aVarName >> > >> > self show: 'Var: ', aVarName, ' redefinition ignored'. >> > >> > This raises the issue: âUse cascaded nextPutAll:âs instead of #, in >> > nextPutAll:â It also pops up the automatic rewrite icon, so I clicked >> on it >> > to see how it would transform the code. Result: >> > >> > duplicateVar: aVarName >> > self >> > show: 'Var: ' , aVarName; >> > show: ' redefinition ignored' >> > >> > Needless to say, thatâs not a behavior preserving transformation. >> > >> > >> > On Apr 22, 2015, at 03:58, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> > >> > Please give me a feedback about your experience, as I want to make it >> even >> > more useful. Either write me an email, or open an entry at: >> > https://github.com/Uko/QualityAssistant/issues >> > >> > >> > >> > >> > ---> Save our in-boxes! http://emailcharter.org <--- >> > >> > Johan Fabry - http://pleiad.cl/~jfabry >> > PLEIAD lab - Computer Science Department (DCC) - University of Chile >> > >> > >> >> >> >> -- >> Cheers >> Cyril Ferlicot >> >> > > -- Mariano http://marianopeck.wordpress.com

April 23, 2015