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

[pharo-project/pharo-core]
by GitHub March 24, 2017

March 24, 2017

Branch: refs/tags/60451 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 6f7772: 60451
by GitHub March 24, 2017

March 24, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 6f7772a796bf7238b33ebcaca3263b10a7cc591e https://github.com/pharo-project/pharo-core/commit/6f7772a796bf7238b33ebcac… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-24 (Fri, 24 Mar 2017) Changed paths: M Refactoring-Core.package/RBMoveMethodToClassRefactoring.class/instance/transforming/transform.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60450.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60451.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60450.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60451.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60451 19863 RBMoveMethodToClassRefactoring reset method protocol https://pharo.fogbugz.com/f/cases/19863 http://files.pharo.org/image/60/60451.zip

1 0

inspector performance improvement
by Tudor Girba March 23, 2017

March 23, 2017

Hi, Andrei and Alex did a great job at improving the performance and scalability of the inspector. There are a couple of main improvements: - Added FastTable support for the Raw presentation for all objects. This implied completing the support for the tree presentation binding to fast table. - Moved the Items presentation for collections to FastTable. - Improved the rendering of Glamour to no longer rely on the default Morph>>#adoptPaneColor. It turns out that using adoptPaneColor triggers a relayout of the morph, even if it is not visible. We extended PanelMorph in the context of Glamour with a less needy logic. I will not tell you how fast it is. I would rather want you to play with it :). The change is already in the Moose image. It is not yet in Pharo, but it will be soon. In the meantime you can be load it in Pharo 6 like this: Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'ConfigurationOfGToolkitCore'; load. (#ConfigurationOfGToolkitCore asClass project version: #stable) load To play with it, try this with both the current version and the new one and the Spec Inspector if you want (just make sure you save the image beforehand): collection := (1 to: 100000000) asArray. [collection inspect] timeToRun. collection := (1 to: 100000000). [collection inspect] timeToRun. (for these two ones notice that Items do not appear at all in the old implementation) [World inspect] timeToRun. There are still a couple of issues open, such as the sorting of the columns. We would need your help with testing this, and report possible missing issues. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

5 5

Fwd: GSoC 2017: Tips on Reviewing Student Proposals
by Serge Stinckwich March 23, 2017

March 23, 2017

Dear all, this is a short update for the Google Summer of Code 2017. The students have to submit your proposals on the Google website before April 3rd. See details below. I dunno exactly who are the students/mentors who are submitting a proposal for Pharo. Can the mentors (or students) send me in private an email about the name of the students/mentors + a title of your project ? Thank you very much. Regards, ---------- Forwarded message ---------- From: Google Summer of Code <summerofcode-noreply(a)google.com> Date: Mon, Mar 20, 2017 at 7:26 PM Subject: GSoC 2017: Tips on Reviewing Student Proposals To: sergestinckwich(a)gmail.com [image: Google Summer of Code] Hi Serge Stinckwich, Thank you for registering to be a GSoC 2017 mentor or organization administrator! We have many new mentors and organizations this year so we wanted to go through some important details to help you understand the process for the next couple of months. Please take the time to reach out to your organization administrator about what is expected of you this year as a mentor. We also encourage you to read the entire Google Summer of Code mentor manual <http://write.flossmanuals.net/gsoc-mentoring/about-this-manual/> and the Roles and Responsibilities doc if you haven't done so already. Both the manual and Roles and Responsibilities doc were written by GSoC veteran Org Admins, Mentors, former students and Google Program Admins. They have helpful information about the program and how to participate successfully at each step in GSoC. *New GSoC Orgs*: the section about participating in your first GSoC has some great tips. To see all emails sent to mentors and org admins visit this page <https://developers.google.com/open-source/gsoc/2017/mentor-oa-announcements> that will continue to be updated throughout the program. Student Proposals As of today, students are able to submit their proposals via the website. Each student may submit up to 5 proposals to the program. They can submit multiple proposals to the same organization for different projects if they wish. Historically, the students with the best proposals reach out to the orgs early to receive feedback before submitting their final proposal. To encourage more students to seek feedback on their proposals we made draft proposals part of the official proposal workflow. Be sure to refresh your dashboard periodically so that you can see when new drafts are ready to review. You will not receive an email. We are encouraging the use of Google Docs for proposals as this will allow you to comment directly on the proposal (if the student sets their sharing settings correctly). Over the next couple of weeks you will be interacting with dozens and in some cases hundreds of students interested in working with your project. We know many of you may become overwhelmed and some students can be impatient, so you may want to have an auto-responder or some sort of canned response to let students know you are looking at their proposals but it could take X days to receive a response. Students *must* submit their final proposal as a PDF through the website. It will be visible to you after the deadline for student applications (April 3 16:00 UTC). You should make your decisions on which students to accept based on the contents of the final PDF proposal and your interactions with the student. Students can delete their proposals and you will not receive an email of the deletion. If a proposal disappears from your list, it is likely because they deleted it. Working with Students All student projects must have at least 1 mentor assigned to the project. We strongly encourage assigning a second mentor as a backup mentor or co-mentor. A mentor should not be the primary mentor for more than one or two students. Mentoring can be a lot of work and we donât want anyone to burn out and become frustrated with the program. Important GSoC 2017 Dates and Deadlines *March 20 - April 3 16:00 UTC*: Mentors and Org Admins review student draft proposals and give students feedback on their proposals. *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 30*: Coding begins *June 26-30*: First evaluation period - mentors evaluate students, 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 Mentors Mailing List If you want to be included on the GSoC mentors mailing list be sure to opt in on your User Profile page. We will add anyone who has opted in to the list every few days for the next month. And then every couple of weeks throughout the program. You can always opt out once you have been added by unsubscribing using the link on any of the emails. Contact Us Please use the gsoc-support(a)google.com email address for questions so that anyone on our team can answer your question for you. We look forward to working with all of you over these next 6 months! Thanks again for being a mentor for GSoC 2017! 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/

1 0

More Windows VM Crashing -_-
by Peter Uhnak March 23, 2017

March 23, 2017

Hi, Originally I thought my VM is crashing because of FT, so I applied some fix from FogBugz (that is now part of Pharo 6), but that didn't help. So I disabled FT in settings and changed fonts to non-FT ones; didn't help. So I completely removed FT2Plugin.dll (now settings just states that FT fonts are not available), but that didn't help either. And obviously there is no crash.dmp whatsoever (this is latest Windows VM). This crash is extremely frustrating because the crash happens _during saving_, which means I am losing code all the time and have to constantly recover them, which really makes my blood boil. Without crash dump I don't even know where and how to start investigating. Windows kindly opens Visual Studio when Pharo crashes, but all it shows to me is assembly, which is not very useful to me. I can somewhat orient myself in the C code of the VM (as I've alredy fixed some other issues in the VM), but here I am lost. <SNIP> 00407D7F ret 00407D80 mov eax,dword ptr ds:[00596E44h] 00407D85 test al,3 00407D87 jne 00407DB2 00407D89 mov ecx,dword ptr ds:[596E08h] 00407D8F lea edx,[ecx-1] 00407D92 cmp eax,edx 00407D94 jb 00407DB2 00407D96 cmp dword ptr ds:[596E10h],eax 00407D9C jb 00407DB2 00407D9E mov ecx,dword ptr ds:[5B89D0h] 00407DA4 cmp dword ptr [eax-4],ecx 00407DA7 jb 00407DB2 00407DA9 mov eax,dword ptr ds:[00596E28h] ---> 00407DAE movzx eax,byte ptr [eax] 00407DB1 ret eax = 00000000 ecx = 04700000 </SNIP> So my question I guess is: How can we fix this? How can I help fix this? Because I've lost countless days of time and energy on this f***ing problem... Peter

5 5

[ANN] PharoNOS
by jan.struz March 23, 2017

March 23, 2017

Hi, I successfully ported SqueakNOS to Pharo, and want to share it with you! It works with Pharo 4.0 image, networking included, ping works! What is different: - I use my own CMake build file, with "out-of-tree" build support, instead of "build.xyz" directories inside source tree + some template scripts to build any VM type, but it is not complete... - I use MUSL <http://www.musl-libc.org/> instead of GlibC, cross-compiling GlibC statically on 64bit for 32bit seems impossible, but anyway I use 32bit environment to build it - It works with pre-opensmalltalk-vm migration directory structure, so the "sync" with latest trunk remains #TODO, or maybe start a new branch again from the latest upstream commit should work too - freetype is included, but will not load any fonts, since the filesystem driver is image-side... so you will need to make new fonts embedded, if you want them - known issues: image snapshot and fileout are not working, current date+time hacked to make fat32 timestamps work - revision needed: timer (heartbeat) vs. GC vs. interrupts enable/disable - there are even some hacks to image-side methods PharoNOS platform directory sources: [pharonos branch] SRC: https://gitlab.com/johnnyzz/pharonos VM sources: [dev branch] SRC: https://gitlab.com/johnnyzz/pharo-vm - added platform directory, build scripts and CMake templates - added VMMaker configs Build Environment (32bit) - Docker image repository, with CI: https://gitlab.com/johnnyzz/dev-build PharoNOS CI (uses previous Docker image): CI: https://gitlab.com/johnnyzz/pharo-nos-build How to run it: You can download fresh disk image from CI and then run: (sudo) kvm -hda build/NOS.img -enable-kvm -cpu kvm32 -vga qxl -m 256 -netdev tap,id=user.3,ifname=tap2,vhost=on -net nic,model=rtl8139,netdev=user.3 -global isa-fdc.driveA= -serial stdio One more thing: Statically linked Pharo Spur32 (headless) VM, with only one dependency - Linux kernel: CI: https://gitlab.com/johnnyzz/pharo-build-static Size: 2,4MB (too big?, but Freetype included too!) enjoy Jan ----- Save The World! -- View this message in context: http://forum.world.st/ANN-PharoNOS-tp4939247.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

10 16

Re: [Pharo-dev] More Windows VM Crashing -_- (Peter Uhnak)
by lb March 22, 2017

March 22, 2017

At 2017-03-22 22:18:12, pharo-dev-request(a)lists.pharo.org wrote: >Send Pharo-dev mailing list submissions to > pharo-dev(a)lists.pharo.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org >or, via email, send a message with subject or body 'help' to > pharo-dev-request(a)lists.pharo.org > >You can reach the person managing the list at > pharo-dev-owner(a)lists.pharo.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Pharo-dev digest..." > > >Today's Topics: > > 1. Collecting of event data still needed? (Pavel Krivanek) > 2. More Windows VM Crashing -_- (Peter Uhnak) > 3. Pharo 6 vm crashed when pasting a big file > (tdupriez(a)ens-paris-saclay.fr) > 4. Re: Pharo 6 vm crashed when pasting a big file (Nicolai Hess) > 5. Re: More Windows VM Crashing -_- (Nicolai Hess) > 6. Re: [ANN] PharoNOS (Hernan Wilkinson) > 7. Re: Pharo 6 vm crashed when pasting a big file > (tdupriez(a)ens-paris-saclay.fr) > 8. Re: Pharo 6 vm crashed when pasting a big file (Eliot Miranda) > 9. Re: [ANN] PharoNOS (jan.struz) > 10. Re: More Windows VM Crashing -_- (Eliot Miranda) > 11. Re: Pharo 6 vm crashed when pasting a big file > (tdupriez(a)ens-paris-saclay.fr) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Wed, 22 Mar 2017 09:25:15 +0100 >From: Pavel Krivanek <pavel.krivanek(a)gmail.com> >To: Discusses Development of Pharo <pharo-dev(a)lists.pharo.org> >Subject: [Pharo-dev] Collecting of event data still needed? >Message-ID: > <CAHN2FzfzwFu0PWsHDMymh_=EnErB6w+aAPEo925vz6a6WuhmCQ(a)mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >>From a Slack discussion: > >Alexandre Bergel [6:03 PM] >@uko : Do we still need the usage data ? > >Alexandre Bergel [6:03 PM] >Having this large red bar is a bit aggressive > >Yuriy Tymchuk [6:06 PM] >Data is always useful. Now as I end my Ph.D. I will not have time to >investigate the collected data any more, so the question is does anybody >else care about the collected data, because yes, I can just remove it. By >the way, I just reuse the morph from Spotter, so it is up to them to define >the style :slightly_smiling_face: > >- > >So the question is: do we still need to display appeal for sending usage >data in Pharo 7? Is anyone analyzing it or do we only irritate users? Such >request can be in the Welcome window. > >Cheers, >-- Pavel >

1 0

Pharo 6 vm crashed when pasting a big file
by tdupriez＠ens-paris-saclay.fr March 22, 2017

March 22, 2017

Hi, The pharo 6 vm crashed when I pasted a long text file in the body of a method. Surprisingly, the vm did not crashed when I pasted a file of approximately the same size but only containing a single string ('adafcawa' copy-pasted on 8000 lines). The crash occured after I: - Opened a fresh image (60450) - Created a package, with a single class, with a single method - Tried to paste the content of the attached file into the methods body (the vm froze for 20-30 seconds then crashed) Ubuntu 16.04 LTS 64 bits vm obtained from http://get.pharo.org/ (the '60+vm' package) image 60450 Thomas

3 4

Collecting of event data still needed?
by Pavel Krivanek March 22, 2017

March 22, 2017

>From a Slack discussion: Alexandre Bergel [6:03 PM] @uko : Do we still need the usage data ? Alexandre Bergel [6:03 PM] Having this large red bar is a bit aggressive Yuriy Tymchuk [6:06 PM] Data is always useful. Now as I end my Ph.D. I will not have time to investigate the collected data any more, so the question is does anybody else care about the collected data, because yes, I can just remove it. By the way, I just reuse the morph from Spotter, so it is up to them to define the style :slightly_smiling_face: - So the question is: do we still need to display appeal for sending usage data in Pharo 7? Is anyone analyzing it or do we only irritate users? Such request can be in the Welcome window. Cheers, -- Pavel

1 0

[pharo-project/pharo-core]
by GitHub March 21, 2017

March 21, 2017

Branch: refs/tags/50771 Home: https://github.com/pharo-project/pharo-core

1 0