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

WTF and Programming Languages

by kilon alios

I dont know if you guys are aware of this talk, very funny , quite weird , so I thought why not share it with you https://www.destroyallsoftware.com/talks/wat

May 7, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

indeed it does not. Tried it no mention of pdflatex. however I am getting loads of warnings , even before your commit I assume you guys are aware of this, but just in case "./compile.sh Generating files for all chapters The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete Done kilon-imac:UpdatedPharoByExample kilon$ ./compile.sh Generating files for all chapters The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete Done kilon-imac:UpdatedPharoByExample kilon$ " On Wed, May 7, 2014 at 10:50 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Ok, so for now updated PBE should not complain about absence of pdflatex > > Uko > > On 07 May 2014, at 21:10, kilon alios <kilon.alios(a)gmail.com> wrote: > > Yes I think reducing screenshots makes sense, especially the ones that do > not directly explain the tools. Reducing them will make it easier to update > PBE in the future. I am also very interested in automating the screenshot > process as has been suggested in another thread, if we able to do this that > will reduce the time to update PBE in future massively. > > I will try to simplify PBE so its much easier to update without > sacrificing quality for the viewer. Obviously screenshots are essential. > > I am also viewing your TODO you have linked on the Readme. > > I have updated the Readme so that links to Damien's Documentation of > Pillar and also to Pharo for the Enterprise , obviously anyone who wants to > contribute must be aware of both of these things. > > I also added Chapter 1 - Quick Tour in Pharo. Just the first part , the > chapter is of course still a WIP. > > I am not so sure what you mean about automated tests, are they for the > example code ? > > I am all for automation. > > > On Mon, May 5, 2014 at 11:08 PM, stepharo <stepharo(a)free.fr> wrote: > >> This is really cool that people want to update the Pharo by Example book. >> This is a really an important task and it will have a real impact. >> You can also reduce the number of screenshots or point related to the >> interaction. >> >> What would be good is to make the automated tests working again because >> we could spot >> if we got some regressions. >> >> Stef >> >> >> How I can help improve Pharo by Example , add chapters and update >>> current ones for Pharo 3 ? >>> >>> What is the process ? >>> >> >> >> > >

May 7, 2014

Re: [Pharo-dev] Improving Pharo By Example

by Yuriy Tymchuk

Ok, so for now updated PBE should not complain about absence of pdflatex Uko On 07 May 2014, at 21:10, kilon alios <kilon.alios(a)gmail.com> wrote: > Yes I think reducing screenshots makes sense, especially the ones that do not directly explain the tools. Reducing them will make it easier to update PBE in the future. I am also very interested in automating the screenshot process as has been suggested in another thread, if we able to do this that will reduce the time to update PBE in future massively. > > I will try to simplify PBE so its much easier to update without sacrificing quality for the viewer. Obviously screenshots are essential. > > I am also viewing your TODO you have linked on the Readme. > > I have updated the Readme so that links to Damien's Documentation of Pillar and also to Pharo for the Enterprise , obviously anyone who wants to contribute must be aware of both of these things. > > I also added Chapter 1 - Quick Tour in Pharo. Just the first part , the chapter is of course still a WIP. > > I am not so sure what you mean about automated tests, are they for the example code ? > > I am all for automation. > > > On Mon, May 5, 2014 at 11:08 PM, stepharo <stepharo(a)free.fr> wrote: > This is really cool that people want to update the Pharo by Example book. > This is a really an important task and it will have a real impact. > You can also reduce the number of screenshots or point related to the interaction. > > What would be good is to make the automated tests working again because we could spot > if we got some regressions. > > Stef > > > How I can help improve Pharo by Example , add chapters and update current ones for Pharo 3 ? > > What is the process ? > > >

May 7, 2014

Re: [Pharo-dev] Making screenshots programmatically for book

by kilon alios

If you happen to come up with code for this , because I am updating the Pharo By Example book for Pharo 3 as you can imagine I would be super interested into looking at such code. Would make my life easier :) On Wed, May 7, 2014 at 6:23 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Damien wrote: > >FYI, it is possible to include Smalltalk code in Pillar files that will > be executed when the Pillar file is compiled. This Smalltalk >code can > write to a stream in order to generate dynamic content. I use it to > generate a part of Pillar documentation > > Ha, that sounds like exactly what I need. Thank you. > > Stephan >

May 7, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

Yes I think reducing screenshots makes sense, especially the ones that do not directly explain the tools. Reducing them will make it easier to update PBE in the future. I am also very interested in automating the screenshot process as has been suggested in another thread, if we able to do this that will reduce the time to update PBE in future massively. I will try to simplify PBE so its much easier to update without sacrificing quality for the viewer. Obviously screenshots are essential. I am also viewing your TODO you have linked on the Readme. I have updated the Readme so that links to Damien's Documentation of Pillar and also to Pharo for the Enterprise , obviously anyone who wants to contribute must be aware of both of these things. I also added Chapter 1 - Quick Tour in Pharo. Just the first part , the chapter is of course still a WIP. I am not so sure what you mean about automated tests, are they for the example code ? I am all for automation. On Mon, May 5, 2014 at 11:08 PM, stepharo <stepharo(a)free.fr> wrote: > This is really cool that people want to update the Pharo by Example book. > This is a really an important task and it will have a real impact. > You can also reduce the number of screenshots or point related to the > interaction. > > What would be good is to make the automated tests working again because we > could spot > if we got some regressions. > > Stef > > > How I can help improve Pharo by Example , add chapters and update current >> ones for Pharo 3 ? >> >> What is the process ? >> > > >

May 7, 2014

Re: [Pharo-dev] System-Hashing and SecureHashAlgorithm ?

by stepharo

> Where to put it? PharoExtras? Elsewhere? > I think that this is important to PharoExtras is a nice place and after we can set up a ci job for it. Stef > Le 7 mai 2014 20:09, "stepharo" <stepharo(a)free.fr > <mailto:stepharo@free.fr>> a Ã©crit : > > Phil > > once you find a solution please update the MySql > > Stef > > On 7/5/14 16:06, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: > > Where is that package gone ? > > It is a dependency of StdMySql. > > TIA > Phil > > >

May 7, 2014

Re: [Pharo-dev] System-Hashing and SecureHashAlgorithm ?

by phil＠highoctane.be

Where to put it? PharoExtras? Elsewhere? Le 7 mai 2014 20:09, "stepharo" <stepharo(a)free.fr> a Ã©crit : > Phil > > once you find a solution please update the MySql > > Stef > > On 7/5/14 16:06, phil(a)highoctane.be wrote: > >> Where is that package gone ? >> >> It is a dependency of StdMySql. >> >> TIA >> Phil >> > > >

May 7, 2014

Re: [Pharo-dev] System-Hashing and SecureHashAlgorithm ?

by stepharo

Phil once you find a solution please update the MySql Stef On 7/5/14 16:06, phil(a)highoctane.be wrote: > Where is that package gone ? > > It is a dependency of StdMySql. > > TIA > Phil

May 7, 2014

Re: [Pharo-dev] Default Pharo 3.0 image downloads

by Esteban Lorenzano

and http://files.pharo.org/image/stable/ is a symlink that has to point to 3.0 now :P On 07 May 2014, at 18:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > http://files.pharo.org/image/30/ > > On 07 May 2014, at 18:46, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> Sean P. DeNigris wrote >>> I'm not sure what pharo.org's links point to >> >> Same as pharo-project.org >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Default-Pharo-3-0-image-downloads-tp4758225p4758229.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >

May 7, 2014

Re: [Pharo-dev] Default Pharo 3.0 image downloads

by Esteban Lorenzano

wellâ¦ that was changed to work like that some time ago. the idea was that when we do bugfixes, we want them to be in your hands as fast as possible. So we link the downloadable version to the latest build. no idea how cool is that, but that was the decision at the moment (it was like that with pharo 2.0 too, and nobody complained :P) Esteban On 07 May 2014, at 18:44, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > The Mac installer and custom image downloads on the 3.0 Release page at > pharo-project.org point to the latest 3.0 i.e. #30847 which is one update > ahead of the released version. Is that what we want? Or do we want to fix > the default release to #30846 until we release 3.0 Summer? I'm not sure what > pharo.org's links point to because I'm having trouble accessing the site > right now (page loads/hangs when resolving intermittently) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Default-Pharo-3-0-image-downloads-tp4758225.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 7, 2014