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

Re: [Pharo-dev] Booklet suggestion

by Ben Coman

On Thu, May 25, 2017 at 9:32 PM, askoh <askoh(a)askoh.com> wrote: > You gave me an idea. > > Since Test Driven Design insists all tests passes before release, we can > piggy back on that by insisting Tutorials, Demos, Examples be tests that > must pass before release. Can we design Tutorials, Demos, Examples like > tests? I think so. > So TDDoc? cheers -ben

May 25, 2017

Re: [Pharo-dev] multiple crashes on macOS Sierra

by Stephane Ducasse

It happened to me too. On Thu, May 25, 2017 at 12:17 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > For me the Bloc image on Ubuntu Linux 14.04 LTS never reopened back. > > All I get is a black screen. > > Damn. > > > Phil > > On Thu, May 25, 2017 at 9:34 AM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Hi doru >> >> Yes I get the same. Now I was also in the bloc image, I got crash when >> resizing the host window. >> >> Stef >> >> On Wed, May 24, 2017 at 10:28 PM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >>> Hi, >>> >>> Today I experienced multiple crashes on macOS Sierra. >>> >>> These happened during regular programming, mostly while typing code. I >>> attached here the crash dump(s). I believe I heard Phil having the same >>> issue with the stable Pharo VM. >>> >>> Does anyone else has the same issue? >>> >>> The VM is: >>> CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 >>> May 2 2017 >>> StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: >>> 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 >>> VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git >>> $ Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 >>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ >>> >>> The Pharo update number is: 60482 >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "From an abstract enough point of view, any two things are similar." >>> >>> >>> >>> >> >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by Stephane Ducasse

What I would like is to extend pillar with a special environment [[[testable=5 3+ 2 ]]] and also [[[screenshot: 10@200 named: 'browserOpen' Browser open ]]] Now I need help on pillar. Stef On Thu, May 25, 2017 at 3:57 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > What I'm doing is > - extracting a subset of pillar > - doc + renderer > - so that we can use it in the image. > Now kasper did a first version (in the repository and if people want to > have a look it will help) > - now I'm remaving the dependency on magritte. > > Stef > > On Thu, May 25, 2017 at 2:03 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> Nice idea. I've seen vague discussion about getting Pillar into the >> standard image for documentation. >> Perhaps it should be raised for consideration for Pharo 7? >> >> Actually you stimulate my thoughts that the Help file might be a >> better place for such snippets, >> so they are always with the image, and don't need to be retyped. Any >> objections? >> >> cheers -ben >> >> On Thu, May 25, 2017 at 4:00 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >> > Ben, >> > >> > I think there is a deeper need here. Writing good document is hard and >> > keeping it in sync with code is harder still. >> > >> > A book/booklet separates content from the code and being frozen in time >> > faces obsolescence. I would prefer to see a guidebook framework in Pharo >> > that every package author can use to create a simple narrative on its >> > features. Package authors and consumers have an incentive to keep the >> code >> > and content in sync. If an Object is a recursion on the notion of a >> > computer, why not provide, say a Note, as a recursive simplification of >> a >> > book? >> > >> > The framework could be on the lines of Plugins, Tests. E.g. >> > >> > Package-Core >> > Package-Plugins >> > Package-Tests >> > *Package-Guide* >> > >> > The guide framework should support active code (say to pop the source >> code >> > for a method), active links to guides on which this package depends, >> > automatic generation of table of contents, index of class references. >> Most >> > of features already exists in Pharo but spread all over. They need a >> home. >> > >> > A package could also extend this basic framework with features (e.g. PDF >> > package could export articles to PDF, Zinc could generate HTML). >> > >> > Regards .. Subbu >> > >> > >> > On Thursday 25 May 2017 07:03 AM, Ben Coman wrote: >> >> >> >> I've seen a few requests for short bits of code to use in playground >> for >> >> a demo presentation. I wonder if it would be good to have a booklet to >> >> gather these - seeded with Sven's excellent article... >> >> https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 >> >> >> >> It could include the recent meta-programming scripts like searching for >> >> all class instance variables starting with a capital letter. >> >> >> >> The book might be named "Snippets", in a format presentable to laser >> >> print on-site - something physical for attendees to take away with them >> >> to quick demo to others back in their office. >> >> >> >> I can take the lead in setting it up. Anyone remember any relevant >> >> posts in our archives? >> >> >> >> cheers -ben >> > >> > >> > >> >> >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by Stephane Ducasse

What I'm doing is - extracting a subset of pillar - doc + renderer - so that we can use it in the image. Now kasper did a first version (in the repository and if people want to have a look it will help) - now I'm remaving the dependency on magritte. Stef On Thu, May 25, 2017 at 2:03 PM, Ben Coman <btc(a)openinworld.com> wrote: > Nice idea. I've seen vague discussion about getting Pillar into the > standard image for documentation. > Perhaps it should be raised for consideration for Pharo 7? > > Actually you stimulate my thoughts that the Help file might be a > better place for such snippets, > so they are always with the image, and don't need to be retyped. Any > objections? > > cheers -ben > > On Thu, May 25, 2017 at 4:00 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > > Ben, > > > > I think there is a deeper need here. Writing good document is hard and > > keeping it in sync with code is harder still. > > > > A book/booklet separates content from the code and being frozen in time > > faces obsolescence. I would prefer to see a guidebook framework in Pharo > > that every package author can use to create a simple narrative on its > > features. Package authors and consumers have an incentive to keep the > code > > and content in sync. If an Object is a recursion on the notion of a > > computer, why not provide, say a Note, as a recursive simplification of a > > book? > > > > The framework could be on the lines of Plugins, Tests. E.g. > > > > Package-Core > > Package-Plugins > > Package-Tests > > *Package-Guide* > > > > The guide framework should support active code (say to pop the source > code > > for a method), active links to guides on which this package depends, > > automatic generation of table of contents, index of class references. > Most > > of features already exists in Pharo but spread all over. They need a > home. > > > > A package could also extend this basic framework with features (e.g. PDF > > package could export articles to PDF, Zinc could generate HTML). > > > > Regards .. Subbu > > > > > > On Thursday 25 May 2017 07:03 AM, Ben Coman wrote: > >> > >> I've seen a few requests for short bits of code to use in playground for > >> a demo presentation. I wonder if it would be good to have a booklet to > >> gather these - seeded with Sven's excellent article... > >> https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 > >> > >> It could include the recent meta-programming scripts like searching for > >> all class instance variables starting with a capital letter. > >> > >> The book might be named "Snippets", in a format presentable to laser > >> print on-site - something physical for attendees to take away with them > >> to quick demo to others back in their office. > >> > >> I can take the lead in setting it up. Anyone remember any relevant > >> posts in our archives? > >> > >> cheers -ben > > > > > > > >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by askoh

You gave me an idea. Since Test Driven Design insists all tests passes before release, we can piggy back on that by insisting Tutorials, Demos, Examples be tests that must pass before release. Can we design Tutorials, Demos, Examples like tests? I think so. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Booklet-suggestion-tp4948195p4948263.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 25, 2017

Re: [Pharo-dev] [Seaside-dev] Updated Seaside Control Panel for Pharo 6 / Seaside 3.2

by Tim Mackinnon

Guys - I really appreciate the work you are putting into this. As an old newcomer - I also think that GitHub has the potential to take away some of the frictionâ¦. Iâve already managed to contribute a few documentation changes via pull request and it was so much easier. Tim > On 25 May 2017, at 12:26, Johan Brichau <johan(a)inceptive.be> wrote: > > This is why I want to move to github and use pull requests. > > Several changes work on Pharo6, but not 5. This is fine, but this also means we also need to adapt configs etc. > Soâ¦ I try to push next version of Seaside, which needs dev version of Greaseâ¦ > However, Grease dev does not work on Pharo6 â¦ and some changes need to be ported to all dialects first... > > â¦ and Iâm already half a day later again :( > > Do not understand me wrong: these contributions are great and itâs exactly what we need (which is why Iâm working on this today) !! > However, things get complicated when the end result is a version mess :( > > Anywayâ¦ making progress: https://travis-ci.org/SeasideSt/Grease/builds/235978258 <https://travis-ci.org/SeasideSt/Grease/builds/235978258> > > So, I should be out of the woods soon. > > Johan > >> On 25 May 2017, at 13:04, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >> >> >>> On 25 May 2017, at 11:43, Stephan Eggermont <stephan(a)stack.nl <mailto:stephan@stack.nl>> wrote: >>> >>> On 24/05/17 16:27, Sven Van Caekenberghe wrote: >>>> I updated the Seaside Control Panel for Pharo 6 / Seaside 3.2. As far as I can see, it works fine now. >>> >>> Did you find the original fix that is already in the repo? >> >> No, I did not. I am sorry. And I did not see those of Philippe either. What a mess ;-) >> >>> Stephan >>> >>> >>> _______________________________________________ >>> seaside-dev mailing list >>> seaside-dev(a)lists.squeakfoundation.org <mailto:seaside-dev@lists.squeakfoundation.org> >>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >> >> _______________________________________________ >> seaside-dev mailing list >> seaside-dev(a)lists.squeakfoundation.org <mailto:seaside-dev@lists.squeakfoundation.org> >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by Ben Coman

Nice idea. I've seen vague discussion about getting Pillar into the standard image for documentation. Perhaps it should be raised for consideration for Pharo 7? Actually you stimulate my thoughts that the Help file might be a better place for such snippets, so they are always with the image, and don't need to be retyped. Any objections? cheers -ben On Thu, May 25, 2017 at 4:00 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > Ben, > > I think there is a deeper need here. Writing good document is hard and > keeping it in sync with code is harder still. > > A book/booklet separates content from the code and being frozen in time > faces obsolescence. I would prefer to see a guidebook framework in Pharo > that every package author can use to create a simple narrative on its > features. Package authors and consumers have an incentive to keep the code > and content in sync. If an Object is a recursion on the notion of a > computer, why not provide, say a Note, as a recursive simplification of a > book? > > The framework could be on the lines of Plugins, Tests. E.g. > > Package-Core > Package-Plugins > Package-Tests > *Package-Guide* > > The guide framework should support active code (say to pop the source code > for a method), active links to guides on which this package depends, > automatic generation of table of contents, index of class references. Most > of features already exists in Pharo but spread all over. They need a home. > > A package could also extend this basic framework with features (e.g. PDF > package could export articles to PDF, Zinc could generate HTML). > > Regards .. Subbu > > > On Thursday 25 May 2017 07:03 AM, Ben Coman wrote: >> >> I've seen a few requests for short bits of code to use in playground for >> a demo presentation. I wonder if it would be good to have a booklet to >> gather these - seeded with Sven's excellent article... >> https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 >> >> It could include the recent meta-programming scripts like searching for >> all class instance variables starting with a capital letter. >> >> The book might be named "Snippets", in a format presentable to laser >> print on-site - something physical for attendees to take away with them >> to quick demo to others back in their office. >> >> I can take the lead in setting it up. Anyone remember any relevant >> posts in our archives? >> >> cheers -ben > > >

May 25, 2017

Re: [Pharo-dev] [Seaside-dev] Updated Seaside Control Panel for Pharo 6 / Seaside 3.2

by Johan Brichau

This is why I want to move to github and use pull requests. Several changes work on Pharo6, but not 5. This is fine, but this also means we also need to adapt configs etc. Soâ¦ I try to push next version of Seaside, which needs dev version of Greaseâ¦ However, Grease dev does not work on Pharo6 â¦ and some changes need to be ported to all dialects first... â¦ and Iâm already half a day later again :( Do not understand me wrong: these contributions are great and itâs exactly what we need (which is why Iâm working on this today) !! However, things get complicated when the end result is a version mess :( Anywayâ¦ making progress: https://travis-ci.org/SeasideSt/Grease/builds/235978258 <https://travis-ci.org/SeasideSt/Grease/builds/235978258> So, I should be out of the woods soon. Johan > On 25 May 2017, at 13:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 25 May 2017, at 11:43, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> On 24/05/17 16:27, Sven Van Caekenberghe wrote: >>> I updated the Seaside Control Panel for Pharo 6 / Seaside 3.2. As far as I can see, it works fine now. >> >> Did you find the original fix that is already in the repo? > > No, I did not. I am sorry. And I did not see those of Philippe either. What a mess ;-) > >> Stephan >> >> >> _______________________________________________ >> seaside-dev mailing list >> seaside-dev(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

May 25, 2017

Re: [Pharo-dev] [Seaside-dev] Updated Seaside Control Panel for Pharo 6 / Seaside 3.2

by Sven Van Caekenberghe

> On 25 May 2017, at 11:43, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 24/05/17 16:27, Sven Van Caekenberghe wrote: >> I updated the Seaside Control Panel for Pharo 6 / Seaside 3.2. As far as I can see, it works fine now. > > Did you find the original fix that is already in the repo? No, I did not. I am sorry. And I did not see those of Philippe either. What a mess ;-) > Stephan > > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

May 25, 2017

Re: [Pharo-dev] multiple crashes on macOS Sierra

by phil＠highoctane.be

For me the Bloc image on Ubuntu Linux 14.04 LTS never reopened back. All I get is a black screen. Damn. Phil On Thu, May 25, 2017 at 9:34 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi doru > > Yes I get the same. Now I was also in the bloc image, I got crash when > resizing the host window. > > Stef > > On Wed, May 24, 2017 at 10:28 PM, Tudor Girba <tudor(a)tudorgirba.com> > wrote: > >> Hi, >> >> Today I experienced multiple crashes on macOS Sierra. >> >> These happened during regular programming, mostly while typing code. I >> attached here the crash dump(s). I believe I heard Phil having the same >> issue with the stable Pharo VM. >> >> Does anyone else has the same issue? >> >> The VM is: >> CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 >> May 2 2017 >> StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: >> 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 >> VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ >> Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ >> >> The Pharo update number is: 60482 >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "From an abstract enough point of view, any two things are similar." >> >> >> >> >

May 25, 2017