- Pharo-dev - lists.pharo.org

[Pharo-project] TFLogin Recaptcha component error

by Dario Trussardi

Hi Tony, i hope this is right reference for signal the problem. I have load the TFLogin into Pharo1.1.1. After i set the captcha key and register the TLTestApp When open in the browser the LoginTestApp the system erase the error: MessageNotUnderstood: BWRecaptchaComponent class>>ajax setRecaptchaComponent | recaptchaClass | captchaComponent := ((recaptchaClass := (Smalltalk at: #BWRecaptchaComponent ifAbsent: [ nil ])) isNil ifFalse: [ captchaComponent ifNil: [ recaptchaClass ajax ]] ifTrue: [ nil ]) I answer proced. Now the standard register option work fine and show the captcha component. When i open the AJAX rendering and do the register option the captcha component is not render. Thank, Dario

March 23, 2011

Re: [Pharo-project] Pharo 1.2 red again

by Dale Henrichs

If someone changes a configuration version directly ... instead of creating a new version, this could happen ... Dale On Mar 23, 2011, at 5:26 AM, Marcus Denker wrote: > > On Mar 23, 2011, at 12:52 PM, Torsten Bergmann wrote: > >> Pharo 1.2 is red again! >> >> DuplicatedVariableError: stylingActive is already defined in Workspace >> >> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/195/ > > > We really need to make sure that the config does not load code if we don't explicitly say so. > > So what code was changed? Why was it loaded? > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 23, 2011

Re: [Pharo-project] [TODO 1.2] TODO list for releasing Pharo Full 1.2

by Miguel CobÃ¡

El miÃ©, 23-03-2011 a las 14:41 +0100, Marcus Denker escribiÃ³: > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage > > 1. 1.2 Build is broken > 2. 1.2 Config needs to load latest code from OB Repository > (or not. Maybe we should just release 1.2.1 and do that in 1.2.2) No. This is the reason the build is sometimes green some times red in hudson. The versions refered by configuration should be frozen to a given version number forever. That is, #stable, #latestVersion, #bleedingEdge and so should be banned from Pharo configurations when building a release. They are ok for end users that just want a version that works in the image they have in front of them, but not for releases, that should be repeteable! > > maybe these we push to 1.2.2: > > 3. Omnibrowser's an extra horizontal scrollbar > 4. In OB: Text in comment pane of Browser uses syntax highlighting > > 5. Update Hudson One-Click build files for 1.2 > > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

March 23, 2011

Re: [Pharo-project] Pharo 1.2 red again

by Miguel CobÃ¡

I mean, the most probable reason for this is that some configuration refers some symbolic version like #stable, #bleedingEdge and that package was updated so that there is a new #stable version whose tests aren't green in Pharo and whose previous-version tests were all green. Cheers El miÃ©, 23-03-2011 a las 13:26 +0100, Marcus Denker escribiÃ³: > On Mar 23, 2011, at 12:52 PM, Torsten Bergmann wrote: > > > Pharo 1.2 is red again! > > > > DuplicatedVariableError: stylingActive is already defined in Workspace > > > > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/195/ > > > We really need to make sure that the config does not load code if we don't explicitly say so. > > So what code was changed? Why was it loaded? > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

March 23, 2011

Re: [Pharo-project] Pharo 1.2 red again

by Miguel CobÃ¡

Maybe we should ask Dale when time permits to add functionality to Metacello so that can check all the dependencies for a given configuration and make sure (or raise some warning in the validation) that some dependency is refered by a symbolic non numeric version (like #stable, #latestVersion, #bleedingEdge) so that this validation can be run by hudson also and verify that all the configurations are frozen to a given number and no dependent on a symbolic version that can change anytime after release of Pharo when a package get a new (#stable for example) version. Cheers El miÃ©, 23-03-2011 a las 13:26 +0100, Marcus Denker escribiÃ³: > On Mar 23, 2011, at 12:52 PM, Torsten Bergmann wrote: > > > Pharo 1.2 is red again! > > > > DuplicatedVariableError: stylingActive is already defined in Workspace > > > > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/195/ > > > We really need to make sure that the config does not load code if we don't explicitly say so. > > So what code was changed? Why was it loaded? > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

March 23, 2011

[Pharo-project] Issue 3854 in pharo: Move taskbar methods from Project to PasteUpMorph

by pharo＠googlecode.com

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3854 by marcus.d...(a)gmail.com: Move taskbar methods from Project to PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3854 Move taskbar methods from Project to PasteUpMorph They look happier there, too. (even though it is a bit crowded). Attachments: MoveTaskBarToWorld.2.cs 1.8 KB

March 23, 2011

Re: [Pharo-project] Magritte extension dealing with graphics

by Schwab,Wilhelm K

Stef, I am fairly certain that morphic/Polymoprh extensions exist. IIRC, it was written up in thesis from your group. Is that what you need, or are you looking for something different? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Wednesday, March 23, 2011 4:11 AM To: Pharo Development Subject: [Pharo-project] Magritte extension dealing with graphics Hi did one of you extended magritte to deal with graphics (Form, InageMorph...)? Stef

March 23, 2011

Re: [Pharo-project] Issue 3841 in pharo: clean Project more: remove Locale and project parameters

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3841 by marcus.d...(a)gmail.com: clean Project more: remove Locale and project parameters http://code.google.com/p/pharo/issues/detail?id=3841 in 13106

March 23, 2011

[Pharo-project] [update 1.3] #13106

by Marcus Denker

13106 ----- Issue 3844: Utilities is in StartupList Issue 2488: LargeInteger ln overflows Issue 3847: The absolute value of a negativeZero should behave like a positive zero Issue 3841: clean Project more: remove Locale and project parameters -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 23, 2011

Re: [Pharo-project] Issue 3847 in pharo: The absolute value of a negativeZero should behave like a positive zero

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3847 by marcus.d...(a)gmail.com: The absolute value of a negativeZero should behave like a positive zero http://code.google.com/p/pharo/issues/detail?id=3847 in 13106

March 23, 2011