September 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Nicolai Hess

2015-09-29 10:14 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > > > 2015-09-29 9:39 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > >> >> >> 2015-09-29 7:05 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: >> >>> Hi Levente, >>> >>> Le 28/09/2015 23:54, Levente Uzonyi a Ã©crit : >>> >>>> On Sun, 27 Sep 2015, Ferlicot D. Cyril wrote: >>>> >>>> An other point is that git file tree will not work on Windows if we do >>>>> not fix the problem of the stdio. And a lot of people out of the >>>>> community use Windows, so this is not a issue we should forget. Most of >>>>> the people I know in company use Windows, so if we want to attract >>>>> people this problem need to be corrected. >>>>> >>>> >>>> If there are so many windows users, then how can it be that none of them >>>> managed to explain what the actual problem with stdio handling is. I had >>>> asked about the problem a while ago, but I still haven't got an answer: >>>> http://forum.world.st/Google-Code-Shutdown-tt4814760.html#a4840937 . >>>> >>> >>> Well, I changed the code using ProcessWrapper with your suggestions >>> following that exchange, but my code stay fairly naive [1] (and would need >>> to run under debug), and I didn't have someone testing on Windows. >>> >> >> Can you give me an example on how to test this >> > > Yes! Thanks! > > Can you run a makefile under Windows? I can prepare one which calls and > loads everything to run the tests for gitfiletree. > > Or just trying to load something like SmaCC from github... > > Gofer new url: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo50/main'; > configurationOf: 'GitFileTree'; loadDevelopment > > Metacello new baseline: 'SmaCC'; repository: 'gitfiletree:// > github.com/ThierryGoubier/SmaCC?protocol=https'; load > > If you manage to get through the SmaCC loading without a crash or a > lockup, then it means it nearly certainly works. > No, it does not work, in MCFileTreeGitRepository class>>#runProcessWrapperGitCommand:in: ... (Smalltalk at: #ProcessWrapper ifAbsent: [ self error: 'Please load ProcessWrapper' ]) ifNotNil: [ :pW | | command | command := pW new useStdout; useStderr; startWithCommand: self gitCommand , ' -C "' , (MCFileTreeFileUtils current directoryPathString: aDirectory) , '" ' , aCommandString. r := command upToEnd. "<<<<<<<<<<<<------------------- MNU False>>upToEnd" ... somehow, the command is a boolean false, instead of a ProcessWrapper. > > Thierry > > >> >> >>> >>> Am I writing that code correctly? If you see the equivalent code using >>> OSProcess[2], you understand that, as GitFileTree is a heavy hitter(*) on >>> the external commands framework, I am prepared to work very closely with >>> that layer including inside the vm plugin code (and David T Lewis helped me >>> a lot to fix random lockups we had). >>> >>> Thierry >>> >>> (*) Running the gitfiletree integration tests launches probably over a >>> hundred external commands in quick succession. >>> >>> [1] >>> https://github.com/dalehenrich/filetree/blob/pharo5.0/repository/Monticello… >>> >>> [2] >>> https://github.com/dalehenrich/filetree/blob/pharo5.0/repository/Monticello… >>> >>> >>>> Levente >>>> >>>> >>> >>> >> >

Sept. 29, 2015

Filtering methods

by Alexandre Bergel

Hi! I can now type in the method list pane. This is fantastic beginning. However it does not work properly. Can someone finish it? For example, once I started to filtering, I cannot use the keys to select a method. Frustrating. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 29, 2015

Re: [Pharo-dev] Hi from VISSOFT'15 / ICSME'15

by Serge Stinckwich

Great ! Please continue the buzz ;-) On Tue, Sep 29, 2015 at 1:38 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I am now attending (very) academic conferences: http://vissoft.info and http://www.icsme.uni-bremen.de . It is fantastic to see and hear a lot about Pharo. > > Thanks to all the researchers around here... > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 29, 2015

Hi from VISSOFT'15 / ICSME'15

by Alexandre Bergel

Hi! I am now attending (very) academic conferences: http://vissoft.info and http://www.icsme.uni-bremen.de . It is fantastic to see and hear a lot about Pharo. Thanks to all the researchers around here... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 29, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Thierry Goubier

2015-09-29 10:50 GMT+02:00 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: > > On 29 Sep 2015, at 1:48 , Dale Henrichs <dale.henrichs(a)gemtalksystems.com> > wrote: > > The big issue for git and windows (in general) is that there is a 255 > character limit on the paths for files .... I recently pruned some file > names for Metacello (on a win-hack branch) just to get Metacello to work > with filetree .. > > Working with Github Desktop[1] for Windows makes the experience of using > git from the command line tolerable on Windows - you get a retty nice bash > shell to work with so as a non-windows user I can work in a pretty familiar > environment ... > > At the moment I'm working with Pharo3.0 on Windows, so I don't have any > useful feedback right now (assuming things have changed a bit on Windows > with Pharo4.0 and Pharo5.0) ... > > Dale > > > IIRC, there is some flag you can set to make (some?) the actual git client > (but not bundled tools) support long filenames on Windows: > git config core.longpaths true > For instance, cloning the PharoVM repo choked (or rather, failed > semi-silently) on some really long selector in an obscure plugin somewhere > until I found that... > Interesting. This could allow gitfiletree(*) to load from a repository where filetree would fail to load... but both would fail upon writing :( (*) gitfiletree loads packages via a call to git archive and may so avoid some of the long paths. Thierry > > Cheers, > Henry >

Sept. 29, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Henrik Johansen

> On 29 Sep 2015, at 1:48 , Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > The big issue for git and windows (in general) is that there is a 255 character limit on the paths for files .... I recently pruned some file names for Metacello (on a win-hack branch) just to get Metacello to work with filetree .. > > Working with Github Desktop[1] for Windows makes the experience of using git from the command line tolerable on Windows - you get a retty nice bash shell to work with so as a non-windows user I can work in a pretty familiar environment ... > > At the moment I'm working with Pharo3.0 on Windows, so I don't have any useful feedback right now (assuming things have changed a bit on Windows with Pharo4.0 and Pharo5.0) ... > > Dale IIRC, there is some flag you can set to make (some?) the actual git client (but not bundled tools) support long filenames on Windows: git config core.longpaths true For instance, cloning the PharoVM repo choked (or rather, failed semi-silently) on some really long selector in an obscure plugin somewhere until I found that... Cheers, Henry

Sept. 29, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Thierry Goubier

2015-09-29 9:39 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-09-29 7:05 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Hi Levente, >> >> Le 28/09/2015 23:54, Levente Uzonyi a Ã©crit : >> >>> On Sun, 27 Sep 2015, Ferlicot D. Cyril wrote: >>> >>> An other point is that git file tree will not work on Windows if we do >>>> not fix the problem of the stdio. And a lot of people out of the >>>> community use Windows, so this is not a issue we should forget. Most of >>>> the people I know in company use Windows, so if we want to attract >>>> people this problem need to be corrected. >>>> >>> >>> If there are so many windows users, then how can it be that none of them >>> managed to explain what the actual problem with stdio handling is. I had >>> asked about the problem a while ago, but I still haven't got an answer: >>> http://forum.world.st/Google-Code-Shutdown-tt4814760.html#a4840937 . >>> >> >> Well, I changed the code using ProcessWrapper with your suggestions >> following that exchange, but my code stay fairly naive [1] (and would need >> to run under debug), and I didn't have someone testing on Windows. >> > > Can you give me an example on how to test this > Yes! Thanks! Can you run a makefile under Windows? I can prepare one which calls and loads everything to run the tests for gitfiletree. Or just trying to load something like SmaCC from github... Gofer new url: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo50/main'; configurationOf: 'GitFileTree'; loadDevelopment Metacello new baseline: 'SmaCC'; repository: 'gitfiletree:// github.com/ThierryGoubier/SmaCC?protocol=https'; load If you manage to get through the SmaCC loading without a crash or a lockup, then it means it nearly certainly works. Thierry > > >> >> Am I writing that code correctly? If you see the equivalent code using >> OSProcess[2], you understand that, as GitFileTree is a heavy hitter(*) on >> the external commands framework, I am prepared to work very closely with >> that layer including inside the vm plugin code (and David T Lewis helped me >> a lot to fix random lockups we had). >> >> Thierry >> >> (*) Running the gitfiletree integration tests launches probably over a >> hundred external commands in quick succession. >> >> [1] >> https://github.com/dalehenrich/filetree/blob/pharo5.0/repository/Monticello… >> >> [2] >> https://github.com/dalehenrich/filetree/blob/pharo5.0/repository/Monticello… >> >> >>> Levente >>> >>> >> >> >

Sept. 29, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Nicolai Hess

2015-09-29 7:05 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Hi Levente, > > Le 28/09/2015 23:54, Levente Uzonyi a Ã©crit : > >> On Sun, 27 Sep 2015, Ferlicot D. Cyril wrote: >> >> An other point is that git file tree will not work on Windows if we do >>> not fix the problem of the stdio. And a lot of people out of the >>> community use Windows, so this is not a issue we should forget. Most of >>> the people I know in company use Windows, so if we want to attract >>> people this problem need to be corrected. >>> >> >> If there are so many windows users, then how can it be that none of them >> managed to explain what the actual problem with stdio handling is. I had >> asked about the problem a while ago, but I still haven't got an answer: >> http://forum.world.st/Google-Code-Shutdown-tt4814760.html#a4840937 . >> > > Well, I changed the code using ProcessWrapper with your suggestions > following that exchange, but my code stay fairly naive [1] (and would need > to run under debug), and I didn't have someone testing on Windows. > Can you give me an example on how to test this > > Am I writing that code correctly? If you see the equivalent code using > OSProcess[2], you understand that, as GitFileTree is a heavy hitter(*) on > the external commands framework, I am prepared to work very closely with > that layer including inside the vm plugin code (and David T Lewis helped me > a lot to fix random lockups we had). > > Thierry > > (*) Running the gitfiletree integration tests launches probably over a > hundred external commands in quick succession. > > [1] > https://github.com/dalehenrich/filetree/blob/pharo5.0/repository/Monticello… > > [2] > https://github.com/dalehenrich/filetree/blob/pharo5.0/repository/Monticello… > > >> Levente >> >> > >

Sept. 29, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Esteban Lorenzano

> On 29 Sep 2015, at 01:13, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Le 28/09/2015 23:54, Levente Uzonyi a Ã©crit : >> >> If there are so many windows users, then how can it be that none of them >> managed to explain what the actual problem with stdio handling is. I had >> asked about the problem a while ago, but I still haven't got an answer: >> http://forum.world.st/Google-Code-Shutdown-tt4814760.html#a4840937 . >> >> Levente >> > > The problem is that gitfiletree use OSProcess and OSProcess use Stdio to > get the state or the exit value of a command for example. > But in Windows Stdio is just an ugly hack. It doesn't use the stdio but > create 3 files (stdin, stderr' stdout) in the working directory and > write/read this files. But as Windows doesn't use that we can't > communicate with the system. ah yes, I remember when I made that :) it was for been able to run CI on windowsâ¦ and I remember I told Christophe âletâs do this crap until we find a real solutionâ. That was like 4yrs ago :P So, I still does not have a real solution because GetStdHandle funtion in windows does not work for non console apps. Maybe we could solve this redirecting the outputs (SetStdHandle)? Iâm not a windows user and I donât really know deeply this stuff, but Iâd gladly accept any contribution to fix this issue (or at least to fix OSProcess). Esteban > > I tried to have some look at it but I don't even know if it is a vm or > an image problem. Some says that the dll for that is wrong, some says > that this is an image problem. I don't have the knowledge and the time > to go deeper on that problem. > > So in order to fix a lot of problem on windows we need to fix the Stdio > but we need someone who have the time and the knowledge and we do not > have a lot of developers that can manage stdio on windows even if we > have users. > > -- > Cheers > Cyril >

Sept. 29, 2015

Re: [Pharo-dev] PharoTouch Demo Video

by stepharo

Le 28/9/15 16:55, Stephan Eggermont a Ã©crit : > On 28-09-15 16:22, Marcus Denker wrote: >> Pharo touch demo with the new OSWindows architecture, touch events, >> vector graphics using Athens and libsdl2. >> >> Thanks the people involved (specifically for the touch project >> Christopher Coat, Mervan Ougdane, Jan-Baptiste Arnaud, >> Eric Lepors and Mathieu Lacaton) and to Thales for sponsoring this >> project. >> >> https://www.youtube.com/watch?v=ksyoGItedVg >> <https://www.youtube.com/watch?v=ksyoGItedVg> > > Nice. What kind of hardware do you need for this? Is it just a > capacitive multi touch screen monitor that supports windows 8/10? yes I think so. > > Stephan > > > >

Sept. 29, 2015