- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

by Esteban Lorenzano

> On 6 Mar 2017, at 07:17, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > First, let me be clear: I *like* sublimish theme (not for my use, but I like it), and I like (a lot) the windows list on spotter, and I like in general all this new additions. By the way, even if I like it, I would not have integrated SublimishTheme. For same reason I didnât integrated DarkMetalTheme: My idea is to have just two themes *in image*: one white, one dark, and allow people to install other themes from catalog. Why? Because each class inside image becomes our responsibility and then a maintainability issue. With themes in particular already happened that existing themes became abandonware inside the image and we needed to clean up, not without problems. cheers, Esteban ps: which means also yes: that issue got integrated because I failed to control the flow of issues... > > And I know, most of those additions are usability enhancements so a good thing. > > But can you guys stop pushing new features into a (in theory) frozen version? > > Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. If I can suggest an orientation, it would be good, for those that use linux and mac (windows is not ready), to test and help fix 64bits version. > > There are still plenty of bugs to fix there, like for example why Spotter does not shows search line. > > Last week I added support to Athens and SDL2 in 64bits but that meant: > > - some important changes in UFFI > - discover something that seems is failing on callbacks for Cairo (no idea if it is a callbacks problem or an image problem that causes a callback problem). > > I would say all this and the fact we are working on 64bits in general deserves a lot of testing. > > I will add links in Pharo page to download 64bits (Iâm at the train now), but in the mean time you can download all from here: > > http://files.pharo.org/get-files/60/pharo-64.zip <http://files.pharo.org/get-files/60/pharo-64.zip> > http://files.pharo.org/get-files/60/pharo64-linux-latest.zip <http://files.pharo.org/get-files/60/pharo64-linux-latest.zip> (linux) > http://files.pharo.org/get-files/60/pharo64-mac-latest.zip <http://files.pharo.org/get-files/60/pharo64-mac-latest.zip> (mac) > http://files.pharo.org/get-files/60/sources.zip <http://files.pharo.org/get-files/60/sources.zip> (in case you need them) > > cheers, > Esteban

March 6, 2017

Frozen is melted (can you guys please be patient?)

by Esteban Lorenzano

Hi, First, let me be clear: I *like* sublimish theme (not for my use, but I like it), and I like (a lot) the windows list on spotter, and I like in general all this new additions. And I know, most of those additions are usability enhancements so a good thing. But can you guys stop pushing new features into a (in theory) frozen version? Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. If I can suggest an orientation, it would be good, for those that use linux and mac (windows is not ready), to test and help fix 64bits version. There are still plenty of bugs to fix there, like for example why Spotter does not shows search line. Last week I added support to Athens and SDL2 in 64bits but that meant: - some important changes in UFFI - discover something that seems is failing on callbacks for Cairo (no idea if it is a callbacks problem or an image problem that causes a callback problem). I would say all this and the fact we are working on 64bits in general deserves a lot of testing. I will add links in Pharo page to download 64bits (Iâm at the train now), but in the mean time you can download all from here: http://files.pharo.org/get-files/60/pharo-64.zip <http://files.pharo.org/get-files/60/pharo-64.zip> http://files.pharo.org/get-files/60/pharo64-linux-latest.zip <http://files.pharo.org/get-files/60/pharo64-linux-latest.zip> (linux) http://files.pharo.org/get-files/60/pharo64-mac-latest.zip <http://files.pharo.org/get-files/60/pharo64-mac-latest.zip> (mac) http://files.pharo.org/get-files/60/sources.zip <http://files.pharo.org/get-files/60/sources.zip> (in case you need them) cheers, Esteban

March 6, 2017

Re: [Pharo-dev] running Hapao using 60429 image - Pharo dies

by Alexandre Bergel

Hi Sheridan, I tried to reproduce the problem you have experienced. I could not see the error you faced. I tried on MacOSX however. Hapao does some method instrumentation, and apparently the Windows VM does not like them. You can see the result on: https://dl.dropboxusercontent.com/u/31543901/TMP/CoverageOfString/index.html You can also download the result from: https://dl.dropboxusercontent.com/u/31543901/TMP/CoverageOfString/Archive.z… I do not have a solution for your problem. But I do have a question: do you really need to measure the coverage of String? I am confident that on a less system-critic class Hapao will give you satisfactory result. On a side note, it is interesting to see that String is covered at only 65%. There is a StringTest, but no subclasses, while String has many subclasses. Cheers, Alexandre > On Mar 5, 2017, at 8:14 PM, sheridan(a)sheridan-mahoney.com wrote: > > Hello, > I was working at loading Hapao into the latest Pharo image, and ran into a problem. I started with a brand new download of Pharo 5.0, and got the latest development image and changes for 6.0 (60429). I then ran: > > Gofer it > smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; > configurationOf: 'Spy2'; > loadStable. > > which ran to completion. > > I then went to check the tests in the String class, so I ran: > > > (Hapao2 runTestsForClasses: String withAllSubclasses , StringTest withAllSubclasses) visualize. > > Pharo started running the tests. Then a message from the operating system came up saying, > > "Pharo.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available". > > I tried this twice, and got the same error message each time. > > Is there something I should be doing differently in terms of how I am loading and running Hapao? > > Many thanks, > > and best regards, > > Sheridan > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 6, 2017

running Hapao using 60429 image - Pharo dies

by sheridan＠sheridan-mahoney.com

Hello, I was working at loading Hapao into the latest Pharo image, and ran into a problem. I started with a brand new download of Pharo 5.0, and got the latest development image and changes for 6.0 (60429). I then ran: Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; configurationOf: 'Spy2'; loadStable. which ran to completion. I then went to check the tests in the String class, so I ran: (Hapao2 runTestsForClasses: String withAllSubclasses , StringTest withAllSubclasses) visualize. Pharo started running the tests. Then a message from the operating system came up saying, "Pharo.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available". I tried this twice, and got the same error message each time. Is there something I should be doing differently in terms of how I am loading and running Hapao? Many thanks, and best regards, Sheridan

March 5, 2017

Re: [Pharo-dev] Spotter idea - bring existing code windows to front

by Andrei Chis

Nice! On Sun, Mar 5, 2017 at 9:04 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Slice in Pharo60Inbox > > https://pharo.fogbugz.com/f/cases/19798/Make-Spotter-look-for-open-windows > > I got it working properly now. > > [image: Inline image 1] > > Do we want this to come before the search for custom menus? Having another search first would make it more difficult to use Spotter to quickly find items in the world menu. > But how is one to package a Spotter extension in a given package without > having to touch GTSpotter extensions core? > We usually package extensions related to the core parts of the IDE in the GT-SpotterExtensions-Core. Otherwise you can create a dedicated package with extensions for a certain project. > > This is indeed easy to understand once gone through the motions and opens > a lot of doors for open data exploration with custom spotters. > > Question: how can I wire several spotters together? > If you click on the arrow to the right of the selected row (or use Meta+ArrowRight) you will trigger the dive-in action that will open Spotter on the selected object. This will load searches specific to that object. For example if you dive in into a window object you will get a search thorough the submorphs and shortcuts associated with the window. They are defined in the Morph class. If you want to add some specific searches that apply to a window you can add them to the SystemWindow class. Cheers, Andrei > > Phil > > > On Sun, Mar 5, 2017 at 7:15 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Nice one, Phil :) >> >> Doru >> >> >> >> > On Mar 4, 2017, at 7:32 PM, phil(a)highoctane.be wrote: >> > >> > I made a little experiment to get the windows listed in spotter. >> > >> > <image.png> >> > >> > I have still an issue with the activation and some weird windows listed >> but should be able to give you just that in a couple hours. >> > >> > This is a good opportunity for me to jump into spotter extensions, thx >> for the nudge :-) >> > >> > Phil >> > >> > On Sat, Mar 4, 2017 at 4:19 PM, Ben Coman <btc(a)openinworld.com> wrote: >> > A quick note on an idea that strikes me, >> > I often find myself with a large number of windows open and I know I >> have a code window open previously but the task bar is a bit opaque to find >> it, >> > and its so cheap to open a new code window from Spotter, thats what I >> do, >> > and open yet another window, making it harder again to find any >> particular window. >> > You can see the downward spiral here. >> > >> > So apart from more discipline is managing the number of windows I have >> open >> > a passing idea is that for if an existing code window is open, Spotter >> brings that to the front rather than opening another window. Optionally, >> if that code window is dirty, as well as bringing it to the front a fresh >> code window be opened as well, so that the two are immediately comparable. >> > >> > cheers -ben >> > >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Yesterday is a fact. >> Tomorrow is a possibility. >> Today is a challenge." >> >> >> >> >> >> >

March 5, 2017

Re: [Pharo-dev] Spotter idea - bring existing code windows to front

by phil＠highoctane.be

Slice in Pharo60Inbox https://pharo.fogbugz.com/f/cases/19798/Make-Spotter-look-for-open-windows I got it working properly now. [image: Inline image 1] But how is one to package a Spotter extension in a given package without having to touch GTSpotter extensions core? This is indeed easy to understand once gone through the motions and opens a lot of doors for open data exploration with custom spotters. Question: how can I wire several spotters together? Phil On Sun, Mar 5, 2017 at 7:15 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Nice one, Phil :) > > Doru > > > > > On Mar 4, 2017, at 7:32 PM, phil(a)highoctane.be wrote: > > > > I made a little experiment to get the windows listed in spotter. > > > > <image.png> > > > > I have still an issue with the activation and some weird windows listed > but should be able to give you just that in a couple hours. > > > > This is a good opportunity for me to jump into spotter extensions, thx > for the nudge :-) > > > > Phil > > > > On Sat, Mar 4, 2017 at 4:19 PM, Ben Coman <btc(a)openinworld.com> wrote: > > A quick note on an idea that strikes me, > > I often find myself with a large number of windows open and I know I > have a code window open previously but the task bar is a bit opaque to find > it, > > and its so cheap to open a new code window from Spotter, thats what I do, > > and open yet another window, making it harder again to find any > particular window. > > You can see the downward spiral here. > > > > So apart from more discipline is managing the number of windows I have > open > > a passing idea is that for if an existing code window is open, Spotter > brings that to the front rather than opening another window. Optionally, > if that code window is dirty, as well as bringing it to the front a fresh > code window be opened as well, so that the two are immediately comparable. > > > > cheers -ben > > > > -- > www.tudorgirba.com > www.feenk.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > >

March 5, 2017

Re: [Pharo-dev] Spotter idea - bring existing code windows to front

by Tudor Girba

Nice one, Phil :) Doru > On Mar 4, 2017, at 7:32 PM, phil(a)highoctane.be wrote: > > I made a little experiment to get the windows listed in spotter. > > <image.png> > > I have still an issue with the activation and some weird windows listed but should be able to give you just that in a couple hours. > > This is a good opportunity for me to jump into spotter extensions, thx for the nudge :-) > > Phil > > On Sat, Mar 4, 2017 at 4:19 PM, Ben Coman <btc(a)openinworld.com> wrote: > A quick note on an idea that strikes me, > I often find myself with a large number of windows open and I know I have a code window open previously but the task bar is a bit opaque to find it, > and its so cheap to open a new code window from Spotter, thats what I do, > and open yet another window, making it harder again to find any particular window. > You can see the downward spiral here. > > So apart from more discipline is managing the number of windows I have open > a passing idea is that for if an existing code window is open, Spotter brings that to the front rather than opening another window. Optionally, if that code window is dirty, as well as bringing it to the front a fresh code window be opened as well, so that the two are immediately comparable. > > cheers -ben > -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

March 5, 2017

[pharo-project/pharo-core]

by GitHub

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

March 5, 2017

[pharo-project/pharo-core] 1906b2: 60429

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 1906b2024a6d49c3259ec96bfeb23d487f72c836 https://github.com/pharo-project/pharo-core/commit/1906b2024a6d49c3259ec96b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-05 (Sun, 05 Mar 2017) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60428.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60429.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60428.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60429.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Shout.package/SHRBTextStyler.class/instance/private/privateStyle_.st M Shout.package/SHTextStylerST80.class/definition.st A Shout.package/SHTextStylerST80.class/instance/accessing/isForWorkspace.st A Shout.package/SHTextStylerST80.class/instance/accessing/isForWorkspace_.st M Shout.package/SHTextStylerST80.class/instance/accessing/workspace_.st A Tool-Base.package/PharoCommonTools.class/instance/private/toolNamed_.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/basicInspector.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/browser.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/changeList.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/changeSorter.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/codeCompletion.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/debugger.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/debuggers.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/fileList.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/finder.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/inspector.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/messageList.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/monticelloBrowser.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/pointerExplorer.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/processBrowser.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/syntaxErrorDebugger.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/testRunner.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/timeProfiler.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/versionBrowser.st A Tool-Base.package/PharoCommonTools.class/instance/registry access/workspace.st Log Message: ----------- 60429 19793 SHTextStylerST80 always parser code as method if workspace is nil https://pharo.fogbugz.com/f/cases/19793 19797 Add access methods in PharoCommonTools instead of using DNU https://pharo.fogbugz.com/f/cases/19797 http://files.pharo.org/image/60/60429.zip

March 5, 2017

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

by Serge Stinckwich

Dear all, we have 10 mentors + 4 admin at the moment. We are looking for me ! Please join the #gsoc-planning Slack channel. Thank you. On Wed, Mar 1, 2017 at 1:45 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > 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/ > > How the program works ? > > Organizations: > Open source projects apply to be mentor organizations. Once accepted, > organizations discuss possible ideas with students and then decide on > the proposals they wish to mentor for the summer. They provide mentors > to help guide each student through the program. > > Mentors: > Existing contributors with the organizations can choose to mentor a > student project. Mentors and students work together to determine > appropriate milestones and requirements for the summer. Mentor > interaction is a vital part of the program. A mentor may propose or > endorse a project and each project has to be about Pharo or its > ecosystem (e.g., a library). Projects will be mentored by one or more > mentors and executed by one student. > > Students: > Students contact the mentor organizations they want to work with and > write up a project proposal for the summer. If accepted, students > spend a month integrating with their organizations prior to the start > of coding. Students then have three months to code, meeting the > deadlines agreed upon with their mentors. Student coding period: May > 30 - Aug 29 (Entire timeline can be viewed at: > https://summerofcode.withgoogle.com/how-it-works/#timeline) Student > stipend: https://developers.google.com/open-source/gsoc/help/student-stipends > > We are currently at the phase of identifying mentors and projects. The > next phases will be about students selecting projects, and the > community selecting the projects with their associated mentors and > students which will be sponsored by the GSOC program. > > How to register ? > Simply by replying to this email and joining the Slack channel... to > have more discussion about what project the mentor will take up, what > she/he wants at the end of the coding period and then we can invite > them to the GSoC org dashboard). > > Hence, we invite regular & enthusiastic Pharo contributors to be a > mentor with Pharo Consortium for GSoC 2017: > > 1. Kindly respond on this thread if you'd like to be a mentor, or wish > to propose a project. > > An existing list of projects is already available here: > http://gsoc.pharo.org/ and we already have a handful of projects and > mentors chosen. Feel free to collaborate with existing mentors as > well. > > 2. Join dedicated channels, #gsoc-students for general interactions > with students & #gsoc-planning channel only for GSOC admins and > mentors on Pharo slack. In order to get an invitation for > pharoproject.slack.com visit the URL here: > http://slackinvites.pharo.org/ > > 3. Please open relevant issues and make a roadmap of the projects > being mentored by you so that students can start contributing to them > already. If you want to mentor a project and there is no open-source > repository at the moment, please built one ASAP. > > 4. If you know any students that might be interested to work on Pharo > during the summer and be a part of GSoC as well, please ask him/her to > start contributing to the Pharo projects, discuss their proposal, > follow instructions that shall be posted soon in this mailing thread > and submit their application by April 3, 2017. > We don't know the number of slots attributed by Google to Pharo org, > but the more students proposal we will receive, the more slots will be > attributed to us. > > We remind you about the mentor responsibilities: > > ... to your Org Admins > > - Communicate availability and interaction expectations > - Inform when mentoring capacity will be reduced, as early as possible > (e.g., family, health, vacation) > - Inform when there is an issue with a student > - Lacking communication, activity, visibility (MIA), or progress > - Participant Agreement violations (e.g., plagiarism, harassment, fraud) > - Bad fit or stepping down > - Formally evaluate student participation. > - Communicate with admin and student before failing > > ... to your Students > > - Help and/or teach the student > - how to be a part of your community > - communicate more effectively and in the open > - work with your orgâs preferred communication channel (IRC, Slack, etc) > - use your orgâs version control system > - ask good questions and get answers to their questions > - provide convincing technical argument and constructive discussion > - be independently motivated and productive > - solve difficult technical problems > - Keep track of their progress, keep student informed as to their status > - Communicate on a regular basis, once a week or better (for GSoC) > - Give constructive feedback, be patient, and be respectful > - Respond to questions within 24 hours (occasionally under 36 hours is ok) > - Establish realistic work objectives and timeline expectations > - Re-evaluate scope with student when significantly ahead of or behind > expectations > - Work with devs and community to facilitate acceptance of student work > > Read more about responsibilities here: > https://developers.google.com/open-source/gsoc/help/responsibilities > > Looking forward to a great guided summer by the talented mentors of > our organisation. > > Warm Regards > Pharo Organisation Admins > (Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk) -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

March 5, 2017