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

Re: [Pharo-project] How to encrypt a password?

by Gary Chambers

If anyone is interested we have some stuff that can read/write KeyedTrees as XML files (registry type of configs but with proper objects (storeString based)). Regards, Gary ----- Original Message ----- From: Mariano Martinez Peck To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, October 26, 2011 5:05 PM Subject: Re: [Pharo-project] How to encrypt a password? On Wed, Oct 26, 2011 at 5:54 PM, John Toohey <jt(a)parspro.com> wrote: Off topic, but is the use of a .pharoconf file documented somewhere? No at all. Pharo does know nothing about it. It is just a plain file you can create and read stuff from there...just as any other file in any other language :) On Wed, Oct 26, 2011 at 05:12, Francois Stephany <tulipe.moutarde(a)gmail.com> wrote: >> But I didn't want to put such password in the code... at >> the end what I did (because my scenario is really stupid and only for >> me), is to read the password from a file in my machine :) hahahahha >> > > That would be the kind of thing that belongs to a .pharoconf file in your > /home directory ;) > > -- ~JT -- Mariano http://marianopeck.wordpress.com

Oct. 26, 2011

Re: [Pharo-project] How to encrypt a password?

by Mariano Martinez Peck

On Wed, Oct 26, 2011 at 5:54 PM, John Toohey <jt(a)parspro.com> wrote: > Off topic, but is the use of a .pharoconf file documented somewhere? > No at all. Pharo does know nothing about it. It is just a plain file you can create and read stuff from there...just as any other file in any other language :) > On Wed, Oct 26, 2011 at 05:12, Francois Stephany > <tulipe.moutarde(a)gmail.com> wrote: > >> But I didn't want to put such password in the code... at > >> the end what I did (because my scenario is really stupid and only for > >> me), is to read the password from a file in my machine :) hahahahha > >> > > > > That would be the kind of thing that belongs to a .pharoconf file in your > > /home directory ;) > > > > > > > > -- > ~JT > > -- Mariano http://marianopeck.wordpress.com

Oct. 26, 2011

Re: [Pharo-project] How to encrypt a password?

by John Toohey

Off topic, but is the use of a .pharoconf file documented somewhere? On Wed, Oct 26, 2011 at 05:12, Francois Stephany <tulipe.moutarde(a)gmail.com> wrote: >> But I didn't want to put such password in the code... at >> the end what I did (because my scenario is really stupid and only for >> me), is to read the password from a file in my machine :) Â hahahahha >> > > That would be the kind of thing that belongs to a .pharoconf file in your > /home directory ;) > > -- ~JT

Oct. 26, 2011

[Pharo-project] [update 1.4] #14209

by Marcus Denker

14209 ----- Issue 4911: Run failures is broken http://code.google.com/p/pharo/issues/detail?id=4911 Issue 4935: Rectangle Cleanup http://code.google.com/p/pharo/issues/detail?id=4935 -- Marcus Denker -- http://marcusdenker.de

Oct. 26, 2011

[Pharo-project] [update 1.3] #13318

by Marcus Denker

13318 ----- Issue 4932: Emergency evaluator http://code.google.com/p/pharo/issues/detail?id=4932 Issue 4919: Class copying issues http://code.google.com/p/pharo/issues/detail?id=4919 -- Marcus Denker -- http://marcusdenker.de

Oct. 26, 2011

[Pharo-project] [update 1.4] #14208

by Marcus Denker

14208 ----- Issue 4932: Emergency evaluator http://code.google.com/p/pharo/issues/detail?id=4932 Issue 4931: dragAnimationFor:transferMorph: is sent but not implemented http://code.google.com/p/pharo/issues/detail?id=4931 Issue 4919: Class copying issues http://code.google.com/p/pharo/issues/detail?id=4919 -- Marcus Denker -- http://marcusdenker.de

Oct. 26, 2011

Re: [Pharo-project] Emergency evaluator

by Marcus Denker

On Oct 26, 2011, at 1:58 PM, Gary Chambers wrote: > Hi. > > At least on Windows with Pharo 1.4a #14168, Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.54] > it seems that key down events come out capitalised. This results in only being able to type > capitals in the emergency evaluator which won't understand the commands. > > Fix attached to use key stroke instead of key down. Thanks, added an issue: http://code.google.com/p/pharo/issues/detail?id=4932 -- Marcus Denker -- http://marcusdenker.de

Oct. 26, 2011

[Pharo-project] Emergency evaluator

by Gary Chambers

Hi. At least on Windows with Pharo 1.4a #14168, Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.54] it seems that key down events come out capitalised. This results in only being able to type capitals in the emergency evaluator which won't understand the commands. Fix attached to use key stroke instead of key down. Regards, Gary

Oct. 26, 2011

Re: [Pharo-project] startup errors

by Igor Stasenko

On 26 October 2011 11:51, Andrea BrÃ¼hlmann <a.bruehlmann(a)netstyle.ch> wrote: > I tried it with this option now, but it did not solve the problem, because > it just saved a new version of the image and quit, but did not open a > debugger. Opening the new version does the same as the original. Did I miss > something? > It should open a debugger. if not, then this is a bug :) It might be, that if error happens in startup phase, then it is not opens a debugger. > I would appreciate a command line option that either opens a debugger or > ignores the errors, because like this you usually have a clean image but if > you have a problem, you can open the image and do something. > > Andrea > > Igor Stasenko schrieb: >> >> On 25 October 2011 23:26, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >>> >>> Sig, >>> >>> All too true, and very pure. Â But what if I just want to save a package, >>> or some data, that might be locked away in the image? Â Â Code is generally >>> safe, since one can recover lost changes into a healthy image, but there can >>> still be other data lurking in an image. >>> >>> A middle-ground approach would be to have command line option that lets >>> the image run. Â One should run w/o it to bring errors to attention, but at >>> least it would be possible to override and at least have an opportunity to >>> recover endangered bits. >>> >> look at settings, there's already an option to save a new version of >> image before quit. >> if you turn this option on, then any unhandled error will open a >> debugger if you open an image saved in such state. >> >>> Bill >>> >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko >>> [siguctua(a)gmail.com] >>> Sent: Tuesday, October 25, 2011 9:40 AM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] startup errors >>> >>> On 24 October 2011 11:40, Andrea BrÃ¼hlmann <a.bruehlmann(a)netstyle.ch> >>> wrote: >>>> >>>> It seems that pharo 1.3 introduced that the image quits if an error >>>> happens >>>> during startup. What are the reasons for this? >>>> >>> The reasons are simple: >>> if image fails to startup properly, there are no way to tell, if some >>> services initialized properly or not (UI is one of them), >>> and so, there are no any guarantees that image could run safely. >>> So, the best thing which you can do is to write error to log and quit. >>> >>> This is because startup manager knows what to start-up and in what >>> order, but it doesn't knows, how critical a given service for properly >>> running the whole image. Therefore, if you don't handle startup errors >>> in your service code, a startup manager has no other choice , but just >>> leave to OS. >>> >>> >>>> Or what's the state of the email below? >>>> >>>> Andrea >>>> >>>> >>>> Camillo Bruni schrieb: >>>>> >>>>> While working on Coral we encountered a rather annoying behavior of >>>>> pharo >>>>> images when starting up. >>>>> >>>>> We wanted to check if we can debug the CoralScriptLoader, but of corse >>>>> since this happens at image startup time this is not a good ideaâ¦ >>>>> HOWEVER we >>>>> were no longer able to run the image as it immediately crashes during >>>>> the >>>>> startup. >>>>> >>>>> Now I wonder if it would make sense to add a couple of on:do: in >>>>> SmalltalkImage >> snapshot:anQuit: to collect the errors of all the >>>>> startup >>>>> scripts and then only show them after all other startupListItems are >>>>> processed. >>>>> >>>>> All in all the behavior would not much differ from what is going on >>>>> right >>>>> now, but would prevent stupid users like me from losing a whole image. >>>>> >>>>> camillo >>>>> >>>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >>> >>> >> >> >> > > -- > AB Â Â | Â ANDREA BRÃHLMANN Â· SOFTWARE ENGINEER > Â Â Â | Â NETSTYLE Â· TERRASSENWEG 18 Â· CH-3012 BERN > Â Â Â | Â TEL Â +41 31 356 42 54 Â· FAX Â +41 31 356 42 51 > Â Â Â | Â WWW.NETSTYLE.CH Â· A.BRUEHLMANN(a)NETSTYLE.CH > > -- Best regards, Igor Stasenko.

Oct. 26, 2011

Re: [Pharo-project] Text for 1.3 announcement?

by StÃ©phane Ducasse

Here is a try We are proud to announce the release of 1.3 of Pharo. This new release is the result of active development from the community and it is composed of: - Cleaning architectural dependencies - Applying code critics to the complete system - Support for server and headless images. Pharo has now a support for stdin, stdout and stderr. - More robust and better startup/shutdown - Better look and feel - Better widgets - Better tools - Weak Announcements - Stratified Proxy - More class comments. - Network improvements based on Zinc And a lot more. A partial but more precise list of changes is available at: http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotThree Remember our goal: we want pharo to be a solid language to build the next generation of systems. Stef marcus can we add this text inside the image and a link on the 1.3 page On Oct 21, 2011, at 8:48 AM, Marcus Denker wrote: > Hi, > > We should officially announce 1.3... > > For that we need a short text to be posted as a news: > > http://www.pharo-project.org/news > > Anyone interested in writing it? > > > -- > Marcus Denker -- http://marcusdenker.de > >

Oct. 26, 2011