gmane.comp.lang.smalltalk.pharo.devel

Re: Posible bug

Sean P. DeNigris — 2012-05-24T20:39:46

Camillo Bruni-3 wrote

I don't know enough about the process - will that guarantee a working build?
Right now, Jenkins "Cog Git Tracker" is failing (not because of the sources
this time). If there was something broken, using the versions of
image/ConfigurationOfXxx, sources, etc. from Jenkins' last successful build
would guarantee success anyway.

Sean

--
View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631744.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Update stream for released images

Sean P. DeNigris — 2012-05-24T20:32:01

Now that there will be bug fixes for released images, it seems like we should
we keep "Software update" in the world menu, no?

Sean

--
View this message in context: http://forum.world.st/Update-stream-for-released-images-tp4631743.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Re: Progress bar in the top left

Sean P. DeNigris — 2012-05-24T16:06:28

Stéphane Ducasse wrote

As I've been working on NewSystemProgressMorph, I've been toying with
whether the progress bar should be directly manipulated, as is the case now,
or should just be another subscriber for progress announcements. This way it
could be disabled by unsubscribing, and any other actions could be taken
additionally/instead (e.g. send progress to stdout, transcript, etc.)

--
View this message in context: http://forum.world.st/Progress-bar-in-the-top-left-tp4631530p4631730.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Re: Suggestions about Nautilus Look

Sean P. DeNigris — 2012-05-24T15:58:28

Fabrizio Perin-3 wrote

Great feedback! Thanks for taking the time to start the discussion...


Fabrizio Perin-3 wrote
The gray icons indicate that the package is clean. When there are unsaved
changes, the color goes to red


Fabrizio Perin-3 wrote
Whatever color we make them, they will be less visible with *some* color
background ;-) I *really* like that the visual color feedback is part of the
testing domain. I know the test passed without moving my eyes to the corner
to read the text. Your point about checking the background color and
altering for some contrast is valid, but seems like a long-shot (how many
people have those bold green/yellow colors as backgrounds?!). I would guess
if you're passionate about it, you should implement it yourself and submit
the code :)

Sean

--
View this message in context: http://forum.world.st/Suggestions-about-Nautilus-Look-tp4631723p4631728.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Re: Progress bar in the top left

Stéphane Ducasse — 2012-05-24T15:32:49

Indeed.


Now sometimes we should have a blocking UI.

Stef

Suggestions about Nautilus Look

Fabrizio Perin — 2012-05-24T15:08:13

Hi all,
I have a couple of propositions about the Nautilus look:

1 - If the Nautilus browser is a package browser why an infinity stack of
grey packages is shown? I think it is possible to safely remove all the
grey package icons since they are not really useful nor meaningful. This
will make the visual impact of nautilus lighter.

2- I think would be nicer to have smaller icons for tests like the one from
omnibrowser. I understand the icons are like buttons but the active area to
trigger the event "run the test" is not the icon itself, isn't it? It is
more in the area around the icon (also these icons appear in strange places
in the code, e.g. MooseModel>>add: which is weird).

3- The text in the message that appear in bottom-left corner that notify
about the test results it is not really visible if the background is yellow
or green so what about to make it black. Or better, what about to make it
black if the background color is green or yellow and leave it white if the
background is red?

4- the buttons to see the bytecode and the decompile code I immagine they
can became useful for some particular development but for normal
development I never had the needed to check the decompiled version of a
method or the bytecode. Different matter are the buttons for the instance
and class variables. It would be cool to make these functionalists less
"visible" making them available in a different way, for example in the
contextual menu that appear in the method editor panel.

What do you think?

Cheers,
Fabrizio

[update 2.0] #20094

Marcus Denker — 2012-05-24T13:58:57

20094
-----

Issue 5959:Failing test: SpecInterpreterTest>>testBuildWindowFor
http://code.google.com/p/pharo/issues/detail?id=5959

Issue 5966:DropListMorph do not pop the list when the text field is clicked
http://code.google.com/p/pharo/issues/detail?id=5966


--
Marcus Denker -- http://marcusdenker.de

Re: [ANN] 5965 Can't allocate semaphores?VirtualMachine>>maxExternalSemaphores: aSize | Not enoughspace for external objects, set a larger size at startup!

Sebastian Sastre — 2012-05-24T12:59:42

I agree with Henrik (both clarifications)

For the record, the error happens with a surprising value in aSize.

It happens when aSize is as low as 260       

o.O

sebastian

o/






On May 24, 2012, at 5:33 AM, Henrik Sperre Johansen wrote:

Re: Pressed Morph feedback on PharoTheme

Goubier Thierry — 2012-05-24T08:36:22

Le 24/05/2012 09:19, Goubier Thierry a écrit :

To correct that bug, a small change in ScrollBar>>mouseLeaveThumb:

event redButtonPressed
ifFalse: [
slider
fillStyle: self normalThumbFillStyle;
borderStyle: self normalThumbBorderStyle;
changed ].
(self containsPoint: event position)
ifTrue: [
upButton
fillStyle: self mouseOverPagingAreaButtonFillStyle;
borderStyle: self mouseOverPagingAreaButtonBorderStyle ]
ifFalse: [
upButton
fillStyle: self normalButtonFillStyle;
borderStyle: self normalButtonBorderStyle ].
(self containsPoint: event position)
ifTrue: [
downButton
fillStyle: self mouseOverPagingAreaButtonFillStyle;
borderStyle: self mouseOverPagingAreaButtonBorderStyle ]
ifFalse: [
downButton
fillStyle: self normalButtonFillStyle;
borderStyle: self normalButtonBorderStyle ]



Thierry

Re: [ANN] 5965 Can't allocate semaphores? VirtualMachine>>maxExternalSemaphores: aSize | Not enough space for external objects, set a larger size at startup!

Henrik Sperre Johansen — 2012-05-24T08:33:54

It's the other way around in this case, what's good in development is 
not always so good in deployment.
In development, you want to be notified of issues as soon as possible.
If they still slip through to deployment, you want them dealt with as 
gracefully as possible.


Well, both that, and the fact it can't be done safely.
The process of increasing its size might lead to lost signals.

99% of the time, setting the size at startup to a larger value than the 
default (before anything but the input semaphore is registered)  is a 
better approach than increasing automatically, and in the remaining 1% 
it is better to fix whatever application issue is causing semaphore 
leaks anyways.

Cheers,
Henry

Re: Pharo Conference

Craig Latta — 2012-05-24T08:15:09

Hi all--

     Unfortunately I'm not able to attend either; other matters conspire
to keep me in Amsterdam today. I do apologize. I hope you're all having
a great time! I add my voice to the chorus eager for videos, and please
do let me know if there's some way I can participate from here.


     cheers!
     Craig

--
Craig Latta
www.netjam.org/resume
+31   6 2757 7177
+ 1 415  287 3547 (no SMS)

Re: Pressed Morph feedback on PharoTheme

Goubier Thierry — 2012-05-24T07:19:17

Le 23/05/2012 17:31, Stéphane Ducasse a écrit :

I think this is when the button has a true state, as used by the 
getStateSelector of the morph. This is visible in the Hierarchy/Flat 
button in Nautilus, where Hierarchy is state == false, and Flat is state 
== true (and has the blue color).

In the case state true, PharoTheme may be falling back on the colors of 
the WateryTheme.

Another bug shown with my change is, if you start to scroll with the 
slider, it depresses correctly, but, as soon as you move outside the 
bounds of the scrollbar, even while pressing the left mouse button, then 
the slider goes back to the "not pressed" state while you are still 
scrolling up or down.


Change with "toggle" buttons instead ?

Playing with the Nautilus GUI, more interesting behavior(s) :
* Select an empty package (_UnpackagedPackage)
* Hierarchy button becomes disabled
but
* Instance / Class button is still enabled
* Comment button is still enabled

Thierry

Re: what is the magic with MCVersionInfo allInstances do: [ :each | each instVarNamed: 'ancestors' put: nil ]. ' ?

Chris Muller — 2012-05-24T01:44:14

The downside is that it tethers you to the network if you happen to
need access to the proxied ancestry.

On Wed, May 23, 2012 at 4:06 PM, Stéphane Ducasse
<stephane.ducasse-MZpvjPyXg2s< at >public.gmane.org> wrote:

Re: Progress bar in the top left

Serge Stinckwich — 2012-05-24T01:36:28

On Wed, May 23, 2012 at 7:37 PM, Guillermo Polito
<guillermopolito-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Is it possible to have an uniform way to present announcement. There
is already the growl-like announcements of tests used by the Nautilus
Browser done ob botton left. Maybe progress bar should be done in the
same screen area.

Regards,

Re: Posible bug

Camillo Bruni — 2012-05-23T22:22:36

check the HOWTOBUILD file in the git repository
+ there is an image.sh script in the /image folder of the git repo

I think the git repo should be the place to keep track of such documentation!

On 2012-05-23, at 18:29, Sean P. DeNigris wrote:

Re: what is the magic with MCVersionInfoallInstances do: [ :each | each instVarNamed: 'ancestors'put: nil ]. ' ?

Stéphane Ducasse — 2012-05-23T21:06:33

On May 23, 2012, at 7:09 PM, Chris Muller wrote:


yes this is probably the way to go.
You mean until the analysis finds a merge?

Stef

Re: Speed dating at PharoConf

2012-05-23T20:45:18

iOS VM Maintainer... Mmmh, get ready :-)

2012/5/23 Esteban Lorenzano <estebanlm-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>

Re: Speed dating at PharoConf

Tudor Girba — 2012-05-23T19:23:57

and mine

Doru



On 23 May 2012, at 18:48, Esteban Lorenzano wrote:


--
www.tudorgirba.com

"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."

Re: [ANN] 5965 Can't allocate semaphores? VirtualMachine>>maxExternalSemaphores: aSize | Not enough space for external objects, set a larger size at startup!

Igor Stasenko — 2012-05-23T18:22:52

Definitely.

Absolutely
(i'm in a good humor today ;)

Re: [ANN] 5965 Can't allocate semaphores?VirtualMachine>>maxExternalSemaphores: aSize | Not enoughspace for external objects, set a larger size at startup!

Sven Van Caekenberghe — 2012-05-23T18:18:10

On 23 May 2012, at 19:48, Marcus Denker wrote:


It might be a bit surprising, but I think Hendrik's reasoning is quite good: you don't want to keep on expanding when there are problems not freeing resources that are limited. A good server needs resource limits.

We can discuss more tomorrow…

Sven

Re: [ANN] 5965 Can't allocate semaphores? VirtualMachine>>maxExternalSemaphores: aSize | Not enough space for external objects, set a larger size at startup!

Igor Stasenko — 2012-05-23T17:57:39

Definitely.