- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About slots and syntax

by Marcus Denker

> On 27 Feb 2015, at 20:47, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > On 27 February 2015 at 16:13, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > Are we sure that we want to use that => > I thought about = but this is not an assignement this is a declaration and normally we use | for declaration. > So what would be other alternatives before the world use => > Yes, everything is not yet fixedâ¦ > But | for local variables is syntax, and it's used as a bracket. It's also the logical or operatorâ¦ > > I'd propose :: because it recalls the :x for block arguments, or -- because it looks like a typographic em-dash: > > slots: { > #local -- ProcessLocalSlot. > #foo -- SomeOtherKindOfSlot. > interesting! > By the way, using an operator in this way is a little strange: what you read does not match the usual precedence rules (#default: is not a factory method of ProcessLocalSlot, it's an accessor on the result of #local => ProcessLocalSlot) > Oh, true.. that needs to be well documented. (having the method in addition on the class side makes sense, I guess). > > Then I still do not understand why we have empty classVariables: to me it does not make sense. I do not get why we like to have empty collections for the sake of having empty collections. We are trapped in some strange ways of thinking. > > Are there strong arguments against a cascade ? Good question. What is clear is that changing methods like subclass:instanceVariableNames:classVariableNames:category: and adding all variants is annoying. E.g. the âwe do not show the empty poolâ (and the slot definiton) is still just done âon the surfaceâ in Natutilus (#definitionForNautilus) as changing #definition is actually tricky to get all the tests green (esp Monticello). https://pharo.fogbugz.com/f/cases/14063/clean-up-definitionForNautilus <https://pharo.fogbugz.com/f/cases/14063/clean-up-definitionForNautilus> Marcus

Feb. 28, 2015

Re: [Pharo-dev] Postdoc position at INRIA Chile

by Alexandre Bergel

Here is the English translation: " Inria Chile was created in Chile in 2012 by Inria (www.inria.fr) in collaboration with nine Chilean universities. The Centre is supported by CORFO, Chilean Development Agency that was in charge of selecting Inria Chileâs project in the framework of the program Attraction of International Centers of Excellence for Competitiveness, aimed at developing and enhancing R&D capabilities for Chile. Inria Chile conducts its R&D activities through a development platform of applied actions, in the view of putting forward solutions for social and economic challenges in Chile, such as energy, including renewable energy, natural resources and âsmart citiesâ. The center is also working in applied topics such as sustainable development, natural disasters management or the development of advanced technologies for Astronomy. We are looking for a candidate interested in working in Chile, closely with a development team in order to carry out one of these actions. Skills are expected in particular (but not only) in the following areas: machine learning, massive data, sensors networks, interactive visualization. â Cheers, Alexandre > On Feb 27, 2015, at 5:21 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Dear All, > > I have just received a announcement for a position at INRIA Chile. > Here is an extract from the call. It is written in Spanish, however it is also open to non-spanish speaker. > > "Inria Chile fue creado en Chile en 2012 por Inria (www.inria.fr) y en colaboracioÌn con 9 universidades chilenas. Cuenta con el apoyo de CORFO, que seleccionoÌ el proyecto de Inria Chile en el marco del concurso AtraccioÌn de Centros de Excelencia Internacional para la Competitividad dedicado a desarrollar y reforzar las capacidades I+D del paiÌs. > > Inria Chile desarrolla sus actividades I+D a traveÌs de una plataforma de desarrollo de acciones aplicadas, que busca proponer soluciones a desafiÌos econoÌmicos y sociales para Chile, tal como energiÌa, en particular energiÌas renovables, recursos naturales y âciudades inteligentesâ. TambieÌn se estaÌ trabajando en temas aplicados como desarrollo sustentable, gestioÌn de cataÌstrofes naturales o el desarrollo de tecnologiÌas avanzadas para la astronomiÌa. > > Buscamos a un postdoc interesado en trabajar part-time en estrecho viÌnculo con un equipo de desarrollo que lleva a cabo una de estas acciones. Las competencias requeridas son particularmente en las aÌreas de: aprendizaje, datos masivos, redes de sensores, visualizacioÌn interactiva. Esta lista no es exhaustiva.â > > If you have a PhD and are interested, please contact me! > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 28, 2015

[pharo-project/pharo-core]

by GitHub

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

Feb. 27, 2015

[pharo-project/pharo-core] 4834e8: 40521

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4834e88ae552b702f80b32799c142bb9101e56a3 https://github.com/pharo-project/pharo-core/commit/4834e88ae552b702f80b3279… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-28 (Sat, 28 Feb 2015) Changed paths: A Graphics-Shapes.package/PathShape.class/README.md A Graphics-Shapes.package/PathShape.class/class/as yet unclassified/vertices_.st A Graphics-Shapes.package/PathShape.class/definition.st A Graphics-Shapes.package/PathShape.class/instance/accessing/basicBounds.st A Graphics-Shapes.package/PathShape.class/instance/accessing/bounds.st A Graphics-Shapes.package/PathShape.class/instance/accessing/bounds_.st A Graphics-Shapes.package/PathShape.class/instance/accessing/vertices.st A Graphics-Shapes.package/PathShape.class/instance/accessing/vertices_.st A Graphics-Shapes.package/PathShape.class/instance/as yet unclassified/addVertex_.st A Graphics-Shapes.package/PathShape.class/instance/as yet unclassified/calculatedBounds.st A Graphics-Shapes.package/PathShape.class/instance/as yet unclassified/containsPoint_.st A Graphics-Shapes.package/PathShape.class/instance/as yet unclassified/segmentsDo_.st A Graphics-Shapes.package/PathShape.class/instance/initialization/initialize.st A Graphics-Shapes.package/Polygon.class/README.md A Graphics-Shapes.package/Polygon.class/definition.st A Graphics-Shapes.package/Polygon.class/instance/as yet unclassified/containsPoint_.st A Graphics-Shapes.package/Polygon.class/instance/as yet unclassified/segmentsDo_.st A Graphics-Shapes.package/Shape.class/README.md A Graphics-Shapes.package/Shape.class/definition.st A Graphics-Shapes.package/Shape.class/instance/as yet unclassified/basicContainsPoint_.st A Graphics-Shapes.package/Shape.class/instance/as yet unclassified/bounds.st A Graphics-Shapes.package/Shape.class/instance/as yet unclassified/containsPoint_.st M Morphic-Base.package/extension/GradientFillStyle/instance/changeColorOf_rampIndex_.st R Polymorph-Geometry.package/PathShape.class/README.md R Polymorph-Geometry.package/PathShape.class/class/as yet unclassified/vertices_.st R Polymorph-Geometry.package/PathShape.class/definition.st R Polymorph-Geometry.package/PathShape.class/instance/accessing/basicBounds.st R Polymorph-Geometry.package/PathShape.class/instance/accessing/bounds.st R Polymorph-Geometry.package/PathShape.class/instance/accessing/bounds_.st R Polymorph-Geometry.package/PathShape.class/instance/accessing/vertices.st R Polymorph-Geometry.package/PathShape.class/instance/accessing/vertices_.st R Polymorph-Geometry.package/PathShape.class/instance/as yet unclassified/addVertex_.st R Polymorph-Geometry.package/PathShape.class/instance/as yet unclassified/calculatedBounds.st R Polymorph-Geometry.package/PathShape.class/instance/as yet unclassified/containsPoint_.st R Polymorph-Geometry.package/PathShape.class/instance/as yet unclassified/segmentsDo_.st R Polymorph-Geometry.package/PathShape.class/instance/initialization/initialize.st R Polymorph-Geometry.package/Polygon.class/README.md R Polymorph-Geometry.package/Polygon.class/definition.st R Polymorph-Geometry.package/Polygon.class/instance/as yet unclassified/containsPoint_.st R Polymorph-Geometry.package/Polygon.class/instance/as yet unclassified/segmentsDo_.st R Polymorph-Geometry.package/Shape.class/README.md R Polymorph-Geometry.package/Shape.class/definition.st R Polymorph-Geometry.package/Shape.class/instance/as yet unclassified/basicContainsPoint_.st R Polymorph-Geometry.package/Shape.class/instance/as yet unclassified/bounds.st R Polymorph-Geometry.package/Shape.class/instance/as yet unclassified/containsPoint_.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - creation/testCreateReflectiveMethodAndInvalidate.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - creation/testInvalidate.st R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - creation/testInvalidateWithLinCount.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - creation/testInvalidateWithLinkCount.st R Reflectivity-Tests.package/ReflectivityExamples.class/instance/as yet unclassified/exampleMethod.st A Reflectivity-Tests.package/ReflectivityExamples.class/instance/example - simple/exampleMethod.st M Reflectivity.package/ReflectiveMethod.class/instance/evaluation/recompileAST.st M Reflectivity.package/ReflectiveMethod.class/instance/evaluation/run_with_in_.st M Reflectivity.package/ReflectiveMethod.class/instance/invalidate/destroyTwin.st A Reflectivity.package/ReflectiveMethod.class/instance/invalidate/installCompiledMethod.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script520.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script521.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40520.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40521.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Help.package/SpecExamples.class/README.md A Spec-Help.package/SpecExamples.class/class/accessing/bookName.st A Spec-Help.package/SpecExamples.class/class/accessing/pages.st A Spec-Help.package/SpecExamples.class/class/pages/firstExample.st A Spec-Help.package/SpecExamples.class/class/pages/moreExamples.st A Spec-Help.package/SpecExamples.class/class/pages/secondExample.st A Spec-Help.package/SpecExamples.class/definition.st A Spec-Help.package/SpecHelpTopics.class/README.md A Spec-Help.package/SpecHelpTopics.class/class/accessing/bookName.st A Spec-Help.package/SpecHelpTopics.class/class/accessing/key.st A Spec-Help.package/SpecHelpTopics.class/class/accessing/pages.st A Spec-Help.package/SpecHelpTopics.class/class/pages/introduction.st A Spec-Help.package/SpecHelpTopics.class/class/pages/terminology.st A Spec-Help.package/SpecHelpTopics.class/definition.st A Spec-Help.package/SpecLayouts.class/README.md A Spec-Help.package/SpecLayouts.class/class/accessing/bookName.st A Spec-Help.package/SpecLayouts.class/class/accessing/pages.st A Spec-Help.package/SpecLayouts.class/class/pages/columns.st A Spec-Help.package/SpecLayouts.class/class/pages/columnsAndRows.st A Spec-Help.package/SpecLayouts.class/class/pages/intro.st A Spec-Help.package/SpecLayouts.class/class/pages/rows.st A Spec-Help.package/SpecLayouts.class/definition.st A Spec-Help.package/TheHeartOfSpec.class/README.md A Spec-Help.package/TheHeartOfSpec.class/class/accessing/bookName.st A Spec-Help.package/TheHeartOfSpec.class/class/accessing/pages.st A Spec-Help.package/TheHeartOfSpec.class/class/pages/initializePresenter.st A Spec-Help.package/TheHeartOfSpec.class/class/pages/initializeWidgets.st A Spec-Help.package/TheHeartOfSpec.class/class/pages/intro.st A Spec-Help.package/TheHeartOfSpec.class/class/pages/layouts.st A Spec-Help.package/TheHeartOfSpec.class/class/pages/widgetInstantiation.st A Spec-Help.package/TheHeartOfSpec.class/definition.st Log Message: ----------- 40521 14420 What to do with Polymorph-Geometry https://pharo.fogbugz.com/f/cases/14420 14950 Spec help added to the Help Browser https://pharo.fogbugz.com/f/cases/14950 15013 enable recompile on run:with:in: https://pharo.fogbugz.com/f/cases/15013 15015 GradientFillStyle color selection broken https://pharo.fogbugz.com/f/cases/15015 http://files.pharo.org/image/40/40521.zip

Feb. 27, 2015

Re: [Pharo-dev] zipped and unzipped methods for ByteArray

by Tudor Girba

Indeed, this is the primary argument for extending string. I understand it is not as nice, but I am somehow not unhappy about it. As I mentioned before, I see it as a pattern that eases embedded DSLs. But, I do agree that there is a danger of abusing this mechanism. Doru On Fri, Feb 27, 2015 at 12:21 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2015-02-26 22:37 GMT+01:00 stepharo <stepharo(a)free.fr>: > >> Why do we have to put everything in string? >> >> why >> Zip string: 'hello' >> Zip bzip string: 'hello' >> Zip gzip string: 'hello' >> >> would not be more modular? >> Zip could be a factory and have subclasses. >> >> This is not because can extend classes that we should think about nicer >> way. >> >> I like for example the DateFormatter strategy related to Date from other >> languages because I can specify the way I want it. >> >> Stef >> >> > Because somehow you can easily pipe unary messages. > > ^'hello' zipped base64Encoded > > versus: > > (Encoder base64 byteArray: (Zip gzip string: 'hello')). > > I much much prefer to read/maintain 1st version > The 2nd one looks like overkill verbiage to me. > > > >> Le 25/2/15 16:52, Juraj Kubelka a Ã©crit : >> >> 25. 2. 2015 v 12:28, Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>> This seems related to adding 'easy of use' methods to String. >>>> >>>> There are many different compression schemes (zip, bzip, bzip2, gzip, >>>> ...), are we going to add them all ? >>>> >>>> How much do we want to couple different parts of the system ? >>>> >>> I prefer to couple the compression schemes with String and ByteArray. >>> Methods like #zipped, #unzipped are not that simple and it is not well >>> apparent how to use that compression scheme. >>> >>> Cheers, >>> Juraj >>> >>> On 25 Feb 2015, at 16:23, Juraj Kubelka <juraj.kubelka(a)gmail.com> >>>>> wrote: >>>>> >>>>> Can I add ByteArray>>#zipped and #unzipped methods the way it is for >>>>> String? I want to compress bytes before sending through internet, for >>>>> example. >>>>> >>>>> Do you agree? >>>>> Thanks, >>>>> Juraj >>>>> >>>> >>>> >>> >>> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 27, 2015

Re: [Pharo-dev] [regression reporter]regression occurred

by Tudor Girba

Thank you! Doru On Fri, Feb 27, 2015 at 5:37 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On Fri, Feb 27, 2015 at 10:22 AM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > >> The issue is waiting integration: >> https://pharo.fogbugz.com/f/cases/14993/Integrate-GTools >> There are still some more bugs to fix but we should integrate >> nevertheless. >> > > In 40 update #520 > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 27, 2015

Re: [Pharo-dev] Recording user actions in GTools

by Tudor Girba

Hi Stef, In the latest version that is ready for integration, diving into a category is a visible button. Also, each button has a tooltip that shows the keybinding as well to enable learnability. Cheers, Doru On Fri, Feb 27, 2015 at 3:59 PM, stepharo <stepharo(a)free.fr> wrote: > What I often really want to do is to scope my search. > find who is sending changed: in that class X. > and I know that we can do it but no idea how. > > Stef > > > Le 27/2/15 15:44, Andrei Chis a Ã©crit : > > > On Thu, Feb 26, 2015 at 8:39 PM, Stephan Eggermont <stephan(a)stack.nl> > wrote: > >> On 26/02/15 16:10, Andrei Chis wrote: >> >>> The recording of data will be opt-out: *you have to explicitly agree >>> with sending usage data*. >>> >> >> Uhhm. That's called opt-in. >> >> Yes, I confused them. > > > >> A practical issue: I have projects/images where it is >> absolutely no problem, and projects where I definitely >> don't want it. All local images is not a good setting. >> For certain directories would work. >> > > You will be able to change this settings in each individual image. > You will further have a default setting that will be persisted to your > preference folder that will apply to all new images. We need this so we do > not ask every time you open a new image. > > Does this address your situation? > > Would you not want to send data from some images because of privacy > issues? > By default we only collect data that does not contain class names, method > names or any code snippet. The only concrete information consists in > category names: "Methods", "Classes", "History", etc. > > Cheers, > Andrei > > >> >> Stephan >> >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 27, 2015

Re: [Pharo-dev] The evil twin in 40516

by Thierry Goubier

Le 27/02/2015 20:26, Marcus Denker a Ã©crit : > >> On 27 Feb 2015, at 19:48, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> Hi Markus, >> >> if I understand correctly some of the possibilities: >> >> - I can use RBParseTreeSearcher / RBParseTreeRewriter on the twin AST. >> >> (any example how to install / invalidate the twin AST after an effective RBParseTreeRewriter operation?) >> > Yes, but I would do it on a copyâ¦ that is, do the change in run:with:in: on a copy, generate code from that, > keep the original. > An AST that follows the text is kind of nice for e.g. navigation. > >> - Any change to the Twin AST is reflected in the method bytecode (as long as one does invalidate). >> > yes. > >> This would mean being able to put tracing code with RB patterns, no? And without having to do a recompilation of the traced method? >> > > Yes. At first I want to have something simple: a MOP based on the MetaLinks. But one could do the same with RB transformations: > put them as annotation on the method, then on recompile take them into account. Maybe I'm not understanding everything, so would that be correct: - If I inject additional behavior with meta-links, then they just annotate the AST and do not really change it. Now, since writing dedicated ast visitors takes quite some code, what could work is to have a RBParseTreeMetaWriter: use a RB pattern to find the right ast node, and add whatever meta-link there. Thierry

Feb. 27, 2015

Smart Suggestions based on text selection such as extract method seems to be broken.

by stepharo

Hi Smart Suggestions based on text selection such as extract method seems to be broken. if I press command-T on a node, when I select extract method, the complete or part of the method is selected. I thought that it was working. Stef

Feb. 27, 2015

latest update broke rename method.

by stepharo

FYI latest update broke rename method. privateRenameMethodFor: aMethod | class selector oldMethodName newMethodName tempOldArguments oldArguments argumentPermutation | class := aMethod methodClass. selector := aMethod selector. oldArguments := aMethod ast arguments collect: [ :each | each token value ]. ^^^^^ tempOldArguments := aMethod ast arguments collect: [ :each | each token value ]. oldMethodName := RBMethodName selector: selector arguments: oldArguments. (newMethodName := self requestMethodNameFor: oldMethodName) ifNil: [ ^ nil ]. argumentPermutation := newMethodName arguments collect: [ :each | tempOldArguments indexOf: each ]. ^ RBRenameMethodRefactoring model: environment renameMethod: selector in: class to: newMethodName selector permutation: argumentPermutation

Feb. 27, 2015