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

[pharo-project/pharo-core]

by GitHub

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

June 11, 2015

[pharo-project/pharo-core] eadef9: 50105

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: eadef90589fff2e2b12c6773b0a0acc98cf97b08 https://github.com/pharo-project/pharo-core/commit/eadef90589fff2e2b12c6773… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-11 (Thu, 11 Jun 2015) Changed paths: M ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/README.md A ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/baselines/baseline05_.st A ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/baselines/baseline06_.st M ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/symbolic versions/development_.st M ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/symbolic versions/stable_.st A ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/versions/version05_.st M NautilusRefactoring.package/ChangesBrowser.class/definition.st A NautilusRefactoring.package/ChangesBrowser.class/instance/accessing/changes_.st A NautilusRefactoring.package/ChangesBrowser.class/instance/accessing/pickedChanges.st R NautilusRefactoring.package/ChangesBrowser.class/instance/api/buildDiffFor_.st R NautilusRefactoring.package/ChangesBrowser.class/instance/api/change_.st A NautilusRefactoring.package/ChangesBrowser.class/instance/private/buildDiffFor_.st R NautilusRefactoring.package/ChangesBrowser.class/instance/private/changes_.st R NautilusRefactoring.package/ChangesBrowser.class/instance/private/pickedChanges.st M NautilusRefactoring.package/ChangesBrowser.class/instance/private/updateChanges.st R RPackage-Core.package/RPackage.class/instance/accessing/removeDefinedMethod_forClass_.st R RPackage-Core.package/RPackage.class/instance/system compatibility/includesMethodReference_.st A RPackage-Core.package/RPackageOrganizer.class/class/class initialization/registerInterestToSystemAnnouncement.st A RPackage-Core.package/RPackageOrganizer.class/class/class initialization/unregisterInterestToSystemAnnouncement.st A RPackage-Core.package/RPackageOrganizer.class/class/private/methodAdded_.st A RPackage-Core.package/RPackageOrganizer.class/class/quieries/isPackageDefinedForClass_.st R RPackage-Core.package/RPackageSet.class/instance/system compatibility/includesMethodReference_.st A RPackage-Core.package/extension/MCPackage/instance/correspondingRPackage.st A RPackage-Core.package/extension/MCPackageManager/class/unregisterForNotifications.st A RPackage-Core.package/extension/String/instance/asPackage.st A RPackage-Core.package/extension/String/instance/asPackageIfAbsent_.st R RPackage-SystemIntegration.package/ClassRepackaged.class/README.md R RPackage-SystemIntegration.package/ClassRepackaged.class/class/instance creation/classRepackaged_oldPackage_newPackage_.st R RPackage-SystemIntegration.package/ClassRepackaged.class/definition.st R RPackage-SystemIntegration.package/ClassRepackaged.class/instance/accessing/classRepackaged.st R RPackage-SystemIntegration.package/ClassRepackaged.class/instance/accessing/classRepackaged_.st R RPackage-SystemIntegration.package/ClassRepackaged.class/instance/accessing/newPackage.st R RPackage-SystemIntegration.package/ClassRepackaged.class/instance/accessing/newPackage_.st R RPackage-SystemIntegration.package/ClassRepackaged.class/instance/accessing/oldPackage.st R RPackage-SystemIntegration.package/ClassRepackaged.class/instance/accessing/oldPackage_.st R RPackage-SystemIntegration.package/MethodRepackaged.class/README.md R RPackage-SystemIntegration.package/MethodRepackaged.class/class/instance creation/methodRepackaged_oldPackage_newPackage_.st R RPackage-SystemIntegration.package/MethodRepackaged.class/definition.st R RPackage-SystemIntegration.package/MethodRepackaged.class/instance/accessing/methodRepackaged.st R RPackage-SystemIntegration.package/MethodRepackaged.class/instance/accessing/methodRepackaged_.st R RPackage-SystemIntegration.package/MethodRepackaged.class/instance/accessing/newPackage.st R RPackage-SystemIntegration.package/MethodRepackaged.class/instance/accessing/newPackage_.st R RPackage-SystemIntegration.package/MethodRepackaged.class/instance/accessing/oldPackage.st R RPackage-SystemIntegration.package/MethodRepackaged.class/instance/accessing/oldPackage_.st R RPackage-SystemIntegration.package/PackageChecker.class/README.md R RPackage-SystemIntegration.package/PackageChecker.class/definition.st R RPackage-SystemIntegration.package/PackageChecker.class/instance/check/check.st R RPackage-SystemIntegration.package/extension/MCPackage/instance/correspondingRPackage.st R RPackage-SystemIntegration.package/extension/MCPackageManager/class/unregisterForNotifications.st R RPackage-SystemIntegration.package/extension/RPackageOrganizer/class/isPackageDefinedForClass_.st R RPackage-SystemIntegration.package/extension/RPackageOrganizer/class/methodAdded_.st R RPackage-SystemIntegration.package/extension/RPackageOrganizer/class/registerInterestToSystemAnnouncement.st R RPackage-SystemIntegration.package/extension/RPackageOrganizer/class/unregisterInterestToSystemAnnouncement.st R RPackage-SystemIntegration.package/extension/String/instance/asPackage.st R RPackage-SystemIntegration.package/extension/String/instance/asPackageIfAbsent_.st R RPackage-SystemIntegration.package/extension/SystemAnnouncer/instance/classRepackaged_from_to_.st R RPackage-SystemIntegration.package/extension/SystemAnnouncer/instance/methodRepackaged_from_to_.st A RPackage-Tests.package/PackageChecker.class/README.md A RPackage-Tests.package/PackageChecker.class/definition.st A RPackage-Tests.package/PackageChecker.class/instance/check/check.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50104.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50105.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50104.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50105.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Announcements.package/ClassRepackaged.class/README.md A System-Announcements.package/ClassRepackaged.class/class/instance creation/classRepackaged_oldPackage_newPackage_.st A System-Announcements.package/ClassRepackaged.class/definition.st A System-Announcements.package/ClassRepackaged.class/instance/accessing/classRepackaged.st A System-Announcements.package/ClassRepackaged.class/instance/accessing/classRepackaged_.st A System-Announcements.package/ClassRepackaged.class/instance/accessing/newPackage.st A System-Announcements.package/ClassRepackaged.class/instance/accessing/newPackage_.st A System-Announcements.package/ClassRepackaged.class/instance/accessing/oldPackage.st A System-Announcements.package/ClassRepackaged.class/instance/accessing/oldPackage_.st A System-Announcements.package/MethodRepackaged.class/README.md A System-Announcements.package/MethodRepackaged.class/class/instance creation/methodRepackaged_oldPackage_newPackage_.st A System-Announcements.package/MethodRepackaged.class/definition.st A System-Announcements.package/MethodRepackaged.class/instance/accessing/methodRepackaged.st A System-Announcements.package/MethodRepackaged.class/instance/accessing/methodRepackaged_.st A System-Announcements.package/MethodRepackaged.class/instance/accessing/newPackage.st A System-Announcements.package/MethodRepackaged.class/instance/accessing/newPackage_.st A System-Announcements.package/MethodRepackaged.class/instance/accessing/oldPackage.st A System-Announcements.package/MethodRepackaged.class/instance/accessing/oldPackage_.st A System-Announcements.package/SystemAnnouncer.class/instance/triggering/classRepackaged_from_to_.st A System-Announcements.package/SystemAnnouncer.class/instance/triggering/methodRepackaged_from_to_.st Log Message: ----------- 50105 15735 Start to move RPackage-SystemIntegration to into RPackage https://pharo.fogbugz.com/f/cases/15735 15744 CatalogBrowser moved to PharoExtras https://pharo.fogbugz.com/f/cases/15744 15742 Small clean up in ChangesBrowser https://pharo.fogbugz.com/f/cases/15742 http://files.pharo.org/image/50/50105.zip

June 11, 2015

Re: [Pharo-dev] New Tool: Catalog Browser in Pharo 5.0

by Torsten Bergmann

Esteban wrote: > > If you want to contribute just tell Esteban so he can add you to the project. > well noâ¦ I just made it public access, so anyone can commit changes thereâ¦ :) > (And I will move it to PharoExtras team soon, thatâs the correct place once integrated in imageâ¦ but wellâ¦ time is tyrant :P) I moved it to PharoExtras, MCZs are copied and config adopted (with a new version 0.5): http://smalltalkhub.com/#!/~PharoExtras/CatalogBrowser/ This is tracked for integration in: https://pharo.fogbugz.com/f/cases/15744/CatalogBrowser-moved-to-PharoExtras BTW: IMHO we can close https://pharo.fogbugz.com/f/cases/15703/ Thanks T.

June 11, 2015

Re: [Pharo-dev] Pratt Parsers for PetitParser

by Camille

> On 11 Jun 2015, at 09:30, Jan KurÅ¡ <kurs(a)iam.unibe.ch> wrote: > > That sounds really cool and useful extension. > Thank you Jan! > Regarding the furthest failure, the core of the problem is the distinction between an error and a failure. Error reports on a problem in the input, while failure is information for choice parser combinator. In general, the furthest failure is a better approximation of an error than the last failure, so we use it. > > I am not sure what exactly is the problem in case of PrattParser. I guess the last failure gives better results for a user? > Yes, with furthest failure I get errors from tokenization instead of my errors. For exemple with the calculator grammar I gave in my first mail when I parse â1+â the furthestFailure is â$- expected at 2â whereas I return âexpression expected at 2â because there's a whole expression missing. Same thing with â(1+2â that returns âdigit expected at 4â instead of â$) expected at 4â. But furthest failure gives wrong messages in other cases to. Consider this sequence parser: keyword := #letter asParser plus , $: asParser. keyword parse: âfoo' This returns 'letter expected at 3â, but no matter how many letters I add to the end Iâll still get âletter expectedâ. I want to get what is really missing: '$: expected at 3â. Maybe returning the âlatest furthest failureâ instead of the âfirst furthest failureâ could solves the problem here (i.e. replacing > with >= in PPContext>>#noteFailure:)? > One has to consider a pratt parser included in the normal parser, e. g. Expressions parsed by pratt in a Java Grammar. Depending where an error occurs, different strategy for choosing the proper failure is necessary :-/ > Indeed, my hack (redefining #parseWithContext:) works only when the Pratt parser is the top parser, but a soon as I compose it Iâm screwed because only parseOn: is sent to the Pratt parser. Thatâs why I wonder if letting the parser decide what to return wouldnât solve the problem: by default the furthest failure but special parsers can still decide. > Regarding tokenization, there is a message token, that returns PPTokenParser, which transforms a parsed input into the PPToken object. Perhaps this might be helpful? > The Pratt tokens are special: a token points back to the parser that generated it (its âkindâ). PPTokenKind subclasses PPFlatteningParser and generates instances of PPPrattToken. A PPTokenKind stores the precedence, the action to be executed when a token of this kind is met at the start of an expression (for terminals and prefixes) and the action to be executed when a token is met in the middle of an expression (for postfixes and infixes). Cheers, Camille > Cheers Jan > > > On Wed, Jun 10, 2015, 20:52 Richard Sargent <richard.sargent(a)gemtalksystems.com <mailto:richard.sargent@gemtalksystems.com>> wrote: > camille teruel wrote > >> On 10 Jun 2015, at 19:11, Chris Cunningham < > > > cunningham.cb@ > > > > wrote: > >> > >> Inteteresting.... > >> > >> On Wed, Jun 10, 2015 at 9:36 AM, Camille < > > > camille.teruel@ > > > <mailto: > > > camille.teruel@ > > > >> wrote: > >> Hello Pharoers and Moosers, > >> > >> I did a Pratt parser extension for PetitParser. > >> > >> > > <snip> > > > >> @PP Devs: > >> I had trouble with the PPContext furthestFailure that is taken into > >> account instead of the failures I return, so I had to redefine > >> #parseWithContext: to return the failures I want. The results given by > >> furthestFailure were not very meaningful in my case (the same is true for > >> PPExpressionParser btw). > >> But I guess it was introduced because it gives good results in other > >> cases. > >> So would it be possible to change this behavior to let the parser decide > >> if it returns the furthestFailure or the original failure? > >> > >> The intent behind the furthestFailure is that it give the failure that > >> gets the furthest into the source stream. It is most useful when there > >> are embedded choice operators in the parser - the original/pre furthest > >> behaviour would return the last failure, which depending on the incoming > >> stream and the order of the choice options could be significantly not > >> useful. > >> > >> I ran into this when working with the sql parser, which started off with > >> the outer choice of (by memory): > >> ^ selectStatement / insertStatement / updateStatement / > >> deleteStatement > >> If I was trying to part a select statement that had an error at the very > >> end of the statement, the parser would return an error talking about how > >> the incoming stream failed in deleteStatement. Not useful. > >> > >> I would be saddened if this further failure was not available. > > > > Yes in that case returning the furthest failure gives better results. > > However, this donât give meaningful messages in all cases. > > For exemple with the calculator I gave in my previous message, if I parse > > â1+â I want to get âexpression expected at: 2â but instead it returns â$- > > expected at 2'. > > Iâm not proposing to remove this feature but to let parsers decide to use > > it or not. > > Something like (changes in bold): > > > > PPParser>>parseWithContext: context > > | result | > > context initializeFor: self. > > result := self parseOn: context. > > > > "Return the furthest failure, it gives better results than the last > > failure" > > (result isPetitFailure and: [ self wantsFurthestFailure and: [ context > > furthestFailure notNil ] ]) > > ifTrue: [ ^ context furthestFailure ]. > > ^ result > > This screams at me. Why not just delegate to the context and use a context > that returns the preferred failure? e.g. end with: > ^context preferredResultFor: result. > > > > > > PPParser>>wantsFurthestFailure > > ^ true > > > > Like this, one can return the failures he wants. > > > > PPPrattParser>>wantsFurthestFailure > > ^ false > > > > > > Camille > > > >> > >> -cbc > > > > > > -- > View this message in context: http://forum.world.st/Pratt-Parsers-for-PetitParser-tp4831456p4831486.html <http://forum.world.st/Pratt-Parsers-for-PetitParser-tp4831456p4831486.html> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

June 11, 2015

Re: [Pharo-dev] New Tool: Catalog Browser in Pharo 5.0

by Esteban Lorenzano

Hi, > On 11 Jun 2015, at 08:55, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > maybe you already noticed. The latest update for Pharo 5 which is 50103 (see [1]). > includes a new tool called "Catalog Browser". > > Where to go > =========== > > You will find it under "Tools" -> "Catalog Browser" and it will display the > configs together with the catalog metadata like project description. this is the most important, so people can actually know what a project is about :) but of course, that depends on you providing information in catalog methods! > > The code is managed with a configuration similar to what we have for > a few other packages/projects. The tool was written by Esteban Lorenzano with small > improvements like spotter integration from my side. Feel free to contribute more features. > > The repository can be found on SmalltalkHub [2]. > > This new tool basically gives you access to all available configurations > aggregated at [3]. You can use a small UI to search and load the configs > (see world menu -> "Tools" -> "Catalog Browser". > > But you can also use Spotter to load a config. > > Example on how to load ScriptManager config: > ============================================ > - open Spotter (SHIFT + ENTER on Windows, ...) > - type in "Script" and you will find a spotter category "Catalog Projects" with "ScriptManager" in it > - just hit enter and the config is loaded > > Same for all others, so try with "Seaside", "MongoTalk", ... > > In the short/mid-term this new tool should replace the existing config browser as it > gives more informations about the projects. > > What to do next: > ================ > - give feedback > - we should update all our configs with catalog descriptions please, this is vital to have a good entry point to your projects. > - it would be nice if the spotter integration would include also a preview of the project > description +1 > - ... > > If you want to contribute just tell Esteban so he can add you to the project. well noâ¦ I just made it public access, so anyone can commit changes thereâ¦ :) (And I will move it to PharoExtras team soon, thatâs the correct place once integrated in imageâ¦ but wellâ¦ time is tyrant :P) Esteban ps: Thanks Torsten to look at it! > > Thanks > Esteban & Torsten > > [1] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-June/110964… > [2] http://www.smalltalkhub.com/#!/~estebanlm/CatalogBrowser > [3] http://catalog.pharo.org/catalog/json<catalogBrowser.png>

June 11, 2015

[pharo-project/pharo-core]

by GitHub

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

June 11, 2015

[pharo-project/pharo-core] 8d0d4b: 50104

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 8d0d4b83a51fc2534b07dc6a7b56038f792cc62f https://github.com/pharo-project/pharo-core/commit/8d0d4b83a51fc2534b07dc6a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-11 (Thu, 11 Jun 2015) Changed paths: A ProfStef-Core.package/AbstractTutorial.class/class/tutorial metainfo/contentsOfTutorials.st A ProfStef-Core.package/PharoTutorial.class/class/accessing/contents.st M ProfStef-Help.package/PharoTutorialHelp.class/class/pages/listOfTutorials.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50103.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50104.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50103.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50104.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50104 15636 PharoTutorial contents https://pharo.fogbugz.com/f/cases/15636 15731 Kill the last two #asTimeStamp methods https://pharo.fogbugz.com/f/cases/15731 15734 More tests for reifications https://pharo.fogbugz.com/f/cases/15734 http://files.pharo.org/image/50/50104.zip

June 11, 2015

Re: [Pharo-dev] Probably Metacello sucksâ¦

by Christophe Demarey

Le 11 juin 2015 Ã 07:52, Yuriy Tymchuk a Ã©crit : > Once Stef mentioned that there is some project for dependency checking. What was it? Maybe we can use that? http://smalltalkhub.com/#!/~PharoExtras/Tool-DependencyAnalyser But take care, it only spots static dependencies (inheritance, reference, extensions, traits).

June 11, 2015

Re: [Pharo-dev] New Tool: Catalog Browser in Pharo 5.0

by Tudor Girba

Really cool! About the spotter integration, it is really nice to be able to search and find new projects like this. Well done. But, there are two things that I would change: - Right now, the processor order is 10. If you search for GTSpotter, you will get the catalog project before the class: [image: Inline image 1] I would rather prefer the order to be next to the Metacello configurations, so I would make it 90. The reason is that the things that are in the image should take precedence because they are much more often used. - For the preview, I would put the details that we have about the project. - Also, if you are at it, it would be nice to add an inspector extension for showing all projects of a CatalogProvider and to add a load action for a CatalogProject object :) Cheers, Doru On Thu, Jun 11, 2015 at 8:55 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > maybe you already noticed. The latest update for Pharo 5 which is 50103 > (see [1]). > includes a new tool called "Catalog Browser". > > Where to go > =========== > > You will find it under "Tools" -> "Catalog Browser" and it will display the > configs together with the catalog metadata like project description. > > The code is managed with a configuration similar to what we have for > a few other packages/projects. The tool was written by Esteban Lorenzano > with small > improvements like spotter integration from my side. Feel free to > contribute more features. > > The repository can be found on SmalltalkHub [2]. > > This new tool basically gives you access to all available configurations > aggregated at [3]. You can use a small UI to search and load the configs > (see world menu -> "Tools" -> "Catalog Browser". > > But you can also use Spotter to load a config. > > Example on how to load ScriptManager config: > ============================================ > - open Spotter (SHIFT + ENTER on Windows, ...) > - type in "Script" and you will find a spotter category "Catalog > Projects" with "ScriptManager" in it > - just hit enter and the config is loaded > > Same for all others, so try with "Seaside", "MongoTalk", ... > > In the short/mid-term this new tool should replace the existing config > browser as it > gives more informations about the projects. > > What to do next: > ================ > - give feedback > - we should update all our configs with catalog descriptions > - it would be nice if the spotter integration would include also a preview > of the project > description > - ... > > If you want to contribute just tell Esteban so he can add you to the > project. > > Thanks > Esteban & Torsten > > [1] > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-June/110964… > [2] http://www.smalltalkhub.com/#!/~estebanlm/CatalogBrowser > [3] http://catalog.pharo.org/catalog/json -- www.tudorgirba.com "Every thing has its own flow"

June 11, 2015

Re: [Pharo-dev] Pharo 4, format on accept/display

by Franck Warlouzet

> Date: Thu, 11 Jun 2015 08:35:10 +0200 > From: stepharo(a)free.fr > To: pharo-dev(a)lists.pharo.org > Subject: Re: [Pharo-dev] Pharo 4, format on accept/display > > > > Le 10/6/15 20:47, Paul DeBruicker a Ã©crit : > > Hi > > > > I've hacked together an implementation of format on accept & display. > > > > > > I know someone is redoing that functionality to better suit future needs. > > > > > > Should I publish what I've got as a slice to the Pharo40Inbox for people to use that may miss it now that do not want to wait for the new hotness? > Yes it is cool :) > :) > new text editor new pretty printer :) > print on read > print on accept > :) Hi, We are working on a new pretty printer and using rubric in Nautilus for the source code area so you will soon be able to format on accept but not only. A format as you read feature will be introduce, if you activate it, it will format the source code with your own preferences every time you read code, and every time you accept. Franck > > > > Thanks > > > > > > Paul > > > >

June 11, 2015