- Pharo-users - lists.pharo.org

Pharo Docs website broken
by David Allouche Jan. 11, 2016

Jan. 11, 2016

Hello, It seems the pharodocs website is broken. Pages for classes are rendered, but the documentation does not display the messages, only their docstrings. That makes it quite unusable. http://files.pharo.org/doc/4.0/#packageList=package.html&classList=package/… <http://files.pharo.org/doc/4.0/#packageList=package.html&classList=package/…> I remember I looked at it once when I started and thought "whee, that's confusing, I'll play around and come back later". Now I understand why that was confusing... Who can fix that?

11 27

[ANN] Pharo Consortium New Gold Member: Synectique
by Marcus Denker Jan. 11, 2016

Jan. 11, 2016

The Pharo Consortium is very happy to announce that Synectique has joined the Consortium as an Gold Member. About - Synectique: http://www.synectique.eu/ <http://www.synectique.eu/> - Pharo Consortium: http://consortium.pharo.org <http://consortium.pharo.org/> The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org <http://association.pharo.org/>

4 3

gtdebugger - icons with text and a couple of others
by Tudor Girba Jan. 11, 2016

Jan. 11, 2016

Hi, Andrei and I took your feedback into account, and now we have this in the last version: - actions have text (this is a feature introduced in Glamour now) - the order of the code actions is better (accept is next to cancel) On top of that, there are a couple of extra features that we did not talk about until now: - whenever there is another kind of debugger available, a new button appears on the top right. When the Bytecode Debugger is loaded, you can always switch to it. Or, when you get in a situation in which the SUnit is available, you can switch to it. - the selection from the inspector is preserved when you move back and forth in the stack. - the panes in the inspector can be closed - stack highlighting is not on by default (it never was actually) - if you âInspect and Goâ, you inspect in place instead of the inspector at the bottom (no extra window) There are probably still glitches, but we think they are fixable. We still would like to add a couple of more features if there is time: - having a table in the stack to show class / method / package - having multiple inspectors in tabs when you inspect in place to not remove the original inspector Please let us know what you think. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Every thing has its own flow."

2 1

PharoLauncher MUST BE the default download of Pharo
by Dimitris Chloupis Jan. 11, 2016

Jan. 11, 2016

Talking about pharo being begineer friendly , PharoLauncher must be the default download for pharo. This is something that I have been promoting for past 2 year and Esteban informed he has been promoting this idea before me. So for those people that believe that pharo is begineer friendly.... prove it.

1 0

Twisted trait
by Hilaire Jan. 10, 2016

Jan. 10, 2016

Hi, When I remove a method from a trait, then save, Monticelly complains it can not find the method in the trait. Seen on Pharo3 Any idea? Thanks -- Dr. Geo http://drgeo.eu

1 0

gtdebugger in pharo 5.0
by Tudor Girba Jan. 9, 2016

Jan. 9, 2016

Hi, We are about to integrate in Pharo a new member of the Glamorous Toolkit: the GTDebugger. As this is a significant change that might affect your workflow, here is some background information to help you deal with the change. First, you should know that the change is not irreversible and it is easily possible to disabled the new debugger through a setting. However, please do take the time to provide us feedback if something does not work out for you. We want to know what can be improved and we try to react as fast as we can. A practical change comes from the fact that the variables are manipulated through a GTInspector, which makes it cheaper to maintain in the longer run. While the first thing that will capture the attention is the default generic interface, the real power comes from the moldable nature of the debugger. Like all other GT tools, GTDebugger is also moldable by design. This means that we can construct custom debuggers for specific libraries at small costs (often measured in a couple of hundred lines of code). For example, the core configuration includes also the SUnit and the bytecode debugger. These are around 150 lines of code. Here is how the bytecode debugger looks like: You can find more information in an introductory overview blog post that also includes some links for further reading: http://www.humane-assessment.com/blog/gtdebugger-in-pharo/ Please let us know what you think. Cheers, Doru -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

4 6

Crash or locked VM
by Hilaire Jan. 9, 2016

Jan. 9, 2016

Hi, I have a situation with a recursive Dr. Geo script where the image crash or get locked (Can't hold on the image). I tried with latest VM as detailed in the joined crash dump. I did not get similar problem with other recursive script. So I may have very special interaction between the objects, but I did not find out. It may also be related to Morph because when instantiating first the canvas and its window (2nd line of the script), then the rest of the script, it does not crash. The crashing image itself can be found there in case of usefulness https://www.dropbox.com/s/rur8ayt8eon6mab/drgeo.image.zip?dl=0 When not crashing it outputs this cherry tree. Thanks Hilaire -- Dr. Geo http://drgeo.eu

3 7

Interogation about recursivity or sequential
by Yann Dubois Jan. 9, 2016

Jan. 9, 2016

Hello World, Happy new year 2016 ! I actually work on an integration of a double linked list on Pharo and I have a little interogation. It's better to use recursivity or senquential algorithm ? Yann

5 4

Pine64
by John Pfersich Jan. 8, 2016

Jan. 8, 2016

I've pre-ordered a Pine64 SBC. The write up says it's got a "1.2 Ghz Quad-Core ARM Cortex A53 64-Bit Processor. It has 64 and 32 Bit execution states for scalable high performance power â including a NEON Multimedia processing engine." Does anybody have an idea whether the vm for the raspberry pi will work with this new computer? This is what the ARM site says about the A53 processor: As well as running 64-bit applications, the Cortex-A53 seamlessly and efficiently runs legacy ARM 32-bit applications. It is highly scalable, from a single multi-core CPU cluster, to a dual-cluster big.LITTLE CPU subsystem in combination with the Cortex-A72or Cortex-A57 processor, to a multi-cluster enterprise system connected through AMBAÂ® 5 CHI Coherent Interconnecttechnology. Full ARMv8-A support in a small and highly configurable package means that the Cortex-A53 is highly suited to a broad range of mobile, consumer, general purpose, and enterprise applications. Sent from my iPad Sent from my iPad

2 1

Halo Menu On Spec Tree Node
by Craig Johnson Jan. 6, 2016

Jan. 6, 2016

Hi All, I had an issue - when I opened a Halo on a Spec tree node in the UI and select the menu Icon, I got a DNU message. However if I selected a normal Morph, the menu Icon worked fine. I'm using Pharo 4.0 released version. Fixed this by changing TreeModel>>iconFor to: iconFor: aNode ^ iconBlock value cull: aNode content*s* cull: aNode Craig

4 4