- Pharo-users - lists.pharo.org

Re: [Pharo-users] GSOC 2016 Application update

by Alexandre Bergel

Thanks Serge! This is a very important effort you are leading Alexandre > On Feb 17, 2016, at 5:27 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > Dear all, > > just a quick update to GSOC application of Pharo this year > > - We have enough topics I guess. I already send a reminder on the > various mailing-list. > List of topics here: > https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics… > > We have to generate the html from the topics list and put the result > on the gsoc.pharo,org website. I ask Uko to have a look to this, but I > don't want to loose to much time on this. I was wondering if we should > transform the list as a Markdown document on github just to keep it > simple. > > - Finish the 2016 Application and Organization profile on Google > website. The questions are a little bit different from 2015 and we > should complete them. > Please find below the answers to the questions right now. > > I add in parenthesis, the number of words of each answers and the > maximum allowed. > > Please us to refine our answers. We need to wrote "guidance for students". > > Thank you. > > ========================================================================== > > Why does your org want to participate in Google Summer of Code? (898/1000) > > Supporting open-source projects is one of the most important > objectives of the Pharo community. Participating at GSoC will increase > the visibility of Pharo project efforts, thus favoring interactions > with other communities. We are also interested in providing > interesting projects to students allowing them to learn and have a fun > job for the summer. > > We expect also to bring more people into our community. That's very > interesting as the Pharo community is trying to be innovation-driven > and more open minded than the Smalltalk community from which we have > evolved. We want people from other communities to join ours and we are > also interested in what is happening outside and to share experiences > or ideas. Fortunately for us, dynamic languages like Python, Ruby, > among others, enjoy increasing popularity. This is an excellent > opportunity to join, show and learn from and with other communities. > > ========================================================================== > > How many potential mentors have agreed to mentor this year? > > 11-15 > > ========================================================================== > > How will you keep mentors engaged with their students? (668/1000) > > We chose mentors from people who are long time in our community and > have proven to be reliable. Usually we try to match mentors with > projects that are important for themselves. This means that the mentor > has an own interest in the project that the student doing it. Also we > try to ensure that there is a co-mentor for every project who can > replace the main mentor if needed. Also it is very important for us to > keep a good record and expand the community, and in previous years we > even managed to organize our own "summer code" programs for a couple > of students, so in the worst case we will find a replacement from the > core part of the community, or the board itself. > > ========================================================================== > How will you help your students stay on schedule to complete their > projects? (886/1000) > > As mentioned before we've already organized our own small "summer > code" programs, as usually we have more interested students than the > fundings that we can spend for them. However we acknowledge that > maintaining student's motivation is very important. We are a very open > and friendly community, and we encourage the students to take part on > the mailing list discussions from the beginning of their projects. > There is a specific pharo-users mailing-list more suitable for > beginners than the pharo-dev mailing-list. > Usually students get feedback and requests from the beginning of their > projects, and they have people interested in the prototypes as soon as > they are ready. From our experience having real users for the project > serves as the best motivation. Also our mentors try to maintain a > constructive and friendly discussion to ensure that the student enjoys > working on the project. > > ========================================================================== > > How will you get your students involved in your community during GSoC? > (608/1000) > > As mentioned above we encourage students to announce their status on > the mailing list as well as discuss questions on our Slack channel. We > also encourage them to write blogs about their project experience to > both promote themselves and give others an opportunity to familiarize > with the project more and share ideas between students. We are > organizing PharoDays every year (this year in Belgium, website: > http://pharodays2016.pharo.org) and we participate to the ESUG > (European Smalltalk User Group) conference in the end of each summer > and plan to invite the students of the best projects to present there. > > ========================================================================== > > Has your org been accepted as a mentoring org in Google Summer of Code before? > > Yes > > ========================================================================== > > Which years did your org participate in GSoC? > > - 2012 > - 2010 > - 2008 > - 2007 > > ========================================================================== > > What is your success/fail rate per year? > > - 2012: 10 projects pass / 3 fail > - 2010: 6 projects pass / 0 fail > - 2008: 5 projects pass / 0 fail > - 2007: 5 projects pass / 0 fail > > > ========================================================================== > > If your org has applied for GSoC before but not been accepted, select the years: > > - 2015 > - 2014 > - 2013 > > ========================================================================== > > What year was your project started? > > 2008 > > ========================================================================== > > Short description of Pharo (166/180) > > Pharo is a pure object-oriented programming language and IDE. We > innovate every part of the development experience to come up with the > best way to work with software. > > ========================================================================== > > Long description of Pharo (1401/2000) > > Pharo is a pure object-oriented programming languagea and IDE. > Pharo's goal is to minify the gap between the state of your mind and > the functionality of your application. Whether you are writing code, > debugging it, inspecting an object, hacking the runtime or tweaking > the IDE there should be nothing that stops you from engaging the > action with ease and grace. > > We work both on improving Pharo itself and on developing end user > applications in Pharo. Below you will see the highlights of most > prominent Pharo features. > > ### Simple & powerful language > No constructors, no types declaration, no interfaces, no primitive > types. Yet a powerful and elegant language with a full syntax fitting > in one postcard! Pharo is objects and messages all the way down. > > ### Feel a live environment > Feel the joy of having immediate feedback at any moment of your > development: Developing, testing, debugging. Even in production > environments, you will never be stuck in compiling and deploying steps > again! > > ### Amazing debugging experience > The Pharo environment includes a debugger unlike anything you've seen > before. It allows you to step through code, restart the execution of > methods, create methods on the fly, and much more! > > ### Pharo is yours > Pharo is made by an incredible community, with more than 80 > contributors for the last revision of the platform and hundreds of > people contributing constantly with frameworks and libraries. > > ========================================================================== > > Guidance for students on how to apply to your organization. Should > include any prerequisites or requirements. You may wish to include a > template or tips for their proposals. > > (0/1500) > > TBD > > ========================================================================== > > - > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 17, 2016

Re: [Pharo-users] [Pharo-dev] gtoolkit 3.10 overview

by Alexandre Bergel

Pretty cool! Alexandre > On Feb 16, 2016, at 7:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I promised to send a summary of the larger changes that came with the recent integration of GToolkit 3.10. Here it is: > http://www.humane-assessment.com/blog/gtoolkit-3-10/ > > Please let us know what you think. > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "What is more important: To be happy, or to make happy?" > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 17, 2016

Re: [Pharo-users] gtoolkit 3.10 overview

by Damien Cassou

Hi Tudor, Tudor Girba <tudor(a)tudorgirba.com> writes: > I promised to send a summary of the larger changes that came with the recent integration of GToolkit 3.10. Here it is: > http://www.humane-assessment.com/blog/gtoolkit-3-10/ thank you for the detailed changelog. Please pay attention to the Settings system. I have the impression that what you did might forbid you to remove any extension in the future. What I see happening is that: 1. people start deactivating some extensions through the Settings 2. they write their Settings in a file so the settings are available for all images 3. in this file, settings are deactivated with Smalltalk code that send setting-specific messages to specific objects 4. you decide to remove an extension and remove the corresponding setting method 5. the user downloads the new Pharo and gets an error because his setting file sends messages that are not understood anymore. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Feb. 17, 2016

Re: [Pharo-users] Font crash Pharo 50 Windows

by Justine STIENNE

I was with StÃ©phane, and I think it's just random. But it's ok, he sent it to the group Pharo dev. Justine 2016-02-17 13:53 GMT+01:00 Blondeau Vincent <vincent.blondeau(a)worldline.com> : > Hi, > > > > Have you done something special to raise these bugs or it is just random ? > > Vincent > > > > *De :* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *De la > part de* Justine STIENNE > *EnvoyÃ© :* mercredi 17 fÃ©vrier 2016 13:40 > *Ã :* Any question about pharo is welcome > *Objet :* Re: [Pharo-users] Font crash Pharo 50 Windows > > > > There is an other bug: > > UndefinedObject(Object)>>doesNotUnderstand: #* > FreeTypeFont>>height > LogicalFont>>height > TextStyle>>newFontArray: > TextStyle class>>fontArray: > [ TextStyle fontArray: {self} ] in LogicalFont(AbstractFont)>>textStyle > Dictionary(Collection)>>detect:ifFound:ifNone: > Dictionary(Collection)>>detect:ifNone: > > > > 2016-02-17 13:33 GMT+01:00 Justine STIENNE <justine.stienne(a)gmail.com>: > > on > > > > 2016-02-17 13:33 GMT+01:00 Justine STIENNE <justine.stienne(a)gmail.com>: > > > > Ok we got several crashes related to fonts on > > > charmaps > "Answer an Array of Strings naming the different character maps > available for setCharMap:" > charmaps ifNil: [ > charmaps := Array new: numCharmaps. > self getCharMapsInto: charmaps ]. > ^charmaps > > > > > > ------------------------------ > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. >

Feb. 17, 2016

Re: [Pharo-users] Font crash Pharo 50 Windows

by Blondeau Vincent

Hi, Have you done something special to raise these bugs or it is just random ? Vincent De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Justine STIENNE EnvoyÃ© : mercredi 17 fÃ©vrier 2016 13:40 Ã : Any question about pharo is welcome Objet : Re: [Pharo-users] Font crash Pharo 50 Windows There is an other bug: UndefinedObject(Object)>>doesNotUnderstand: #* FreeTypeFont>>height LogicalFont>>height TextStyle>>newFontArray: TextStyle class>>fontArray: [ TextStyle fontArray: {self} ] in LogicalFont(AbstractFont)>>textStyle Dictionary(Collection)>>detect:ifFound:ifNone: Dictionary(Collection)>>detect:ifNone: 2016-02-17 13:33 GMT+01:00 Justine STIENNE <justine.stienne(a)gmail.com<mailto:justine.stienne@gmail.com>>: on 2016-02-17 13:33 GMT+01:00 Justine STIENNE <justine.stienne(a)gmail.com<mailto:justine.stienne@gmail.com>>: Ok we got several crashes related to fonts on charmaps "Answer an Array of Strings naming the different character maps available for setCharMap:" charmaps ifNil: [ charmaps := Array new: numCharmaps. self getCharMapsInto: charmaps ]. ^charmaps ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Feb. 17, 2016

Re: [Pharo-users] Font crash Pharo 50 Windows

by Justine STIENNE

There is an other bug: UndefinedObject(Object)>>doesNotUnderstand: #* FreeTypeFont>>height LogicalFont>>height TextStyle>>newFontArray: TextStyle class>>fontArray: [ TextStyle fontArray: {self} ] in LogicalFont(AbstractFont)>>textStyle Dictionary(Collection)>>detect:ifFound:ifNone: Dictionary(Collection)>>detect:ifNone: 2016-02-17 13:33 GMT+01:00 Justine STIENNE <justine.stienne(a)gmail.com>: > on > > > 2016-02-17 13:33 GMT+01:00 Justine STIENNE <justine.stienne(a)gmail.com>: > >> >> Ok we got several crashes related to fonts on >> >> >> charmaps >> "Answer an Array of Strings naming the different character maps >> available for setCharMap:" >> charmaps ifNil: [ >> charmaps := Array new: numCharmaps. >> self getCharMapsInto: charmaps ]. >> ^charmaps >> > >

Feb. 17, 2016

Re: [Pharo-users] Font crash Pharo 50 Windows

by Justine STIENNE

on 2016-02-17 13:33 GMT+01:00 Justine STIENNE <justine.stienne(a)gmail.com>: > > Ok we got several crashes related to fonts on > > > charmaps > "Answer an Array of Strings naming the different character maps > available for setCharMap:" > charmaps ifNil: [ > charmaps := Array new: numCharmaps. > self getCharMapsInto: charmaps ]. > ^charmaps >

Feb. 17, 2016

Font crash Pharo 50 Windows

by Justine STIENNE

Ok we got several crashes related to fonts on charmaps "Answer an Array of Strings naming the different character maps available for setCharMap:" charmaps ifNil: [ charmaps := Array new: numCharmaps. self getCharMapsInto: charmaps ]. ^charmaps

Feb. 17, 2016

Re: [Pharo-users] GSOC 2016

by Serge Stinckwich

Regarding the html generation from topics, Peter and Uko are working on something to automate everything. If you want to propose new ideas, please send github PR to : https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics… Can we add Peter (github ID: peteruhnak) as a contributor to Pharo org on github ? Thank you all. On Thu, Feb 11, 2016 at 2:02 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Dear pharoers, > > this year Pharo consortium (and community) is going to take part in the > Google Summer of Code event[1] as a standalone organization. This is > an opportunity to promote Pharo, get some job done and have students > paid. > > Currently we are at the most important stage as we are preparing the > organization application, and hoping that we will be accepted and > granted decent amount of project slots. Everyone can help with > application by submitting ideas for student projects. > > I reuse the list of the last year : > https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics… > > It is in STON format, and result is being generated at: http://gsoc.pharo.org/ > > Please add (or update) your ideas following the format of existing projects and > open a pull request with them (you will need a github account). > Preferably submit ideas with possible mentors, but if none are > available at the moment ideas without mentors are also welcome. > > The template to submit projects is : > > PharoTopic new > title: 'The name of your project; > contact: 'email address'; > supervisors: 'Supervisors names'; > keywords: 'keywords separated by spaces; > context: 'a description of the context of the project'; > goal: 'description of the goal'; > level: 'Beginner or Intermediate or Advanced'; > yourself. > > We will need a lot of projects/idea before February 19th 2016, the > deadline for applying to GSOC 2016. > > Do not hesitate to ask me questions. > > If you don't know how to edit the list, please send your project description > following the template to me. > > [1] https://summerofcode.withgoogle.com/ > > Regards, > > -- > 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/

Feb. 17, 2016

Re: [Pharo-users] GSOC 2016 Application update

by Stephan Eggermont

On 17-02-16 11:14, Martin BÃ¤hr wrote: > Excerpts from Stephan Eggermont's message of 2016-02-17 10:30:24 +0100: >>> How will you help your students stay on schedule to complete their >>> projects? (886/1000) >> I have had excellent experiences with a compressed scrum, using a (near) >> daily cycle where the student demos todays code and discusses steps for >> the next day. > > i am not very familiar with scrum. it was my understanding that daily standup > is part of a regular scrum. so you make a plan for a week or two, and talk > about the progress every day. Yes. I found a scheduling horizon of two weeks way too far, especially when starting a project. Experiments need to be much smaller, and doing a daily demo of both successful and unsuccessful experiments helped uncover failures in mental models quickly. Stephan

Feb. 17, 2016