March 2017 - Pharo-users - lists.pharo.org

customizing veryDeepCopy
by Peter UhnÃ¡k March 2, 2017

March 2, 2017

Hi, is there a way of customizing what should be copied during veryDeepCopy? For example I want to clone my (domain) model tree, however the objects have Announcers which I do not want to copy. Alternative is of course to implement the copying behavior by myself, but I feel like veryDeepCopy should be the appropriate way, no? Thanks, Peter

4 3

Google Summer of Code 2017: Call for students for Pharo Consortium
by Serge Stinckwich March 2, 2017

March 2, 2017

*** Please forward this message to students that might be interested *** Heartiest Congratulations ! Pharo Consortium has been selected as a mentor organisation for Google Summer of Code 2017. Google Summer of Code is a global program focused on introducing students to open source software development. Students work on a 3 month programming project with an open source organisation during their break from university. Read more at https://summerofcode.withgoogle.com/ Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback (think IDE and OS rolled into one). Everything in Pharo is an object. The entire syntax of Pharo fits on a postcard coding can be done directly in the debugger. Pharo has super cool tools that empower you and make you super efficient. Pharo's goal is to deliver a clean, innovative, free and open-source immersive environment. By providing a stable and small core system, excellent developing tools, and maintained releases, Pharo is an attractive platform to build and deploy mission critical applications. Pharo fosters a healthy ecosystem of both private and commercial contributors who advance and maintain the core system and its external packages. More information about Pharo is available here: http://www.pharo.org/ We invite all the prospective eligible students to code their summer away with Pharo Consortium. Student Responsibilities ...to your Mentor - Submit quality work - Regularly communicate work completed, what you intend to do next, and blockers - Ask for help when something is preventing you from achieving a goal - Give indication that you are alive and working daily (GSoC) - Re-evaluate work scope when significantly ahead of expectations (GSoC) - Communicate with your mentor AND the broader community - Inform when work capacity will be reduced, as early as possible (e.g., family, health, other work) (GSoC) - Listen and respond to feedback ...to the Org Admin Let them know when there are - Interaction issues with any mentor or community member - Significant disagreements involving your work or changes to your work plan Read more about responsibilities here: https://developers.google.com/open-source/gsoc/help/responsibilities Hence, we invite enthusiastic student developers contributors to work with Pharo Consortium for GSoC 2017. 1. A first list of projects are available here : http://gsoc.pharo.org/ but more can be found by interacting with mentors from the Pharo community. 2. Join dedicated channels, #gsoc-students for general interactions with students on Pharo slack. In order to get an invitation for pharoproject.slack.com visit the URL here: http://slackinvites.pharo.org/ Discuss with mentors about the complexity and skills required for the different projects. 3. Please help fix bugs, open relevant issues, suggest changes, additional features, help build a roadmap, and interact with mentors on mailing list and/or slack to get a better insight into projects. Better the contributions, Better are the chances of selection. Before applying: * Knowledge about OOP * Basic idea about Pharo & Smalltalk syntax and ongoing projects * Past experience with Pharo & Smalltalk * Interaction with organisation You can start with the Pharo MOOC : http://files.pharo.org/mooc/ Guidelines for Proposal: * Introduction: Clearly defined problem. Current state of things. Issues you wish to solve and why. Conclude with solution. * Project goals: Format it like a list. Propose a clear list of deliverables, explaining exactly what you promise to do and what you do not plan to do. âFuture developmentsâ can be mentioned. It is better to promise less and deliver more than to promise a lot and then fall short. * Implementation: Longer and more detailed. Provide technical details, show that you understand the technology and illustrate key technical elements of your proposed solution. * Timeline: Make it weekly. Set goals for each week. Be upfront about other commitments, including exams, classes, travel, internships, jobs, etc. * Benefits to Community: Make your case a benefit to the organization. * Related Work: Research and write how the project fits into the target organization. Explain related works, similarities & differences. * About me: Provide full contact information, email addresses, websites, IRC nick, postal address and telephone. Write a few sentences about yourself, previous experiences and why you think youâre the best for this job. Submit your proposal early. Keep it short. Include necessary information. Get it reviewed in the mailing list or Slack channel before submitting it. The deadline for submitting your proposal is March 20th to April 3rd on https://summerofcode.withgoogle.com/ Looking forward to great talent joining our organisation this summer. Warm Regards Pharo Organisation Admins (Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk)

2 1

Fwd: Welcome to GSoC 2017!
by Serge Stinckwich March 2, 2017

March 2, 2017

Dear all, please find below more information about the GSOC 2017 program. Among the changes for 2017 that we should pay attention, two are quite important: - Students can only be accepted into GSoC 2 times. Google Admins will do a sanity check on all accepted students once you select your students in late April so you do not need to be concerned about this. - If you are a university, we expect you to select students outside of your program. Selecting students from your university is okay but if *all* of the students you select are from your university then you likely wonât be accepted into GSoC again. I will ask for the last item, because I dunno if they are talking about the Pharo org or the mentors. Regards, ---------- Forwarded message ---------- From: Google Summer of Code <summerofcode-noreply(a)google.com> Date: Thu, Mar 2, 2017 at 12:15 AM Subject: Welcome to GSoC 2017! To: sergestinckwich(a)gmail.com [image: Google Summer of Code] Hi Serge Stinckwich, This year marks our biggest program ever! We have 201 open source organizations participating in GSoC 2017 and we expect to accept more students than ever before as well. And welcome to 37 organizations participating in their first GSoC! Right now you should be chatting with proactive, excited students. Remember to keep your Ideas List updated and make it clear and simple to understand so students can easily find your Ideas - if it requires multiple clicks to get to the Ideas List that is not ideal. We want to give you a quick overview of the next few months and address some of the common questions you may have these first few weeks of the program. *New changes (and some reminders) for 2017* - There are 3 evaluation periods this year where mentors are required to complete an evaluation of their student. After the first 4 weeks of coding, after 8 weeks of coding and then at the end (after 12 weeks of coding). The evaluation forms are shorter than previous years so they should take less time to complete. - Students can only be accepted into GSoC 2 times. Google Admins will do a sanity check on all accepted students once you select your students in late April so you do not need to be concerned about this. - If you are a university, we expect you to select students outside of your program. Selecting students from your university is okay but if *all* of the students you select are from your university then you likely wonât be accepted into GSoC again. - New org payment system using Payoneer. We are no longer requiring OAs to register for a Google supplier account and instead orgs will do what students do and create an account with Payoneer. This will allow for orgs to receive payments *much* faster, with orgs receiving their stipend payments in September. (more details to come in May) - We are now allowing 13-17 year olds to be mentors for GSoC as long as they have parental consent to be a part of the program. An additional form is required. *Inviting Mentors to your Organization* Organization Administrators should be reaching out to mentors and sending them invitations to be a part of their organization. The mentor will then click the link in the email they receive to create their account. PLEASE NOTE: Right now first time mentors should wait a few days to register until we have announced that we have fixed a small validation error on the site not allowing mentors to choose â0â as an option to the question âHow many times have you participated as a GSoC mentor previously?â They canât edit that field once they put a number into it and we are trying to get a good idea of how many new mentors we have each year. Thank you for your patience. *GSoC Mentor-invite Mailing List* For those that have opted into the GSoC mentor mailing list (available on your profile page) we will bulk add you to the list on March 6th. Then we will add additional folks who opt in about once a week throughout the program period. You can remove yourself through the groups interface at any time. You can also update your settings to receive a daily digest of emails and other options. This generally is not a very high traffic list but there will be more questions over the next two months on this list than probably later in the program. The GSoC mentor mailing list is a great way to ask questions of other org admins and mentors and to get their feedback and help. *Important Upcoming Dates* *Now - March* *20:* Proactive students will reach out to you and ask questions about your ideas list and receive feedback from your org so they can start crafting their project proposals. *March 20 - April 3 16:00 UTC*: Students will submit their draft proposals through the program website for you to give solid feedback on. *April 3 - 16:* Review all submitted student proposals with your org and consider how many you want to select and how many you can handle. Decide on the minimum/maximum number of student slots to request. *April 17, 16:00 UTC*: Deadline to submit slot requests (OAs enter requests) *April 19, 16:00 UTC*: Slot allocations are announced by Google *April 19 - 24 16:00 UTC* : Select the proposals to become student projects. At least 1 mentor must be assigned to each project before it can be selected. (OAs enter selections) *April 24 - May 4:* Google Program Admins will do another review of student eligibility *May 4*: Accepted GSoC students/projects are announced *May 4 - 29*: Community Bonding Period *May 29*: Deadline to notify Google Admins of an inactive student that you wish to be removed from the program *May 30*: Coding begins *June 26-30*: First evaluation period - mentors evaluate their students and students evaluate mentors *July 24 - 28*: Second evaluation period - mentors evaluate students, students evaluate mentors *August 21- 29*: Students wrap up their projects and submit final evaluation of their mentor *August 29 - September 5*: Mentors submit final evaluations of students *September 6*: Students passing GSoC 2017 are announced *More Information* If you have not yet read the Roles and Responsibilities <https://developers.google.com/open-source/gsoc/help/responsibilities>undefined page created with the help of GSoC Org admins and mentors, we highly encourage you to read this and share it with your prospective mentors - it will help everyone understand what is expected of them over the next 6 months. You may also want to check out the Mentor Manual, which contains important information for both Mentors and Org Admins at each stage of the program. If you have any questions please contact us at gsoc-support(a)google.com undefined Best, Stephanie and Mary Google Open Source Programs Office This email was sent to serge.stinckwich(a)gmail.com. You are receiving this email because of your participation in Google Summer of Code 2017. https://summerofcode.withgoogle.com To leave the program and stop receiving all emails, you can go to your profile <https://summerofcode.withgoogle.com/dashboard/profile/> and request deletion of your program profile. For any questions, please contact gsoc-support(a)google.com. Replies to this message go to an unmonitored mailbox. Â© 2017 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

2 1

GMail example html
by Jeff Gray March 2, 2017

March 2, 2017

I copied the example from Zodiac. Changed to my credentials and got a simple message mailed out successfully. Then I tried changing to an html message: | mailMessage | mailMessage := MailMessage empty. mailMessage setField: 'subject' toString: 'Mail Test'. mailMessage body: (MIMEDocument contentType: MIMEDocument contentTypeHtml content: '<html><body>This is test Pharo <> </body></html>'). ZdcSecureSMTPClient sendUsingGMailAccount: 'myname(a)mydomain.com' password: 'MyPWord01' to: 'myothername(a)myotherdomain.com' message: mailMessage. What appeared in the email content was this: <html><body>This is test Pharo <[http://pharo.org> </body></html]http://pharo.org'>Pharo </body></html> Where did I go wrong? Thanks. -- View this message in context: http://forum.world.st/GMail-example-html-tp4936801.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

1 1

Re: [Pharo-users] Socket, network, testing and coding
by Juraj Kubelka March 2, 2017

March 2, 2017

Hi, > El 28-02-2017, a las 14:27, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> escribiÃ³: > > > De: Benoit St-Jean <bstjean(a)yahoo.com> > Asunto: Socket, network, testing and coding > Fecha: 28 de febrero de 2017, 14:27:58 CLST > Para: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Responder a: Benoit St-Jean <bstjean(a)yahoo.com> > > > Hi guys, > > Quick question regarding sockets and testing. > > I'm trying to implement a simple communication protocol to exchange data (strings) between 2 images and I was wondering what was the easiest way to test/develop my code? I want to be able to do something similar to a chat client between 2 images where none of those 2 images acts as a server. So data can originate from any of those 2 images and both images have to "listen" to each other. Besides, both images would have to transmit/receive on the same port. > > 1) Is this possible (the way I want to do/test it)? Yes, you can test it. > 2) How do I simulate something like this on a *single* machine running those 2 images? Something like this: | listener clientSocket serverSocket | listener := Socket newTCP. [ listener listenOn: 0 backlogSize: 4. clientSocket := Socket newTCP. clientSocket connectTo: #[127 0 0 1] port: listener localPort. clientSocket waitForConnectionFor: 1. serverSocket := listener waitForAcceptFor: 1. ] ensure: [ listener destroy ]. since then you have client and server socket. You can call it clientOne, clientTwo. > 3) Do I need to have one of those 2 images act as a "serverâ ? At least one image has to serve as a server (listen to connections). Maybe you could use a discovery service protocol. I do not have any experience about it. > 4) Any helpful tip and/or interesting link to propose? > 5) Can you think of any simple code or example I could look at to understand what I need to do? There is a Trantor project where you could learn from: http://smalltalkhub.com/#!/~EvanDonahue/Trantor <http://smalltalkhub.com/#!/~EvanDonahue/Trantor> You can check an example here: TRNLog exampleOpenChatWithUserIdUsingTrantor But you are going to be more interested in testing: TrantorNodeTest Download it using: Gofer it smalltalkhubUser: 'EvanDonahue' project: 'Trantor'; configuration; loadBleedingEdge. And maybe Zinc (part of the Pharo image) has also good test examples. Cheers, Juraj > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > >

2 1

Re: [Pharo-users] Socket, network, testing and coding
by Evan Donahue March 2, 2017

March 2, 2017

Hi, Depending on what exactly you are doing, you could either use or look at the source of: http://smalltalkhub.com/#!/~EvanDonahue/P2P It is basically a simple API for setting up image-to-image networked communication. You make a server object, set it running, and then open a connection from a client image. The threading etc is all handled. A simple chat system only takes a couple lines, and there is a well commented example of a simple multi (3+) person chat server in the examples package. Yes, one image does need to be the "server," but it only matters for setting up the initial connection. After that, they are essentially peer to peer, and either party can send to the other. I would imagine that this still fits your requirements, unless you have a very special use case like UDP hole punching, which I ultimately plan to implement one day when I return to this project. But the current form is very stable and complete. Let me know if you have any questions. Cheers, Evan -- View this message in context: http://forum.world.st/Proof-of-Concept-FileTree-and-Fossil-tp4936260p493649… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 1

[ANN] Pharo Sprint tomorrow, March 3
by Marcus Denker March 2, 2017

March 2, 2017

We will organize a Pharo sprint / Moose dojo March, 03, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Clean issue tracker to prepare for release Pharo6 â¢ remove Pharo6 tag from not-important cases â¢ Check Pharo5 Issues and pending back-ports Remotely, you can join us on Slack. During the sprint, we will try to synchronize local and remote Pharo sprinters. Known Local Sprint meetings: Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come. Santiago/Chile: At DCC (https://www.dcc.uchile.cl) Universidad de Chile. Avenida Beauchef 851, edificio poniente, tercer piso, oficina 307, Santiago, Chile. Chile sprint will be 9:00 local time and finish at a lunch time (13:00). https://association.pharo.org/event-2451866

2 2

Re: [Pharo-users] Socket, network, testing and coding
by Denis Kudriashov March 2, 2017

March 2, 2017

Hi. Look also on these projects (in order from low level to high): - http://smalltalkhub.com/#!/~Pharo/TCPServer. - http://smalltalkhub.com/#!/~Pharo/Basys - http://smalltalkhub.com/#!/~Pharo/Seamless 2017-02-28 18:27 GMT+01:00 Benoit St-Jean via Pharo-users < pharo-users(a)lists.pharo.org>: > > > ---------- ÐÐµÑÐµÑÑÐ»Ð°ÐµÐ¼Ð¾Ðµ ÑÐ¾Ð¾Ð±ÑÐµÐ½Ð¸Ðµ ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Tue, 28 Feb 2017 17:27:58 +0000 (UTC) > Subject: Socket, network, testing and coding > Hi guys, > > Quick question regarding sockets and testing. > > I'm trying to implement a simple communication protocol to exchange data > (strings) between 2 images and I was wondering what was the easiest way to > test/develop my code? I want to be able to do something similar to a chat > client between 2 images where none of those 2 images acts as a server. So > data can originate from any of those 2 images and both images have to > "listen" to each other. Besides, both images would have to > transmit/receive on the same port. > > 1) Is this possible (the way I want to do/test it)? > 2) How do I simulate something like this on a *single* machine running > those 2 images? > 3) Do I need to have one of those 2 images act as a "server" ? > 4) Any helpful tip and/or interesting link to propose? > 5) Can you think of any simple code or example I could look at to > understand what I need to do? > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > >

1 0

Re: [Pharo-users] Seaside : including a static stylesheet.
by Dominique Dartois March 1, 2017

March 1, 2017

Thank you Sven. I have tried successfully the FileLibrary but I want to be able to modify the stylesheet without using Pharo which will be running on a remote server. Using static documents seemed the solution to me. > On 28 Feb 2017, at 18:53, Dominique Dartois <dom(a)dartois.org> wrote: > > In the Seaside book, chapter 17.2 I read I can include a stylesheet this way : > > updateRoot: anHtmlRoot > super updateRoot: anHtmlRoot. > anHtmlRoot stylesheet url: 'http://seaside.st/styles/main.css' > > On my development machine (macOS) I use http://localhost:8080/myApp as the server address and I don?t know the root directory of the Seaside integrated web server. > > Can anyone help me to find this directory? The easiest way is to use a Seaside FileLibrary subclass to serve your static CSS file. This is described in that same chapter 17. > Thanks. --- Dominique Dartois

2 1

Voyage and Association
by Hilaire March 1, 2017

March 1, 2017

Hi, I am having trouble to persist in a Voyage repository Association formed with a key being a non string object (let's say a Month) and value a non basic object, instance of a model object. So far, I have an error bsonTypeCode not understood on my value object. I could implement bsonTypeCode, but I suspect I will have trouble too with the key, as I see from Voyage code it is persisted as a String. An idea how to overcome this (without modifying my model)? Fuel was persisting it fine. Thanks Hilaire -- Dr. Geo http://drgeo.eu

2 2