Re: [Pharo-dev] RB Tests failing

Mark told me that he will publish them. Stef On 30/9/14 11:37, Nicolai Hess wrote: 2014-09-30 11:02 GMT+02:00 Yuriy Tymchuk >: Hi, now when you download a new Pharo4 image there are 3 tests failing/erroring: Failures: RBRenameInstanceVariableTe

Re: [Pharo-dev] ZnEasy and post:data:

ZnClient is your friend (it is a builder) : ZnClient new url: 'http://some/thing'; formAt: #foo put: #bar; formAt: 'baz' put: 'quux'; post. HTH, Sven PS: Check out the 'accessing request' protocol for more ways to construct your request. Also, the response is kept in the object: #post

Re: [Pharo-dev] GTPlayground Play Button Semantics

I know what it was :). I was asking what would the goal be of an explorer now. Doru On Wed, Oct 1, 2014 at 10:39 PM, Esteban Lorenzano wrote: > it was the tree-shaped inspector, it does not have sense anymore with the > new inspector (since everything is rolled into one). > > > On 01 Oct 2014,

[Pharo-dev] ZnEasy and post:data:

Hey all, This is probably me missing something, but: for an upcoming presentation, I wanted to find the tersest way to demonstrate making an HTTP POST.  Something equivalent to Python's requests.post('http://some/thing', data={'foo': 'bar', 'baz': 'quux'}) The closest I could come up wit

Re: [Pharo-dev] GTPlayground Play Button Semantics

it was the tree-shaped inspector, it does not have sense anymore with the new inspector (since everything is rolled into one). > On 01 Oct 2014, at 22:33, Tudor Girba wrote: > > What is explorer? > > Doru > > On Wed, Oct 1, 2014 at 10:12 PM, stepharo > wrote: > Alex

Re: [Pharo-dev] GTPlayground Play Button Semantics

The play symbol is also used for run. That is why we used that icon. But, we can change it. Ideas? Btw, all the icons used in GT and Moose are drawn by me and licensed under CC Attribution: https://github.com/girba/mooseart Cheers, Doru On Wed, Oct 1, 2014 at 10:12 PM, stepharo wrote: > Alex

Re: [Pharo-dev] GTPlayground Play Button Semantics

What is explorer? Doru On Wed, Oct 1, 2014 at 10:12 PM, stepharo wrote: > Alex > > play looks like flash or music not like executing. > > We all complain that smalltalk is weak and that people can make silly > statements like > Java is compiled and Smalltalk intepreted (I read that in the >

Re: [Pharo-dev] GTPlayground Play Button Semantics

Ok, I will try to explain again: Cmd+i means inspect. When I am in a class browser, it means that the inspector windows opens up. But, when I am in the inspector, it can simply mean open a new pane to the right. Then if you explicitly want to open a window you use an imperative Inspect that we ca

Re: [Pharo-dev] GTPlayground Play Button Semantics

Alex play looks like flash or music not like executing. We all complain that smalltalk is weak and that people can make silly statements like Java is compiled and Smalltalk intepreted (I read that in the lecture)!!! But this is our fault. In my book you will not see evaluating an express

Re: [Pharo-dev] GTPlayground Play Button Semantics

On 1/10/14 16:55, Tudor Girba wrote: Cmd+g sounds like fun :). The other thing could be to have cmd+i as a replacement for cmd+o when you are in the inspector. When outside, Cmd+i would spawn an inspector window if the surrounding browser does not support in-place inspection (like the playgr

Re: [Pharo-dev] GTPlayground Play Button Semantics

On 1/10/14 16:06, Esteban Lorenzano wrote: and btw, what about remap cmd+o to cmd+e (like “execute”) ? + 1 and rename open to execute! Esteban On 01 Oct 2014, at 16:05, Sven Van Caekenberghe > wrote: On 01 Oct 2014, at 16:00, Andrei Chis

Re: [Pharo-dev] GTPlayground Play Button Semantics

Open is not a good name. I want to execute something not opening it. I would never think that open is executing an expression and inspecting the result. Stef On 1/10/14 16:05, Sven Van Caekenberghe wrote: On 01 Oct 2014, at 16:00, Andrei Chis wrote: On Wed, Oct 1, 2014 at 3:14 PM, Sven Va

Re: [Pharo-dev] IMPORTANT: Contributing to "Configurated" sub-projects

crap… I was victim of IMAP OSX Mail bug. This answer should be linked to other thread, sorry. > On 01 Oct 2014, at 20:12, Esteban Lorenzano wrote: > > Process can always be enhanced, of course. But in fact what we did now was > just to formalise what was already happening (with Zinc, for exam

Re: [Pharo-dev] GTPlayground Play Button Semantics

Process can always be enhanced, of course. But in fact what we did now was just to formalise what was already happening (with Zinc, for example). so we can continue enhancing it from here. about your fears: - all sub-projects will be (we still need to move some there) under “Pharo” umbrella,

Re: [Pharo-dev] IMPORTANT: Contributing to "Configurated" sub-projects

basically, if you working on a subproject, you should not mess with others. so, if you fixing, lets say, GTools, dirtiness should affect just him. If not, then you, gtool maintainers or pharo core maintainers made a mistake (or all of them). of course, that works *just* for sub-projects manage

Re: [Pharo-dev] Confused about the GTInspector State Tab

On 1 oct. 2014, at 18:38, stepharo wrote: > >> To distinguish between the different types of variables, we could add >> another column with a tag, like we have in the GTDebugger (e.g., Slot / >> Derived). What do you think? > > I do not like slots. > Because not all the objects have that. A

Re: [Pharo-dev] IMPORTANT: Contributing to "Configurated" sub-projects

And confusing as one can see here: https://pharo.fogbugz.com/f/cases/14137 Will we end up in "I need access to repo", "please add me as contributor to" hell and slow down the integration process as one has to wait until the responsible person has time (and is willing to accept the change)? I

Re: [Pharo-dev] GTPlayground Play Button Semantics

cmd+e does not look like to be more explicit to me. Something that I find a little bit confusing, is “play” vs “open”. The button is a play button. But in the menu, it says “open”. Why not being consistent with “play”? Alexandre On Oct 1, 2014, at 7:06 AM, Esteban Lorenzano wrote: > and btw,

Re: [Pharo-dev] Confused about the GTInspector State Tab

To distinguish between the different types of variables, we could add another column with a tag, like we have in the GTDebugger (e.g., Slot / Derived). What do you think? I do not like slots. Because not all the objects have that. Raw Items are working better to me Cheers, Doru On Wed, O

Re: [Pharo-dev] Confused about the GTInspector State Tab

On 1/10/14 16:30, Tudor Girba wrote: Hi, Indeed, the goal of State is to show the raw state of every object. In case we miss something, we should add that. Sven, if you see that this is not happening, let's start on a case to case basis. Doru call it "raw" and not state. Especially if state

Re: [Pharo-dev] IMPORTANT: Contributing to "Configurated" sub-projects

Esteban Lorenzano wrote: Hi, As you might or might not seen, we are moving Pharo into a different architecture: From a monolitic "one-image-is-all", we are (very slowly) going into an small kernel and a set of sub-projects who will populate the image and provide all required features. In genera

Re: [Pharo-dev] IMPORTANT: Contributing to "Configurated" sub-projects

sounds great! sebastian o/ > On 01/10/2014, at 12:41, Esteban Lorenzano wrote: > > Hi, > > As you might or might not seen, we are moving Pharo into a different > architecture: From a monolitic "one-image-is-all", we are (very slowly) going > into an small kernel and a set of sub-projects w

[Pharo-dev] IMPORTANT: Contributing to "Configurated" sub-projects

Hi, As you might or might not seen, we are moving Pharo into a different architecture: From a monolitic "one-image-is-all", we are (very slowly) going into an small kernel and a set of sub-projects who will populate the image and provide all required features. In general, the idea is that the

Re: [Pharo-dev] GTPlayground Play Button Semantics

Le 1 oct. 2014 à 16:55, Tudor Girba a écrit : > Cmd+g sounds like fun :). > > The other thing could be to have cmd+i as a replacement for cmd+o when you > are in the inspector. When outside, Cmd+i would spawn an inspector window if > the surrounding browser does not support in-place inspection

Re: [Pharo-dev] Confused about the GTInspector State Tab

Hmm, a column for a tag would take even more space and for most objects it will only be Slot. Also with the icons and the arrow for collapsing it might not look so good. The other solution is to display all derived variables at the top, perhaps with a different color or/and in italic. On Wed, Oc

Re: [Pharo-dev] GTPlayground Play Button Semantics

Hi Sven, Thanks a lot for these questions. Please keep them coming. These first impressions are really important because we have the opportunity to evolve. @Everyone: if you see me or Andrei providing arguments is not to say that we want to be right, but simply to show what we took into considera

Re: [Pharo-dev] GTPlayground Play Button Semantics

Cmd+g sounds like fun :). The other thing could be to have cmd+i as a replacement for cmd+o when you are in the inspector. When outside, Cmd+i would spawn an inspector window if the surrounding browser does not support in-place inspection (like the playground). To force inspect in a new window we

Re: [Pharo-dev] Confused about the GTInspector State Tab

To distinguish between the different types of variables, we could add another column with a tag, like we have in the GTDebugger (e.g., Slot / Derived). What do you think? Cheers, Doru On Wed, Oct 1, 2014 at 4:28 PM, Andrei Chis wrote: > > > > On Wed, Oct 1, 2014 at 3:08 PM, Sven Van Caekenbergh

Re: [Pharo-dev] Confused about the GTInspector State Tab

Hi, Indeed, the goal of State is to show the raw state of every object. In case we miss something, we should add that. Sven, if you see that this is not happening, let's start on a case to case basis. Btw, if you want to know what gets shown in State, you can simply inspect the result of Object>>

Re: [Pharo-dev] Confused about the GTInspector State Tab

On Wed, Oct 1, 2014 at 3:08 PM, Sven Van Caekenberghe wrote: > I am confused about the GTInspector State tab. What is its definition ? > > I would say that it shows the raw, fundamental, implementation form of the > object, in essence what EyeBasicInspector showed. And that additional tabs > offe

Re: [Pharo-dev] Confused about the GTInspector State Tab

On 01 Oct 2014, at 15:08, Sven Van Caekenberghe wrote: > I am confused about the GTInspector State tab. What is its definition ? > > I would say that it shows the raw, fundamental, implementation form of the > object, in essence what EyeBasicInspector showed. And that additional tabs > offer

Re: [Pharo-dev] GTPlayground Play Button Semantics

so far, we want to keep cmd+o to open tools. then what about cmd+g for “cmd+go” (and as Guille says, an internal joke for “cmd+gDoit”) :P Esteban > On 01 Oct 2014, at 16:15, Andrei Chis wrote: > > If we want to keep cmd+o for opening the tools then it make sense to use > cmd+e. > Just it c

Re: [Pharo-dev] GTPlayground Play Button Semantics

If we want to keep cmd+o for opening the tools then it make sense to use cmd+e. Just it could be a little confusing because cmd+e was already user before to open the explorer. We wanted a new shortcut to avoid this confusion. But I am not against using cmd+e On Wed, Oct 1, 2014 at 4:06 PM, Esteba

Re: [Pharo-dev] GTPlayground Play Button Semantics

and btw, what about remap cmd+o to cmd+e (like “execute”) ? Esteban > On 01 Oct 2014, at 16:05, Sven Van Caekenberghe wrote: > > > On 01 Oct 2014, at 16:00, Andrei Chis > wrote: > >> >> >> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe wrote: >> W

Re: [Pharo-dev] GTPlayground Play Button Semantics

On 01 Oct 2014, at 16:00, Andrei Chis wrote: > > > On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe wrote: > Was it a conscious decision to make the GTPlayground Play button act as 'play > all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting tha

Re: [Pharo-dev] GTPlayground Play Button Semantics

On Wed, Oct 1, 2014 at 4:00 PM, Andrei Chis wrote: > Does this seem ok to you? makes perfect sense to me. Toolbar is for global stuff, context menu for contextual stuff. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without lo

Re: [Pharo-dev] Confused about the GTInspector State Tab

But we cannot all start doing different things, right ? There should be some design and structure, that is why I am asking. On 01 Oct 2014, at 15:59, Esteban Lorenzano wrote: > cool thing of this new inspector is that is super easy to extend with what > you want > So wouldn’t be complicated to

Re: [Pharo-dev] GTPlayground Play Button Semantics

On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe wrote: > Was it a conscious decision to make the GTPlayground Play button act as > 'play all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting that I cannot select some expression and 'play > it'. A works

Re: [Pharo-dev] Confused about the GTInspector State Tab

cool thing of this new inspector is that is super easy to extend with what you want So wouldn’t be complicated to add that functionality :) Esteban > On 01 Oct 2014, at 15:51, Ben Coman wrote: > > Sven Van Caekenberghe wrote: >> I am confused about the GTInspector State tab. What is its defi

Re: [Pharo-dev] Confused about the GTInspector State Tab

Sven Van Caekenberghe wrote: I am confused about the GTInspector State tab. What is its definition ? I would say that it shows the raw, fundamental, implementation form of the object, in essence what EyeBasicInspector showed. And that additional tabs offer alternative, more user friendly views

[Pharo-dev] [pharo-project/pharo-core] 6d0d66: 40276

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 6d0d667c65fb0ff32cad8d3e06f8614ab93d1543 https://github.com/pharo-project/pharo-core/commit/6d0d667c65fb0ff32cad8d3e06f8614ab93d1543 Author: Jenkins Build Server Date: 2014-10-01 (Wed, 01 Oct 2014

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/40276 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] GTPlayground Play Button Semantics

+1 On Wed, Oct 1, 2014 at 10:14 AM, Sven Van Caekenberghe wrote: > Was it a conscious decision to make the GTPlayground Play button act as > 'play all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting that I cannot select some expression and 'play > it'. A

Re: [Pharo-dev] Confused about the GTInspector State Tab

I agree. I often want to see the real implementation and not the view that the system wants me to believe. Stef I am confused about the GTInspector State tab. What is its definition ? I would say that it shows the raw, fundamental, implementation form of the object, in essence what EyeBasi

[Pharo-dev] GTPlayground Play Button Semantics

Was it a conscious decision to make the GTPlayground Play button act as 'play all' (evaluate the whole workspace contents) ? If so, why ? I find it quite limiting that I cannot select some expression and 'play it'. A workspace/playground is like a notebook containing lots of different things.

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/40275 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] f82136: 40275

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f821362cb2335e34c3c60ad34adccd29882fc70c https://github.com/pharo-project/pharo-core/commit/f821362cb2335e34c3c60ad34adccd29882fc70c Author: Jenkins Build Server Date: 2014-10-01 (Wed, 01 Oct 2014

[Pharo-dev] Confused about the GTInspector State Tab

I am confused about the GTInspector State tab. What is its definition ? I would say that it shows the raw, fundamental, implementation form of the object, in essence what EyeBasicInspector showed. And that additional tabs offer alternative, more user friendly views. Why then does it not show al

[Pharo-dev] [pharo-project/pharo-core] 7e5c91: 40274

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 7e5c915040ac9fea3447288cfe9f26f3f1e4244f https://github.com/pharo-project/pharo-core/commit/7e5c915040ac9fea3447288cfe9f26f3f1e4244f Author: Jenkins Build Server Date: 2014-10-01 (Wed, 01 Oct 2014

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/40274 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] is Kommiter working for you in 40 latest?

> On 01 Oct 2014, at 07:37, stepharo wrote: > > is Kommiter working for you in 40 latest? > Because I get an error tellling to me that it cannot find Applications / > Pharo? I was also getting this some time ago. Didn’t check since then Uko >

Re: [Pharo-dev] is Kommiter working for you in 40 latest?

Le 1 oct. 2014 à 07:37, stepharo a écrit : > is Kommiter working for you in 40 latest? yes, works fine for me smime.p7s Description: S/MIME cryptographic signature

Re: [Pharo-dev] GTInspector + Fuel

On Wed, Oct 1, 2014 at 2:25 AM, Tudor Girba wrote: > Hi Mariano, > > I am not sure I understand the implication of using > addPostMaterializationAction: > in combination with the inspector materialization extension. Where do you > see the opportunity? > > What I thought is the following. if

[Pharo-dev] [pharo-project/pharo-core] 11e333: 40273

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 11e333080d87e57dd8d889e4088b73ad3b1440bd https://github.com/pharo-project/pharo-core/commit/11e333080d87e57dd8d889e4088b73ad3b1440bd Author: Jenkins Build Server Date: 2014-10-01 (Wed, 01 Oct 2014

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/40273 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] GTTool bug:

On 01 Oct 2014, at 10:58, Tudor Girba wrote: > I think this is the wrong thing to do. We should reimplement the method in > the UIManager. > Yes! > Doru > > On Wed, Oct 1, 2014 at 10:30 AM, Andrei Chis > wrote: > There is an acceptsContents: on GLMSystemWindow that delegates to the mode

Re: [Pharo-dev] GTTool bug:

I think this is the wrong thing to do. We should reimplement the method in the UIManager. Doru On Wed, Oct 1, 2014 at 10:30 AM, Andrei Chis wrote: > There is an acceptsContents: on GLMSystemWindow that delegates to the > model, which in this case is the playground. > > On Wed, Oct 1, 2014 at 10

Re: [Pharo-dev] GTTool bug:

There is an acceptsContents: on GLMSystemWindow that delegates to the model, which in this case is the playground. On Wed, Oct 1, 2014 at 10:26 AM, Tudor Girba wrote: > How did you fix it? > > Doru > > On Wed, Oct 1, 2014 at 10:22 AM, Andrei Chis > wrote: > >> I fixed for now the part with acce

Re: [Pharo-dev] GTTool bug:

How did you fix it? Doru On Wed, Oct 1, 2014 at 10:22 AM, Andrei Chis wrote: > I fixed for now the part with acceptsContents: > This should work when the issue is integrated > > UIManager default > edit: 'jlklkjk' > label: 'lkjlkjjkl'. > > On Wed, Oct 1, 2014 at 9:50 AM, Tudor G

Re: [Pharo-dev] GTTool bug:

I fixed for now the part with acceptsContents: This should work when the issue is integrated UIManager default edit: 'jlklkjk' label: 'lkjlkjjkl'. On Wed, Oct 1, 2014 at 9:50 AM, Tudor Girba wrote: > Exactly. > > I created an entry for this: > > https://pharo.fogbugz.com/f/cases

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

It is tripple click :). If you click first to set the cursor, you still have to click three times to select the whole line. The nice thing though is that even if the cursor is not there, you still only require triple click to select the whole line. It's actually quite nice, but we would need the

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

I guess it should be double click on cursor because first click places the cursor. When you open TextEdit with some text and do 3 consecutive clicks. After the second click it selects the word your cursor is on, after 3rd one it selects line that your cursor is on. I don’t know, maybe other peop

Re: [Pharo-dev] GTTool bug:

Exactly. I created an entry for this: https://pharo.fogbugz.com/f/cases/14133/UIManager-should-not-overuse-the-workspace-for-editing Cheers, Doru On Wed, Oct 1, 2014 at 9:20 AM, Marcus Denker wrote: > > On 30 Sep 2014, at 20:41, stepharo wrote: > > > edit: aText label: labelString accept: an

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

Hi Uko, I think you mean that triple clicking on the cursor when it is inside the line should select the line, right? Cheers, Doru On Wed, Oct 1, 2014 at 8:54 AM, Yuriy Tymchuk wrote: > If my 2 cents make sense, it will be nice to have things similar to text > editors. E.g. triple click for

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

Why it has to be black or white just implement both or all of these ideas and let user choose in pharo settings. Problem solved Στις 1 Οκτ 2014 9:55 π.μ., ο χρήστης "Yuriy Tymchuk" έγραψε: > If my 2 cents make sense, it will be nice to have things similar to text > editors. E.g. triple click for

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

Hi Stef, Thanks for your comments. In particular, the one about clicking on the current cursor. I never saw it like that because I always used the mouse. So in fact, I was wrong in seeing it as click-pause-click because it should have been as click-on-cursor. I actually like this one. However, th

Re: [Pharo-dev] GTTool bug:

On 30 Sep 2014, at 20:41, stepharo wrote: > edit: aText label: labelString accept: anAction >"Open an editor on the given string/text" > >^(Smalltalk tools workspace openLabel: labelString) >acceptContents: aText; >acceptAction: anAction; >yourself. > > Yes,