January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] need a working RFB server

by Luc Fabresse

2011/1/19 sergio_101 <sergiolist(a)village-buzz.com> > anyone know where i can find one? > > there used to be one here: > > http://source.lukas-renggli.ch/unsorted This one works well for me. #Luc > > > but it looks like it's down.. > > thanks! > > -- > ---- > peace, > sergio > photographer, journalist, visionary > > http://www.CodingForHire.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 > >

Jan. 19, 2011

Re: [Pharo-project] Any Clue..

by Schwab,Wilhelm K

Of course. But the IDE should be smart enough to prevent disaster. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Yanni Chiu [yanni(a)rogers.com] Sent: Wednesday, January 19, 2011 11:22 AM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Any Clue.. On 19/01/11 8:48 AM, Schwab,Wilhelm K wrote: > Sig, > > Are we discussing the same OS? What you are describing matches my experience on Windows; on Linux, AFAIK, one can just stomp all over the files and leave a mess. Perhaps something has changed to make it safer since I last trashed an image that way. > > I agree that there are times when it does not matter, so any safety mechanism needs to be optional, or better yet tied to a development session vs. a deployed session. > > Bill I run a common .image file that is interpreted multiple times with a different start up script. There is no .changes file. This works on MacOSX and Ubuntu. This is the behaviour I want to have, so such a "safety mechanism" would definitely need to be optional. -- Yanni

Jan. 19, 2011

Re: [Pharo-project] Any Clue..

by Yanni Chiu

On 19/01/11 8:48 AM, Schwab,Wilhelm K wrote: > Sig, > > Are we discussing the same OS? What you are describing matches my experience on Windows; on Linux, AFAIK, one can just stomp all over the files and leave a mess. Perhaps something has changed to make it safer since I last trashed an image that way. > > I agree that there are times when it does not matter, so any safety mechanism needs to be optional, or better yet tied to a development session vs. a deployed session. > > Bill I run a common .image file that is interpreted multiple times with a different start up script. There is no .changes file. This works on MacOSX and Ubuntu. This is the behaviour I want to have, so such a "safety mechanism" would definitely need to be optional. -- Yanni

Jan. 19, 2011

Re: [Pharo-project] Issue 3543 in pharo: Merge latest Glamour theme

by pharo＠googlecode.com

Updates: Cc: tudor.girba Comment #1 on issue 3543 by marcus.d...(a)gmail.com: Merge latest Glamour theme http://code.google.com/p/pharo/issues/detail?id=3543 I can not merge it 'Could not find version ''Glamour-Morphic-Theme-FernandoOlivero.23''. Maybe you need to add a repository?'

Jan. 19, 2011

Re: [Pharo-project] Issue 3509 in pharo: Multi-part MIME support for MailMessage

by Norbert Hartl

I'm not sure but I think there was a discussion about Zinc http components and how it will be integrated into pharo. What is the status on this? Seeing the issue report below I think there should be made some decision. Zinc has quite some good mime multipart support. No need to double efforts. Maybe the mime parts should factored out of Zinc and should be integrated first to make up a good mime support. Http based on mime can follow. Norbert On 19.01.2011, at 15:49, pharo(a)googlecode.com wrote: > Updates: > Status: Closed > > Comment #3 on issue 3509 by marcus.d...(a)gmail.com: Multi-part MIME support for MailMessage > http://code.google.com/p/pharo/issues/detail?id=3509 > > 13002 > >

Jan. 19, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2 Importance-High Comment #2 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 I just saw that, too. Horrible

Jan. 19, 2011

Re: [Pharo-project] Issue 3552 in pharo: Delete Package "DeleteMe"

by pharo＠googlecode.com

Comment #1 on issue 3552 by marianopeck: Delete Package "DeleteMe" http://code.google.com/p/pharo/issues/detail?id=3552 I think this is a test that it is not doing its dutty of deleting it in the #tearDown

Jan. 19, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Comment #1 on issue 3520 by Benjamin...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 Yes it's really boring ^^

Jan. 19, 2011

[Pharo-project] [update 1.3] #13002

by Marcus Denker

13002 ----- Issue 3422: Use UIManager instead of Workspace Issue 3509: Multi-part MIME support for MailMessage -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 19, 2011

Re: [Pharo-project] Issue 3509 in pharo: Multi-part MIME support for MailMessage

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3509 by marcus.d...(a)gmail.com: Multi-part MIME support for MailMessage http://code.google.com/p/pharo/issues/detail?id=3509 13002

Jan. 19, 2011