October 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Thanks for Pharo

by Peter UhnÃ¡k

On Sat, Oct 17, 2015 at 3:35 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Le 17/10/2015 00:14, Jimmie Houchin a Ã©crit : > > Sometimes conversations revolve around perceived deficiencies in > > Pharo. What Pharo is missing. Or what Pharo doesn't do as well as my > > previous language, my favorite language, my other language, etc... > > These conversations are necessary to understand where Pharo is and to > > provide understanding on where Pharo needs some work. > > > > However, not enough gets said sometimes for all the goodness Pharo > > already provides and thanks to all of those who have contributed over > > the years to Smalltalk/Pharo. > > 100% agree. When people report about perceived deficiencies, it means > these people do care about Pharo. And yes, it is always rewarding (in > both direction as you mention it) to say goodness to the Pharo people. > So I join for an applause to Stef, Markus, Esteban, Eliot, Ben, Tudor, > Igor, Stephan, Damien, Torsten, Thierry, Alexandre, Sean, Phil, > Nicolai, and many more... > +Float fmax

Oct. 17, 2015

Re: [Pharo-users] Thanks for Pharo

by Hilaire

Le 17/10/2015 00:14, Jimmie Houchin a Ã©crit : > Sometimes conversations revolve around perceived deficiencies in > Pharo. What Pharo is missing. Or what Pharo doesn't do as well as my > previous language, my favorite language, my other language, etc... > These conversations are necessary to understand where Pharo is and to > provide understanding on where Pharo needs some work. > > However, not enough gets said sometimes for all the goodness Pharo > already provides and thanks to all of those who have contributed over > the years to Smalltalk/Pharo. 100% agree. When people report about perceived deficiencies, it means these people do care about Pharo. And yes, it is always rewarding (in both direction as you mention it) to say goodness to the Pharo people. So I join for an applause to Stef, Markus, Esteban, Eliot, Ben, Tudor, Igor, Stephan, Damien, Torsten, Thierry, Alexandre, Sean, Phil, Nicolai, and many more... Regarding Pharo distinctives, its live nature makes it perfect for learners. There is a global interest in educating kids to not only learn ICT but to understand it through programming. Scratch demonstrates it perfectly for primary education. Pharo itself is nice for secondary education, senior hight school I think. I experimented it a bit with the DrGeo environment, it went fine, but I really did not get enough opportunity and my student are two youngs to have interesting mathematics situation modeled with it. I hope to have some more motivation to experiment it more. Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

Oct. 17, 2015

Making a ring pie chart draggrable

by Offray Vladimir Luna CÃ¡rdenas

Hi all :), When I'm starting to prototype a visualization I like to make all elements draggable so I can test easily several layouts. This works well for simple elements, but I can't understand well how to make it work with complex ones like the|||RTPieBuilder. |Consider the code at http://ws.stfx.eu/1HC0HALHUKIC . There I create a ring pie chart and visualize it. I would like to make it draggable and add more elements to a the view. I have browsed the layout chapter by Peter on Agile visualization[1], but still I don't get it. I will made a detailed reading to catch what I'm missing and redo some proposed exercises, but any help is greatly appreciated. [1] https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Layout/0107… Cheers, Offray

Oct. 17, 2015

Re: [Pharo-users] CiteZen and Pharo 5 / Pharo4 tests

by Stephan Eggermont

On 17-10-15 12:02, Peter UhnÃ¡k wrote: > On Fri, Oct 16, 2015 at 6:50 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: >> Uhm, there is a green build on >> https://ci.inria.fr/pharo-contribution/job/Citezen/ > > Well that's nice, but if you install it via Catalog Browser, which should > be the correct way to install packages it is not working. (Maybe because > green is development and not stable). > Just promote #development to #stable and copy a configuration to the metarepo. It is a safe-to-fail experiment. Just do it. (and perhaps als add a #pharo5 spec & build) Stephan

Oct. 17, 2015

Re: [Pharo-users] CiteZen and Pharo 5 / Pharo4 tests

by Peter UhnÃ¡k

On Fri, Oct 16, 2015 at 6:50 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 16-10-15 13:17, Peter UhnÃ¡k wrote: > >> Hi, >> >> I wanted to use CiteZen, but there's no Pharo 5 version (wouldn't even >> load), >> >> so I tried Pharo 4 instead but the tests are not passing: >> all CZBibTest fail on MessageNotUnderstood: >> Metaclass>>allMethodsInCategory: >> >> is this known problem? Do I need to use a very specific build of Pharo 4? >> > > Uhm, there is a green build on > https://ci.inria.fr/pharo-contribution/job/Citezen/ Well that's nice, but if you install it via Catalog Browser, which should be the correct way to install packages it is not working. (Maybe because green is development and not stable).

Oct. 17, 2015

Thanks for Pharo

by Jimmie Houchin

Sometimes conversations revolve around perceived deficiencies in Pharo. What Pharo is missing. Or what Pharo doesn't do as well as my previous language, my favorite language, my other language, etc... These conversations are necessary to understand where Pharo is and to provide understanding on where Pharo needs some work. However, not enough gets said sometimes for all the goodness Pharo already provides and thanks to all of those who have contributed over the years to Smalltalk/Pharo. I know sometimes we get stuck in the minutiae and lose the big picture. I just want to say thanks to all that have contributed to Pharo in big and small way. Thank you. A special thanks to Stef, Marcus and company who have been working hard on this all the way back when it was still Squeak. Who had a vision for a clean, empowering, business ready, vision fulfilling Smalltalk inspired tool we call Pharo. Thanks. And a thanks to Eliot and all who contribute on the VM side of things. Enabling us to have a nicely performing and stable vm to run the Pharo image. My apologies for not naming everyone who deserves thanks. I intend no offense to anyone not named, but also deserving. Your names are included in all the contributor documentation. Thanks. And while I am being thankful, which is a good habit for all of us to be in. Being thankful not only improves the spirits of those being thanked. But those of us who are grateful are the biggest beneficiaries. I want to take time to appreciate some things in Pharo that make us appreciate having a tool like Pharo and which distinguishes itself from other languages and environments. I think these things either distinguish themselves either in the relative uniqueness or in quality of their implementation. They are not necessarily distinguishing from other Smalltalks but from other non-Smalltalk languages. Superior persistent live object environment. This is the game changer and affects and enables all other benefits. """I'm not complaining. I know that there is a good chance that we break the system when improving it. I have no problem with that and I prefer a living system with some bugs for a while than a dead system with no bug""" Stef - Sept. 7, 2015 IDE, debugging and refactoring, all live, all the time. Because of the truly persistent live environment, there is no concept of shutdown, restart. We only know hibernate and resume. This is to use OS terms. For me this is an amazing boost to productivity. I can at any time save my image. Even close my saved image and resume exactly where I stopped. At any time, on any supported OS, on any machine. Powerful. There truly is no edit, compile, run cycle similar to other languages, even dynamically typed languages with REPLs. If I am not in Pharo, even if that language has an amazing notebook or repl available. It is nothing like coding in the live environment. The separation of editor and the compiler and/or application or VM makes development not as smooth and fluid. Even if I can enter and execute code in a notebook or repl to explore and learn in a version of a live environment. I still at some point have to leave my editing environment and write, edit and save my source code. And yes there are languages, editors, IDEs and tools that attempt to close the gap. But no, there still is a significant gap. The edited source code is the only thing that persists. Everything that gets executed in the repl or notebook is transient and will go away. MIT, equivalent or better licensed ecosystem. For me these are game changers. They set a standard by which I view any other programming experience. Thusly all other programming experience falls far short. Whenever I (we) experience a present weakness in Pharo. Remember the above. Not only does Pharo have these distinguishing factors. I do not know of any language or environment which even has a culture or worldview of programming which seeks to bring these features to their favored language or tools. Every time I have to restart my computer I think, Smalltalk solved this decades ago. Ugh!!! Where is my Pharo machine. :) If you have any Pharo distinctives that you appreciate and would like to share. Reply and let us know. What I mean by distinctive is something that Pharo (or Smalltalk) has that is either not in other languages or is in general significantly inferior. Especially those that other languages have no vision to ever have. It just isn't a part of who they are. If we keep these things before us as we work through the tedious work of cleaning the image, repairing fail attempts at various things. Or anything that may be a frustration for the moment, but is temporary. Remember what we gain and are blessed with having, that we would lose any where else. Or at a minimum have a far inferior substitute. And look forward to what we will have as these things become complete. The future is ours. Let's enjoy the journey. Just some thoughts in my head I wanted to let out. This is reminder to me. If any of you are blessed and inspired, that is a plus. Thanks and Shalom. Jimmie

Oct. 16, 2015

VanIsle CampSmalltalk Autumn Edition, 6th - 8th November 2015

by Sebastian Heidbrink

Hi Smalltalk enthusiasts! the Vancouver Island Smalltalkers have decided to have a small CampSmalltalk again. Last Spring Edition Camp in Nanaimo was a nice familiarand constructive meeting. If youâre in the general pacific north-west region do consider coming along. When: Friday & Saturday November 6-8th Location: Makerspace Nanaimo 2221 McGarrigle Rd Nanaimo, BC Canada their website: makerspacenanaimo.org !!!!!!!!!!!! PLEASE SIGNUP @ https://www.picatic.com/event14133068326629 !!!!!!!!!!!!!!!!! Schedule/Presentations: We have the Space all weekend long and we would like to dicuss our options and ideas for a BIG CampSmalltalk in Spring 2016 in Nanaimo. If you are interested in ... VisualWorks APPEX and Sioux frameworks (Jerry Kott will be around) ... any kind of ScratchOnPI projects, eg. PiTouch, AstroPi, ... (Tim Rowledge) ... combining your Smalltalk project with any other peripheral device ... would like to try a different Smalltalk out ... just want to chat and meet old and new friends ....then this should be the perfect weekend to do this and come over to Makerspace in Nanaimo. Please contact us directly if you have questions regarding travel or accomodationa. We got some valuable feedback from last CampSmalltalks' participants. Please let us also know if youâre interested. Tim and Sebastian

Oct. 16, 2015

Re: [Pharo-users] Updated Pharo By Example

by Dimitris Chloupis

I agree and its a good thinking you created this issue. There is no commitment, no obligation, no strings attaches. We all do what we want to do. Just because you report an issue does not mean you have to solve the issue. Reporting an issue is already very helpful and pharo really needs reporting of issues whether is with the documentation or pharo itself. This is why I never asked for more people to contribute rather I asked for existing resources that I have not noticed . On Fri, Oct 16, 2015 at 8:55 PM Lyn Headley <laheadle(a)gmail.com> wrote: > [I have submitted the following issue but am posting here for the sake of > discussion] > > Pharo is used by software developers, and software developers depend on > packages. Therefore I believe that one of the first things a new Pharo user > will want to do is install packages written by others. But Pharo By Example > contains no mention of the ConfigurationOfXYZ method of installing packages > (and does not mention the configuration browser -- an awesome tool for new > users to get excited about what is out there). You could introduce these > topics without getting too deep into Metacello, but... > > I also think Metacello should be introduced fairly early. Any application > will almost certainly have dependencies and it is important to be able to > load your application into a fresh image. Metacello is essential for this, > so it is essential for Pharo. > > Chapter 8 could probably be expanded to include these topics, which are > more fundamental than Morphic or Seaside. Note that the Seaside chapter > recommends installing an old one-click image! This is a great chance to use > Configurations. > > What do you think of this idea? And yes, I realize I can contribute this > myself, but I currently decline the commitment. > > Lyn > > On Thu, Oct 15, 2015 at 5:42 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > >> First of all thanks to all the people helping with the documentation. >> >> Now I think its the time to replace the old PBE with UPBE , we dont need >> to change the website just link to the newest pdf here >> >> >> https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample… >> >> Because UPBE at this moment is light years ahead of PBE. I just added doc >> for Spotter, Dark Theme, and the new Nautilus icons. >> >> If any of you wants to fix something on UPBE and does not have the >> confidence to do it directly , because you dont understand Pillar or you >> dont feel confident yet with Pharo you can still help me tremendously by >> adding your comment , your corrected text or your addition documentation as >> github issue here and I will put it in the book ASAP. >> >> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues >> >> I will be resolving at least one issue per week from now on to make sure >> that UPBE is being pushed forward and remains by far the most up to date >> documentation of Pharo anywhere in this universe. But I cannot guarantee >> for other universes. >> >> So please help , even a tiny bit of help is great because we can all make >> Pharo far easier for newcomers with much better documentation and expand >> UPBE to every direction. >> >> All hail Pharo ! >> > >

Oct. 16, 2015

Re: [Pharo-users] Updated Pharo By Example

by Lyn Headley

[I have submitted the following issue but am posting here for the sake of discussion] Pharo is used by software developers, and software developers depend on packages. Therefore I believe that one of the first things a new Pharo user will want to do is install packages written by others. But Pharo By Example contains no mention of the ConfigurationOfXYZ method of installing packages (and does not mention the configuration browser -- an awesome tool for new users to get excited about what is out there). You could introduce these topics without getting too deep into Metacello, but... I also think Metacello should be introduced fairly early. Any application will almost certainly have dependencies and it is important to be able to load your application into a fresh image. Metacello is essential for this, so it is essential for Pharo. Chapter 8 could probably be expanded to include these topics, which are more fundamental than Morphic or Seaside. Note that the Seaside chapter recommends installing an old one-click image! This is a great chance to use Configurations. What do you think of this idea? And yes, I realize I can contribute this myself, but I currently decline the commitment. Lyn On Thu, Oct 15, 2015 at 5:42 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > First of all thanks to all the people helping with the documentation. > > Now I think its the time to replace the old PBE with UPBE , we dont need > to change the website just link to the newest pdf here > > > https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample… > > Because UPBE at this moment is light years ahead of PBE. I just added doc > for Spotter, Dark Theme, and the new Nautilus icons. > > If any of you wants to fix something on UPBE and does not have the > confidence to do it directly , because you dont understand Pillar or you > dont feel confident yet with Pharo you can still help me tremendously by > adding your comment , your corrected text or your addition documentation as > github issue here and I will put it in the book ASAP. > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues > > I will be resolving at least one issue per week from now on to make sure > that UPBE is being pushed forward and remains by far the most up to date > documentation of Pharo anywhere in this universe. But I cannot guarantee > for other universes. > > So please help , even a tiny bit of help is great because we can all make > Pharo far easier for newcomers with much better documentation and expand > UPBE to every direction. > > All hail Pharo ! >

Oct. 16, 2015

Re: [Pharo-users] CiteZen and Pharo 5 / Pharo4 tests

by Stephan Eggermont

On 16-10-15 13:17, Peter UhnÃ¡k wrote: > Hi, > > I wanted to use CiteZen, but there's no Pharo 5 version (wouldn't even > load), > > so I tried Pharo 4 instead but the tests are not passing: > all CZBibTest fail on MessageNotUnderstood: Metaclass>>allMethodsInCategory: > > is this known problem? Do I need to use a very specific build of Pharo 4? Uhm, there is a green build on https://ci.inria.fr/pharo-contribution/job/Citezen/ Stephan

Oct. 16, 2015