Le 02/04/2014 22:51, Pharo4Stef a écrit :
On 02 Apr 2014, at 13:31, Goubier Thierry wrote:
Le 02/04/2014 08:12, Tudor Girba a écrit :
The language itself is less interesting for me, but what makes it stand
out is that it has a coherent and robust philosophy behind and
phenomenal goals to
Le 03/04/2014 01:03, Igor Stasenko a écrit :
cool
+1
but that means we need a resident configs in image, which IMO is a plus.
right now we don't.
You can cope with a pre-existing classification for stuff already in the
image, and configs for the additional stuff. Works. A touch is the
abil
Igor Stasenko wrote
> cool
Yes, very!
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Re-Nautilus-Package-Tree-tp4738896p4752462.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
GitHub wrote
> 13143 Integrate Versionner 2.7
> ...
> Which include these:...
Great job! Thanks, Christophe (and Marcus for integrating so quickly) :)
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/pharo-project-pharo-core-af5386-30809-tp4752340p4752464.html
Sent fro
Tudor Girba-2 wrote
> I just read the news.
>
> I am happy you are fine!
+1 to both. And thank you for letting us know you are okay!
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Thanks-to-all-of-you-who-asked-tp4752334p4752465.html
Sent from the Pharo Smalltalk De
Cool. I just loaded the latest NB and Athens (as Igor sent around) but my
image is not fully up to date. I'll try downloading a new one and reloading
my work from packages. I just wanted to make sure that this was worth the
effort. If that doesn't work, then I'll send Igor my image.
Cheers,
Jeff
Crossed my mind: create some visualizations using Roassal about the
quake(s) in Chile and advertise your local biz presence. #datajournalism,
This can turn big.
Le 3 avr. 2014 10:22, "Sean P. DeNigris" a écrit :
> Tudor Girba-2 wrote
> > I just read the news.
> >
> > I am happy you are fine!
>
>
Hi,
I just stumbled across a strange piece of code, and I am wondering about
the reasons behind it:
FileSystemStore>>creationTime: aPath
self
nodeAt: aPath
ifPresent: [ :entry | ^ self basicCreationTime: entry ]
ifAbsent: [ ^ false ].
In what case does returning "false" make sense?
Doru
--
ww
Branch: refs/tags/30810
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 1e1e45faf48b5245176cde218225385cc2e8d76b
https://github.com/pharo-project/pharo-core/commit/1e1e45faf48b5245176cde218225385cc2e8d76b
Author: Jenkins Build Server
Date: 2014-04-03 (Thu, 03 Apr 2014
Ben Coman wrote:
I
am requesting that the following fix be integrated.
https://pharo.fogbugz.com/f/cases/13065/Windows-FileSystem-test-bar-not-an-absolute-path
This corrects semantics on Windows where '/tmp/bar/' is not considered
an absolute path name, so that gets located under the imag
Branch: refs/tags/30811
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: a80092aabb962bd0cca04b93df1b2f300973487c
https://github.com/pharo-project/pharo-core/commit/a80092aabb962bd0cca04b93df1b2f300973487c
Author: Jenkins Build Server
Date: 2014-04-03 (Thu, 03 Apr 2014
I was pleasantly surprised that you had not loads of casualties with such a
big earthquake. And I was also wondering how many people are from Chile in
this mailing list. As a Greek I have plenty of experience with quakes
though none as big as that one. Should have been quite a shaking. I guess
even
+1
methods should return one single type of object. The only question: what time
should be returned? Or should it be nil?
On 03.04.2014, at 11:12, Tudor Girba wrote:
> Hi,
>
> I just stumbled across a strange piece of code, and I am wondering about the
> reasons behind it:
>
> FileSystemSt
Hi all
do you see a glitch when I resize a window?
Because it is not really nice.
Stef
I see it on Mac. On Windows it works fine. I thought this was a known issue.
Doru
On Thu, Apr 3, 2014 at 1:54 PM, Pharo4Stef wrote:
> Hi all
>
> do you see a glitch when I resize a window?
> Because it is not really nice.
> Stef
>
>
--
www.tudorgirba.com
"Every thing has its own flow"
I think it should be either a NoDate object, or an exception.
Doru
On Thu, Apr 3, 2014 at 1:06 PM, Max Leske wrote:
> +1
>
> methods should return one single type of object. The only question: what
> time should be returned? Or should it be nil?
>
> On 03.04.2014, at 11:12, Tudor Girba wrote:
On 3 avr. 2014, at 13:54, Pharo4Stef wrote:
> Hi all
>
> do you see a glitch when I resize a window?
> Because it is not really nice.
Nope, nothing in latest image at least.
Does it happen in a fresh image?
> Stef
>
exception sounds reasonable to me, since you will usually know if a path exists
beforehand.
On 03.04.2014, at 14:14, Tudor Girba wrote:
> I think it should be either a NoDate object, or an exception.
>
> Doru
>
>
> On Thu, Apr 3, 2014 at 1:06 PM, Max Leske wrote:
> +1
>
> methods should r
On 3 avr. 2014, at 14:15, Tudor Girba wrote:
> I see it on Mac. On Windows it works fine. I thought this was a known issue.
Weird I'm on osx too and I see nothing.
In what image/VM does it happen for you?
>
> Doru
>
>
> On Thu, Apr 3, 2014 at 1:54 PM, Pharo4Stef wrote:
> Hi all
>
> do yo
It happens all the time on Mac. It is not so obvious in the default Pharo
image because of the background. In the Moose image, the background is
white and you see it immediately when resizing or dragging a window.
Doru
On Thu, Apr 3, 2014 at 2:16 PM, Camille Teruel wrote:
>
> On 3 avr. 2014, at
On 3 avr. 2014, at 14:21, Tudor Girba wrote:
> It happens all the time on Mac. It is not so obvious in the default Pharo
> image because of the background. In the Moose image, the background is white
> and you see it immediately when resizing or dragging a window.
I tried with many windows in
2014-04-03 13:21 GMT+01:00 Tudor Girba :
> It happens all the time on Mac. It is not so obvious in the default Pharo
> image because of the background. In the Moose image, the background is
> white and you see it immediately when resizing or dragging a window.
>
> Doru
>
>
> On Thu, Apr 3, 2014 at
Hi,
Here it is on the very latest of Pharo 3:
https://www.dropbox.com/s/hfi5j64e9kyim14/Screenshot%202014-04-03%2014.56.33.png
Pharo3.0 Latest update: #30811
'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid:
acc98e51-2fba-4841-a965-2975997bba66 Mar 20 2014
NBCogit NativeBoost-CogPlu
On 3 avr. 2014, at 14:58, Tudor Girba wrote:
> Hi,
>
> Here it is on the very latest of Pharo 3:
> https://www.dropbox.com/s/hfi5j64e9kyim14/Screenshot%202014-04-03%2014.56.33.png
Ok, now I remember that I had that once several months ago, but I don't
remember under which setting.
I solved i
On Thu, 3 Apr 2014, Igor Stasenko wrote:
On 3 April 2014 00:11, Sven Van Caekenberghe wrote:
Hi,
Is it possible to have a simple lock-free atomic counter in Pharo 3.0 ?
nextId
^ idCounter := idCounter + 1
Or is it still possible that two process entering th
Funny that you do not see the same issues.
I reproduce it consistently like this:
- On 10.9.2 on a MacBook Pro with Retina display
- Download the latest Pharo 3 and the latest VM and run it:
curl -L get.pharo.org/30+vmLatest | sh
- Open a workspace or any other window and drag it around
Doru
D
I hate to bust this old evilness out, but is it feasible to abuse
#become: for this purpose? I haven't used it in so long I don't
actually remember whether that's feasible semantics with ivars.
On Thu, Apr 3, 2014, at 09:08 AM, Levente Uzonyi wrote:
> On Thu, 3 Apr 2014, Igor Stasenko wrote:
>
>
2014-04-03 15:32 GMT+01:00 Serge Stinckwich :
> This is this kind of glitches (see screenshot) ?
> I already talk about that some months ago in the mailing-list.
>
Mine are usually more noticeable, but yes, something on those lines (pun
absolutely intended).
Cheers,
Sergi
2014-04-03 14:04 GMT+01:00 Camille Teruel :
> I solved it with 'start drawing/stepping again' as Sergi said.
>
But I said not to quote me! ;-)
Cheers,
Sergi
that happens in retina displays.
I’m aware… no time yet to fix it :(
Esteban, still on holidays
On 03 Apr 2014, at 11:32, Serge Stinckwich wrote:
> This is this kind of glitches (see screenshot) ?
> I already talk about that some months ago in the mailing-list.
>
> On Thu, Apr 3, 2014 at 3:11
Okay. One more time.
This is interference between Cairo and Freetype plugin..
if you using same font as rest of pharo (drawn outside of Athens)
and then the very same font for rendering with Athens,
then you will get weird font artifacts,
because in-image freetype code uses different scale units
On 03 Apr 2014, at 16:42, Esteban Lorenzano wrote:
> that happens in retina displays.
> I’m aware… no time yet to fix it :(
esteban do you think that this is related to the VM?
I would find that strange.
>
> Esteban, still on holidays
>
> On 03 Apr 2014, at 11:32, Serge Stinckwich wrote:
>
Hi guys
I need your brain cells.
When I execute the test
testBasic
| context process debugger printedString |
context := [ 20 factorial ] asContext.
process := Process
forContext: context
priority: Processor userInterruptPriority.
2014-04-03 17:33 GMT+01:00 Ben Coman :
> Can all those with the problem report their graphics card? My System >
> System Reporter > GFX Hardware Details are...
>
NVIDIA Geforce 630 here.
even using ensure: to make sure that the process is terminated it is not really
working.
I have the impression that there is a problem and that the tests does not
really finishes but this is really difficult to debug.
> Hi guys
>
> I need your brain cells.
>
> When I execute the test
>
> te
When I use
| context process |
context := [ 20 factorial ] asContext.
process := Process
forContext: context
priority: Processor userInterruptPriority.
[
debugger := Smalltalk tools debugger new
process: p
| context process debugger |
context := [ 20 factorial ] asContext.
process := Process
forContext: context
priority: Processor userInterruptPriority.
[
debugger := Smalltalk tools debugger new
process: pro
On Apr 2, 2014, at 12:10 PM, Goubier Thierry wrote:
> MCWorkingCopyBrowser>>basicSaveVersionIn:
> basicSaveVersionIn: aRepository
> | newVersion waitForVersion |
> waitForVersion := Semaphore new.
>
> UIManager default defer: [
> newVersion := workingCopy n
Can one of you do the following experience to let me know if I’m totally mad or
not?
1 - Add Transcript show:'initializePresenter'; cr.
in the SpecDebugger>>initializePresenter
as below:
initializePresenter
super initializePresenter.
Transcript show:'initializePresenter';
Indeed this is normal because initializeAutoRefresh does not exist!
So a nice endless loop.
On 03 Apr 2014, at 21:21, Pharo4Stef wrote:
> Can one of you do the following experience to let me know if I’m totally mad
> or not?
>
> 1 - Add Transcript show:'initializePresenter'; cr.
> in th
And now I understand because we forgot to remove this message sent when
removing the polling behavior of inspector.
On 03 Apr 2014, at 21:23, Pharo4Stef wrote:
> Indeed this is normal because initializeAutoRefresh does not exist!
> So a nice endless loop.
>
>
> On 03 Apr 2014, at 21:21, Pharo
ok now I understand: an endless loop inside the debugger creation. I do not
understand why we did not address it with clement
because we open the debugger and other when we fixed the logic of the inspector
(to avoid polling refresh).
Stef
On 03 Apr 2014, at 21:13, Pharo4Stef wrote:
>
> | cont
Could it be that one of the processes called from this code is specifically
setting the cursor back to normal? That would defeat the whole Cursor wait
showWhile: process.
Progress bars or other non-shared state do seem safer to utilize for core
activities like this.
-cbc
On Thu, Apr 3, 2014 at
Hi
I would like to know if the monkey is currently running and not stalled but I
cannot find the jenkins job doing it.
Stef
https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/
On 03 Apr 2014, at 22:02, Pharo4Stef wrote:
> Hi
>
> I would like to know if the monkey is currently running and not stalled but I
> cannot find the jenkins job doing it.
>
> Stef
On 3 April 2014 16:42, Esteban Lorenzano wrote:
> that happens in retina displays.
> I’m aware… no time yet to fix it :(
>
> Esteban, still on holidays
>
btw, again and again i forgetting ask you to show me what i should change
to disable "half resolution" mode
while on retina displays..
i wann
Hey,
I remembered removing the initializeAutoRefresh code from the debugger.
Perhaps I didn't commit that package. Or I forgot this one.
2014-04-03 12:34 GMT-07:00 Pharo4Stef :
> ok now I understand: an endless loop inside the debugger creation. I do
> not understand why we did not address it w
Okay, i think i got it..
Here is what happens:
- the font size is usually specified in points, not x@y points, but
typographical points,
which is
1/72 inch
TextStyle pointsToPixels: 14
TextStyle pointsToPixels: 14 => 18.668
pointsToPixels: points
^points * self pixelsPerInch /
On Fri, Apr 04, 2014 at 02:55:01AM +0200, Igor Stasenko wrote:
>
> there is one caveat, that if you really want to see exactly , say 16 points
> sized font on your screen,
> it is not possible without knowing the display resolution - how many pixels
> in one inch (hence
> #pixelsPerInch ).
> Unfor
I’m sorry but I will stop working on this issue since I do not have time for
pharo anymore this week and the next one.
Apparently I’m the only one to care about this bogus logic so let it be but be
prepared to have too many hanging process around.
Stef
> Hey,
>
> I remembered removing the ini
Igor
I was wondering the following: ? But TextStyle is not about strikefont?
Stef
On 04 Apr 2014, at 02:55, Igor Stasenko wrote:
> Okay, i think i got it..
>
> Here is what happens:
> - the font size is usually specified in points, not x@y points, but
> typographical points,
> which is
> 1
>
> I don't think there is any way for the VM to know the #pixelsPerInch of the
> display, regardless of the display resolution.
There is no api in the OS for that? It would be really strange that we cannot
know such information.
> Maybe that implies that some
> calibration would be needed in t
It is hard for everyone to get a complex issue cleanly integrated.
On 04 Apr 2014, at 08:30, Pharo4Stef wrote:
> I’m sorry but I will stop working on this issue since I do not have time for
> pharo anymore this week and the next one.
> Apparently I’m the only one to care about this bogus logic
55 matches
Mail list logo
