- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] OSSubprocess first milestone

by Mariano Martinez Peck

On Thu, Jan 14, 2016 at 4:43 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Awesome work Mariano , I love the documentation. > > Question : Does your library use the new FFI (Unified FFi) ? > > It does use the new FFI which is in latest Pharo 5.0. The Unified FFI as far as I understand in a simple rename of a couple of things. I will have to update my code for it, yes, but should be trivial. But..as far as I know, it has not been yet integrated into the image the changes, right? > On Thu, Jan 14, 2016 at 9:36 PM stepharo <stepharo(a)free.fr> wrote: > >> Thanks Mariano! >> >> Stef >> >> Le 14/1/16 19:33, Mariano Martinez Peck a Ã©crit : >> >> Dear all, >> >> I am happy to tell you I have a first prototype of the tool for executing >> OS processes: >> >> <https://github.com/marianopeck/OSSubprocess> >> https://github.com/marianopeck/OSSubprocess >> >> As I said many times, the main idea was to be as much as possible >> FFI-based, only for executing OS commands and, from my point of view, a >> better end-user API. Also, as for the first step, I had to focus on >> Linux/OSX. >> >> I would like to thank Pharo Consortium for the sponsor of this >> development effort. Here is the first milestone! >> >> There are many things on my to-do but I think the code is ready for some >> usage, testing, code review and feedback! >> >> All classes and all methods have comments and I have quite some unit >> tests. All tests are green in my OSX and a CentOS box. >> >> *Important: you CANNOT have OSProcess installed in the same image as >> OSSubprocess. This is because I am reusing his SIGCHLD handler and for the >> time being both cannot coexist. * >> >> Keep in mind that the tool may be unstable and that MAY mean a VM crash. >> So use with care, mostly the first time. If all tests passes, then there >> are much less chances of something going bad. >> >> Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY >> influenced by a subset of the OSProcess project. There are parts which I >> even simply copied and adapted them (OSSPipe, OSSAttachableStream, >> OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the >> idea of ThisOSProcess representing the VM process, the child watcher, and >> many others). In addition, I AM STILL USING (maybe as a first step?) some >> of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD >> handler or the creation of pipes. >> >> In github url you have all the documentation of the project, included how >> to install it and use it. >> >> *Finally, if you test it in a OS different than OSX and CentOS please >> share with me the results (about the tests).* Tomorrow the >> ConfigurationOf should also appear in the Catalog of Pharo 5.0. >> >> Any feedback is appreciated. >> >> Best, >> >> >> -- Mariano http://marianopeck.wordpress.com

Jan. 14, 2016

Re: [Pharo-dev] [ANN] OSSubprocess first milestone

by Dimitris Chloupis

Awesome work Mariano , I love the documentation. Question : Does your library use the new FFI (Unified FFi) ? On Thu, Jan 14, 2016 at 9:36 PM stepharo <stepharo(a)free.fr> wrote: > Thanks Mariano! > > Stef > > Le 14/1/16 19:33, Mariano Martinez Peck a Ã©crit : > > Dear all, > > I am happy to tell you I have a first prototype of the tool for executing > OS processes: > > https://github.com/marianopeck/OSSubprocess > > As I said many times, the main idea was to be as much as possible > FFI-based, only for executing OS commands and, from my point of view, a > better end-user API. Also, as for the first step, I had to focus on > Linux/OSX. > > I would like to thank Pharo Consortium for the sponsor of this development > effort. Here is the first milestone! > > There are many things on my to-do but I think the code is ready for some > usage, testing, code review and feedback! > > All classes and all methods have comments and I have quite some unit > tests. All tests are green in my OSX and a CentOS box. > > *Important: you CANNOT have OSProcess installed in the same image as > OSSubprocess. This is because I am reusing his SIGCHLD handler and for the > time being both cannot coexist. * > > Keep in mind that the tool may be unstable and that MAY mean a VM crash. > So use with care, mostly the first time. If all tests passes, then there > are much less chances of something going bad. > > Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY > influenced by a subset of the OSProcess project. There are parts which I > even simply copied and adapted them (OSSPipe, OSSAttachableStream, > OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the > idea of ThisOSProcess representing the VM process, the child watcher, and > many others). In addition, I AM STILL USING (maybe as a first step?) some > of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD > handler or the creation of pipes. > > In github url you have all the documentation of the project, included how > to install it and use it. > > *Finally, if you test it in a OS different than OSX and CentOS please > share with me the results (about the tests).* Tomorrow the > ConfigurationOf should also appear in the Catalog of Pharo 5.0. > > Any feedback is appreciated. > > Best, > > >

Jan. 14, 2016

Re: [Pharo-dev] [ANN] OSSubprocess first milestone

by stepharo

Thanks Mariano! Stef Le 14/1/16 19:33, Mariano Martinez Peck a Ã©crit : > Dear all, > > I am happy to tell you I have a first prototype of the tool for > executing OS processes: > > https://github.com/marianopeck/OSSubprocess > > As I said many times, the main idea was to be as much as possible > FFI-based, only for executing OS commands and, from my point of view, > a better end-user API. Also, as for the first step, I had to focus on > Linux/OSX. > > I would like to thank Pharo Consortium for the sponsor of this > development effort. Here is the first milestone! > > There are many things on my to-do but I think the code is ready for > some usage, testing, code review and feedback! > > All classes and all methods have comments and I have quite some unit > tests. All tests are green in my OSX and a CentOS box. > > *Important: you CANNOT have OSProcess installed in the same image as > OSSubprocess. This is because I am reusing his SIGCHLD handler and for > the time being both cannot coexist. * > > Keep in mind that the tool may be unstable and that MAY mean a VM > crash. So use with care, mostly the first time. If all tests passes, > then there are much less chances of something going bad. > > Important disclaimer: my tool (OSSubproccess from now onward) is > HIGHLY influenced by a subset of the OSProcess project. There are > parts which I even simply copied and adapted them (OSSPipe, > OSSAttachableStream, OSSUnixProcessExitStatus). Other parts, I took > them as inspiration (the idea of ThisOSProcess representing the VM > process, the child watcher, and many others). In addition, I AM STILL > USING (maybe as a first step?) some of the OSProcess PLUGIN (not > OSProcess image side), such as the SIGCHLD handler or the creation of > pipes. > > In github url you have all the documentation of the project, included > how to install it and use it. > > *Finally, if you test it in a OS different than OSX and CentOS please > share with me the results (about the tests).* Tomorrow the > ConfigurationOf should also appear in the Catalog of Pharo 5.0. > > Any feedback is appreciated. > > Best,

Jan. 14, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] 0d016b: 50527

by stepharo

Thanks guys I will be able to start producing the new version of the videos for the mooc. Stef Le 14/1/16 19:50, GitHub a Ã©crit : > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 0d016b26ee0e42f8c1960fefefde84d9f1444739 > https://github.com/pharo-project/pharo-core/commit/0d016b26ee0e42f8c1960fef… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2016-01-14 (Thu, 14 Jan 2016) > > Changed paths: > M ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/symbolic versions/stable_.st > A ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/versions/version083_.st > M Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/drawOn_.st > R Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/toSelectionRow_primary_.st > M Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/updating/updateExposedRows.st > A Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/accessing colors/colorForSelection_.st > M Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/private/selectRowIndex_event_.st > M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/definition.st > A Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/accessing/selectionColor_.st > M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event handling/mouseEnter_.st > M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event handling/mouseLeave_.st > M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialization/initialize.st > M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/defaultColor.st > A Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/selectionColor.st > R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/README.md > R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance creation/new.st > R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance creation/table_row_primary_.st > R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/definition.st > R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/instance/initialization/initializeTable_row_primary_.st > M Nautilus.package/AbstractNautilusUI.class/instance/private/runTestsOfClass_notifying_.st > R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50526.st > A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50527.st > R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50526.st > A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50527.st > M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > > Log Message: > ----------- > 50527 > 17379 FastTable mouse over on highlighted item > https://pharo.fogbugz.com/f/cases/17379 > > 17386 Nautilus test notification should show test results > https://pharo.fogbugz.com/f/cases/17386 > > http://files.pharo.org/image/50/50527.zip > >

Jan. 14, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 14, 2016

[pharo-project/pharo-core] 0d016b: 50527

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0d016b26ee0e42f8c1960fefefde84d9f1444739 https://github.com/pharo-project/pharo-core/commit/0d016b26ee0e42f8c1960fef… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-14 (Thu, 14 Jan 2016) Changed paths: M ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/symbolic versions/stable_.st A ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/versions/version083_.st M Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/drawOn_.st R Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/toSelectionRow_primary_.st M Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/updating/updateExposedRows.st A Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/accessing colors/colorForSelection_.st M Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/private/selectRowIndex_event_.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/definition.st A Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/accessing/selectionColor_.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event handling/mouseEnter_.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event handling/mouseLeave_.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialization/initialize.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/defaultColor.st A Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/selectionColor.st R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/README.md R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance creation/new.st R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance creation/table_row_primary_.st R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/definition.st R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/instance/initialization/initializeTable_row_primary_.st M Nautilus.package/AbstractNautilusUI.class/instance/private/runTestsOfClass_notifying_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50526.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50527.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50526.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50527.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50527 17379 FastTable mouse over on highlighted item https://pharo.fogbugz.com/f/cases/17379 17386 Nautilus test notification should show test results https://pharo.fogbugz.com/f/cases/17386 http://files.pharo.org/image/50/50527.zip

Jan. 14, 2016

[ANN] OSSubprocess first milestone

by Mariano Martinez Peck

Dear all, I am happy to tell you I have a first prototype of the tool for executing OS processes: https://github.com/marianopeck/OSSubprocess As I said many times, the main idea was to be as much as possible FFI-based, only for executing OS commands and, from my point of view, a better end-user API. Also, as for the first step, I had to focus on Linux/OSX. I would like to thank Pharo Consortium for the sponsor of this development effort. Here is the first milestone! There are many things on my to-do but I think the code is ready for some usage, testing, code review and feedback! All classes and all methods have comments and I have quite some unit tests. All tests are green in my OSX and a CentOS box. *Important: you CANNOT have OSProcess installed in the same image as OSSubprocess. This is because I am reusing his SIGCHLD handler and for the time being both cannot coexist. * Keep in mind that the tool may be unstable and that MAY mean a VM crash. So use with care, mostly the first time. If all tests passes, then there are much less chances of something going bad. Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY influenced by a subset of the OSProcess project. There are parts which I even simply copied and adapted them (OSSPipe, OSSAttachableStream, OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the idea of ThisOSProcess representing the VM process, the child watcher, and many others). In addition, I AM STILL USING (maybe as a first step?) some of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD handler or the creation of pipes. In github url you have all the documentation of the project, included how to install it and use it. *Finally, if you test it in a OS different than OSX and CentOS please share with me the results (about the tests).* Tomorrow the ConfigurationOf should also appear in the Catalog of Pharo 5.0. Any feedback is appreciated. Best, -- Mariano http://marianopeck.wordpress.com

Jan. 14, 2016

Launcher 0.2.9 opens Spur images

by Damien Cassou

Hi list, thanks to the awesome work of Vincent Blondeau, Stephan Eggermont and Cyril Ferlicot, Pharo Launcher 0.2.9 can be configured to open both spur and pre-spur Pharo images. You can download this version from http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher. You can safely replace your existing Launcher installation with the new one. Your images won't be affected and you will still be able to launch them. The VM coming with these builds is a pre-spur VM because Launcher is based on Pharo 4. If you want to launch Pharo 5 spur images, you need to separately download a Pharo 5 Spur VM from http://get.pharo.org/vm50 and configure the location of this VM in the Launcher settings (icon at the bottom left of the Launcher window). What I like about this release is that I didn't do anything but changing the version number in https://ci.inria.fr/pharo/view/all/job/Launcher :-). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Jan. 14, 2016

Re: [Pharo-dev] Bug in protocol and method selection

by stepharo

Hi Henrik Did you create a bug entry so that we integrate it? Stef Le 14/1/16 14:57, Henrik Nergaard a Ã©crit : > Hi Stef, > > Do the error still happen if you merge: > > Name: Morphic-Widgets-FastTable-HenrikNergaard.148 > Author: HenrikNergaard > Time: 13 January 2016, 3:40:48.807358 pm > UUID: b807ebde-ad62-ce41-977a-e6cdce230e93 > Ancestors: Morphic-Widgets-FastTable-CyrilFerlicot.147 > > ? > > Best regards, > Henrik > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Yuriy Tymchuk > Sent: Thursday, January 14, 2016 1:43 PM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] Bug in protocol and method selection > > Stef, > > I cannot see the issue, moreover there were no changes in QA that touch Nautilus. > > Maybe this is because of FastTable highlighting: when you hover over a selected list item, it changes color to the hover color, so when you select an item you cannot see the you selected it because you see the tower color. This was already fixed, but not yes integrated. > > Uko > >> On 14 Jan 2016, at 13:33, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> I will take a look. Just to make sure: this is not the FT coloring thing, right? >> >> Uko >> >>> On 14 Jan 2016, at 13:06, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi >>> >>> There is a problem in latest Pharo. I cannot select (and keep the >>> selection selected) of a method and method protocol. >>> To me it looks like QA is interferring but I do not know. >>> This is the kind of glitches that can kill our effort doing videos. >>> We have a strong deadline for producing such videos. beginning of >>> march but we want to get done before any help is welcome. >>> >>> Stef >>> >> > > >

Jan. 14, 2016

Re: [Pharo-dev] About LayoutFrame>>fractions:offsets:

by stepharo

Yes fullFrame would be better. Now we should rewrite all the senders and I do not have cycles now for that. But if people want to do a pass go ahead. better LayoutFrame identity :) >> Well, maybe the comment could say that the 0@0 corner: 1@1 rectangle is the identity ;) No because we do not want to have rectangle anymore. >> >> That this is the identity is not obvious in fact, unless you consider what algorithm is used to compute layouts. I tend to think that this (0@0 corner: 1@1) rectangle is the full area (the max area?)... not the identity of something. >> >> Why not LayoutFrame fullFrame ? > Indeed, this sounds better. > > Doru > >> Thierry > -- > www.tudorgirba.com > www.feenk.com > > "Be rather willing to give than demanding to get." > > > > > >

Jan. 14, 2016