January 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Question about attribution under the MIT License

by Sven Van Caekenberghe

This might be relevant too: http://meta.stackexchange.com/questions/272956/a-new-code-license-the-mit-t… Somewhere in the text they say: << You are also welcome to use the MIT License as it is traditionally interpreted: by preserving the full license with relevant fields (copyright year and copyright holder) completed. >> Literally this would not be very practical, but somehow preserving names should be doable. > On 08 Jan 2016, at 19:55, monty <monty2(a)programmer.net> wrote: > > This line form the text of the license suggests we should really be bundling the full license text with our code, not just stating "this code is MIT" on the STH project page: > > "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." > > Because of this, I've started adding #catalogLicense methods to STH Configs I manage that return the entire MIT license text with a copyright statement. I think everyone should do the same. > >> Sent: Friday, January 08, 2016 at 11:08 AM >> From: "Sven Van Caekenberghe" <sven(a)stfx.eu> >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Subject: [Pharo-dev] Question about attribution under the MIT License >> >> Hi, >> >> I have a been wondering recently about attribution under the MIT License. >> >> Code in Pharo and code contributed to Pharo is and should be licensed under the MIT License. >> >> https://en.wikipedia.org/wiki/MIT_License >> >> Contributors sign an extra agreement. >> >> http://files.pharo.org/media/PharoSoftwareDistributionAgreement.pdf >> >> Here, contributors give a license so Pharo can include their code. >> >> As I read the MIT license the original author keeps the copyright and about the only requirement is that that copyright shall be included when the code is used. The extra agreement does not transfer copyright. >> >> So, all authors should be mentioned in the general Pharo MIT license. >> >> The reason I was thinking about this is that many people on the list seems to be under the impression that MIT licensed code means that you can freely copy it, like most recently in the discussions about Dophin Smalltalk. I think copying MIT licensed code requires proper attribution. >> >> If people copy (my, someone else's) code from Pharo to somewhere else, I want them to at least acknowledge that fact, preferably include a general Pharo (contributors) copyright, but ideally (my, their) copyright. >> >> But that would also mean that Pharo has to do the same. I think we should list and update the official contributor list, including the historical list of original authors going back. >> >> Am I right or wrong ? >> >> How do other people feel about this ? >> >> Sven >> >> >> >

Jan. 15, 2016

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

by Damien Cassou

On January 14, 2016 7:33:56 PM GMT+01:00, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >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, Quick feedback: - the API seems great - thank you very much for the documentation - I wonder why you pass strings for stdout and stderr instead of streams - it would be nice to be able to subclass OSSUnixProcessExitStatus for some commands. E.g., GitProcessExitStatus could have a method isMergeConflict - how can I implement something like tail --follow -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Jan. 15, 2016

Powerful ARM server

by Ben Coman

This might make a good CI server for ARM, or ARM based Pharo cloud. http://hothardware.com/news/amd-unveils-64-bit-arm-based-opteron-a1100-soc-… cheers -ben

Jan. 15, 2016

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

by David T. Lewis

On Thu, Jan 14, 2016 at 03:33:56PM -0300, Mariano Martinez Peck wrote: > 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! Bravo Mariano! Dave

Jan. 15, 2016

Re: [Pharo-dev] error "please insert disk" (windows vm)

by Nicolai Hess

attached a patch on http://bugs.squeak.org/view.php?id=7841 I think this could be applied on pharo win32 source as well. maybe with some small changes 2015-11-16 10:00 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > I opened another bug report at mantis - > > http://bugs.squeak.org/view.php?id=7841 > > I can create a patch with the proposed solution. > > > > 2015-11-06 8:42 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> we have the following bug report >> 16928 >> <https://pharo.fogbugz.com/f/cases/16928/no-disk-in-the-drive-reply-to-World…> >> "no disk in the drive" reply to World | Save As (and other places) >> >> "On a clean Pharo4.0 #40618 image, on Windows 7 >> World Menu | Save As brings up a modal alert window, "There is no disk in >> the drive. Please insert a disk into drive <etc>" >> >> On my system, it does this 4 times. >> >> I'm assuming that each instance refers to one of the card-reader drives >> which are attached, but without a card inserted. >> >> This is a pain to deal with every single time a File Browser or World | >> Save As dialog is opened. >> >> Could the alerts either be >> - only raised when that specific drive is requested by a user action >> or, less preferably >> - given by a non-modal window, and fading away after a period" >> >> I was able to reproduce this error on squeaks and pharos window vm. >> (insert a usb card reader, with card, wait some time , remove only the >> card, >> every access on this drive, for example open a FileList and scroll to the >> drive letter). >> >> >> The solution I found is to call SetErrorMode( >> *SEM_FAILCRITICALERRORS)* >> I would like to propose the following change to sqwin32directory.c >> wrap the call to FindFirstFileW/FindNextFileW with >> >> UINT prevMode = SetErrorMode(SEM_FAILCRITICALERRORS); >> call FindFirstFileW/FindNextFileW >> SetErrorMode(prevMode); >> >> ... >> >> and call this functions in at least dir_lookup() >> (the other file/directory methods are save). >> >> Alternative solution, we could call the SetErrorMode function once at >> program start >> but I don't know if there are other "useful" errors message that we don't >> want to disable. >> >> I tested both solution, both seems to work fine. >> >> What do you think? >> >> >> >> >> >

Jan. 14, 2016

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