Re: [Pharo-users] [UFFI] Call a function where argument type is char ** (argv)

2016-06-04 Thread Esteban Lorenzano
Hi, sorry late response, I just missed this mails. but… I do not have much to say… what you did should work. Except (I think I’d need to look at your code closer) you need to change the argument of argv to FFIExternalArray*, or you need to pass the handle to the function. Something like thi

Re: [Pharo-users] One comment to new Pharo5 debugger

2016-06-04 Thread Sabine Manaa
Hi Tudor, thank you for the explanation, which explains the situation. Speaking only for me: I never used custom debuggers, I always used the default debugger in different smalltalk IDEs and so, I am used to a kind of "standard". But as your signature points out "Every thing should have the right

Re: [Pharo-users] One comment to new Pharo5 debugger

2016-06-04 Thread Esteban Lorenzano
Hi, > On 04 Jun 2016, at 12:18, Sabine Manaa wrote: > > Hi Tudor, > > thank you for the explanation, which explains the situation. > > Speaking only for me: I never used custom debuggers, I always used the > default debugger in different smalltalk IDEs and so, one could say you never used

Re: [Pharo-users] [UFFI] Call a function where argument type is char ** (argv)

2016-06-04 Thread Esteban Lorenzano
Hi, but this will not work either (I just realised). This is complicated matter and confuses many (even me, some times :P). I will try explain. Technically, when you do array := (FFIExternalArray externalNewType: 'void*' size: parameters size) autoRelease. you are declaring (in C) (void*)

Re: [Pharo-users] One comment to new Pharo5 debugger

2016-06-04 Thread Tudor Girba
Hi, > On Jun 4, 2016, at 12:18 PM, Sabine Manaa wrote: > > Hi Tudor, > > thank you for the explanation, which explains the situation. > > Speaking only for me: I never used custom debuggers, I always used the > default debugger in different smalltalk IDEs and so, I am used to a kind of > "s

[Pharo-users] the impact of moldability

2016-06-04 Thread Tudor Girba
Hi, There were a couple of emails in the recent period that questioned the usefulness of moldability (the ability of developers to customize their tools deeply and inexpensively). More specifically, the question was about the moldability of the GTDebugger. I put together a couple of thoughts o

[Pharo-users] Issue on Seaside beginning

2016-06-04 Thread Cheikhou Oumar KA
Hello. I am following #PharoMOOC and it become more and more exciting. I were doing TinyBlog exercise and I got an issue. I looked at the forum but any solution and I am stuck now like many others. I have created my class TBApplicationRootComponent, create a server that listen at :8080 and start

Re: [Pharo-users] Issue on Seaside beginning

2016-06-04 Thread Cyril Ferlicot D.
Le 04/06/2016 19:00, Cheikhou Oumar KA a écrit : > Hello. > > I am following #PharoMOOC and it become more and more exciting. > > I were doing TinyBlog exercise and I got an issue. I looked at the forum > but any solution and I am stuck now like many others. > > I have created my class TBApplica

Re: [Pharo-users] One comment to new Pharo5 debugger

2016-06-04 Thread Tudor Girba
Hi, > On Jun 4, 2016, at 7:09 PM, Ben Coman wrote: > > > > On Sat, Jun 4, 2016 at 11:28 PM, Gabriel Cotelli wrote: > Hi, > I undestand and really liked the idea of a moldable debugger and it's true > that the button actions act over the stack, however the decision on what > action to use is

Re: [Pharo-users] Issue on Seaside beginning

2016-06-04 Thread Cheikhou Oumar KA
> Hi, > I think I already got this problem when I loaded Seaside 3.2 in an image > where Seaside 3.1 was present. Thanks for this. 2016-06-04 17:10 GMT+00:00 Cyril Ferlicot D. : > Le 04/06/2016 19:00, Cheikhou Oumar KA a écrit : > > Hello. > > > > I am following #PharoMOOC and it become more a

Re: [Pharo-users] One comment to new Pharo5 debugger

2016-06-04 Thread Ben Coman
On Sun, Jun 5, 2016 at 1:17 AM, Tudor Girba wrote: > Hi, > >> On Jun 4, 2016, at 7:09 PM, Ben Coman wrote: >> >> >> >> On Sat, Jun 4, 2016 at 11:28 PM, Gabriel Cotelli wrote: >> Hi, >> I undestand and really liked the idea of a moldable debugger and it's true >> that the button actions act over

Re: [Pharo-users] Issue on Seaside beginning

2016-06-04 Thread stepharo
Hi Cheikhou We will have a look. I will contact Luc and Damien because I do not follow the Seaside set up. May be we messed up with the setup of the seaside image we gave you. Did you save your code? So that you can reload it with the https://ci.inria.fr/pharo-contribution/job/Seaside/

Re: [Pharo-users] One comment to new Pharo5 debugger

2016-06-04 Thread Ben Coman
On Jun 4, 2016 14:11, "Ben Coman" wrote: > >> >> >> On Sat, Jun 4, 2016 at 11:28 PM, Gabriel Cotelli >> wrote: >> >>> Hi, >>> I undestand and really liked the idea of a moldable debugger and it's >>> true that the button actions act over the stack, however the decision on >>> what action to use i

Re: [Pharo-users] [Moose-dev] Re: the impact of moldability

2016-06-04 Thread Tudor Girba
Hi, > On Jun 4, 2016, at 7:34 PM, Ben Coman wrote: > > Nice read and some interesting statistics. Thanks > It makes sense when laid > out like that, but its a question of internalising the knowledge to > make use of moldability more often. Indeed. This is a challenge. In this regard, picking

Re: [Pharo-users] the impact of moldability

2016-06-04 Thread stepharo
I like the way you react to my criticisms. In fact each time I complain you make progress. You should really thank me in fact. And you can name me if it makes you feel better. ;) Now what you should measure is the ratio over engineering - complexity of the solution vs. spread of usage.

Re: [Pharo-users] Issue on Seaside beginning

2016-06-04 Thread Cheikhou Oumar KA
Hi Stef > You got a problem with such image > https://ci.inria.fr/pharo-contribution/job/PharoWeb/PHARO=50,VERSION=stable,VM=vm/lastSuccessfulBuild/artifact/PharoWeb.zip Yes I saved my code in Smalltalkhub. i loaded it in this new image and It works perfectly. May be there the problem come from

Re: [Pharo-users] [Moose-dev] how to set a code completion schema in GT inspector?

2016-06-04 Thread Tudor Girba
Not now. This would be another thing to approach from a moldable point of view. Doru > On May 27, 2016, at 3:55 PM, Alexandre Bergel wrote: > > Hi! > > Is there a way to provide a strategy to complete code in GT? > For example, if I would like to specialize the completion in case I am > writ

[Pharo-users] Pharo 5 hanging and crashing

2016-06-04 Thread Gerry Weaver
Hello All, I am new to Pharo and Smalltalk in general. I have been experimenting with Pharo 5 trying to get acquainted with the environment and the language. I have been having some issues with the image hanging and crashing. This happens when trying code in the Play Ground and especially when

Re: [Pharo-users] the impact of moldability

2016-06-04 Thread Tudor Girba
Hi Stef, > On Jun 4, 2016, at 8:38 PM, stepharo wrote: > > I like the way you react to my criticisms. In fact each time I complain you > make progress. You should really thank me in fact. Thanks for reading. I try my best to welcome criticism even when the tone is not appropriate. I do not a

Re: [Pharo-users] Pharo 5 hanging and crashing

2016-06-04 Thread Tudor Girba
Hi, Pharo 5 is the current release, and you should use this one :). Do you have a specific scenario that we can use to reproduce the crashing behavior? Cheers, Doru > On Jun 4, 2016, at 11:48 PM, Gerry Weaver wrote: > > Hello All, > > I am new to Pharo and Smalltalk in general. I have bee

Re: [Pharo-users] Issue on Seaside beginning

2016-06-04 Thread Luc Fabresse
Hi Cheikhou, Ok, this is good that you found a solution. Can you post your solution on the MOOC forum to help other people that might be blocked? Thanks, #Luc 2016-06-04 20:58 GMT+02:00 Cheikhou Oumar KA : > Hi Stef > > > You got a problem with such image > > > > https://ci.inria.fr/pharo-cont

Re: [Pharo-users] Pharo 5 hanging and crashing

2016-06-04 Thread Gerry Weaver
Hi, I'm afraid I don't have any steps to reproduce the issues at the moment. I was just playing around and it hung or crashed frequently enough that it became a bit tedious. I just wondered, if anyone else was having problems. It would seem that I may be alone in this, so I'll try to figure out

[Pharo-users] Pharo MOOC: A propossed change on factorial

2016-06-04 Thread Offray Vladimir Luna Cárdenas
Hi all, I'm advancing on the Pharo MOOC trying to catch the rest of the people. It has been a really interesting learning experience. Now I'm making the Block lesson on week 2 and I have found the factorial example with its code. With the quality assistant It noticed no spaces at the beginni

[Pharo-users] problem getting moose

2016-06-04 Thread Ben Coman
I wanted to try out Peter's XMI Analyser with Roassal and went to download Moose but had a couple of problems. First try... In the Launcher under Common Tools, I downloaded and Moose 5.1(stable) fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but got a problem - big pause, no prog

Re: [Pharo-users] Pharo 5 hanging and crashing

2016-06-04 Thread Tudor Girba
Hi, This is certainly not something that should happen. Pharo 5 is deemed ready for production and many of us are using it since a long time :). It is still possible that you encountered a bug, and having a reproducible case can help us spot it. Meanwhile, when you say crashing, do you mean th

Re: [Pharo-users] Pharo 5 hanging and crashing

2016-06-04 Thread Gerry Weaver
Hi, I'm using the term "hanging" to mean that the image locked up or became unresponsive. When I use the term "crashing", I mean the image aborted. I have also seen a few cases where the image would hang first and then abort a few seconds later. This usually results after a few error windows ha

Re: [Pharo-users] problem getting moose

2016-06-04 Thread Ben Coman
On Sun, Jun 5, 2016 at 1:34 PM, Ben Coman wrote: > I wanted to try out Peter's XMI Analyser with Roassal and went to > download Moose but had a couple of problems. > > First try... > In the Launcher under Common Tools, I downloaded and Moose 5.1(stable) > fine, but it is Pharo 4, so tried to downl

Re: [Pharo-users] problem getting moose

2016-06-04 Thread Tudor Girba
Hi, > On Jun 5, 2016, at 7:34 AM, Ben Coman wrote: > > I wanted to try out Peter's XMI Analyser with Roassal and went to > download Moose but had a couple of problems. > > First try... > In the Launcher under Common Tools, I downloaded and Moose 5.1(stable) > fine, but it is Pharo 4, so tried t

Re: [Pharo-users] problem getting moose

2016-06-04 Thread Tudor Girba
Hi, I figured out the problem. When you run that script, you actually load "4.4-beta.1 [ConfigurationOfMoose]” This is because of the mismatch between what loadDevelopment means in Gofer and the meaning of the symbolic version in Metacello. Instead, please use this: Metacello new