January 2018 - Pharo-users - lists.pharo.org

How can I outsource instance data ?

by Photon

Hello, I am messing around with an ordered collection of a class wich contains a matrix. As it the size grew I started to wonder if my code was something one should not do or if one would maybe outsource some data. I don`t know if it`s just in the RAM if iI start the VM. In that case i would overkill it at some point or not? So i thought of storing the data on harddrive to be able to recall it later when I need to but get it out of the running VM for the moment. Maybe you can enlighten me regarding this. In this picture you can see that my data is basicly stored inside of a inspector at the moment. So it would be cool to store the whole thing on harddrive. <http://forum.world.st/file/t371759/inspector.png> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 17, 2018

Re: [Pharo-users] How to declare a do:[] loop for a matrix to read and acces its elements?

by Photon

yes I worked with a grid all the time. Thanks for showig me the code. I did it all the time without copy and was wondering big time xD -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 17, 2018

Re: [Pharo-users] [ANN] PharoLauncher v1.1 released!

by Mariano Martinez Peck

Thanks Christophe!! This is very cool! On Wed, Jan 17, 2018 at 10:03 AM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > Thank you a lot Christophe! > I really enjoy using PharoLauncher. > > Juraj > > > On Jan 16, 2018, at 17:46, Christophe Demarey <Christophe.Demarey(a)inria.fr> > wrote: > > Hi all, > > I just released *PharoLauncher 1.1*. There are now 64-bits versions for > Mac and Linux. Jenkins build is now managed through a Jenkins file. > > Here is the changelog (details on https://github.com/pharo- > project/pharo-launcher/issues): > New features: > #66 new command: import an image into the launcher default image folder > #65 new command: remove a template from "Downloaded templates" > #64 new command: create a local template from an image and remove the image > #57 new option: run an image from a login shell to inherit from shell > startup scripts to set up environment variables. > #54 It is now possible to run an image anywhere on your file system if you > click "launch" and no image is selected > #23 Pharo Launcher now has an "about" box giving its description, version > and a link to the bug tracker. > Improvements: > #62 Pharo Launcher should not load default Pharo settings > #51 Pharo Launcher now sets the current directory to the directory > containing the image (was the VM directory). Avoid confusions in Pharo 7 > images. > Bux fixes: > #60 hardReset option causes troubles to PharoLauncher > #56 #, was sent to nil > #55 Display name of Pharo 7 images unusable > #52 Cannot open a Pharo 2 image > #47 Cannot run pharo 50 pre-Spur images > > You can get platform bundles from files.pharo.org: > http://files.pharo.org/pharo-launcher/1.1/ > > Regards, > Christophe. > > > -- Mariano http://marianopeck.wordpress.com

Jan. 17, 2018

Re: [Pharo-users] Commander feedback

by Juraj Kubelka

Thank you Denis. I was able to create two Calypso commands that generate abstract and concrete accept: methods. Cheers, Juraj > On Jan 17, 2018, at 12:16, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > And thank's a lot, Juraj. > > Very impressive review :). I will answer questions later > > 2018-01-17 16:04 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>>: > Hy Juraj, > > Do not spend time in Calypso part and even do not read it :). It is super outdated and very draft. I am now working on it. > > I will look you changes soon. > > 2018-01-17 15:07 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>>: > Hi Denis, > > I finally read Section 3. I left two comments where I do not understand why something happens. I will appreciate a further explanation :-) > > Here is the pull request: https://github.com/SquareBracketAssociates/Booklet-Infrastructure/pull/2 <https://github.com/SquareBracketAssociates/Booklet-Infrastructure/pull/2> > > I have found out that the code in the Calypso chapter does not work. I was able to change some of them. Do you want me to commit what I was able to change? Well, you should check if the changes are correct. > > Cheers, > Juraj > > >> On Dec 27, 2017, at 13:20, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: >> >> Hi Juraj. >> >> You can find new version hereÂ https://github.com/SquareBracketAssociates/Booklet-Infrastructure <https://github.com/SquareBracketAssociates/Booklet-Infrastructure>. It is still draft version but in general all parts are covered now. >> >> 2017-12-06 12:47 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>>: >> Hi Denis, >> >> Thank you. Let me know. I will be happy to help. >> >> Juraj >> >> >>> On Dec 5, 2017, at 18:43, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: >>> >>> Hi Juraj. >>> >>> Yes. documentation needs to be improved. I made only pass on it. >>> Now there is new Commander version. The code still in dev branch <https://github.com/dionisiydk/Commander/tree/dev>. The basic idea is same but some names are changed and internally it is based onÂ ClassAnnotation's <https://github.com/dionisiydk/ClassAnnotation>. It became more simple and flexible. >>> This week I should release new Calypso version. And after I will work on documentation for both projects. Commander will be first. And next week I will have update on it. >>> >>> 2017-12-05 21:05 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>>: >>> Hi, >>> >>> I like the idea of the Commander library https://github.com/dionisiydk/Commander <https://github.com/dionisiydk/Commander> >>> I am trying to understand how to use it, but I struggle to understand it as documentation includes quiete complex examples: https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> >>> >>> I believe that it would be useful to have a tutorial that shows: >>> >>> 1. create a command CmdOne including methods, >>> 2. create a activator ActOne including methods, >>> 3. create a context CtxOne including methods, >>> 4. execute and you obtain a collection with one item (CmdOne instance?) >>> 5. create command CmdTwo with some methods >>> 6. execute and you obtain a collection with two items >>> >>> Then next section could describe how to make a UI on top of this. >>> >>> Thank's for initiative. It is exactly what I will do. >>> >>> >>> Learning it by exploring Calypso is too complex, because it involves more objects and I actually do not see how to do the previous steps. >>> >>> I agree, current version is a bit complicated inside. But it is already fixed. And there will be update soon. >>> >>> >>> I will be happy to help with the documentation. >>> My question is: How can I proceed the mentioned steps? >>> >>> I would appreciate for your help. I will call you for review next week. >>> >>> Best regards, >>> Denis >>> >>> >>> Thanks, >>> Juraj >> >> > > >

Jan. 17, 2018

[ANN] Updating Consultants Listing

by Marcus Denker

Hi, We have http://consultants.pharo.org <http://consultants.pharo.org/> I want to change it to - not be a forward to files.pharo.org <http://files.pharo.org/> - be auto-generated from the https://association.pharo.org <https://association.pharo.org/> But we should update it already before that is finished. So: If you want to be listed, please send your infos in the form: PharoConsultant { #name : Your name', #email : your(a)email.com', #website : 'http://your-website.com', #id : 'yourname (currently not used for anything)', #location : 'City, Country of your business', #languages : 'what languages do you speak', #industryExperienceSince : 1994, #pharoExperienceSince : 2008, #areasOfExpertise : 'what are your areas of expertise. E.g. business apllications, user interface, legacy, ...', #smalltalkExperienceSince : 2002 } (or open a pull request at: https://github.com/pharo-project/pharo-project-consultants/ <https://github.com/pharo-project/pharo-project-consultants/>) Marcus

Jan. 17, 2018

Re: [Pharo-users] Commander feedback

by Denis Kudriashov

And thank's a lot, Juraj. Very impressive review :). I will answer questions later 2018-01-17 16:04 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hy Juraj, > > Do not spend time in Calypso part and even do not read it :). It is super > outdated and very draft. I am now working on it. > > I will look you changes soon. > > 2018-01-17 15:07 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: > >> Hi Denis, >> >> I finally read Section 3. I left two comments where I do not understand >> why something happens. I will appreciate a further explanation :-) >> >> Here is the pull request: https://github.com/Sq >> uareBracketAssociates/Booklet-Infrastructure/pull/2 >> >> I have found out that the code in the Calypso chapter does not work. I >> was able to change some of them. Do you want me to commit what I was able >> to change? Well, you should check if the changes are correct. >> >> Cheers, >> Juraj >> >> >> On Dec 27, 2017, at 13:20, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> Hi Juraj. >> >> You can find new version here https://github.com/Square >> BracketAssociates/Booklet-Infrastructure >> <https://github.com/SquareBracketAssociates/Booklet-Infrastructure>. It >> is still draft version but in general all parts are covered now. >> >> 2017-12-06 12:47 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: >> >>> Hi Denis, >>> >>> Thank you. Let me know. I will be happy to help. >>> >>> Juraj >>> >>> >>> On Dec 5, 2017, at 18:43, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>> >>> Hi Juraj. >>> >>> Yes. documentation needs to be improved. I made only pass on it. >>> Now there is new Commander version. The code still in dev branch >>> <https://github.com/dionisiydk/Commander/tree/dev>. The basic idea is >>> same but some names are changed and internally it is based on >>> ClassAnnotation's <https://github.com/dionisiydk/ClassAnnotation>. It >>> became more simple and flexible. >>> This week I should release new Calypso version. And after I will work on >>> documentation for both projects. Commander will be first. And next week I >>> will have update on it. >>> >>> 2017-12-05 21:05 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: >>> >>>> Hi, >>>> >>>> I like the idea of the Commander library https://github.com/dio >>>> nisiydk/Commander >>>> I am trying to understand how to use it, but I struggle to understand >>>> it as documentation includes quiete complex examples: >>>> https://ci.inria.fr/pharo-contribution/view/Books/ >>>> job/PharoBookWorkInProgress/lastSuccessfulBuild/artifact/boo >>>> k-result/Commander/Commander.html >>>> >>>> I believe that it would be useful to have a tutorial that shows: >>>> >>>> 1. create a command CmdOne including methods, >>>> 2. create a activator ActOne including methods, >>>> 3. create a context CtxOne including methods, >>>> 4. execute and you obtain a collection with one >>>> item (CmdOne instance?) >>>> 5. create command CmdTwo with some methods >>>> 6. execute and you obtain a collection with two >>>> items >>>> >>>> Then next section could describe how to make a UI on top of this. >>>> >>> >>> Thank's for initiative. It is exactly what I will do. >>> >>> >>>> >>>> Learning it by exploring Calypso is too complex, because it involves >>>> more objects and I actually do not see how to do the previous steps. >>>> >>> >>> I agree, current version is a bit complicated inside. But it is already >>> fixed. And there will be update soon. >>> >>> >>>> >>>> I will be happy to help with the documentation. >>>> My question is: How can I proceed the mentioned steps? >>>> >>> >>> I would appreciate for your help. I will call you for review next week. >>> >>> Best regards, >>> Denis >>> >>> >>>> Thanks, >>>> Juraj >>>> >>> >>> >> >> >

Jan. 17, 2018

Re: [Pharo-users] Commander feedback

by Denis Kudriashov

Hy Juraj, Do not spend time in Calypso part and even do not read it :). It is super outdated and very draft. I am now working on it. I will look you changes soon. 2018-01-17 15:07 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: > Hi Denis, > > I finally read Section 3. I left two comments where I do not understand > why something happens. I will appreciate a further explanation :-) > > Here is the pull request: https://github.com/SquareBracketAssociates/ > Booklet-Infrastructure/pull/2 > > I have found out that the code in the Calypso chapter does not work. I was > able to change some of them. Do you want me to commit what I was able to > change? Well, you should check if the changes are correct. > > Cheers, > Juraj > > > On Dec 27, 2017, at 13:20, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Juraj. > > You can find new version here https://github.com/SquareBracketAssociates/ > Booklet-Infrastructure > <https://github.com/SquareBracketAssociates/Booklet-Infrastructure>. It > is still draft version but in general all parts are covered now. > > 2017-12-06 12:47 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: > >> Hi Denis, >> >> Thank you. Let me know. I will be happy to help. >> >> Juraj >> >> >> On Dec 5, 2017, at 18:43, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> Hi Juraj. >> >> Yes. documentation needs to be improved. I made only pass on it. >> Now there is new Commander version. The code still in dev branch >> <https://github.com/dionisiydk/Commander/tree/dev>. The basic idea is >> same but some names are changed and internally it is based on >> ClassAnnotation's <https://github.com/dionisiydk/ClassAnnotation>. It >> became more simple and flexible. >> This week I should release new Calypso version. And after I will work on >> documentation for both projects. Commander will be first. And next week I >> will have update on it. >> >> 2017-12-05 21:05 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: >> >>> Hi, >>> >>> I like the idea of the Commander library https://github.com/dio >>> nisiydk/Commander >>> I am trying to understand how to use it, but I struggle to understand it >>> as documentation includes quiete complex examples: https://ci.inria.fr/ >>> pharo-contribution/view/Books/job/PharoBookWorkInProgress/la >>> stSuccessfulBuild/artifact/book-result/Commander/Commander.html >>> >>> I believe that it would be useful to have a tutorial that shows: >>> >>> 1. create a command CmdOne including methods, >>> 2. create a activator ActOne including methods, >>> 3. create a context CtxOne including methods, >>> 4. execute and you obtain a collection with one >>> item (CmdOne instance?) >>> 5. create command CmdTwo with some methods >>> 6. execute and you obtain a collection with two >>> items >>> >>> Then next section could describe how to make a UI on top of this. >>> >> >> Thank's for initiative. It is exactly what I will do. >> >> >>> >>> Learning it by exploring Calypso is too complex, because it involves >>> more objects and I actually do not see how to do the previous steps. >>> >> >> I agree, current version is a bit complicated inside. But it is already >> fixed. And there will be update soon. >> >> >>> >>> I will be happy to help with the documentation. >>> My question is: How can I proceed the mentioned steps? >>> >> >> I would appreciate for your help. I will call you for review next week. >> >> Best regards, >> Denis >> >> >>> Thanks, >>> Juraj >>> >> >> > >

Jan. 17, 2018

Re: [Pharo-users] Commander feedback

by Juraj Kubelka

Hi Denis, I finally read Section 3. I left two comments where I do not understand why something happens. I will appreciate a further explanation :-) Here is the pull request: https://github.com/SquareBracketAssociates/Booklet-Infrastructure/pull/2 <https://github.com/SquareBracketAssociates/Booklet-Infrastructure/pull/2> I have found out that the code in the Calypso chapter does not work. I was able to change some of them. Do you want me to commit what I was able to change? Well, you should check if the changes are correct. Cheers, Juraj > On Dec 27, 2017, at 13:20, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Juraj. > > You can find new version hereÂ https://github.com/SquareBracketAssociates/Booklet-Infrastructure <https://github.com/SquareBracketAssociates/Booklet-Infrastructure>. It is still draft version but in general all parts are covered now. > > 2017-12-06 12:47 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>>: > Hi Denis, > > Thank you. Let me know. I will be happy to help. > > Juraj > > >> On Dec 5, 2017, at 18:43, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: >> >> Hi Juraj. >> >> Yes. documentation needs to be improved. I made only pass on it. >> Now there is new Commander version. The code still in dev branch <https://github.com/dionisiydk/Commander/tree/dev>. The basic idea is same but some names are changed and internally it is based onÂ ClassAnnotation's <https://github.com/dionisiydk/ClassAnnotation>. It became more simple and flexible. >> This week I should release new Calypso version. And after I will work on documentation for both projects. Commander will be first. And next week I will have update on it. >> >> 2017-12-05 21:05 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>>: >> Hi, >> >> I like the idea of the Commander library https://github.com/dionisiydk/Commander <https://github.com/dionisiydk/Commander> >> I am trying to understand how to use it, but I struggle to understand it as documentation includes quiete complex examples: https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> >> >> I believe that it would be useful to have a tutorial that shows: >> >> 1. create a command CmdOne including methods, >> 2. create a activator ActOne including methods, >> 3. create a context CtxOne including methods, >> 4. execute and you obtain a collection with one item (CmdOne instance?) >> 5. create command CmdTwo with some methods >> 6. execute and you obtain a collection with two items >> >> Then next section could describe how to make a UI on top of this. >> >> Thank's for initiative. It is exactly what I will do. >> >> >> Learning it by exploring Calypso is too complex, because it involves more objects and I actually do not see how to do the previous steps. >> >> I agree, current version is a bit complicated inside. But it is already fixed. And there will be update soon. >> >> >> I will be happy to help with the documentation. >> My question is: How can I proceed the mentioned steps? >> >> I would appreciate for your help. I will call you for review next week. >> >> Best regards, >> Denis >> >> >> Thanks, >> Juraj > >

Jan. 17, 2018

Re: [Pharo-users] [ANN] PharoLauncher v1.1 released!

by Juraj Kubelka

Thank you a lot Christophe! I really enjoy using PharoLauncher. Juraj > On Jan 16, 2018, at 17:46, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Hi all, > > I just released PharoLauncher 1.1. There are now 64-bits versions for Mac and Linux. Jenkins build is now managed through a Jenkins file. > > Here is the changelog (details on https://github.com/pharo-project/pharo-launcher/issues <https://github.com/pharo-project/pharo-launcher/issues>): > New features: > #66 new command: import an image into the launcher default image folder > #65 new command: remove a template from "Downloaded templates" > #64 new command: create a local template from an image and remove the image > #57 new option: run an image from a login shell to inherit from shell startup scripts to set up environment variables. > #54 It is now possible to run an image anywhere on your file system if you click "launch" and no image is selected > #23 Pharo Launcher now has an "about" box giving its description, version and a link to the bug tracker. > Improvements: > #62 Pharo Launcher should not load default Pharo settings > #51 Pharo Launcher now sets the current directory to the directory containing the image (was the VM directory). Avoid confusions in Pharo 7 images. > Bux fixes: > #60 hardReset option causes troubles to PharoLauncher > #56 #, was sent to nil > #55 Display name of Pharo 7 images unusable > #52 Cannot open a Pharo 2 image > #47 Cannot run pharo 50 pre-Spur images > > You can get platform bundles from files.pharo.org <http://files.pharo.org/>: http://files.pharo.org/pharo-launcher/1.1/ <http://files.pharo.org/pharo-launcher/1.1/> > Regards, > Christophe.

Jan. 17, 2018

Re: [Pharo-users] Google Summer of Code 2018 with Pharo Consortium

by Serge Stinckwich

Just a reminder that we need your subject idea ! The deadline to apply is January 23, 2018. Thank you ! On Wed, Jan 10, 2018 at 6:10 AM, Jigyasa Grover <grover.jigyasa1(a)gmail.com> wrote: > Hello Pharo-ers ! > > On behalf of the community, I would like to thank each one of you for their > significant contribution in the previously concluded *Google Summer of Code > 2017* with *Pharo Consortium*. We aspire to take-off on a long flight after > this successful stint by applying to participate in the upcoming *Google > Summer of Code 2018*. > > As many of you might know, Google Summer of Code is a global program > focused > on bringing more student developers into open source software development. > Students work with an open source organization on a 3 month programming > project during their break from school. Read more about the program here: > https://summerofcode.withgoogle.com/ > > The deadline for organisations to apply is January 23, 2018 which is fast > approaching. As an open source evangelist and a Pharo developer, I would > like to invite all the experienced members to be a part of the "GSoC 2018 > with Pharo Consortium" Team and mentor students. Propose fresh ideas for > projects which shall help improve Pharo or volunteer to mentor any of the > existing one (Listed here: http://gsoc.pharo.org/) To add your own > project > idea to the list, visit http://gsoc.pharo.org/#adding-a-proposal > > Looking forward to an appreciable representation from the Pharo community. > > Best regards > Jigyasa Grover > Pharo Consortium Org Admin, Google Summer of Code 2017 [hidden email] > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

Jan. 17, 2018