April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] VM Building on Fedora: SDL2 failure

by Sean P. DeNigris

Nicolai Hess wrote > Mixing 64 bit / 32 bit environments/toolchain? Yes, where I went wrong is too embarrassing to mention ha ha, so I'll move on to the next errors... <http://forum.world.st/file/n4820011/Screenshot_2015-04-16_12.png> p.s. sorry about the screenshots but it's a server running in VirtualBox so I can't copy/paste ----- Cheers, Sean -- View this message in context: http://forum.world.st/VM-Building-on-Fedora-SDL2-failure-tp4819999p4820011.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015

Re: [Pharo-dev] [Pharo-users] [Esug-list] [ANN] Pharo 4.0 is released!

by Richard Wettel

Great! And thank you all! Ricky â Sent from Mailbox On Thu, Apr 16, 2015 at 5:24 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Thank you all ! > On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> Please spread widely. >> Sorry for multiple posts. >> >> (this post can be see here: http://pharo.org/news/pharo-4.0-released) >> >> Dear World, >> >> Pharo 4.0 (http://www.pharo.org) is here. >> >> Pharo is a pure object-oriented programming language and a powerful >> environment, focused on simplicity and immediate feedback. >> >> Many things have changed in Pharo. Here are some highlights: >> - Inspector/Playground/Spotter are new moldable development tools for >> inspecting, coding and searching objects. >> - Slots model instance variables as first class entities and enable >> meta-programming on this level. >> - ShoreLine reporter introduces a way to report system errors and collect >> statistics, that we will use for future improvements >> - Dark theme. >> >> These are just the more prominent highlights, but the details are just as >> important. We have closed 1697 issues in Pharo 4. Take a moment to go >> through a more detailed recount of the progress: >> >> >> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md >> >> Pharo is improving on many fronts, but one of the most prominent changes >> is the addition of moldable tools for inspection and search. These tools >> provide extension mechanisms that allow every object to define ways in >> which it can be understood effectively. To provide an idea of the impact of >> the already existing extensions, the map below shows the Pharo classes >> grouped in packages, highlighting in red those parts of the system that >> have at least one such custom view coming with the main distribution. The >> spread of these extensions shows that moldability is powerful mechanism >> that can be used in many contexts. >> >> >> Remember that Pharo is your platform. We thank all the contributors of >> this release: >> >> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, >> Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury >> Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, >> Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei >> Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, >> Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane >> Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, >> Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, >> Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, >> Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max >> Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila >> Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot >> Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, >> Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, >> Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian >> Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, >> Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin >> >> And all those who contributed indirectly, by reporting bugs, participating >> in discussion threads, providing feedback... >> >> Pharo 4.0 is another big step. And, the best is yet to come. >> >> Enjoy! >> The Pharo Team >> >> >> _______________________________________________ >> Esug-list mailing list >> Esug-list(a)lists.esug.org >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >> >> > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/

April 16, 2015

VM Building on Fedora: SDL2 failure

by Sean P. DeNigris

I installed all the packages listed at https://github.com/philippeback/pharovm-centos65/blob/master/packages-to-in…, plus SDL2 and SDL2-devel, and got the following error: <http://forum.world.st/file/n4819999/Screenshot_2015-04-16_12.png> Any ideas? Thanks in advance! ----- Cheers, Sean -- View this message in context: http://forum.world.st/VM-Building-on-Fedora-SDL2-failure-tp4819999.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015

Re: [Pharo-dev] [Esug-list] [ANN] Pharo 4.0 is released!

by Serge Stinckwich

Thank you all ! On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Please spread widely. > Sorry for multiple posts. > > (this post can be see here: http://pharo.org/news/pharo-4.0-released) > > Dear World, > > Pharo 4.0 (http://www.pharo.org) is here. > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > Many things have changed in Pharo. Here are some highlights: > - Inspector/Playground/Spotter are new moldable development tools for > inspecting, coding and searching objects. > - Slots model instance variables as first class entities and enable > meta-programming on this level. > - ShoreLine reporter introduces a way to report system errors and collect > statistics, that we will use for future improvements > - Dark theme. > > These are just the more prominent highlights, but the details are just as > important. We have closed 1697 issues in Pharo 4. Take a moment to go > through a more detailed recount of the progress: > > > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md > > Pharo is improving on many fronts, but one of the most prominent changes > is the addition of moldable tools for inspection and search. These tools > provide extension mechanisms that allow every object to define ways in > which it can be understood effectively. To provide an idea of the impact of > the already existing extensions, the map below shows the Pharo classes > grouped in packages, highlighting in red those parts of the system that > have at least one such custom view coming with the main distribution. The > spread of these extensions shows that moldability is powerful mechanism > that can be used in many contexts. > > > Remember that Pharo is your platform. We thank all the contributors of > this release: > > Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, > Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury > Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, > Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei > Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, > Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane > Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, > Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, > Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, > Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max > Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila > Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot > Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, > Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, > Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian > Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, > Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin > > And all those who contributed indirectly, by reporting bugs, participating > in discussion threads, providing feedback... > > Pharo 4.0 is another big step. And, the best is yet to come. > > Enjoy! > The Pharo Team > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 16, 2015

Re: [Pharo-dev] HELP WANTED - Frameworks, tools, etc. ready to use

by Nicolai Hess

2015-04-16 17:06 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 16 Apr 2015, at 16:44, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-04-16 15:48 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> Hi, >> >> I want to add a âresourcesâ page in pharo.org. >> The reason is simple: we are used to know (more or less) what we have, >> but people doing a search of what is pharo, etc. does not know what they >> can have *just downloading it*. >> I made a mall list. >> I need you to help me to complete it. >> >> Keep in mind this is high level stuff (not details), frameworks and tools >> that can be used out of the box for people downloading Pharo. >> >> thanks! >> Esteban >> >> >> > Suggestions: > > - I would move "Refactoring Tools" to frameworks, or do we have a > Refactoring Tool besides Code Critics and Nautilus refactoring support? > - Glamour is more a framework than a GUI library > > > ok, this two. > > - I would remove OSWindow it does not work "out of the boxâ. > > > not quite. With SDL2 is very usableâ¦ it is rough, thatâs trueâ¦ but it > works :) > :) > (and stable vm come with sdl2 for all platforms, too) > > - there is a "Graphics" entry in category "Graphics", some hints what you > would like to see for this entry? > > > yeahâ¦ name not good. This is the old graphics library (the one we actually > use to display the world), I donât know how to call itâ¦ BitBlt graphics, > perhaps? > "Canvas" or "Bitmap graphics" > > Esteban > >

April 16, 2015

Re: [Pharo-dev] HELP WANTED - Frameworks, tools, etc. ready to use

by Esteban Lorenzano

and as is obviously not as clear as it should, let me rephrase what Iâm asking for: packages that are in the image and not in my list *and are interesting for end users* :) cheers, Esteban > On 16 Apr 2015, at 15:48, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > I want to add a âresourcesâ page in pharo.org <http://pharo.org/>. > The reason is simple: we are used to know (more or less) what we have, but people doing a search of what is pharo, etc. does not know what they can have *just downloading it*. > I made a mall list. > I need you to help me to complete it. > > Keep in mind this is high level stuff (not details), frameworks and tools that can be used out of the box for people downloading Pharo. > > thanks! > Esteban > > > Full library including: Collections, Caches, Networking, I/O, Threads (Green), Sockets... > > > Development Tools > ================= > - GTInspector > - GTPlayground > - GTSpotter > - Nautilus > - Debugger > - TestRunner > - Versionner > - Code Critics > - Refactoring Tools > - Profilers > > Development > =========== > > Frameworks > ---------- > - Announcements > - Regex > - Keymapping > - Multilingual (Latin, UTF8, Korean, Russian, Simplified Chinese, japanese, Greek, ...) > - Command Line > > Testing > ------- > - SUnit > > GUI > --- > - OSWindow > - Glamour > - Spec > - Morphic (With full widget set and Rubric, TxText) > > Graphics > -------- > - Athens > - Balloon > - Graphics > - Fonts (FreeType) > > FFI > --- > - NativeBoost > > Networking > ---------- > - Zinc/Zodiac > > I/O > --- > - FileSystem > - Compression (Zip, GZip) > > Serializer > ---------- > - Fuel > > Crypt > ----- > - CRC, DSA, MD5, SHA1, SHA256, Adler32 > > JIT > --- > - AsmJit > > SCM > --- > - Gofer > - Monticello > - Metacello > > Tutorial > ======== > - ProfStef >

April 16, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Damien Cassou

Sean P. DeNigris <sean(a)clipperadams.com> writes: > Thanks for the clarification! Where are the Nix and Gentoo infrastructure > hosted? I think we should collect all of these things under github/pharo for Nix, this is in the nixpkgs repository: https://github.com/NixOS/nixpkgs/tree/master/pkgs/development/pharo for Gentoo, it seems that several people contributed several recipes. I put JC on CC so he can tell more. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] HELP WANTED - Frameworks, tools, etc. ready to use

by Esteban Lorenzano

> On 16 Apr 2015, at 16:44, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-04-16 15:48 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > Hi, > > I want to add a âresourcesâ page in pharo.org <http://pharo.org/>. > The reason is simple: we are used to know (more or less) what we have, but people doing a search of what is pharo, etc. does not know what they can have *just downloading it*. > I made a mall list. > I need you to help me to complete it. > > Keep in mind this is high level stuff (not details), frameworks and tools that can be used out of the box for people downloading Pharo. > > thanks! > Esteban > > > > Suggestions: > > - I would move "Refactoring Tools" to frameworks, or do we have a Refactoring Tool besides Code Critics and Nautilus refactoring support? > - Glamour is more a framework than a GUI library ok, this two. > - I would remove OSWindow it does not work "out of the boxâ. not quite. With SDL2 is very usableâ¦ it is rough, thatâs trueâ¦ but it works :) (and stable vm come with sdl2 for all platforms, too) > - there is a "Graphics" entry in category "Graphics", some hints what you would like to see for this entry? yeahâ¦ name not good. This is the old graphics library (the one we actually use to display the world), I donât know how to call itâ¦ BitBlt graphics, perhaps? Esteban

April 16, 2015

Re: [Pharo-dev] HELP WANTED - Frameworks, tools, etc. ready to use

by Esteban Lorenzano

Hernan, > On 16 Apr 2015, at 16:48, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Ok about descriptions, but Pharo compatibility versions should be provided for each package, if not you would end with hundreds of packages not loadable in Pharo 4....and people then have to guess which is the right Pharo version for a package. as my mail says, this are the frameworks already in the image, not a list of cool stuff people can download, but the things are already there. So in case of version, all versions are the same: 4.0 For downloaded packages there is already: http://catalog.pharo.org <http://catalog.pharo.org/> (which will be enhanced in the future, but is already there). cheers, Esteban > > Your list is more or less the "core" packages already loaded by default in Pharo images. > > HernÃ¡n > > 2015-04-16 11:38 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> On 16 Apr 2015, at 16:32, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: >> >> You didn't specified which Pharo version. >> >> And you didn't provided even a minimal description... for an outsider Monticello and Metacello sounds almost the same, same with GTPlayground and GTSpotter, etc. > > this is for *you* to help me, not the final web page. > >> >> Cheers, >> >> HernÃ¡n >> >> >> >> >> 2015-04-16 10:48 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> Hi, >> >> I want to add a âresourcesâ page in pharo.org <http://pharo.org/>. >> The reason is simple: we are used to know (more or less) what we have, but people doing a search of what is pharo, etc. does not know what they can have *just downloading it*. >> I made a mall list. >> I need you to help me to complete it. >> >> Keep in mind this is high level stuff (not details), frameworks and tools that can be used out of the box for people downloading Pharo. >> >> thanks! >> Esteban >> >> >> Full library including: Collections, Caches, Networking, I/O, Threads (Green), Sockets... >> >> >> Development Tools >> ================= >> - GTInspector >> - GTPlayground >> - GTSpotter >> - Nautilus >> - Debugger >> - TestRunner >> - Versionner >> - Code Critics >> - Refactoring Tools >> - Profilers >> >> Development >> =========== >> >> Frameworks >> ---------- >> - Announcements >> - Regex >> - Keymapping >> - Multilingual (Latin, UTF8, Korean, Russian, Simplified Chinese, japanese, Greek, ...) >> - Command Line >> >> Testing >> ------- >> - SUnit >> >> GUI >> --- >> - OSWindow >> - Glamour >> - Spec >> - Morphic (With full widget set and Rubric, TxText) >> >> Graphics >> -------- >> - Athens >> - Balloon >> - Graphics >> - Fonts (FreeType) >> >> FFI >> --- >> - NativeBoost >> >> Networking >> ---------- >> - Zinc/Zodiac >> >> I/O >> --- >> - FileSystem >> - Compression (Zip, GZip) >> >> Serializer >> ---------- >> - Fuel >> >> Crypt >> ----- >> - CRC, DSA, MD5, SHA1, SHA256, Adler32 >> >> JIT >> --- >> - AsmJit >> >> SCM >> --- >> - Gofer >> - Monticello >> - Metacello >> >> Tutorial >> ======== >> - ProfStef >> >> > >

April 16, 2015

Re: [Pharo-dev] Pillar: Link to anchor in same document

by Damien Cassou

Hi Sean, Sean P. DeNigris <sean(a)clipperadams.com> writes: > I'm updating the Pharo website and want to link to an anchor on the same > page. > > And after reading > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > , I tried: > *Ubuntu ppa instructions>ubuntu* > but it linked to http://pharo.org/ubuntu instead of > http://pharo.org/gnu-linux-installation.STAGE#ubuntu > > Then I tried: > *Ubuntu ppa instructions>@ubuntu* -> linked back to the same page, but no > anchor was appended > *Ubuntu ppa instructions>#ubuntu* -> worked, but rendered the link text as > "Â¿?Ubuntu ppa instructions" > > How should I handle this? For the time being I'll leave the last version > which works at least... there is a bug in Pillar. We've just spent 1h on it with Cyril and our conclusion is that the current numbering feature of Pillar is too complex to be maintained. We will rewrite it. In the meantime, you just can't use anchors. I'm sorry. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015