gmane.comp.lang.smalltalk.pharo.devel

Re: Working directory

Sean P. DeNigris — 2012-05-26T00:59:17

Igor Stasenko wrote

Oops, I took the error handler off the wrong call...
should have been

And, the question still stands as to whether OSP and FS should have two
separate concepts of the working directory...

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

Re: Working directory

Igor Stasenko — 2012-05-26T00:38:17

yeah.. one of the problems, that we're running Pharo image tests on
successfull build.

But these tests are not including the tests for "optional" components,
like OSProcess..
Because if we ship VM with PluginA, PluginB,
apparently we should run tests which testing those plugins, to check
that they are functional,
even if they are not used by default into Pharo image(s).

Re: Working directory

David T. Lewis — 2012-05-26T00:33:21

+1

Thanks Igor.

Dave

On Sat, May 26, 2012 at 02:13:34AM +0200, Igor Stasenko wrote:

Re: Progress bar in the top left

Schwab,Wilhelm K — 2012-05-26T00:28:47

There are times when it is necessary to protect the user from themselves.  Modal to a particular window can be a VERY good thing.

Several years ago, I remember watching in horror as my chairman was tinkering with a UI I had created that was not sufficiently modal, and he was at extreme risk of losing a lot of "work" as a result.  You had to be there...

BTW, he's a great guy and would have put it down to a learning experience for us both, not to mention a major bug report.  I promptly made it modal, and all was well for years after that.

Bill



________________________________________
From: pharo-project-bounces-bM+ny+RY8h+a+bCvCPl5/gCzwTLBPCX0< at >public.gmane.org [pharo-project-bounces< at >lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse< at >inria.fr]
Sent: Friday, May 25, 2012 9:12 AM
To: Pharo-project-bM+ny+RY8h+a+bCvCPl5/gCzwTLBPCX0< at >public.gmane.org
Subject: Re: [Pharo-project] Progress bar in the top left

I meant modal.


stef

Re: Working directory

Igor Stasenko — 2012-05-26T00:13:34

we should integrate the chdir fix to osprocess
into jenkins vms

On 25 May 2012 22:17, Sean P. DeNigris <sean-HdtZGoKLKd41HXoXgX+rmQ< at >public.gmane.org> wrote:

Re: Book search: PL history and paradigms

Frank Shearar — 2012-05-25T22:20:24

Well, objects are closures, so it makes sense to say that Java has
closures. It doesn't have _lightweight_ closures with a decent syntax,
but it does still have closures!

Message passing is "message passing concurrency", which isn't the
"message passing" in "message passing vs method invocation".

Of course, the chart isn't meant to imply that some language X with
paradigms A, B and C can't support paradigm D: you can, for instance,
implement the logic programming paradigm in Scheme (miniKanren),
Clojure (core.logic) and, well, not in Smalltalk yet (other than the
embedded Prologs) because I haven't finished Nutcracker yet!

frank

On 25 May 2012 22:56, Hernan Wilkinson <hernan.wilkinson-3GCau816QQ9BDgjK7y7TUQ< at >public.gmane.org> wrote:

Re: Book search: PL history and paradigms

Hernan Wilkinson — 2012-05-25T21:56:54

I have not read the book, but seeing the principal programming paradigm
poster makes me think about how good it is because Java and Smalltalk are
wrongly categorized, at least for what I understand of the poster (java
with closure, smalltalk not in the message passing category)

On Wed, May 23, 2012 at 8:11 AM, Frank Shearar <frank.shearar-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

Re: Book search: PL history and paradigms

Max Leske — 2012-05-25T21:32:08

Thanks Frank, I'll take a look at those.

Cheers,
Max


On 23.05.2012, at 13:11, Frank Shearar wrote:

Re: InputEventFetcher depending on Cursor and Form

Igor Stasenko — 2012-05-25T21:24:06

There is no reason to setup event fetcher, if there is nobody to
consume events (like Morphic) in image.

I would

1. remove event fetcher registration from startup list
2. change

MorphicUIManager>>onSnapshot: resuming
"The resuming argument is true when image boots from disk,
and false, if user just did an image snapshot."

"if we resuming, check if we're still interactive "

resuming ifTrue: [
Smalltalk isInteractive ifFalse: [
^ self nonInteractiveManager onSnapshot: resuming ].
Smalltalk isHeadless ifTrue: [
^ self headlessManager onSnapshot: resuming ]].

+++ InputEventFetcher startup.

SystemWindow wakeUpTopWindowUponStartup
---------------
then we no need to guess where to put Sensor in startup sequence,
because it will start up in right place, right before the guy who
going to consume events.
Starting it up before this place makes little sense anyways - no
events will be handled.
Shutdown then can be thrown out..

As a bonus, there will be no pointless shutdown/startup when you savi

Working directory

Sean P. DeNigris — 2012-05-25T20:17:25

When OSProcess is integrated, we will have two different concepts of the
working directory:
  fsPwd := '/Volumes/Sean''s Universe/sean/.jenkins/jobs/Dynabook/'
asFileReference.
  [ FileSystem disk changeDirectory: fsPwd ] on: Exception do: [].
  FileSystem disk workingDirectory = fsPwd. "true"

  ospPwd := '/Volumes/Sean''s
Universe/sean/.jenkins/jobs/Dynabook/workspace'.
  OSProcess thisOSProcess chDir: ospPwd.
  FileSystem disk workingDirectory = ospPwd. "false"
  (PipeableOSProcess command: 'pwd') output trimRight = ospPwd "true"

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

Re: loading athens - a user perspective

Igor Stasenko — 2012-05-25T17:35:14

No, but frankly, please tell me what was unclear to you, and why you
thought that sending a trace
will be helpful to resolve the problem.
Because this is not a bug, and behavior is correct, so what that trace
serves for?

Re: loading athens - a user perspective

Serge Stinckwich — 2012-05-25T16:51:41


Envoyé de mon iPhone

Le 25 mai 2012 à 20:23, Igor Stasenko <siguctua-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> a écrit :


Ahah, so maybe I will send more useless stack traces ;-)

Pharo Sprint – Saturday 10h00 – RMoD Lab

Camillo Bruni — 2012-05-25T14:09:06

We would like to invite you to a Pharo Sprint on saturday at 10h00:

http://www.doodle.com/t5uv5fhmm7adi6cs

It will be held in the RMoD lab:

http://rmod.lille.inria.fr/web/pier/contact

The entrance will be closed and can only be opened with a badge.
For those who standing in front of a closed door, call one of the 
following badge-owners:

Camillo Bruni+33 7 86 95 40 78
Marcus Denker+33 3 62 65 52 58

see you!

SmallInteger>>digitAt: protocol

Sean P. DeNigris — 2012-05-25T15:16:47

Maybe a small matter, but SmallInteger>>digitAt: is in the "system
primitives" protocol, even though it doesn't call a primitive. OTOH,
LargePositiveInteger does use a primitive for #digitAt:

--
View this message in context: http://forum.world.st/SmallInteger-digitAt-protocol-tp4631830.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

InputEventFetcher depending on Cursor and Form

Guillermo Polito — 2012-05-25T13:40:15

Does InputEventFetcher really depend on Cursor & Form to install/uninstall
the event fetch process?

install
    "InputEventFetcher install"

    Smalltalk addToStartUpList: self after: Cursor.
    Smalltalk addToShutDownList: self after: Form.

    Default := self new.
    Default startUp


Guille

Re: loading athens - a user perspective

Igor Stasenko — 2012-05-25T13:23:26

Should i put more elaborate error message?
A 'function unavailable' is exception which you get when... function
is not available.

I just thinking how to prevent receiving a huge and worthless stack traces. :)
One way is of course write documentation.. :)


On 25 May 2012 12:39, Serge Stinckwich <serge.stinckwich< at >gmail.com> wrote:

Re: Progress bar in the top left

Stéphane Ducasse — 2012-05-25T13:12:16

I meant modal.


stef

Re: Bug fixes for 1.4

Stéphane Ducasse — 2012-05-25T12:58:19

On May 24, 2012, at 11:55 PM, Sean P. DeNigris wrote:


Sometimes we miss/forget to tag important fixes to be put back in

[update 2.0] #20095

Marcus Denker — 2012-05-25T12:40:21

20095
-----

Issue 5971:Nautilus: Opening issue when opening on a method
http://code.google.com/p/pharo/issues/detail?id=5971

Issue 5970:CommandLine eval does not work completely
http://code.google.com/p/pharo/issues/detail?id=5970

Issue 5962:62 tests failing after integrating Issue 5755:
http://code.google.com/p/pharo/issues/detail?id=5962

Issue 5972:Clean in perform: aSelector orSendTo: another
http://code.google.com/p/pharo/issues/detail?id=5972



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

Re: loading athens - a user perspective

Fernando Olivero — 2012-05-25T12:18:30

You shouldnt use Brew, because it cant compile universal binaries.

Athens, with a  cairo backend, uses NativeBoost which needs 32 bit
libraries, because CogGM is targeted to 32 bits.

I also tried with Brew, that's why i found out is hard to instruct
brew to compile universal binaries.

Fernando

On Fri, May 25, 2012 at 12:39 PM, Serge Stinckwich
<serge.stinckwich-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Monitoring Seaside using ruby god.

mail list — 2012-05-25T12:06:03

I have had some great success monitoring three seaside images serving  an email application.  I thought I would share the script as it offers more features than using daemontools and I have been using ruby god for years now so I am quite comfortable with its stability.

Ruby God:  http://godrb.com

My application admin.ses.sg.estormtech.com/ficonabemail

My god script.
changes directory to the image directory [seaside_root]
monitors http, memory usage and cpu usage and restarts its.
send an email if this happens.  If you want the contact script, just drop me an email.  (the c.notify below).  (You can also find it on github)

Scott

- i receive an email when the image has to be restarted similar to below... 
Message: seaside2 [trigger] process 11692 exited {:exit_code=>6, :pid=>11692, :thread_group_id=>11692, :exit_signal=>17} (ProcessExits)
Host: xxxxxx
Priority: 
Category: 



SEASIDE_GROUPS ={:seaside1=> {},:seaside2=>{}, :seaside3=>{} }
SEASIDE_GROUPS[:seaside1]={:group => "seaside1",:seaside_root =>  "/v