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

Re: [Pharo-dev] [ann] moldable editor - documenter and examples without pragma magic

by Tudor Girba

Hi, > On Sep 2, 2017, at 10:49 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tudor. > > Could you show example with parameters? Is it possible to inspect it and how it works? The whole point was to have examples depend on each other without injecting parameters. One interesting thing about having dependencies between examples inferred statically is that we can build interesting tools. An example is a unit of comprehension and testing. For example, inspecting an example can show all dependencies, and the overall picture can transform into a logical tutorial. You can also have assertions inside examples, and run them as tests. Below you can see a picture of inspecting the examples from GtMondrian. There are a few red ones in the first pane. Selecting an example shows how it depends on other examples. At the same time, you can also see the sources expanded. What this means is that we can use the same effort and engine for both testing and documentation purposes. I will show a real case study on Monday in which we used examples as the only mechanism to drive an extensive project. It works remarkably well and we did not need classic tests at all. We call this example-driven development :). >From the same interface, you can also run an example like this (pressing the play button - you can also execute it directly from the list of examples): > And what the difference now from existing <example> methods ? <example> are rather free form unary methods and are typically used for morphs like this: exampleListWithExplicitFilterAndActionButton2 <example> | list | list := ... list openInWindow In contrast, <gtExample> marks a method that returns an object, ideally in a side-effect free manner. This object can then be used both to be viewed in different ways through inspector extensions, and can also serve as a starting point for further explorations. Cheers, Doru > > 2017-09-01 23:51 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > When we announced the GT Documenter as an application for the moldable editor, one of the remarks was that GT Examples implementation relies too much on pragma magic. > > We are now happy to announce that this is no longer the case because Andrei did a great job and rebuilt examples without the need for static pragmas for specifying dependencies. > > So, now we can example dependencies simply through normal calls: > > emptyView > <gtExample> > ^ GtMondrian new > > twoNodes > <gtExamples> > view := self emptyView > view nodes with: {1 . 2} > > ... and the engine can figure out the static dependencies. This means that examples can be used both as plain unary methods, and as replacement for tests. We think this should address the worry of examples being too heavy (the current implementation is ~350 lines). > > With a bit of extra effort, we also adapted GT Documenter to expand the example dependencies as seen below. This means that examples can now be used directly as units of documentation as well. > > We think this is significant. > > <Playground-mondrian-self-send-examples.png> > > Cheers, > The feenk team > > > -- > www.tudorgirba.com > www.feenk.com > > "We are all great at making mistakes." -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

Sept. 2, 2017

Re: [Pharo-dev] [ann] moldable editor - documenter and examples without pragma magic

by Denis Kudriashov

Hi Tudor. Could you show example with parameters? Is it possible to inspect it and how it works? And what the difference now from existing <example> methods ? 2017-09-01 23:51 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > When we announced the GT Documenter as an application for the moldable > editor, one of the remarks was that GT Examples implementation relies too > much on pragma magic. > > We are now happy to announce that this is no longer the case because > Andrei did a great job and rebuilt examples without the need for static > pragmas for specifying dependencies. > > So, now we can example dependencies simply through normal calls: > > emptyView > <gtExample> > ^ GtMondrian new > > twoNodes > <gtExamples> > view := self emptyView > view nodes with: {1 . 2} > > ... and the engine can figure out the static dependencies. This means that > examples can be used both as plain unary methods, and as replacement for > tests. We think this should address the worry of examples being too heavy > (the current implementation is ~350 lines). > > With a bit of extra effort, we also adapted GT Documenter to expand the > example dependencies as seen below. This means that examples can now be > used directly as units of documentation as well. > > We think this is significant. > > > Cheers, > The feenk team > > > -- > www.tudorgirba.com > www.feenk.com > > "We are all great at making mistakes." > > > > > > > > >

Sept. 2, 2017

[ann] moldable editor - documenter and examples without pragma magic

by Tudor Girba

Hi, When we announced the GT Documenter as an application for the moldable editor, one of the remarks was that GT Examples implementation relies too much on pragma magic. We are now happy to announce that this is no longer the case because Andrei did a great job and rebuilt examples without the need for static pragmas for specifying dependencies. So, now we can example dependencies simply through normal calls: emptyView <gtExample> ^ GtMondrian new twoNodes <gtExamples> view := self emptyView view nodes with: {1 . 2} ... and the engine can figure out the static dependencies. This means that examples can be used both as plain unary methods, and as replacement for tests. We think this should address the worry of examples being too heavy (the current implementation is ~350 lines). With a bit of extra effort, we also adapted GT Documenter to expand the example dependencies as seen below. This means that examples can now be used directly as units of documentation as well. We think this is significant. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."

Sept. 1, 2017

Re: [Pharo-dev] BOF at ESUG - How about a BOF on Gemstone development environments?

by Stephane Ducasse

Tim guille will do a presentation about the new process and esteban one on Iceberg and we should really release videos. stef On Fri, Sep 1, 2017 at 1:43 PM, Tim Mackinnon <tim(a)testit.works> wrote: > I'm envious as I couldn't make it to Esug - but I'd love to hear any conclusions/insights from that bof. Iceberg/git is such a transformative step that we need all the knowledge spread we can get. > > Tim > > Sent from my iPhone > >> On 1 Sep 2017, at 12:40, Reg Krock via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >> >> <mime-attachment> > >

Sept. 1, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Stephane Ducasse

I know your feelings. I got a bad time back in July on my mac. Iceberg blew up on me on anything I tried. So I did something else and waited for a better version. On Fri, Sep 1, 2017 at 5:54 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2017-08-31 20:05 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> Hi nicolai >> >> here is what I do. >> I always download the latest image via a bash script because updating can >> fail since loading package without a baseline may break. >> >> After I use the set up described by guille blog post and I reuse my >> downloaded clone (to avoid to trash my SSD). >> >> Esteban told me that he will do a video: >> - for producing a PR >> - for reviewing >> >> Stef >> > > Thanks, that would be great. looking forward to it, but for now I think I > will quit trying this. It is too frustrating. I can not even try to explore > icebergs functionality because it is crashing all the time. > > > > >> >> On Thu, Aug 31, 2017 at 12:06 AM, Nicolai Hess <nicolaihess(a)gmail.com> >> wrote: >> >>> Hi, >>> >>> I am now able to use iceberg on windows, thanks for the help. >>> >>> But I am still a bit unsure about how the review and contribution >>> workflow should work. >>> >>> up to pharo 6 I just load a latest image, >>> - load the slice from a fogbugz number and was able to review the change >>> - or create a slice and upload it to the inbox >>> >>> in pharo 7 >>> - what is the equivalent to "getting the latest image" (and being able >>> to load and review a fix), >>> up to pharo 6 I just >>> - load the latest image in pharolauncher (or from the command line). >>> - opened the inbox repository. >>> - load and review change/fix >>> - throw away this change (close image without save) >>> - reopen that image to move on with the next item to review. >>> >>> But now, do I have to update my local branch for every new pull >>> request ? And how do I do this ? In other git project I would, I would >>> fetch upstream, checkout master, merge with upstream/master, push >>> the master to my fork origin >>> How should this be done with my pharo 7 fork ? (And do we only work >>> on the development brach instead of the master)? >>> >>> And do I this only in the command line or do I manage my fork (and >>> keep it up to date) from within pharo with iceberg ? >>> How do I actually access the pull requests from within pharo ? Maybe >>> I am stupid, but I just can not find it. >>> I would like do this steps, (as I was used to it from the prior >>> contribution process, by loading code from the inbox) >>> - Just look at the changes >>> - apply the changes >>> - throw away this changes, and move one with the next fix review >>> >>> And the same for creating a fix / pull request. Do I need to be up to >>> date with my own fork, or only the local copy of the pharo repository ? >>> Again, for pharo 6 I would just load a latest image, make my changes / >>> code fixes and create a slice. Save to the inbox -> done. >>> And looking at iceberg, I have really no clue how to upload a fix. >>> >>> I see that other people are using the new process, and I feel a bit lost >>> and closed out of the pharo 7 development process, as I am at the moment >>> unable to understand how this work. >>> Are there any other resources I missed ? >>> >>> >>> >>> >>> 2017-08-11 19:30 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> >>>> Nicolai >>>> >>>> I started super simple. I clone and point my fresh dled image to the >>>> use the clone. >>>> Then I can do simple PR and review the issues. >>>> I will do the installation several times to learn (but not clone). >>>> >>>> I'm not sure that it is needed but I have >>>> cd /Users/ducasse/Library/Preferences/pharo/7.0 >>>> >>>> StartupPreferencesLoader default executeAtomicItems: { >>>> StartupAction >>>> name: 'Git Settings' >>>> code: [ >>>> FileStream stdout >>>> cr; nextPutAll: 'Setting the ssh >>>> credentials'; cr. >>>> Iceberg enableMetacelloIntegration: true. >>>> IceCredentialsProvider useCustomSsh: true. >>>> IceCredentialsProvider sshCredentials >>>> username: 'git'; >>>> publicKey: >>>> '/Users/ducasse/.ssh/id_rsa.pub'; >>>> privateKey: >>>> '/Users/ducasse/.ssh/id_rsa'. >>>> IceCredentialsProvider >>>> plaintextCredentials: >>>> (IcePlaintextCredentials new username: 'Ducasse'; password: 'xxxx' ; >>>> yourself ). >>>> FileStream stdout >>>> cr; nextPutAll: 'Finished'; cr ]. >>>> }. >>>> >>>> >>>> >>>> On Fri, Aug 11, 2017 at 9:46 AM, Guillermo Polito < >>>> guillermopolito(a)gmail.com> wrote: >>>> >>>>> I extended the document with some windows specific instructions also. >>>>> >>>>> On Fri, Aug 11, 2017 at 9:31 AM, Guillermo Polito < >>>>> guillermopolito(a)gmail.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Fri, Aug 11, 2017 at 12:34 AM, Nicolai Hess <nicolaihess(a)gmail.com >>>>>> > wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> 2017-08-10 17:17 GMT+02:00 Guillermo Polito < >>>>>>> guillermopolito(a)gmail.com>: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I've made some write up for the pharo part (not metacello or >>>>>>>> external projects) >>>>>>>> >>>>>>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>>>>>> ribute-a-fix-to-Pharo >>>>>>>> >>>>>>>> Of course, expect bugs on it :) Not everything is smooth. If you >>>>>>>> have comments, they are welcome. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> [image: Inline-Bild 1] >>>>>>> >>>>>>> >>>>>>> In option 2, I think this should be "Click on the Edit button", >>>>>>> >>>>>> >>>>>> Thanks, fixed! >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Guille >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Guille Polito >>>>>>>> >>>>>>>> >>>>>>>> Research Engineer >>>>>>>> >>>>>>>> French National Center for Scientific Research - >>>>>>>> *http://www.cnrs.fr* <http://www.cnrs.fr> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>>>>>> >>>>>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> >>>>>> Guille Polito >>>>>> >>>>>> >>>>>> Research Engineer >>>>>> >>>>>> French National Center for Scientific Research - *http://www.cnrs.fr* >>>>>> <http://www.cnrs.fr> >>>>>> >>>>>> >>>>>> >>>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>>>> >>>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> >>>>> Guille Polito >>>>> >>>>> >>>>> Research Engineer >>>>> >>>>> French National Center for Scientific Research - *http://www.cnrs.fr* >>>>> <http://www.cnrs.fr> >>>>> >>>>> >>>>> >>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>>> >>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>> >>>> >>>> >>> >> >

Sept. 1, 2017

Re: [Pharo-dev] review pull request changes view

by Stephane Ducasse

How? On Fri, Sep 1, 2017 at 5:56 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 1 Sep 2017, at 17:47, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2017-09-01 17:44 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> >> On 1 Sep 2017, at 17:18, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> >> >> >> 2017-09-01 17:11 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>> >>> On 1 Sep 2017, at 17:06, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>> >>> >>> >>> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess <nicolaihess(a)gmail.com> >>> wrote: >>>> >>>> >>>> Oh no! >>>> >>>> Now iceberg shows an empty list. Where is the pharo repository gone ? >>>> It took me a week to be at this point :( >>>> >>>> I reenabled the setting "Include system repositories by default", but >>>> still, the window is empty: >>>> >>>> <grafik.png> >>>> >>>> >>>> How can I get back the system repository ? >>> >>> >>> I'm not 100% sure but I think you just need to click on "add local >>> repository", point the pharo clone and add src as subdirectory. >>> >>> >>> mmm no. >>> Better: >>> >>> IceCommitInfo allInstances anyOne repository register. >>> >>> (assuming anyOne will answer a pharo package) >> >> >> hm, no. >> >> "IceCommitInfo allInstances" is empty. >> >> >> weirdâ¦ using 6.1? >> > > no, should I ? > I loaded the latest pharo 7 (or is it the same as 6.1?) > (get.pharo.org/70+vm) > > > no, is okâ¦ in fact what happened is that unloading iceberg removed the > instances of IceCommitInfo > so, I do not think this is a valid way to update on 7.0â¦ easier is just to > clone iceberg (with iceberg) and update it as any other project. > > Esteban > > >> >> >> >>> >>> >>> Esteban >>> >>> >>> >>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >>> >>> http://www.synectique.eu >>> 2 rue Jacques PrÃ©vert 01, >>> 59650 Villeneuve d'ascq France > >

Sept. 1, 2017

Re: [Pharo-dev] The mooc is looking for forum moderators

by Stephane Ducasse

Thank you Rajula we should reply to the question of the mooc followers and help them On Fri, Sep 1, 2017 at 6:12 PM, Rajula Vineet <Vineet.Reddy(a)iiitb.org> wrote: > Hey, > > I know I am new here. And I am not sure what exactly forum moderation is. > But I would be happy to involve. Do let me know if I can do it. > > Rajula > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 1, 2017

Re: [Pharo-dev] State of 64bits? Errors during configuration loading

by Cyril Ferlicot

On ven. 1 sept. 2017 at 20:24, Tim Mackinnon <tim(a)testit.works> wrote: > I've probably done 100 builds on 64bits - I've had one crash (reported > here). > > So it's not common, but does happen. > > Tim > > Sent from my iPhone > We must be unlucky :) 2 builds, 2 vm crashes. > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Sept. 1, 2017

Re: [Pharo-dev] State of 64bits? Errors during configuration loading

by Tim Mackinnon

I've probably done 100 builds on 64bits - I've had one crash (reported here). So it's not common, but does happen. Tim Sent from my iPhone > On 1 Sep 2017, at 17:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > I am using it everyday without problemsâ¦ but this is a limited test ;) > if you get crashes, I would like to have those reports to see what can we do. > > Esteban > >> On 1 Sep 2017, at 17:01, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >> >> Hi, >> >> I would like to know the state of the 64bits builds. At Synectique we >> tried to build on of our tools in 64bits on ubuntu slaves but we get a >> lot a VM crashes. >> >> We get the image/vm with this command: >> >> wget --quiet -O - get.pharo.org/64/$PHARO+$VM | bash >> >> $PHARO = 61 >> $VM = vm >> >> Here is the command we launch: >> >> ./pharo Pharo.image --no-default-preferences eval --save 'Metacello new >> repository:'\''http://smalltalkhub.com/mc/*******/*********/main'\''; >> configuration: '\''********'\''; >> version: #development; >> load' >> >> And I join an example of log we get when the vm crash. >> >> Is that a known issue? >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> http://www.synectique.eu >> 2 rue Jacques PrÃ©vert 01, >> 59650 Villeneuve d'ascq France >> <dump.txt> > >

Sept. 1, 2017

Re: [Pharo-dev] The mooc is looking for forum moderators

by Rajula Vineet

Hey, I know I am new here. And I am not sure what exactly forum moderation is. But I would be happy to involve. Do let me know if I can do it. Rajula -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 1, 2017