Pharo-dev

By thread

pharo-dev@lists.pharo.org

3 participants
144635 messages

Screenshot of Pharo 64 bits

by ClÃ©ment Bera

Today I helped Esteban porting the 32 to 64 bits bootstrap to Pharo. It looks like we have a Pharo 64 bits image on 64 bits VM running on Mac & Linux. Here is the wonderful screenshot showing the amazing result: [image: Inline image 1]

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Yuriy Tymchuk

By the way, we can add a rule that checks if a package has a comment. Because for example I had no idea that you can comment packages. > On 24 May 2016, at 14:37, Cyril Ferlicot Delbecque <cyril.ferlicot(a)gmail.com> wrote: > > > > On 24/05/2016 13:19, Christophe Demarey wrote: >> >>> Le 24 mai 2016 Ã 10:08, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : >>> >>> there is a space: same as class comment now. >> >> >> only for the class comment, not for other package metadata >> > > Maybe the package comment can be at the place of the class comment when > the package is selected and for the other metadatas a button that would > open a new window can be add to Nautilus? For now there is some free > space close to the scope button. > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France >

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Cyril Ferlicot Delbecque

On 24/05/2016 13:19, Christophe Demarey wrote: > >> Le 24 mai 2016 Ã 10:08, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : >> >> there is a space: same as class comment now. > > > only for the class comment, not for other package metadata > Maybe the package comment can be at the place of the class comment when the package is selected and for the other metadatas a button that would open a new window can be add to Nautilus? For now there is some free space close to the scope button. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Yuriy Tymchuk

> On 24 May 2016, at 10:09, Cyril Ferlicot Delbecque <cyril.ferlicot(a)gmail.com> wrote: > > > > On 24/05/2016 07:44, Sven Van Caekenberghe wrote: >> >> The missing class comments are totally unacceptable, we should refuse these. >> > > +10000 > > It is really frustrating to take free time to improve the comments of > the current classes and to see that there is dozens of classes without > comment added in the same time. > >> Apart from BlueInk (a code formatter), I have never heard or seen the others ;-) >> >>> How would a new user discover what these are? >> >> If these are important to end users, they should be mentioned somewhere. >> > > Another important think about it is to remember that the user don't know > what the community knows. I see for example setting talking about > Renkaku, about Growl, about a lot of stuffâ¦ But how as a use should I > know what I need to do with the setting "Renkaku's rule"? This is only > an example (I do not target you Yuriy :) ) but there is a lot everywhere > in Pharo. Because people should give more feedback. Now as you point this out I know that I have to improve. But at the moment when I was implementing the stuff my main goal was to provide the functionality somewhere else then just a script on class side, and after Iâve managed to copy the bottom and make it work I was very happy and didnât think that itâs not clear for users. Now I know and can elaborate on that. > >> This has been suggested before. I actually like the current approach, I would not want to click open trees all the time. >> > > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France >

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Yuriy Tymchuk

> On 24 May 2016, at 04:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages > with no class comments. How would a new user discover what these are? How comes that Renraku has no class comments?

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Esteban Lorenzano

> On 24 May 2016, at 13:19, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > >> Le 24 mai 2016 Ã 10:08, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : >> >> there is a space: same as class comment now. > > > only for the class comment, not for other package metadata you can use the same: if package is selected, then shows package comment, if class is selected, then class comment.

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Christophe Demarey

> Le 24 mai 2016 Ã 10:08, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > there is a space: same as class comment now. only for the class comment, not for other package metadata

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Cyril Ferlicot Delbecque

On 24/05/2016 07:44, Sven Van Caekenberghe wrote: > > The missing class comments are totally unacceptable, we should refuse these. > +10000 It is really frustrating to take free time to improve the comments of the current classes and to see that there is dozens of classes without comment added in the same time. > Apart from BlueInk (a code formatter), I have never heard or seen the others ;-) > >> How would a new user discover what these are? > > If these are important to end users, they should be mentioned somewhere. > Another important think about it is to remember that the user don't know what the community knows. I see for example setting talking about Renkaku, about Growl, about a lot of stuffâ¦ But how as a use should I know what I need to do with the setting "Renkaku's rule"? This is only an example (I do not target you Yuriy :) ) but there is a lot everywhere in Pharo. > This has been suggested before. I actually like the current approach, I would not want to click open trees all the time. > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Esteban Lorenzano

there is a space: same as class comment now. > On 24 May 2016, at 10:00, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > I already have support for package comments with cargo (including ui) using the package manifest. In fact, it is more. I have support for package metadata on packages (cf screenshot) > The question is how do you integrate that with current browser? When you select a package, the class creation template is displayed and there is no much space to display other things. > > <Capture dâÃ©cran 2016-05-24 Ã 09.55.44.png> > > > >> Le 24 mai 2016 Ã 09:15, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> a Ã©crit : >> >> >> >> Le 24/5/16 Ã 08:21, Esteban Lorenzano a Ã©crit : >>>> On 24 May 2016, at 08:05, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: >>>> >>>> When people use a configuration and add a description >>>> >>>> hovering over the package show you the description and this helps for real. >>> yes, this is super coolâ¦ but I would like the possibility to toggle a âcommentâ for packages too :) >> >> Sure I push the manifest also for that. >> So let us make every package gets a manifest and add a button to display the description. >>> >>> Esteban >>> >>>> >>>> Stef >>>> >>>> Le 24/5/16 Ã 04:00, Sean P. DeNigris a Ã©crit : >>>>> Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages >>>>> with no class comments. How would a new user discover what these are? >>>>> >>>>> Also, not new to Pharo 5.0, but thinking as a new user... Nautilus presents >>>>> the system as an overwhelming mess of top level packages. I guess this is >>>>> because we're showing packages, which are a dependency/SCM artifact, instead >>>>> of capturing/representing logical domain relations. There are so many >>>>> packages that start with e.g. System. It is not relevant to the user that >>>>> they are packaged separately, unless one is hacking that library. These >>>>> should all be collapsed under a top-level System node. >>>>> >>>>> >>>>> >>>>> ----- >>>>> Cheers, >>>>> Sean >>>>> -- >>>>> View this message in context: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954p4896956.html <http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954p4896956.html> >>>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com <http://nabble.com/>. >>>>> >>>>> >>>> >>> >>> >> >> >

May 24, 2016

Re: [Pharo-dev] What's new in Pharo 5.0

by Christophe Demarey

I already have support for package comments with cargo (including ui) using the package manifest. In fact, it is more. I have support for package metadata on packages (cf screenshot) The question is how do you integrate that with current browser? When you select a package, the class creation template is displayed and there is no much space to display other things. > Le 24 mai 2016 Ã 09:15, stepharo <stepharo(a)free.fr> a Ã©crit : > > > > Le 24/5/16 Ã 08:21, Esteban Lorenzano a Ã©crit : >>> On 24 May 2016, at 08:05, stepharo <stepharo(a)free.fr> wrote: >>> >>> When people use a configuration and add a description >>> >>> hovering over the package show you the description and this helps for real. >> yes, this is super coolâ¦ but I would like the possibility to toggle a âcommentâ for packages too :) > > Sure I push the manifest also for that. > So let us make every package gets a manifest and add a button to display the description. >> >> Esteban >> >>> >>> Stef >>> >>> Le 24/5/16 Ã 04:00, Sean P. DeNigris a Ã©crit : >>>> Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages >>>> with no class comments. How would a new user discover what these are? >>>> >>>> Also, not new to Pharo 5.0, but thinking as a new user... Nautilus presents >>>> the system as an overwhelming mess of top level packages. I guess this is >>>> because we're showing packages, which are a dependency/SCM artifact, instead >>>> of capturing/representing logical domain relations. There are so many >>>> packages that start with e.g. System. It is not relevant to the user that >>>> they are packaged separately, unless one is hacking that library. These >>>> should all be collapsed under a top-level System node. >>>> >>>> >>>> >>>> ----- >>>> Cheers, >>>> Sean >>>> -- >>>> View this message in context: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954p4896956.html >>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>>> >>>> >>> >> >> > >

May 24, 2016

Jump to page: