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

Fwd: FOSDEM 2016 devroom selection
by stephan Oct. 23, 2015

Oct. 23, 2015

-------- Forwarded Message -------- Subject: FOSDEM 2016 devroom selection Date: Thu, 22 Oct 2015 13:18:25 +0200 From: Johan van Selst <johans(a)fosdem.org> To: devrooms(a)fosdem.org Hi, I'm sorry to inform you that we declined your devroom proposal. To clarify, your request was perfectly valid, but we had to choose. Unfortunately we do not have a sufficient number of rooms at our disposal to cover all requests. This year, we had over 60 requests for a devroom and were only able to accept 37 of those. However, some requests have been combined into a single devroom. Nevertheless, there are other ways to participate in FOSDEM too. You can still: - have a stand at FOSDEM, - hold a 15 minute 'lightning talk' in one of the biggest rooms, - speak in one of the other devrooms (CfP to follow), - hold a session in the community meeting room (new; CfP to follow). The full list of accepted devrooms will be published on the FOSDEM website later this week. On behalf of the FOSDEM devroom team, Johan van Selst

4 3

Feedback on #assert: vs. #assert:equals:
by Nahuel Garbezza Oct. 23, 2015

Oct. 23, 2015

Hi everyone, I'm using Pharo for teaching and we use TDD since the beginning. I've noticed that if you use #assert: on a test, like this: self assert: object messageReturningBoolean It gives you strange results in terms of feedback if the result is not a boolean. I would expect an AssertionFailed (yellow test) but I got a NonBooleanReceiver (red test). What we do in our course is to write the assertion like this: self assert: object messageReturningBoolean equals: true So we got a "expected true but was <other object>" error which is a lot more helpful to the students. I was thinking that is better to have #assert: implementation based on #assert:equals:. It is like saying #assert:equals: is the "primitive" assertion message, which makes sense to me since you are always comparing if an object is equal to another, there's no reason to handle the booleans' case differently. What do you think? Thank you! Nahuel

4 4

Artefact and WideString
by Hilaire Oct. 22, 2015

Oct. 22, 2015

Hello, Is it me, or is there a problem with WideString and Artefact? The following produces an empty page: page add: ((PDFFormattedTextElement from: 10mm @ 20mm to: 277mm @ 30mm) alignment: PDFAlignment left; text: 'Argent de poche : 1â¬'). The text is WideString. Removing the â¬, it went ok. Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

6 10

[ANN] The next Pharo Sprints at Lille
by Marcus Denker Oct. 22, 2015

Oct. 22, 2015

Hello, We looked at the calendar and fixed the dates for all public sprints that we will do this year here locally. These are all Fridays: Sept 11 Oct 23 Nov 27 Dec 18 Here is the invitation for this Friday: âââââââââââââââââââââââ We will organize a Pharo sprint / Moose dojo Friday, 11th September, starting at 10:00am. (Local Time Lille). It will be at the Inria Lille, Building B, third floor (RMoD offices). Remotely, you can join us on the official IRC channel #pharo on irc.freenode.net server. During the sprint, we will try to synchronize local and remote Pharo sprinters. As the building is not open to the public, please contact us before if you plan to come.

4 3

Codepage 437
by Norbert Hartl Oct. 22, 2015

Oct. 22, 2015

Is there any way to read a codepage 437 encoded file with pharo? thanks, Norbert

3 4

crashed image ?
by Jean Baptiste Arnaud Oct. 21, 2015

Oct. 21, 2015

Hi, maybe a useful question :-) I crashed a image :-) And I ask myself: - There are a more advance (thinking bout maybe epicea) change browser ? Because a list of 1293801283 changes and just 1 options select all (which is broken you should use shortcut) will not really helpme - Oz is usable on 5.0 image ? That can be the more efficient solution. Just want to stop some process. I exactly know what trigger the crash. And the "Igor hex tricksâ will not work here. Export my code. - why cannot drag a .change on another image anymore ? bug or choice ? Best Regards JB jbaptiste.arnaud(a)gmail.com

5 13

How to place the main window on the screen?
by stepharo Oct. 20, 2015

Oct. 20, 2015

Hi guys I found how I can change the size of the main pharo window but I could not find how I can place it in a given location. Stef

1 0

Thanks for Pharo
by Jimmie Houchin Oct. 20, 2015

Oct. 20, 2015

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

10 16

Voting for removing Seaside chapter from UPBE
by Dimitris Chloupis Oct. 20, 2015

Oct. 20, 2015

I already mentioned this in Github issues but here is my take on this I vote for the complete removal of the Seaside chapter for several reasons a) Its not a begineer orientated chapter as is the focus of this book b) its not general purpose as is the focus of this book c) far harder to keep this updated constantly which again is the focus of this book, since not many of us use seaside d) It already has its own book and its own documentation which we can easily refer to. e) Its not even part of Pharo standard distribution So I vote for the complete removal of this chapter so we have one less thing to worry about updating and since its my personal opinion that it does not fit the general character of this book. I would like your thoughts on this since its a big change.

3 4

Oct. 20, 2015

Hi, I'm a newcomer in Pharo and start to learn how to use Pharo. In page 42 of UPBE(Vesion:2015-10-17 ), I don't know where I write the constant methods and UPBE didn't tell me in which pane to type them. Could you tell me ? Andy Zhu

5 8