January 2017 - Pharo-dev - lists.pharo.org

Re: AioPlugin not present

by Davide Varvello

Thanks Esteban, I'm gonna download the vm, try the plugin and feedback you. Thanks Davide EstebanLM wrote >> On 23 Jan 2017, at 00:56, David T. Lewis < > lewis@.msen > > wrote: >> >> On Sun, Jan 22, 2017 at 05:00:04PM +0100, Thierry Goubier wrote: >>> >>> Le 22/01/2017 ? 15:50, Davide Varvello via Pharo-dev a ?crit : >>>> Hi Thierry, >>>> >>>> I need it for the OSProcess. When my code calls OSProcess the warning >>>> (http://imgur.com/a/9jhMy) appears. >>>> >>>> It happens only once. If I close the warning window It does not happen >>>> again, but of course if I restart the image it appears once again, so I >>>> have >>>> to find a way to include it or another workaround >>>> >>>> Cheers >>>> Davide >>> >>> Hi Davide, >>> >>> I do use OSProcess in some cases; last time, I just rewrote that part to >>> emit a notification (and not raise a popup). >>> >>> Regards, >>> >>> Thierry >> >> I am not sure why the AIOPlugin is not being included in the VMs. > > me neither :) > I added AioPlugin (as external) to all linux distributionsâ¦ they will be > available in latest VMs. > > can someone test it? > > Esteban > >> >> Whatever the reason for that, the notifier about the missing plugin was >> too annoying, so I got rid of it in the latest OSProcess update: >> >> Name: OSProcess-Base-dtl.56 >> Time: 17 January 2017, 8:47:36.321587 am >> >> OSProcess 4.6.7 >> >> Add nil checks in #shutDown: to prevent failures when exiting existing >> image with a VM that does not include OSPP (e.g. SqueakJS). >> >> For AIO event hander, if the AIO plugin is not present, write an error >> to console rather than interrupting the image with a notifer. Reduces >> the >> annoyance level if VM provider provides OSPP but neglects to include the >> AIO plugin. >> >> Dave >> >> -- View this message in context: http://forum.world.st/AioPlugin-not-present-tp4929932p4930510.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 23, 2017

Re: [Pharo-dev] Pharo by Example 50 released!

by Serge Stinckwich

Congrats for the hard work ! On Sun, Jan 22, 2017 at 4:53 PM, stepharong <stepharong(a)free.fr> wrote: > https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/ > > Super special thanks to Nicolai Hess that pushed me to do the last steps to > release. > Thanks Nicolai your steady commits pushed me! > > Stef > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 23, 2017

Re: [Pharo-dev] Google summer of code

by Serge Stinckwich

Thank you Uko to join the team :-) On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > I can also update my projects and help with the application if needed (I was > a part of the application team for the last two years I think) > > Uko > > On 22 Jan 2017, at 16:33, Jigyasa Grover <grover.jigyasa1(a)gmail.com> wrote: > > Also, a good application is equally important as the list of clearly defined > projects. > > - J > > On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich > <serge.stinckwich(a)gmail.com> wrote: >> >> The list of previous projects is here: >> https://github.com/pharo-project/pharo-project-proposals >> >> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover >> <grover.jigyasa1(a)gmail.com> wrote: >> > Dear Prof Serge >> > >> > Thanks for the introduction. >> > >> > Dear Alexandre >> > I have been a past Google Summer of Code student and also mentor budding >> > developers in Google Code-In. >> > This time, I was hoping to plug-in the loopholes which might have been >> > present in last year's organisation application. >> > Kindly let me know how can we collaborate further on this. >> > Looking forward to your response. >> > Thanks and Regards >> > Jigyasa >> > >> > >> > On Sat, Jan 21, 2017 at 9:06 AM, <serge.stinckwich(a)gmail.com> wrote: >> >> >> >> >> >> >> >> >> >> >> >> EnvoyÃ© de mon iPhone >> >> Le 20 janv. 2017 Ã 22:21, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> a Ã©crit >> >> : >> >> >> >> What do we do? >> >> >> >> >> >> >> >> We have to apply ! ;-) >> >> >> >> We talk with Jigyasa Grover who is doing an internship in my lab at the >> >> moment and she is willing to help. Jigyasa was a student in a former >> >> Google >> >> Summer of code and is involved in several open-source initiative like >> >> Women >> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn. >> >> >> >> You can find a small presentation during last FOSSASIA : " >> >> >> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA >> >> 2016" >> >> >> >> https://m.youtube.com/watch?v=uLIzylxvIz4 >> >> >> >> She has done a streaming video this morning also: http://goo.gl/UyclKP >> >> http://youtube.com/watch?v=2iRG_jpOL54 >> >> >> >> Anyone to help her setup a small team for Pharo proposal to Google >> >> Summer >> >> of Code this year ? >> >> >> >> >> >> On 20 Jan 2017, at 20:38, Alexandre Bergel <alexandre.bergel(a)me.com> >> >> wrote: >> >> >> >> Hi everyone- >> >> >> >> Google Summer of Code 2017 has officially begun! Organization >> >> applications >> >> open today, Thursday January 19 and are open through Thursday, February >> >> 9th. >> >> Please see our program site, official timeline and FAQ for more >> >> details. >> >> >> >> What makes a good organization application? Take a look at our manuals >> >> for >> >> tips and best practices. >> >> >> >> We look forward to seeing each of your applications and kicking off >> >> another great year of GSoC. If you have any questions, donât hesitate >> >> to >> >> reach out to gsoc-support(a)google.com. Weâre here to help! >> >> >> >> Google Open Source Programs Office >> >> -- >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >> Alexandre Bergel http://www.bergel.eu >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> >> > >> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 23, 2017

Re: [Pharo-dev] Collections and Kernel

by Ben Coman

On Tue, Jan 24, 2017 at 12:14 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > On Mon, Jan 23, 2017 at 3:55 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> I do not think that to have the package "Kernel" as the smallest system >> subset is the good way to go. The minimal system should be a set of >> well-structured packages so it still makes sense to have packages like >> Collections-* where some of them are supposed to be mandatory and others >> optional. >> >> So: >> 1) not in that form >> > 2) Kernel package deserves better modularization but in that case names >> will be like Kernel-* >> >> > Ok. > > The problem with the names Collections-* and Kernel-* is that pkg-* > currently means a different package tag inside a package and not a > different package, while the dependency analyser tool analyse dependencies > on packages not package tags. > > Right now it's difficult for me to keep the dependencies right for my > package as the dependency analyser tool shows me a dependency on the whole > Collection and Kernel packages while I need to enforce a dependency to a > subset of these 2 packages. > > Now that I read my mail again I think the problem is not with the packages > but with the dependency analyser tool. I should define a set of classes and > enforce my package to depend only on those classes as the current packages > are too wide and they won't be split in a way I need in the near future. > Do you mean having a script that temporarily organises your subset of classes into MyProvidersPackage to you use that with Dependency Analyser? Or do you have some other method of feeding DA a subset of classes? cheers -ben > > Cheers > > > >> But of course we should discuss the best approach. >> >> Cheers, >> -- Pavel >> >> >> >> 2017-01-23 15:36 GMT+01:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >> >>> Hi everyone, >>> >>> As I am working on an optimising JIT compiler for the Cog VM written in >>> Smalltalk and partly running in the Smalltalk runtime, I am very careful >>> about dependencies. I would like to limit the dependencies of the optimiser >>> to the Kernel. >>> >>> The main problem I have is that there are no collections in the Pharo >>> Kernel except MethodDictionary and DependentsArray. The optimiser depends >>> on Array, ByteArray, OrderedCollection, Set and Dictionary which are not >>> part of the Kernel. >>> >>> The second problem is that there are lots of things in the Kernel that >>> the optimiser do not depend on even though everything is in the Kernel >>> package, for example, the optimiser does not depend on anything related to >>> Time/Chronology, on Numbers other than SmallIntegers or Protocol logic. >>> >>> This leads to questions. I know that with the bootstrap incoming, some >>> people have answers to these questions, but I would like to the >>> conversation happening on the mailing list so everyone can contribute. >>> >>> Question 1) Is there any plan to make a 'Kernel-Collection' package, >>> which includes Array, ByteArray, OrderedCollection, Set and Dictionary, but >>> not the rest of the collections ? >>> >>> Question 2) Is there any plan to split the Kernel (or maybe the Kernel >>> and all its dependencies ?) into smaller pieces, for example 'KernelCore', >>> which includes the existing Kernel *but* other Numbers than SmallIntegers, >>> Protocol logic and Time Chronology, which could be moved to >>> 'KernelExtended' or something like that ? >>> >>> I understand that those problems are not easy, but I would like to know >>> if there is a generic plan so I can correctly decide on what dependencies I >>> can have or not. >>> >>> Thanks, cheers, >>> >> >> >

Jan. 23, 2017

Re: [Pharo-dev] Epicea user experience report

by Ben Coman

On Wed, Jan 11, 2017 at 3:29 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > I created an entry in fogbugz and had progress: > > https://pharo.fogbugz.com/f/cases/19534/Unify-Epicea-UIs > > Cheers, > Martin > hi Martin, I like the result - especially when opening a fresh image and directly going World > Tools > Code Changes the current session already exists as an empty session. Watching the file system I see the session file is not created until an edit is made, which is good. However after making the a change so the session file is created, then Save&Quit, then reopening the Image and Epicea, I expected to see two sessions but see only the last session. The current session doesn't show up until a new change is made, which feels like the session hasn't changed so confused me for a while. I'm not seeing my name as author of methods. I can't remember exactly but I thought this was previously visible in the right pane. Its nice having just one World menu item one level higher than before. cheers -ben

Jan. 23, 2017

Re: [Pharo-dev] AST node replacement API

by John Brant

On 01/23/2017 10:00 AM, Yuriy Tymchuk wrote: > I think that we hacked too much :). I like how ParsetreeRewriter is working, but I think that it would be nice to have some API to say: ok, I have this node, now I want to replace it (maybe it should generate a new changed tree), so the pattern syntax would be more of a nice interface instead of a single entry point. > > Anyway, I also think that this substitution without reformatting is really cool. I need to double check it, because I think that many uses do not use auto fix from lint rules because it reformats their code. The RB works at the AST level, so you always need to replace a node. If you want to specify your own custom source when doing a replacement, you could create a method like this: RBProgramNode>>replaceWith: aNode andSource: aString | method | parent ifNil: [ self error: 'This node doesn''t have a parent' ]. method := self methodNode. method notNil ifTrue: [ method map: self to: aNode ]. aNode parent: self parent. self addReplacement: (RBStringReplacement replaceFrom: self start to: self stop with: aString). parent replaceNode: self withNode: aNode Then you could use it with something like this: | source method | source := 'method ^1'. method := RBParser parseMethod: source. method body statements first value replaceWith: (RBParser parseExpression: '2 - 1') andSource: '2 - 1'. method newSource Here, the "-" and "1" should appear on separate lines. However, if you gave invalid source, you get the formatted version: | source method | source := 'method ^1'. method := RBParser parseMethod: source. method body statements first value replaceWith: (RBParser parseExpression: '2 - 1') andSource: '2 - 2'. method newSource Here the "2 - 2" expression in the replacement source, isn't equal to the "2 - 1" expression node that was provided so it uses the formatted code of the parse tree. John Brant

Jan. 23, 2017

Re: [Pharo-dev] AST node replacement API

by Denis Kudriashov

2017-01-23 17:00 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > I think that we hacked too much :). I like how ParsetreeRewriter is > working, but I think that it would be nice to have some API to say: ok, I > have this node, now I want to replace it (maybe it should generate a new > changed tree), so the pattern syntax would be more of a nice interface > instead of a single entry point. > > Anyway, I also think that this substitution without reformatting is really > cool. I need to double check it, because I think that many uses do not use > auto fix from lint rules because it reformats their code. > Yes, I also hate extract temp/method because it reformats original method

Jan. 23, 2017

Re: [Pharo-dev] Google summer of code

by Yuriy Tymchuk

I can also update my projects and help with the application if needed (I was a part of the application team for the last two years I think) Uko > On 22 Jan 2017, at 16:33, Jigyasa Grover <grover.jigyasa1(a)gmail.com> wrote: > > Also, a good application is equally important as the list of clearly defined projects. > > - J > > On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>> wrote: > The list of previous projects is here: > https://github.com/pharo-project/pharo-project-proposals <https://github.com/pharo-project/pharo-project-proposals> > > On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover > <grover.jigyasa1(a)gmail.com <mailto:grover.jigyasa1@gmail.com>> wrote: > > Dear Prof Serge > > > > Thanks for the introduction. > > > > Dear Alexandre > > I have been a past Google Summer of Code student and also mentor budding > > developers in Google Code-In. > > This time, I was hoping to plug-in the loopholes which might have been > > present in last year's organisation application. > > Kindly let me know how can we collaborate further on this. > > Looking forward to your response. > > Thanks and Regards > > Jigyasa > > > > > > On Sat, Jan 21, 2017 at 9:06 AM, <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>> wrote: > >> > >> > >> > >> > >> > >> EnvoyÃ© de mon iPhone > >> Le 20 janv. 2017 Ã 22:21, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> a Ã©crit : > >> > >> What do we do? > >> > >> > >> > >> We have to apply ! ;-) > >> > >> We talk with Jigyasa Grover who is doing an internship in my lab at the > >> moment and she is willing to help. Jigyasa was a student in a former Google > >> Summer of code and is involved in several open-source initiative like Women > >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn. > >> > >> You can find a small presentation during last FOSSASIA : " > >> > >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA > >> 2016" > >> > >> https://m.youtube.com/watch?v=uLIzylxvIz4 <https://m.youtube.com/watch?v=uLIzylxvIz4> > >> > >> She has done a streaming video this morning also: http://goo.gl/UyclKP <http://goo.gl/UyclKP> > >> http://youtube.com/watch?v=2iRG_jpOL54 <http://youtube.com/watch?v=2iRG_jpOL54> > >> > >> Anyone to help her setup a small team for Pharo proposal to Google Summer > >> of Code this year ? > >> > >> > >> On 20 Jan 2017, at 20:38, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> > >> wrote: > >> > >> Hi everyone- > >> > >> Google Summer of Code 2017 has officially begun! Organization applications > >> open today, Thursday January 19 and are open through Thursday, February 9th. > >> Please see our program site, official timeline and FAQ for more details. > >> > >> What makes a good organization application? Take a look at our manuals for > >> tips and best practices. > >> > >> We look forward to seeing each of your applications and kicking off > >> another great year of GSoC. If you have any questions, donât hesitate to > >> reach out to gsoc-support(a)google.com <mailto:gsoc-support@google.com>. Weâre here to help! > >> > >> Google Open Source Programs Office > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >> > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ <http://www.doesnotunderstand.org/> > >

Jan. 23, 2017

Re: [Pharo-dev] Collections and Kernel

by ClÃ©ment Bera

On Mon, Jan 23, 2017 at 3:55 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > I do not think that to have the package "Kernel" as the smallest system > subset is the good way to go. The minimal system should be a set of > well-structured packages so it still makes sense to have packages like > Collections-* where some of them are supposed to be mandatory and others > optional. > > So: > 1) not in that form > 2) Kernel package deserves better modularization but in that case names > will be like Kernel-* > > Ok. The problem with the names Collections-* and Kernel-* is that pkg-* currently means a different package tag inside a package and not a different package, while the dependency analyser tool analyse dependencies on packages not package tags. Right now it's difficult for me to keep the dependencies right for my package as the dependency analyser tool shows me a dependency on the whole Collection and Kernel packages while I need to enforce a dependency to a subset of these 2 packages. Now that I read my mail again I think the problem is not with the packages but with the dependency analyser tool. I should define a set of classes and enforce my package to depend only on those classes as the current packages are too wide and they won't be split in a way I need in the near future. Cheers > But of course we should discuss the best approach. > > Cheers, > -- Pavel > > > > 2017-01-23 15:36 GMT+01:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > >> Hi everyone, >> >> As I am working on an optimising JIT compiler for the Cog VM written in >> Smalltalk and partly running in the Smalltalk runtime, I am very careful >> about dependencies. I would like to limit the dependencies of the optimiser >> to the Kernel. >> >> The main problem I have is that there are no collections in the Pharo >> Kernel except MethodDictionary and DependentsArray. The optimiser depends >> on Array, ByteArray, OrderedCollection, Set and Dictionary which are not >> part of the Kernel. >> >> The second problem is that there are lots of things in the Kernel that >> the optimiser do not depend on even though everything is in the Kernel >> package, for example, the optimiser does not depend on anything related to >> Time/Chronology, on Numbers other than SmallIntegers or Protocol logic. >> >> This leads to questions. I know that with the bootstrap incoming, some >> people have answers to these questions, but I would like to the >> conversation happening on the mailing list so everyone can contribute. >> >> Question 1) Is there any plan to make a 'Kernel-Collection' package, >> which includes Array, ByteArray, OrderedCollection, Set and Dictionary, but >> not the rest of the collections ? >> >> Question 2) Is there any plan to split the Kernel (or maybe the Kernel >> and all its dependencies ?) into smaller pieces, for example 'KernelCore', >> which includes the existing Kernel *but* other Numbers than SmallIntegers, >> Protocol logic and Time Chronology, which could be moved to >> 'KernelExtended' or something like that ? >> >> I understand that those problems are not easy, but I would like to know >> if there is a generic plan so I can correctly decide on what dependencies I >> can have or not. >> >> Thanks, cheers, >> > >

Jan. 23, 2017

Re: [Pharo-dev] AST node replacement API

by Yuriy Tymchuk

I think that we hacked too much :). I like how ParsetreeRewriter is working, but I think that it would be nice to have some API to say: ok, I have this node, now I want to replace it (maybe it should generate a new changed tree), so the pattern syntax would be more of a nice interface instead of a single entry point. Anyway, I also think that this substitution without reformatting is really cool. I need to double check it, because I think that many uses do not use auto fix from lint rules because it reformats their code. Cheers. Uko > On 23 Jan 2017, at 16:28, John Brant <brant(a)refactoryworkers.com> wrote: > > > > On 01/23/2017 07:48 AM, Yuriy Tymchuk wrote: >> Hi everyone, >> >> does anyone have a better knowledge about replacing nodes in AST? Because what I saw is that there are methods like replaceSourceWith: that can be sent to an AST node with another AST node as a parameter. But this is not enough to get a new source code. Because when you ask the AST for newSource it generates a new source by taking replacements into account, parses the new source, compares it with itself and in case the new parse tree is equal it returns the new source. So itâs not enough to just use replaceSourceWith: but you also have to replace the current node with a new one it AST. >> >> Now the question is: am I doing something wrong, or we have strange API because we need to replace both source and node, replacing only one of them does not workâ¦ > > > This code was created so that some refactoring could be performed without having to format the entire parse tree. For example, converting direct variable access to use accessors should be able to rewrite the code without having to reformat. > > When you perform the replaceWith: on a node or the rewriter performs a node replacement, it calls the replaceMethodSource: method. That method calls the replaceSourceWith: method (replaceSourceWith: is a "private" method). The replaceSourceWith: methods test the source/replacement nodes for certain patterns. If the replacement fits the condition of the pattern, then it adds the appropriate text edit operations that should transform the old source into the new source. If the replaceSourceWith: doesn't recognize what is being done, then it dispatches the replaceSourceFrom: message to the replacement node. Currently, this handles cases were any section of code is being replaced with a variable or literal. > > Anyway, after all replacements are performed, it gets the new source like you explain. It performs a sanity check on the edited source. If it isn't parse tree equivalent to the rewritten tree, then it assumes that something went wrong in a replaceSourceWith: or replaceSourceFrom: method and uses the formatted code of the rewritten tree instead. > > > John Brant >

Jan. 23, 2017