- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo sprint @ lille Friday 21 of January

by Benjamin Van Ryseghem

I'll be there ^^ Ben 2011/1/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > we will have a pharo sprint at Lille Friday 21 of January. If you want to > join let us know that we organize for the food. > The sprint will happen in our rooms at LIFL > http://rmod.lille.inria.fr/web/pier/contactr/ > > Stef >

Jan. 9, 2011

Re: [Pharo-project] Issue 3521 in pharo: StringMorphEditor doesn't work

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3521 by aplantec: StringMorphEditor doesn't work http://code.google.com/p/pharo/issues/detail?id=3521 in InBox SLICE-Issue-3521-StringMorphEditor-doesnt-work

Jan. 9, 2011

[Pharo-project] Issue 3521 in pharo: StringMorphEditor doesn't work

by pharo＠googlecode.com

Status: Accepted Owner: aplantec Labels: Milestone-1.2 New issue 3521 by aplantec: StringMorphEditor doesn't work http://code.google.com/p/pharo/issues/detail?id=3521 Used to edit a StringMorph is the 'string morph are editable' is set to true. Do we need that ?

Jan. 9, 2011

[Pharo-project] SqueakSSL Plugin for Mac OS X

by Sven Van Caekenberghe

On 04 Jan 2011, at 18:16, Sven Van Caekenberghe wrote: > Hi, > > Has anyone got the Squeak SSL plugin [1] to work on Mac OS X, more specifically for the Cog VM family, Pharo 1.1.1 or later and Mac OS X 10.6.5 ? If not, is there some how to guide on building plugins ? > > TIA, > > Sven > > [1] http://www.squeaksource.com/SqueakSSL I have found the Google project website for the plugin: http://code.google.com/p/squeakssl/ where binary versions of the plugin can be downloaded for Windows, Mac and Linux. I got this to work in a Cog VM on Mac OS X, however not without at least one problem: SqueakSSL>>#certState always returns -1 on Mac OS X simply because this is hardcoded in sqMacSSL.c: 248: /* We are connected. Verify the cert. */ 249: ssl->state = SQSSL_CONNECTED; 250: ssl->certFlags = -1; While on Linux, in in sqUnixOpenSSL.c: 292: /* Check the result of verification */ 293: result = SSL_get_verify_result(ssl->ssl); 294: if(ssl->loglevel) printf("sqAcceptSSL: SSL_get_verify_result = %d\n", result); 295: /* FIXME: Figure out the actual failure reason */ 296: ssl->certFlags = result ? SQSSL_OTHER_ISSUE : SQSSL_OK; Still not a full implementation, but better (and others report SqueakSSL is working on Linux). The OpenSSL calls used on Linux seem to exist identically on Mac OS X. (BTW, there are two instances of this code in the C file.) Changing the example code in SqueakSSL class>>google: to skip the certState check: "Verify that the cert is valid" ssl certState = 0 ifFalse:[ self error: 'The certificate is invalid (code: ', ssl certState,')'. ]. Results in a working example. If I only knew how to recompile the plugin I could try to build a better one, I have however never done this (nor built a VM). Is there anybody else interested in helping out ? Sven

Jan. 9, 2011

Re: [Pharo-project] Gofer problem installing packages with the same name

by Lukas Renggli

No, Gofer doesn't look in repositories you don't specify. However, it uses and prefers your local package-cache if it contains a newer version of your package (which is likely the case in your example). You can disable the package-cache by sending something like #disablePackageCache to your Gofer instance (I don't have an image at hand right now, but you find it in the code and documentation). Gofer is part of Pharo and not maintained in my repository anymore. This #update method should be removed it is not supposed to work anymore. Lukas On Sunday, 9 January 2011, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi list, > I have some issues with Gofer, maybe already known. When I evaluate: > > Gofer new > Â Â Â Â squeaksource: 'Subjectivity'; > Â Â Â Â package: 'Subjectivity'; > Â Â Â Â load. > > it seems that Gofer takes the first package named Subjectivity it > founds which in this case is > http://www.squeaksource.com/Decisionstrategy.html while I wanted to > take it from http://www.squeaksource.com/Subjectivity.html (please see > the screenshot). > After then I've tried to update "Gofer upgrade" for a fix, but it > seems it cannot connect to http://source.lukas-renggli.ch and then > entered in an endless loop. Any hint? > (Using Pharo1.2beta Latest update: #12294) > > Cheers, > > -- > HernÃ¡n Morales > Information Technology Manager, > Institute of Veterinary Genetics. > National Scientific and Technical Research Council (CONICET). > La Plata (1900), Buenos Aires, Argentina. > Telephone: +54 (0221) 421-1799. > Internal: 422 > Fax: 425-7980 or 421-1799. > -- Lukas Renggli www.lukas-renggli.ch

Jan. 9, 2011

[Pharo-project] Gofer problem installing packages with the same name

by HernÃ¡n Morales Durand

Hi list, I have some issues with Gofer, maybe already known. When I evaluate: Gofer new squeaksource: 'Subjectivity'; package: 'Subjectivity'; load. it seems that Gofer takes the first package named Subjectivity it founds which in this case is http://www.squeaksource.com/Decisionstrategy.html while I wanted to take it from http://www.squeaksource.com/Subjectivity.html (please see the screenshot). After then I've tried to update "Gofer upgrade" for a fix, but it seems it cannot connect to http://source.lukas-renggli.ch and then entered in an endless loop. Any hint? (Using Pharo1.2beta Latest update: #12294) Cheers, -- HernÃ¡n Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.

Jan. 9, 2011

Re: [Pharo-project] Issue 3514 in pharo: Failing Test: NewTextMorphTests.testAcceptContents

by pharo＠googlecode.com

Comment #3 on issue 3514 by stephane.ducasse: Failing Test: NewTextMorphTests.testAcceptContents http://code.google.com/p/pharo/issues/detail?id=3514 Thanks. I need to relax from proposal writing and I will do some integration after.... (but I need to read a phd).

Jan. 9, 2011

[Pharo-project] Pharo sprint @ lille Friday 21 of January

by StÃ©phane Ducasse

Hi guys we will have a pharo sprint at Lille Friday 21 of January. If you want to join let us know that we organize for the food. The sprint will happen in our rooms at LIFL http://rmod.lille.inria.fr/web/pier/contactr/ Stef

Jan. 9, 2011

Re: [Pharo-project] Issue 3514 in pharo: Failing Test: NewTextMorphTests.testAcceptContents

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 3514 by aplantec: Failing Test: NewTextMorphTests.testAcceptContents http://code.google.com/p/pharo/issues/detail?id=3514 just make EditableTextMorph understand #enableTextChange EditableTextMorph>>enableTextChange ^ self enabled Fixed SLICE-Issue-3514-Failing-Test-NewTextMorphTeststestAcceptContents

Jan. 9, 2011

Re: [Pharo-project] wiki style help

by Alain Plantec

super then. I open an issue Alain Le 08/01/2011 15:16, StÃ©phane Ducasse a Ã©crit : > Ok I suggest to integrate that in 1.2 because this is important. > > Now let me open a big can of worms but we truly need it. > When you write documentation (I did several experiments with Soup) the documentation in class comment is cool because you to not have to have > " and " and '' ' ' '' '" everytimes you manipulate a string or a comment. > Now you do not want to have huge class comments I would prefer to have a couple of methods and it does not work: you put back the crappy unnestable " > ugly boring.... better not putting comments. > > So I would really like to have > */ this is a nice nestable comment > > "hkjkhhkjh " > 'hkjjkh' > 1 + 2 > > */yet another comment: increbile this is a nested ones: yes you know > Smalltalkers are discovering the world/* > > /* > > As you see stealing the C comment syntax is a plus because everybody knows it. > I remember a discussion on VW about possible syntax to support that. > Before replying to this point thing hard because we need that support. > > Stef > > > On Jan 8, 2011, at 10:15 AM, Alain Plantec wrote: > >> Hi all, >> very cool, thanks Torsten. >> Now, I think it's better to wait 1.3 because 1.2 >> is almost ready ... >> and I would use $! instead of $= as section >> marker to keep Pier compatibility. >> Cheers >> Alain >> Le 07/01/2011 14:16, Torsten Bergmann a Ã©crit : >>> Hi, >>> >>> Nice idea, I like the "wiki help description" for three reasons: >>> >>> - its pragma based AND allows for definition of structured books >>> (so Lukas should be satisfied since he can define content >>> without dependency on help system) >>> >>> - it allows us to reuse existing swiki contents >>> (if the full syntax is supported we can query existing >>> swikis!) >>> >>> So it is a nice idea and would be a good addition. >>> >>> >>> I reworked Alains code to better fit the pluggable architecture >>> of the HelpSystem framework (now using a builder): >>> >>> Use an updated 1.2 core image, code is attached >>> >>> 1. File in "Foo.st" (which defines a simple help description) >>> => no dependency on any help system >>> >>> 2. First I added a registration mechanism (pragma<systemHelp> >>> so one can add own help types to the system help >>> (the one that appears when you open the default help browser) >>> >>> => load "AddToSystemHelpFix.1.cs" >>> => at least this fix should go into Core 1.2, so >>> no ugly hacks are necessary to appear in the >>> default help browser >>> >>> I added a now fixed issue for core 1.2 on: >>> http://code.google.com/p/pharo/issues/detail?id=3511 >>> >>> 3. I reworked Alains code so it uses a WikiStyleHelpBuilder >>> (similar to the other builders) and a WikiStyleHelp as >>> a new help type >>> >>> => see WikiStyleHelp.5.cs >>> => if we agree on this we can integrated it into core too, >>> currently it is in an own class category/package >>> => "HelpBrowser openOn: WikiStyleHelp" >>> will show all contents defined using the wiki style syntax, >>> so only the one defined in class Foo appears >>> => "HelpBrowser open" >>> will show all help in the system (including the ones >>> defined in Foo) >>> => since it uses the new registration mechanism (see 2. above) >>> all these topics will also appear in the help browser >>> that is accessible from the menu >>> >>> I would vote for adding this to core 1.2 too. It's additional, >>> nothing should break. What do you all think... >>> >>> And thanks Alain for the idea and initial code!!! >>> >>> Have fun >>> T. >>> >>> >>> >>> >>> >>> >>> >> >

Jan. 9, 2011