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

Re: [Pharo-users] Pharo Spur 64 VM

by ClÃ©ment Bera

Hi Raffaello, Reportedly, the VM without the JIT (pure interpreter, also called PharoS or StackVM) works on windows 64 and FFI works with it if the VM compiled with clang but not with gcc. There is no configuration for Pharo right now. It should not be hard to add a pharo configuration to have the image start-up, but I don't think several libraries such as Athens/Cairo or libgit would work out of the box, so it's not clear such a configuration would make a lot of sense. There is no PharoS-spur64 repository on files.pharo.org right now either. Windows support is not ready mostly because: - Some C types are different in x64 between Unix and windows - Calling conventions are different in x64 bits between Unix and Windows Calling conventions have impact in switching between the interpreter and the JIT runtime and in FFI. C types being different have impact for the VM compilation and in FFI. If someone looks into it, I guess in a day of work we could have the Stack VM working with Spur 64 for Pharo without support for some librairies. There might be uncommon crashes to fix over the first week of use. With several more weeks of work (maybe a couple months), the StackVM with all libraries should be production-ready. The JIT support will take more time, hopefully it will be done in a year from now. Maybe I should mention that the company who funded 64 bits support is using the VM on Mac for development and Linux for production, so Windows was not a priority and not done. We have to rely on open-source contributors, non paid, to add Windows support and that takes time. Nicolas Cellier added the support for the 64 bits Stack VM on his free time. If someone is investing money, the 64 bits Windows VM could reach production sooner (I guess within 6 months) because someone could work full time on it. Regards, On Thu, Mar 2, 2017 at 4:04 PM, <raffaello.giulietti(a)lifeware.ch> wrote: > On 07/02/17 07:13, Esteban Lorenzano wrote: > > > >> On 6 Feb 2017, at 21:41, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> > wrote: > >> > >> Le 06/02/2017 Ã 21:31, Benoit St-Jean via Pharo-users a Ã©crit : > >> > >> > >> Hi! > >> > >> IIRC, the windows VM will need some more time to be ready. Only Linux > >> and OSX ones are usable at the moment. > > > > ^ this. > > as Cyril says, win 64bits vm is still not ready (and it will take some > more time to be). > > > > Esteban > > > > > Just for general curiosity, what are the main stumbling blocks in the > road to a Windows 64 bit Pharo? > > > Raffaello > > >

March 2, 2017

Re: [Pharo-users] customizing veryDeepCopy

by Denis Kudriashov

Hi. Look how Morph implements it. Morphs customize it a lot 2017-03-02 16:08 GMT+01:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > 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 >

March 2, 2017

customizing veryDeepCopy

by Peter UhnÃ¡k

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

March 2, 2017

Re: [Pharo-users] Pharo Spur 64 VM

by raffaello.giulietti＠lifeware.ch

On 07/02/17 07:13, Esteban Lorenzano wrote: > >> On 6 Feb 2017, at 21:41, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >> >> Le 06/02/2017 Ã 21:31, Benoit St-Jean via Pharo-users a Ã©crit : >> >> >> Hi! >> >> IIRC, the windows VM will need some more time to be ready. Only Linux >> and OSX ones are usable at the moment. > > ^ this. > as Cyril says, win 64bits vm is still not ready (and it will take some more time to be). > > Esteban > Just for general curiosity, what are the main stumbling blocks in the road to a Windows 64 bit Pharo? Raffaello

March 2, 2017

Re: [Pharo-users] Fwd: Welcome to GSoC 2017!

by Ben Coman

On Thu, Mar 2, 2017 at 3:49 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com > wrote: > 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. > I think in either case, it is just a matter of spreading the slots around. Any concentration of slots in one location would be poor. But there are 12 academic partners, so hopefully there'll be some good student applicants from each, plus others. cheers -ben > > 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/ >

March 2, 2017

Re: [Pharo-users] GMail example html

by Jeff Gray

Gah - nabble rendered my source. It was supposed to show a string with an anchor tag embedded in it :-( -- View this message in context: http://forum.world.st/GMail-example-html-tp4936801p4936805.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 2, 2017

GMail example html

by Jeff Gray

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.

March 2, 2017

Re: [Pharo-users] Socket, network, testing and coding

by Denis Kudriashov

2017-03-01 4:39 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: > There is a Trantor project where you could learn from: > http://smalltalkhub.com/#!/~EvanDonahue/Trantor > You can check an example here: TRNLog exampleOpenChatWithUserIdUsing > Trantor > But you are going to be more interested in testing: TrantorNodeTest > Finally I look at Trantor too (I read about it in past) So I see that kind of remote Smalltalk was implemented there but with special idea on Replicated Datatypes which I not understand from code. But I am sure if it would be implemented on top of Seamless many things will be simplified a lot and we will have very nice network stack: TCPServer -> BasysNetwork -> SeamlessNetwork -> "Replicated object network". Look at Basys and Seamless <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> docs if you are interesting in such solution

March 2, 2017

Re: [Pharo-users] Socket, network, testing and coding

by Denis Kudriashov

2017-03-01 5:09 GMT+01:00 Evan Donahue <emdonahu(a)gmail.com>: > Hi, > > Depending on what exactly you are doing, you could either use or look at > the > source of: > > http://smalltalkhub.com/#!/~EvanDonahue/P2P > I look at P2P code. It is very close to my Basys framework. If you interesting to compare look at doc https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…. One difference for example is that basys peers maintain connection pools on each network side.

March 2, 2017

Re: [Pharo-users] [ANN] Pharo Sprint tomorrow, March 3

by Johan Fabry

Whoops â¦ many many apologies! This was supposed to go directly to Marcus. Jetlag is a b*tch. -- Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > On 02 Mar 2017, at 10:11, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Marcus, I should be there between 10 and 10:30. I will call you when I arrive, your number is still +33 6 17 43 75 42 ? > > I will need to leave early though :-( I think 3PM at the latest â¦ > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > >> On 02 Mar 2017, at 08:53, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> 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 >> >> >> >

March 2, 2017