March 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Magritte extension

by Mariano Martinez Peck

Hi, Before a longer answer, what is TBSMagritteReport ? Is it yours or is it some magritte extension for Bootstrap? Thanks, On Fri, Mar 17, 2017 at 3:54 AM, Asbath Sama biyalou <asamabiyalou(a)yahoo.com > wrote: > Hello. > > I am using Magritte to generate reports for a pharo class. I want to > customize generated components in order to have a better design. > > My class is Match > > Object subclass: #Match > instanceVariableNames: 'date_match hour_match status actions stadium > comments teams goals1 goals2 competition' > classVariableNames: '' > category: MyProject-Entity' > > > Descriptions for some variables. > > Stadium is also a Class. > > Match>>descriptionStadium > <magritteDescription> > ^ MASingleOptionDescription new > label: 'Stadium'; > priority: 305; > accessor: #stadium; > options: Team allStadiumsName; > componentClass: TBSMagritteSelectListComponent; > beRequired; > yourself > > > Match>>descriptionTeams > <magritteDescription> > ^ MAMultipleOptionDescription new > label: 'Teams'; > priority: 805; > accessor: #teams; > options: Team allTeamsName; > componentClass: MAMultiselectListComponent; > yourself > > > The generated component in the form is not very pretty. I want to have > multiple checkbox. > > > Match>>descriptionStatus > <magritteDescription> > ^ MASingleOptionDescription new > label: 'Status'; > priority: 505; > accessor: #status; > options: #('Pas en cours' 'En Cours' 'Mi-temps' 'TerminÃ©'); > componentClass: TBSMagritteSelectListComponent; > yourself > > > For the report I use the class SEMatchReport > > TBSMagritteReport subclass: #SEMatchReport > instanceVariableNames: 'report' > classVariableNames: '' > category: 'MyProject-Components' > > > SEMatchReport class>>from > | report matchs commandColumn | > matchs := Match selectAll. > report:= self rows: matchs description: (self > filteredDescriptionsFrom: matchs anyOne). > > commandColumn := MACommandColumn new. > > (SEMatchReport new session isSimpleAdmin) > ifTrue: [ > report addColumn: (commandColumn > addCommandOn: report selector: #editMatch: text: 'Modifier'; > yourself; > addCommandOn: report selector: #addAction: text: 'Ajouter > une action'; yourself ) ] > ifFalse: [ > report addColumn: (commandColumn > addCommandOn: report selector: #editMatch: text: 'Modifier'; > yourself; > addCommandOn: report selector: #deleteMatch: text: > 'Supprimer'; yourself; > addCommandOn: report selector: #addAction: text: 'Ajouter > une action'; yourself ) ]. > > ^ report > > I want to put some bootstrapp icons near commandColumn actions. like > pencil or delete on 'Supprimer'. > > > SEMatchReport class>>filteredDescriptionsFrom: aMatch > ^ aMatch magritteDescription select: [ :each | #(date_match > hour_match stadium goals1 goals2 teams) > includes: each accessor selector ] > > I notice that on the generated report on column stadium we have > aStadium. We don't have the value (the name). I don't know how to > mention it in the filtered descriptions. > > Change the color of lines in the report, etc. All that things. > > Sorry for the bad english. > > Thanks. > > Asbath > > -- Mariano http://marianopeck.wordpress.com

March 17, 2017

Re: [Pharo-users] Specifying library dependencies in UFFI

by Mark Bestley

Not that well on macOS. Yes it works but you want to launch Pharo from thr Dock and not via the command line. But yes put the DLLs in with the VM files should work in all main OSs Mark On 17/03/2017 08:44, raffaello.giulietti(a)lifeware.ch wrote: > Hi Pierce, > > sure, this works on any Unix-like system. > > > > On 17/03/17 03:37, Pierce Ng wrote: >> On Wed, Mar 15, 2017 at 09:31:45AM +0100, Raffaello Giulietti wrote: >>> Suppose my code directly accesses "my.dll" which, in turn, depends >>> on "her.dll" which my code does not need directly and suppose that >>> library is located in folder "<path-to-her-folder>". How can I >>> enforce the UFFI to perform the search there? >> >> >> On Linux, I use a shell script "gopharo" to run the VM: >> >> #!/bin/sh >> PHAROVMPATH=$(dirname `readlink -f "$0"`) >> LD_LIBRARY_PATH="$PHAROVMPATH" exec "$PHAROVMPATH/pharo" $@ >> >> LD_LIBRARY_PATH is customizable. In my case, I place 3rd party files like >> libsqlite.so, libunqlite.so together with the standard VM files. >> >> Pierce >> >> > > > -- Mark

March 17, 2017

Re: [Pharo-users] doesNotUnderstand: infinit loop

by Esteban A. Maringolo

2017-03-17 6:46 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2017-03-16 18:07 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: >> >> I got used to save the image before debugging a single test and/or recover >> lost changes. But this is certainly hard if you want to do TDD :) >> >> Is this related with the debugger UI (GT) or with the underlying >> frameworks? > > > No. Problem is in Context methods: #stepToHome: and > #runUntilErrorOrReturnFrom:. They called from DebugSession #stepThrough: and > #stepOver: I don't know the internals of the debugger, nor the Context execution, but this sometimes happens when running the test, without an open debugger. I will try to find a case and report it to the latest issue you created. Thanks for your support. Esteban A. Maringolo

March 17, 2017

Re: [Pharo-users] Recreating Live Coding experience in C++ and Python [ was: Re: Specifying library dependencies in UFFI]

by Dima Makhnin

Why all the hype about python? why not more flexible languages like JavaScript ES6, or Perl5 that are capable of preserving string to object literal isomorphism out of the box? Of course Dynamic Languages are fine for this, that's essentially what Objective C is; C + FakeTalk. I dream of a future where we can throw out the silly C processor macros and replace them with a real script engine; eg write c in a php file and have it generate code at preprocessor time, and if you need help at runtime, load the php runtime, and interact with it. This can be done in any language, For SmallTalk it's something like objective c but objective c is halfway there, it didn't replace c preprocessor with inline smalltalk. But yeah, hopefully we see more elegant compiletime-runtime interop in the future. On Mar 17, 2017 6:21 AM, "Dimitris Chloupis" <kilon.alios(a)gmail.com> wrote: > > With any tech, there is always this hype cycle with the disullusionment >> after the "peak of excitement" and that is needed to reach the >> productivity. >> >> I would urge all Pharo users to keep pushing and not let go of the >> vision, because there is really nothing like Pharo around. >> > > The one things I love about Pharo is Live Coding. The ability to change > the code while it executes without all this recompile-restart nonsense. > > I also was under the assumption you were when it came to live coding that > none is doing better than Smalltalk and Lisp. So just for fun I went on to > experiment how easy it would be to re implement live coding in C++ and > Python. I was not expecting much if anything. > > With Python it was super easy, I only need a main loop, wrap the loop > inside an exception that in case of an error would catch the error , not > stop the execution but rather using the import tools that come with Python > will import the module. Worked like a charm. > > I use this to develop a blender addon. > > But the really shock was how easy it was to do this with C++. I thought > that memory leaks would make live coding with C++ impossible , I was dead > wrong. Apparently OS exceptions can capture even crashes, they wont allow > the executable to crash. Instead of python modules I use DLLs on windows , > .dylibs on MacOS and .so on Ubuntu. Executable is a tiny loop reloading the > dlls and providing to them a pointer to a very large array that contains > the entire memory of the app, DLLs handle the memory to share it between > objects etc. > > https://github.com/kilon/LiveCPP > > Next step is integrating iPython and also python debugger and testing unit > testing with live coding. > > So yes definetly learn Pharo because it has many hidden gems , if you are > newcomer. But if you miss Pharo , like me, when you code in other language, > despair not, its very easy to recreate at least live coding. >

March 17, 2017

Recreating Live Coding experience in C++ and Python [ was: Re: Specifying library dependencies in UFFI]

by Dimitris Chloupis

> With any tech, there is always this hype cycle with the disullusionment > after the "peak of excitement" and that is needed to reach the > productivity. > > I would urge all Pharo users to keep pushing and not let go of the vision, > because there is really nothing like Pharo around. > The one things I love about Pharo is Live Coding. The ability to change the code while it executes without all this recompile-restart nonsense. I also was under the assumption you were when it came to live coding that none is doing better than Smalltalk and Lisp. So just for fun I went on to experiment how easy it would be to re implement live coding in C++ and Python. I was not expecting much if anything. With Python it was super easy, I only need a main loop, wrap the loop inside an exception that in case of an error would catch the error , not stop the execution but rather using the import tools that come with Python will import the module. Worked like a charm. I use this to develop a blender addon. But the really shock was how easy it was to do this with C++. I thought that memory leaks would make live coding with C++ impossible , I was dead wrong. Apparently OS exceptions can capture even crashes, they wont allow the executable to crash. Instead of python modules I use DLLs on windows , .dylibs on MacOS and .so on Ubuntu. Executable is a tiny loop reloading the dlls and providing to them a pointer to a very large array that contains the entire memory of the app, DLLs handle the memory to share it between objects etc. https://github.com/kilon/LiveCPP Next step is integrating iPython and also python debugger and testing unit testing with live coding. So yes definetly learn Pharo because it has many hidden gems , if you are newcomer. But if you miss Pharo , like me, when you code in other language, despair not, its very easy to recreate at least live coding.

March 17, 2017

Re: [Pharo-users] [ANN] Release of the Spec book

by Johan Fabry

Hi Phil, yes this is correct, in the end we did not need to make any changes to that version so it is the 1.0 version. -- Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org <http://emailcharter.org/> . Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > On 17 Mar 2017, at 10:44, phil(a)highoctane.be wrote: > > The book PDF is dated Feb 2016. Is this correct? > > Phil > > On Fri, Mar 17, 2017 at 10:16 AM, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > Great work from the two of you, as usual ! > > Thanks for the effort, it must have been a lot of work. > > I immediately ordered a print copy for my growing Pharo book collection. > > > On 17 Mar 2017, at 09:32, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > > > > Hi all, > > > > StÃ©phane and I are happy to announce the 1.0 release of the book on Spec, the UI framework for Pharo!! > > > > This book was needed because the existing documentation was not really user-friendly and dispersed. I gathered everything I could find, sorted, filtered and rewrote, in collaboration with Stef. This is the reference documentation of Spec for Pharo 5 and 6, as well as my Magnum Opus on Spec (I have other ones on other topics ;-) ). We hope it will be useful for you. > > > > A small overview of the content: This book first shows the basics of Spec and how it enables reuse of UIs. It then treats UI layout in detail before moving on to explaining the management of windows. Some of the more advanced widgets are also discussed as well as the dynamic features of Spec. Lastly, the book also contains a chapter with tips and tricks. > > > > You can download a pdf of the book at http://files.pharo.org/books/spec-tutorial/ <http://files.pharo.org/books/spec-tutorial/> and also buy a hardcopy here: http://www.lulu.com/shop/johan-fabry-and-stÃ©phane-ducasse/the-spec-ui-fram… <http://www.lulu.com/shop/johan-fabry-and-st%C3%A9phane-ducasse/the-spec-ui-…> Itâs only 9.99EUR so so you can easily afford it, and moreover all proceedings of sales go the the Pharo association ! > > > > -- > > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org <http://emailcharter.org/> . > > > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > > > > > > >

March 17, 2017

Re: [Pharo-users] doesNotUnderstand: infinit loop

by Denis Kudriashov

2017-03-17 10:46 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > 2017-03-16 18:07 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > >> I got used to save the image before debugging a single test and/or >> recover lost changes. But this is certainly hard if you want to do TDD :) >> >> Is this related with the debugger UI (GT) or with the underlying >> frameworks? >> > > No. Problem is in Context methods: #stepToHome: and > #runUntilErrorOrReturnFrom:. They called from DebugSession #stepThrough: > and #stepOver: Another problem that we do not have tests for all these debugger actions.

March 17, 2017

Re: [Pharo-users] doesNotUnderstand: infinit loop

by Denis Kudriashov

2017-03-16 18:07 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > I got used to save the image before debugging a single test and/or recover > lost changes. But this is certainly hard if you want to do TDD :) > > Is this related with the debugger UI (GT) or with the underlying > frameworks? > No. Problem is in Context methods: #stepToHome: and #runUntilErrorOrReturnFrom:. They called from DebugSession #stepThrough: and #stepOver:

March 17, 2017

Re: [Pharo-users] [ANN] Release of the Spec book

by phil＠highoctane.be

The book PDF is dated Feb 2016. Is this correct? Phil On Fri, Mar 17, 2017 at 10:16 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Great work from the two of you, as usual ! > > Thanks for the effort, it must have been a lot of work. > > I immediately ordered a print copy for my growing Pharo book collection. > > > On 17 Mar 2017, at 09:32, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > > > Hi all, > > > > StÃ©phane and I are happy to announce the 1.0 release of the book on > Spec, the UI framework for Pharo!! > > > > This book was needed because the existing documentation was not really > user-friendly and dispersed. I gathered everything I could find, sorted, > filtered and rewrote, in collaboration with Stef. This is the reference > documentation of Spec for Pharo 5 and 6, as well as my Magnum Opus on Spec > (I have other ones on other topics ;-) ). We hope it will be useful for you. > > > > A small overview of the content: This book first shows the basics of > Spec and how it enables reuse of UIs. It then treats UI layout in detail > before moving on to explaining the management of windows. Some of the more > advanced widgets are also discussed as well as the dynamic features of > Spec. Lastly, the book also contains a chapter with tips and tricks. > > > > You can download a pdf of the book at http://files.pharo.org/books/ > spec-tutorial/ and also buy a hardcopy here: http://www.lulu.com/shop/ > johan-fabry-and-stÃ©phane-ducasse/the-spec-ui-framework/ > paperback/product-23040294.html Itâs only 9.99EUR so so you can easily > afford it, and moreover all proceedings of sales go the the Pharo > association ! > > > > -- > > Does this mail seem too brief? Sorry for that, I donât mean to be rude! > Please see http://emailcharter.org . > > > > Johan Fabry - http://pleiad.cl/~jfabry > > PLEIAD and RyCh labs - Computer Science Department (DCC) - > University of Chile > > > > > > > >

March 17, 2017

Re: [Pharo-users] [ANN] Release of the Spec book

by Sven Van Caekenberghe

Great work from the two of you, as usual ! Thanks for the effort, it must have been a lot of work. I immediately ordered a print copy for my growing Pharo book collection. > On 17 Mar 2017, at 09:32, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Hi all, > > StÃ©phane and I are happy to announce the 1.0 release of the book on Spec, the UI framework for Pharo!! > > This book was needed because the existing documentation was not really user-friendly and dispersed. I gathered everything I could find, sorted, filtered and rewrote, in collaboration with Stef. This is the reference documentation of Spec for Pharo 5 and 6, as well as my Magnum Opus on Spec (I have other ones on other topics ;-) ). We hope it will be useful for you. > > A small overview of the content: This book first shows the basics of Spec and how it enables reuse of UIs. It then treats UI layout in detail before moving on to explaining the management of windows. Some of the more advanced widgets are also discussed as well as the dynamic features of Spec. Lastly, the book also contains a chapter with tips and tricks. > > You can download a pdf of the book at http://files.pharo.org/books/spec-tutorial/ and also buy a hardcopy here: http://www.lulu.com/shop/johan-fabry-and-stÃ©phane-ducasse/the-spec-ui-fram… Itâs only 9.99EUR so so you can easily afford it, and moreover all proceedings of sales go the the Pharo association ! > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > >

March 17, 2017