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

Re: [Pharo-users] [Moose-dev] [ann] gtdebugger in pharo 5.0

by Tudor Girba

Hi, Thanks indeed for the feedback. I think not quite all are bugs, but see more details inside. > On Jan 14, 2016, at 12:59 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Hi Nicolai, > > Thanks for reporting these issues. They are indeed bugs and we are working on fixing them. > > Cheers, > Andrei > > On Tue, Jan 12, 2016 at 11:24 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-01-08 11:24 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > We are about to integrate in Pharo a new member of the Glamorous Toolkit: the GTDebugger. As this is a significant change that might affect your workflow, here is some background information to help you deal with the change. > > First, you should know that the change is not irreversible and it is easily possible to disabled the new debugger through a setting. However, please do take the time to provide us feedback if something does not work out for you. We want to know what can be improved and we try to react as fast as we can. > > A practical change comes from the fact that the variables are manipulated through a GTInspector, which makes it cheaper to maintain in the longer run. > > Accept and Cancel buttons shouldn't be there > or should not act on if the codepane hasn't changed. > (every press on "accept" writes a new method version, although the contents didn't changed - tested on > Latest update: #50524 ) Good catch. This will happen even if the button would not be present. > Most (all?) other tools don't have Accept/Cancel buttons. The logic is that these are actions that do not depend on the selection, so in Glamour we map these on actions that are applicable to the entire presentation. A similar approach is present in the inspector, although probably it does not appear so prominently because there is no text. We could try to add them in a dropdown menu. Would that help? > - I really miss the "List Methods using 'varname'/List Methods storing into âvarname' Please open an issue for this. > - is "stackTop" now gone ? I thought you wanted to add it to the stack ? > - thisContext is gone as well ? These were removed due to emergency mail exchange that happened during the last weekend. > - the Bytecode/GT button is badly placed, it looks like the "downarrow" window menu icon > is a dropdown menu with label âBytecode" We could try to fix by adding more space to the left of the menu bar in the theme. Could you open an issue? > (since when do we put buttons in the title pane? Since Glamour makes it easy to have them there :). The GTPlayground and GTInspector have them, too. > - the evaluator pane is shown as "dirty", as it does not make a difference if we > accept the text in this pane, there shouldn't be a dirty indicator. This is a problem that seems to exist with basically every pharoScript in Glamour. You commented on an issue for this: https://pharo.fogbugz.com/f/cases/16757/GLMHighlighterTextRubEditingMode-al… > - you can not use the inspector pane to change inst var values This is a problem but it is not specific to the debugger. > - there is no way to refresh the inspector pane Indeed. Would it be enough if we added a refresh for the whole debugger? Cheers, Doru > I don't open bugtracker entries now, I 'll wait maybe this issues aren't bugs but > features. > > > nicolai > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

Jan. 15, 2016

Re: [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, defaultReadStreamCreationBlock: [ process createTempFileToBeUsedAsReadStreamOn: '/tmp' ]; In the readme, the piece of code containing that is a bit suspicious because it depends on the fact that the block is evaluated after the variable 'process' is assigned. -- 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

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

by Luc Fabresse

Hi Mariano, Thanks to tackle and document these things! I did not read all what you wrote yet, but do you have also the possibility to process stdout/stderr while the external process is running and not only on exit? Something like: OSSUnixSubprocess new command: 'reallyLongToExecuteCommandWithLotsOfThingsOnStdout'; redirectStdout; redirectStderr; runAndDo: [ :process :outStream :errStream | "I can analyze outStream / errStream" "and even show status to the user" ] each: 5 seconds; onExitDo: [ :process :outStream :errStream | "cleanup" ] Cheers, #Luc 2016-01-15 8:20 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > And for those who would like to use it (or for Mac OS X users), a > GitFileTree version using it is available by loading it this way: > > Metacello new > baseline: 'FileTree'; > repository: 'github://dalehenrich/filetree:issue_171/repository'; > load: 'Git' > > Regards, > > Thierry > > Le 14/01/2016 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, >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > >

Jan. 15, 2016

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

by Thierry Goubier

And for those who would like to use it (or for Mac OS X users), a GitFileTree version using it is available by loading it this way: Metacello new baseline: 'FileTree'; repository: 'github://dalehenrich/filetree:issue_171/repository'; load: 'Git' Regards, Thierry Le 14/01/2016 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, > > -- > Mariano > http://marianopeck.wordpress.com

Jan. 15, 2016

Re: [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

Re: [Pharo-users] Working with a compressed Fuel file?

by Mariano Martinez Peck

And what happened with the vm gzip crash? Still around? On Tue, Jan 5, 2016 at 3:43 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 05-01-16 16:29, Stephan Eggermont wrote: > >> Writing out the 71712 unique definitions in this project separately is >> 54MB. The project consists of 17 packages with 2723 package versions, >> the total number of pointers to the definitions is 2.2 million. >> The total should be below 100MB >> > > Thanks to the help of Max and Thierry I found the problem. > > Set withAll: (MCVersionInfo allInstances collect: [ :each | each id ]) > 7155 > > MCVersionInfo allInstances size 2726588 > > 2030 versions of VMMaker-> 2029+2028+2027+...+1 MCVersionInfo's ideally... > > Stephan > > > > > -- Mariano http://marianopeck.wordpress.com

Jan. 15, 2016

Re: [Pharo-users] [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-users] Spec: Populating a playground with a particular content (was Re: Spec: Binding widgets how to)

by Nicolai Hess

2016-01-14 17:20 GMT+01:00 Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> : > Hi Nicolai, > > That was the issue. Now it's working! I was trying to test different > combinations to see why UI updating was not happening but I got the > variations wrong (one true, another false, instead of both false :-) ). > > The next step I'm working on in populating the GTPlayPage with some > particular content. In my previous interface I made something like this: > > -[1]--------------------- > GrafoscopioBrowser>>panelAsCodeFor: aNode > "Shows an interactive playground for Smalltalk code in a node body" > > browser := GLMTabulator new. > browser title: 'CÃ³digo'. > browser column: #code. > browser transmit > to: #code; > transformed: [ GTPlayPage new content: aNode body ]; > andShow: [ :a | a custom: GTPlayground new ]. > browser sendToOutside: #nodeBody from: #code -> #text. > ^ browser. > ------------------------ > > In this one I tried some variation of GlamourPresentationModel>>glmPres > that let the user predefine a content for the GTPlayPage like this: > > -[2]---------------------- > glmPresWithContent: aString > glmPres isNil ifTrue:[ > glmPres := GTPlayground new startOn: (GTPlayPage new content: > aString)]. > ^glmPres > --------------------------- > > but if I try running the interface with this I get: > "MessageNotUnderstood: GlamourPresentationModel>>content:", so I think that > something more is needed to create Playgrounds in the Spec-Glamour that are > pre-populated with content. > > How can I create a playground inside a Spec-Glamour interface that is > already populated with a given content? > > I would expect (content is the GlamourPresentationModel) content glmPres codePresentation text: 'new text'. but it does not work. > Thanks, > > Offray > > On 14/01/16 03:56, Nicolai Hess wrote: > > > > 2016-01-13 23:07 GMT+01:00 Offray Vladimir Luna CÃ¡rdenas < > <offray(a)riseup.net>offray(a)riseup.net>:ui insp presentationClass: > GTInspector startOn: 42. > > Hi, >> >> I've reading the code at [1] but I'm still having problems understanding >> the dynamic spec. I have created a small dictionary and populated with >> data, then created the accessors and initializePresenter, initializeWidgets >> and rebuildWithdCodeLayout and rebuildWithTextLayout, as you can see on the >> following snippets, but nothing happens despite the debugging Transcript is >> showing me that the content subwidget has the proper model, but is not >> rebuild in the GUI. >> >> Any help is, as always, very much appreciated. >> > > Hi Offray, > > I think you have to call > self needRebuild: false. > in both rebuild... methods. > Otherwise the all "inner"-widgets are rebuild: > > > >> >> [1] >> https://github.com/spec-framework/documentation/blob/master/output/book.md#… >> >> ---------------------- >> DynamicDict>>initializeWidgets >> >> | data | >> data := { 'first' -> 'I\"m just text' . 'second' -> 'ProfStef >> openPharoZenWorkspace'} asOrderedDictionary. >> list := self newList. >> list items: data keys. >> content := self newText. >> self focusOrder >> add: list; >> add: content. >> ---------------------- >> DynamicDict>>initializePresenter >> list whenSelectedItemChanged: [:item | >> item = 'first' >> ifTrue: [ self rebuildWithTextLayout ]. >> item = 'second' >> ifTrue: [ self rebuildWithCodeLayout ]. >> ] >> ---------------------- >> DynamicDict>>rebuildWithCodeLayout >> | newLayout | >> >> content := self instantiate: GlamourPresentationModel. >> newLayout := SpecLayout composed >> newRow: [:row | >> row >> add: #list right: 0.7; >> add: #content left: 0.3]; >> yourself. >> self needRebuild: true. >> content needRebuild: true. >> Transcript show: 'cÃ³digo + ', self content asString, String cr. >> self buildWithSpecLayout: newLayout. >> ---------------------- >> DynamicDict>>rebuildWithTextLayout >> | newLayout | >> >> content := self newText. >> newLayout := SpecLayout composed >> newRow: [:row | >> row >> add: #list right: 0.7; >> add: #content left: 0.3]; >> yourself. >> self needRebuild: false. >> list needRebuild: false. >> content needRebuild: true. >> Transcript show: 'texto + ', self content asString, String cr.. >> self buildWithSpecLayout: newLayout. >> ---------------------- >> >> Cheers, >> >> Offray >> >> On 10/01/16 13:39, Johan Fabry wrote: >> >> Sorry for the lateness and short reply but Iâm involved in a bunch of >> other things that are taking almost all of my time ... >> >> From what I understand and what I can see in your code, you want to >> modify a widget when the UI is open. However you never trigger the >> rebuilding of the window. For example, see the Spec docs that I sent, where >> in 9.1 there is code that calls buildWithSpecLayout: . >> >> Actually, I am not sure you need to subclass DynamicComposableModel since >> the number of widgets never changes. You can use a normal ComposableModel >> subclass and use what is detailed in 9.1 to change the layout between the >> two options you want to have (a TextModel or a GlamourPresentationModel). >> >> On Jan 8, 2016, at 23:07, Offray Vladimir Luna CÃ¡rdenas < >> <offray(a)riseup.net>offray(a)riseup.net> wrote: >> >> Shouldn't be #right dynamically defined according to the values of 'item' >> and be replaced on the m2 layout? >> >> >> >> >> ---> Save our in-boxes! http://emailcharter.org <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry >> PLEIAD and RyCh labs - Computer Science Department (DCC) - University >> of Chile >> >> >> > >

Jan. 14, 2016

Re: [Pharo-users] A Turing Machine simulator written in Pharo

by Julien Delplanque

No problem, I will do that. :) Julien On 14/01/16 16:33, Sven Van Caekenberghe wrote: > Julien, > >> On 14 Jan 2016, at 15:42, Julien Delplanque <julien(a)tamere.eu> wrote: >> >> Hey everyone, >> >> I had a course named "Calculabilty and Complexity" last year and I implemented a Turing >> Machine simulator using Pharo just to see how easy/hard it would be (it was quite easy :) ). >> >> I also wrote a little thing on medium about it [1] (I just took half an hour to review it and >> I thought it was time to publish it). > Very nice, this is important. > > Would you be interested to have your article included in https://medium.com/concerning-pharo ? If so, I believe you have to submit it and then I can accept it. I would love to have it there. > > Sven > >> Just announcing it in case it case someone need/is interested by this. >> >> There is also a github repository for the source code [2]. >> >> Julien >> >> [1]: https://medium.com/@juliendelplanque/a-turing-machine-simulator-written-in-… >> [2]: https://github.com/juliendelplanque/turing-machine >> >

Jan. 14, 2016

Re: [Pharo-users] A Turing Machine simulator written in Pharo

by Julien Delplanque

:) On 14/01/16 16:05, stepharo wrote: > Thanks I never got any lecture on this machine so I will read it :) > But there is no explanation about the mathematical model (there is too much things to say), just how to simulate it... :) > > Le 14/1/16 15:42, Julien Delplanque a Ã©crit : >> Hey everyone, >> >> I had a course named "Calculabilty and Complexity" last year and I >> implemented a Turing >> Machine simulator using Pharo just to see how easy/hard it would be >> (it was quite easy :) ). >> >> I also wrote a little thing on medium about it [1] (I just took half >> an hour to review it and >> I thought it was time to publish it). >> >> Just announcing it in case it case someone need/is interested by this. >> >> There is also a github repository for the source code [2]. >> >> Julien >> >> [1]: >> https://medium.com/@juliendelplanque/a-turing-machine-simulator-written-in-… >> [2]: https://github.com/juliendelplanque/turing-machine >> >> > >

Jan. 14, 2016