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

Re: [Pharo-dev] block syntax experiments

by stepharo

> Is Coral using the Opal compiler for its syntax extensions? it extends petitParser. Now the challenges of Coral are not in the syntax. But How can we call system call, how can we manipule OS variable. How can we edit a "script" and debug it inside the image and publish it as a dead file. Remember Coral is not about forcing us to edit in vim, but to have a living scripts that we be debugged and published as dead files or zombified on demand. Stef > > - Francisco > > >> On 3 Jun 2015, at 16:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 03 Jun 2015, at 17:12, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> On Wed, Jun 3, 2015 at 4:14 PM, Francisco Garau >>> <francisco.garau(a)gmail.com> wrote: >>>>> On 3 June 2015 at 05:56, Ben Coman <btc(a)openinworld.com> wrote: >>>>> >>>>> I think that would confuse me, and maybe break syntax highlighting. >>>>> It *looks* like a message send to nothing. >>>> >>>> That might be a good thing as there is no object needed to resolve the >>>> method lookup. You already have the "method" to evaluate, which is obviously >>>> the block. >>>> >>>> It's a bit heretic, but the more I think, the more I like it. >>> Well, if its an itch you need to scratch, go ahead :) >>> But it might be a struggle to get the community to accept it into >>> Pharo, and hence possibly a maintenance burden for you each Pharo >>> release. >> It would make a nice tutorial how to hack the compiler for experimentsâ¦ >> >> Marcus >> >> >

June 4, 2015

Re: [Pharo-dev] block syntax experiments

by Sean P. DeNigris

stepharo wrote > Remember Coral is not about forcing us to edit in vim, but to have a > living scripts that > we be debugged and published as dead files or zombified on demand. That sounds reeeally interesting! I never understood that before. I heard that Coral was obsolete because the important parts were integrated as the command line handlers... ----- Cheers, Sean -- View this message in context: http://forum.world.st/block-syntax-experiments-tp4830097p4830418.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 4, 2015

[pharo-project/pharo-core] 26e83f: 50088

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 26e83faea0cb84a5be0469a11555fbe0d185011b https://github.com/pharo-project/pharo-core/commit/26e83faea0cb84a5be0469a1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-04 (Thu, 04 Jun 2015) Changed paths: M DebuggerActions.package/DebugAction.class/instance/accessing/category.st M DebuggerActions.package/DebugAction.class/instance/accessing/category_.st M DebuggerActions.package/DebugAction.class/instance/accessing/defaultCategory.st R Kernel.package/Categorizer.class/instance/accessing/addCategory_.st R Kernel.package/Categorizer.class/instance/accessing/addCategory_before_.st R Kernel.package/Categorizer.class/instance/accessing/categoryOfElement_.st R Kernel.package/Categorizer.class/instance/accessing/changeFromCategorySpecs_.st R Kernel.package/Categorizer.class/instance/accessing/changeFromString_.st R Kernel.package/Categorizer.class/instance/accessing/classifyAll_under_.st R Kernel.package/Categorizer.class/instance/accessing/classify_under_.st R Kernel.package/Categorizer.class/instance/accessing/classify_under_suppressIfDefault_.st R Kernel.package/Categorizer.class/instance/accessing/elementCategoryDict.st R Kernel.package/Categorizer.class/instance/accessing/isEmptyCategoryNamed_.st R Kernel.package/Categorizer.class/instance/accessing/isEmptyCategoryNumber_.st R Kernel.package/Categorizer.class/instance/accessing/listAtCategoryNamed_.st R Kernel.package/Categorizer.class/instance/accessing/listAtCategoryNumber_.st R Kernel.package/Categorizer.class/instance/accessing/numberOfCategoryOfElement_.st R Kernel.package/Categorizer.class/instance/accessing/removeCategory_.st R Kernel.package/Categorizer.class/instance/accessing/removeElement_.st R Kernel.package/Categorizer.class/instance/accessing/removeEmptyCategories.st R Kernel.package/Categorizer.class/instance/accessing/renameCategory_toBe_.st R Kernel.package/Categorizer.class/instance/accessing/sortCategories.st A Kernel.package/Categorizer.class/instance/operations/addCategory_.st A Kernel.package/Categorizer.class/instance/operations/addCategory_before_.st A Kernel.package/Categorizer.class/instance/operations/changeFromCategorySpecs_.st A Kernel.package/Categorizer.class/instance/operations/changeFromString_.st A Kernel.package/Categorizer.class/instance/operations/classifyAll_under_.st A Kernel.package/Categorizer.class/instance/operations/classify_under_.st A Kernel.package/Categorizer.class/instance/operations/classify_under_suppressIfDefault_.st A Kernel.package/Categorizer.class/instance/operations/removeCategory_.st A Kernel.package/Categorizer.class/instance/operations/removeElement_.st A Kernel.package/Categorizer.class/instance/operations/removeEmptyCategories.st A Kernel.package/Categorizer.class/instance/operations/renameCategory_toBe_.st A Kernel.package/Categorizer.class/instance/operations/sortCategories.st A Kernel.package/Categorizer.class/instance/private/elementCategoryDict.st A Kernel.package/Categorizer.class/instance/private/listAtCategoryNumber_.st A Kernel.package/Categorizer.class/instance/private/numberOfCategoryOfElement_.st A Kernel.package/Categorizer.class/instance/queries - protocol/listAtProtocolNamed_.st A Kernel.package/Categorizer.class/instance/queries - protocol/protocolOfElement_.st A Kernel.package/Categorizer.class/instance/queries/categoryOfElement_.st A Kernel.package/Categorizer.class/instance/queries/listAtCategoryNamed_.st A Kernel.package/Categorizer.class/instance/testing/isEmptyCategoryNamed_.st A Kernel.package/Categorizer.class/instance/testing/isEmptyCategoryNumber_.st A Kernel.package/CompiledMethod.class/instance/accessing-backward compatible/category.st R Kernel.package/CompiledMethod.class/instance/accessing/category.st M Kernel.package/CompiledMethod.class/instance/accessing/protocol.st M Komitter.package/extension/MCMethodDefinition/instance/koClass.st A Monticello.package/MCMethodDefinition.class/instance/accessing-backward/category.st R Monticello.package/MCMethodDefinition.class/instance/accessing/category.st M Monticello.package/MCMethodDefinition.class/instance/accessing/diffSource.st A Monticello.package/MCMethodDefinition.class/instance/accessing/protocol.st M Monticello.package/MCMethodDefinition.class/instance/installing/removeSelector_fromClass_.st R OpalCompiler-Core.package/CompilationContext.class/instance/accessing/category.st R OpalCompiler-Core.package/CompilationContext.class/instance/accessing/category_.st A OpalCompiler-Core.package/CompilationContext.class/instance/accessing/protocol.st A OpalCompiler-Core.package/CompilationContext.class/instance/accessing/protocol_.st A OpalCompiler-Core.package/CompilationContext.class/instance/backward compatibility/category.st A OpalCompiler-Core.package/CompilationContext.class/instance/backward compatibility/category_.st M OpalCompiler-Core.package/SyntaxErrorNotification.class/README.md M Ring-Core-Kernel.package/RGMethodDefinition.class/instance/accessing/protocol.st M Ring-Monticello.package/extension/MCMethodDefinition/instance/asRingDefinition.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50087.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50088.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50087.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50088.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50088 15646 Cleaning method category api should be protocol (part 1) http://files.pharo.org/image/50/50088.zip

June 4, 2015

[pharo-project/pharo-core]

by GitHub

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

June 4, 2015

Re: [Pharo-dev] [Pharo-users] [ann] moose 5.1

by Alexandre Bergel

Impressive!!!!!!! Wonderful team! Alexande -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 4, 2015, at 4:17 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > We are happy to announce version 5.1 of the Moose Suite: > *http://moosetechnology.org/#install* <http://moosetechnology.org/#install*> > > <moose-5-1.png> > > Description > --- > This is a minor release. The key highlights are: > - It is based on Pharo 4.0. > - Roassal2 comes with several new builder, most notably the new Mondrian builder (RTMondrian) and the chart drawing engine (RTGrapher). > - GTSpotter has preview abilities and was extended for multiple search use cases including the navigation through Moose models. > - GTPlayground was extended with sharing possibilities and transparent backup. > - GTExample now offers support for documenting classes with example instances. > - Moose Finder and GTInspector come with more custom presentations. > - PetitParser has seen performance corrections and has been extended with the ability to parse whitespace languages. > > > Installation > --- > The Moose Suite 5.1 comes for each platform as a separate bundle: > - Moose Suite 5.1 for Mac > http://moosetechnology.org/res/download/moose_suite_5_1-mac.zip <http://moosetechnology.org/res/download/moose_suite_5_1-mac.zip> > - Moose Suite 5.1 for Windows > http://moosetechnology.org/res/download/moose_suite_5_1-win.zip <http://moosetechnology.org/res/download/moose_suite_5_1-win.zip> > - Moose Suite 5.1 for Linux > http://moosetechnology.org/res/download/moose_suite_5_1-linux.zip <http://moosetechnology.org/res/download/moose_suite_5_1-linux.zip> > > The Moose Suite 5.1 can also be loaded in a Pharo 4.0 image either from the Configuration Browser, or by executing the following script: > > Gofer new > smalltalkhubUser: 'Moose' project: 'Moose'; > configuration; > loadStable > > > Enjoy, > The Moose team >

June 4, 2015

Re: [Pharo-dev] [Moose-dev] Re: Fwd: Magritte = Auto-GT Presentation

by Sean P. DeNigris

Tudor Girba-2 wrote > Indeed. We already had a similar discussion in the context of XMLParser. > The current idea is to package GT extensions directly in the project, and > not in GT. That sound's good. I want to have Magritte load this by default in Pharo 4.0, but I guess the only way is to directly refer to the Glamour-Magritte-Presentations package from the Magritte config ( don't tell Christophe ;) ) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Re-Moose-dev-Re-Fwd-Magritte-Auto-GT-Presentation-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 4, 2015

Re: [Pharo-dev] [Pharo-users] [ann] moose 5.1

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote >> On 04 Jun 2015, at 10:07, Aliaksei Syrel < > alex.syrel@ > > wrote: >> >> Juhuuuuu, thanks Doru! :) >> Congratulations, Moose! > > +100 Yes!!! ----- Cheers, Sean -- View this message in context: http://forum.world.st/ann-moose-5-1-tp4830357p4830385.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 4, 2015

Re: [Pharo-dev] [Pharo-users] [ann] moose 5.1

by Peter UhnÃ¡k

Well done! Looking forward to the enjoyment of using it. :) Peter On Thu, Jun 4, 2015 at 10:23 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 04 Jun 2015, at 10:07, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > > > Juhuuuuu, thanks Doru! :) > > Congratulations, Moose! > > +100 > > > Cheers, > > Alex > > On Jun 4, 2015 9:17 AM, "Tudor Girba" <tudor(a)tudorgirba.com> wrote: > > We are happy to announce version 5.1 of the Moose Suite: > > *http://moosetechnology.org/#install* > > > > <moose-5-1.png> > > > > Description > > --- > > This is a minor release. The key highlights are: > > - It is based on Pharo 4.0. > > - Roassal2 comes with several new builder, most notably the new Mondrian > builder (RTMondrian) and the chart drawing engine (RTGrapher). > > - GTSpotter has preview abilities and was extended for multiple search > use cases including the navigation through Moose models. > > - GTPlayground was extended with sharing possibilities and transparent > backup. > > - GTExample now offers support for documenting classes with example > instances. > > - Moose Finder and GTInspector come with more custom presentations. > > - PetitParser has seen performance corrections and has been extended > with the ability to parse whitespace languages. > > > > > > Installation > > --- > > The Moose Suite 5.1 comes for each platform as a separate bundle: > > - Moose Suite 5.1 for Mac > > http://moosetechnology.org/res/download/moose_suite_5_1-mac.zip > > - Moose Suite 5.1 for Windows > > http://moosetechnology.org/res/download/moose_suite_5_1-win.zip > > - Moose Suite 5.1 for Linux > > http://moosetechnology.org/res/download/moose_suite_5_1-linux.zip > > > > The Moose Suite 5.1 can also be loaded in a Pharo 4.0 image either from > the Configuration Browser, or by executing the following script: > > > > Gofer new > > smalltalkhubUser: 'Moose' project: 'Moose'; > > configuration; > > loadStable > > > > > > Enjoy, > > The Moose team > > > > >

June 4, 2015

Re: [Pharo-dev] [Pharo-users] [ann] moose 5.1

by Sven Van Caekenberghe

> On 04 Jun 2015, at 10:07, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Juhuuuuu, thanks Doru! :) > Congratulations, Moose! +100 > Cheers, > Alex > On Jun 4, 2015 9:17 AM, "Tudor Girba" <tudor(a)tudorgirba.com> wrote: > We are happy to announce version 5.1 of the Moose Suite: > *http://moosetechnology.org/#install* > > <moose-5-1.png> > > Description > --- > This is a minor release. The key highlights are: > - It is based on Pharo 4.0. > - Roassal2 comes with several new builder, most notably the new Mondrian builder (RTMondrian) and the chart drawing engine (RTGrapher). > - GTSpotter has preview abilities and was extended for multiple search use cases including the navigation through Moose models. > - GTPlayground was extended with sharing possibilities and transparent backup. > - GTExample now offers support for documenting classes with example instances. > - Moose Finder and GTInspector come with more custom presentations. > - PetitParser has seen performance corrections and has been extended with the ability to parse whitespace languages. > > > Installation > --- > The Moose Suite 5.1 comes for each platform as a separate bundle: > - Moose Suite 5.1 for Mac > http://moosetechnology.org/res/download/moose_suite_5_1-mac.zip > - Moose Suite 5.1 for Windows > http://moosetechnology.org/res/download/moose_suite_5_1-win.zip > - Moose Suite 5.1 for Linux > http://moosetechnology.org/res/download/moose_suite_5_1-linux.zip > > The Moose Suite 5.1 can also be loaded in a Pharo 4.0 image either from the Configuration Browser, or by executing the following script: > > Gofer new > smalltalkhubUser: 'Moose' project: 'Moose'; > configuration; > loadStable > > > Enjoy, > The Moose team >

June 4, 2015

Re: [Pharo-dev] Versionner Wipes per-package #repository: setting

by Christophe Demarey

Le 3 juin 2015 Ã 22:51, Sean P. DeNigris a Ã©crit : > demarey wrote >> I find very strange to have packages of a project in different >> repositories. When I saw this kind of things, it was in configurations >> using packages from another project without declaring this external >> project in the config... Could you tell me more about your use case? > > Hee hee, you caught me ;) I agree that we shouldn't encourage such > irresponsible behavior, and request only that we limit the punishment to > having to hand-write, instead of decapitation! no problem ;) Please add a bug entry. I will take a look if it's can be done quickly. Cheers, Christophe.

June 4, 2015