- Pharo-dev - lists.pharo.org

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

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

by Cyril Ferlicot Delbecque

On 24/05/2016 04:00, Sean P. DeNigris wrote: > Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages > with no class comments. How would a new user discover what these are? > BlueInk is the new configurable formatter. In Chroma there is only one classe with a class comment. Flashback is the new decompiler. Renkaku I don't know what it is but I know this is use by QualityAssistant. -- 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 stepharo

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

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

by Esteban Lorenzano

> 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 :) 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

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

by Esteban Lorenzano

> On 24 May 2016, at 04:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > 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. I do agree with this, but we need to find a way to do itâ¦ But we need to think how to do it. My main idea is to offer âviewsâ (always configurable in settings so power users can take what they want), something like: - using manifests, we can add tagging of packages. For instance, Nautilus can be tagged #browser, Monticelo #vcs, #versionControl, etcâ¦ so we can offer searchsâ¦ and even offer a nautlus a view âby tagââ¦ - another view can be âhide system packagesâ: user does not need to directly see many of those packages, so we could filter them (I would also use a property in manifests for this) Another thing, not related to views but possible and easy to implement (but not to complete, of course) I want to add is the possibility of package comments (also using the manifest) so we can offer a high level view (often a class does not explains what a package is, like Renrakuâ¦ that can be a nice (?, no idea what it does means) fantasy name, but it does not offer any explanation of what it is for). I think this two ideas can make the environment a lot betterâ¦ what do you think? Esteban

May 24, 2016

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

by stepharo

When people use a configuration and add a description hovering over the package show you the description and this helps for real. 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

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60030 Home: https://github.com/pharo-project/pharo-core

May 24, 2016

[pharo-project/pharo-core] eaac18: 60030

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: eaac18e0a2053591d14e561dc7c0df244ee82296 https://github.com/pharo-project/pharo-core/commit/eaac18e0a2053591d14e561d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-24 (Tue, 24 May 2016) Changed paths: R Morphic-Widgets-Windows.package/WindowActivated.class/instance/as yet unclassified/isActivated.st A Morphic-Widgets-Windows.package/WindowActivated.class/instance/testing/isActivated.st R Morphic-Widgets-Windows.package/WindowAnnouncement.class/instance/as yet unclassified/isActivated.st R Morphic-Widgets-Windows.package/WindowAnnouncement.class/instance/as yet unclassified/isDeActivated.st A Morphic-Widgets-Windows.package/WindowAnnouncement.class/instance/testing/isActivated.st A Morphic-Widgets-Windows.package/WindowAnnouncement.class/instance/testing/isDeActivated.st R Morphic-Widgets-Windows.package/WindowCollapsed.class/instance/as yet unclassified/isCollapsed.st A Morphic-Widgets-Windows.package/WindowCollapsed.class/instance/testing/isCollapsed.st R Morphic-Widgets-Windows.package/WindowDeActivated.class/instance/as yet unclassified/isDeActivated.st A Morphic-Widgets-Windows.package/WindowDeActivated.class/instance/testing/isDeActivated.st R Morphic-Widgets-Windows.package/WindowExpanded.class/instance/as yet unclassified/isExpanded.st A Morphic-Widgets-Windows.package/WindowExpanded.class/instance/testing/isExpanded.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/source/splitCascadeBetween_from_.st M Refactoring-Core.package/RBSplitCascadeRefactoring.class/README.md M Refactoring-Environment.package/RBBrowserEnvironment.class/instance/accessing-classes/allClasses.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60029.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60030.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60029.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60030.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60030 18296 DNU on split cascade refactoring https://pharo.fogbugz.com/f/cases/18296 18298 duplicate elements in RBClassEnvironments result set https://pharo.fogbugz.com/f/cases/18298 18314 wrong or missing metho protokoll name for WindowAnnouncements https://pharo.fogbugz.com/f/cases/18314 http://files.pharo.org/image/60/60030.zip

May 24, 2016