[Pharo-project] Finder?

this is strange since 1234 numberOfDigitsInBase: 10 -> 4 but the finder does not report it for 1234 . 10 . 4 Stef

[Pharo-project] SqueakSource3 (was: Re: Pharo Sources Google Hit Ratio)

Am 2011-02-22 um 23:59 schrieb Stéphane Ducasse: > what is squeaksource3? > when did it start? > Stef > > I do not know the exact circumstances of squeaksource's amazing low > google index, but I think we can change this. Set up some Seaside servers for Google to crawl? >>> >

Re: [Pharo-project] SqueakSource3 (was: Re: Pharo Sources Google Hit Ratio)

On Fri, Feb 25, 2011 at 10:14 AM, Tobias Pape wrote: > Am 2011-02-22 um 23:59 schrieb Stéphane Ducasse: > > what is squeaksource3? > > when did it start? > > Stef > > > > I do not know the exact circumstances of squeaksource's amazing low > > google index, but I think we can change this.

Re: [Pharo-project] SqueakSource3 (was: Re: Pharo Sources Google Hit Ratio)

On 2011-02-25, at 10:19, laurent laffont wrote: > On Fri, Feb 25, 2011 at 10:14 AM, Tobias Pape wrote: > >> Am 2011-02-22 um 23:59 schrieb Stéphane Ducasse: >>> what is squeaksource3? >>> when did it start? >>> Stef >>> >>> I do not know the exact circumstances of squeaksource's amazing lo

[Pharo-project] Issue 3756 in pharo: Browser title

Status: Accepted Owner: aplan...@gmail.com New issue 3756 by aplan...@gmail.com: Browser title http://code.google.com/p/pharo/issues/detail?id=3756 'class' is always added even an instance method is browsed

Re: [Pharo-project] Issue 3756 in pharo: Browser title

Updates: Status: Fixed Labels: Milestone-1.3 Comment #1 on issue 3756 by aplan...@gmail.com: Browser title http://code.google.com/p/pharo/issues/detail?id=3756 SLICE-Issue-3756-Browser-title

Re: [Pharo-project] [COTDC] 18 - SMxMorphicAlarm

On Feb 24, 2011, at 8:49 46PM, laurent laffont wrote: > Finally a funny class ;) > > I rephrase a little: > > I represent a message sent to be scheduled by the SMxWorldState. I'm the > exact duplicate of MorphicAlarm in the Simple Morphic world (see MorphicAlarm > comment). > > > And in Mor

Re: [Pharo-project] Finder?

On Feb 25, 2011, at 10:09 AM, Stéphane Ducasse wrote: > this is strange since 1234 numberOfDigitsInBase: 10 -> 4 > but the finder does not report it for > 1234 . 10 . 4 > Only methods that are added to the class MethodFinder by hand are tested. If you add #numberOfDigitsInBase: to #init

Re: [Pharo-project] [squeak-dev] Re: SqueakSource3 (was: Re: Pharo Sources Google Hit Ratio)

Am 2011-02-25 um 10:23 schrieb Camillo Bruni: […] >>> >>> Squeaksource3 is at >>> http://squeaksource.com/squeaksource3.html (when working) >>> and a (manual, not-up-to-date) mirror at >>> http://seaside.gemstone.com/ss/squeaksource3.html >>> >>> I started this thing around mid-last ye

Re: [Pharo-project] SqueakSource3 (was: Re: Pharo Sources Google Hit Ratio)

Am 2011-02-25 um 10:19 schrieb laurent laffont: > > On Fri, Feb 25, 2011 at 10:14 AM, Tobias Pape wrote: > […] > >> I started this thing around mid-last year in efforts >> to get SqueakSource working on Seaside3, Magritte2 >> and gemstone with Email support, while integrating >> the different sq

Re: [Pharo-project] Issue 3752 in pharo: [bug+fix] Symbol>>allInstances should answer all symbols

Comment #2 on issue 3752 by ryd...@gmail.com: [bug+fix] Symbol>>allInstances should answer all symbols http://code.google.com/p/pharo/issues/detail?id=3752 I agree with Nicolas in that introducing exceptions like this is a bad idea

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

Otto, The changes you made to the configuration mean that the XMLParser packages are fetched from the gemsource repository for *all* platforms, and not only for GemStone. I don't think this should be the intention. The official code for the XMLParser for Pharo and Squeak are located in a squeak

Re: [Pharo-project] Issue 3722 in pharo: The Finder tool's help screen is poorly written and has bad grammar

Updates: Status: Duplicate Mergedinto: 3743 Comment #3 on issue 3722 by marcus.d...@gmail.com: The Finder tool's help screen is poorly written and has bad grammar http://code.google.com/p/pharo/issues/detail?id=3722 Can you provide *one* merged Finder version that is ready to

Re: [Pharo-project] [COTDC] 18 - SMxMorphicAlarm

Laurent Laffont - @lolgzs Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ On Fri, Feb 25, 2011 at 12:08 PM, Henrik Johansen < henrik.s.johan...@veloxit.no> wrote: > > On Feb 24, 2011, at 8:49 46PM, laurent laffont wrote:

[Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

Still I do not understand: Evaluate this in an updated Pharo core 1.2: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSup

Re: [Pharo-project] Issue 3743 in pharo: Fix Finder UI (add shortcuts and more commands)

Comment #7 on issue 3743 by marcus.d...@gmail.com: Fix Finder UI (add shortcuts and more commands) http://code.google.com/p/pharo/issues/detail?id=3743 Issue 3722 has been merged into this issue.

Re: [Pharo-project] Issue 3699 in pharo: Beeper beep raises MNU

Updates: Status: Closed Comment #7 on issue 3699 by marcus.d...@gmail.com: Beeper beep raises MNU http://code.google.com/p/pharo/issues/detail?id=3699 in 1.2 12338

Re: [Pharo-project] SqueakSource3 (was: Re: Pharo Sources Google Hit Ratio)

On Fri, Feb 25, 2011 at 12:38 PM, Tobias Pape wrote: > Am 2011-02-25 um 10:19 schrieb laurent laffont: > > > > On Fri, Feb 25, 2011 at 10:14 AM, Tobias Pape wrote: > > […] > > > >> I started this thing around mid-last year in efforts > >> to get SqueakSource working on Seaside3, Magritte2 > >> a

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

I personally thing if we ever want to release 1.2, we need to start to be more radical. The XML package breaks the build? So let's remove it completely. Let's ship 1.2, but without all the packages that are problematic. Same for any other package that has a failing test. Marcus On Fe

[Pharo-project] [update 1.2] #12338

12338 - - Issue 3699: Beeper beep raises MNU - remove SocketTests as they are failing on the testserver -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph

Updates: Status: Closed Comment #17 on issue 3482 by marcus.d...@gmail.com: InterimSoundMorph references to SketchMorph http://code.google.com/p/pharo/issues/detail?id=3482 Test is not failing anymore for Undeclared

Re: [Pharo-project] Issue 3571 in pharo: [Failing Test] Tests.Release.ReleaseTest.testUndeclared

Updates: Status: Closed Comment #4 on issue 3571 by marcus.d...@gmail.com: [Failing Test] Tests.Release.ReleaseTest.testUndeclared http://code.google.com/p/pharo/issues/detail?id=3571 test is green as of buid #149

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

Marcus, I've worked on this this week: - I've fixed ReleaseTest.testUndeclared and RBInlineMethodFromComponentTest.testInlineEmptyComponentMethod - For all Metacello tests, the fix is available but Dale said: "I haven't released my changes yet ... once I'm satisfied with the the behavior on Pharo

Re: [Pharo-project] Issue 3589 in pharo: ClassComment in OB

Updates: Status: Closed Comment #9 on issue 3589 by marcus.d...@gmail.com: ClassComment in OB http://code.google.com/p/pharo/issues/detail?id=3589 (No comment was entered for this change.)

Re: [Pharo-project] Issue 3711 in pharo: DefaultStubs in Undeclared

Updates: Status: Closed Comment #5 on issue 3711 by marcus.d...@gmail.com: DefaultStubs in Undeclared http://code.google.com/p/pharo/issues/detail?id=3711 fixed as of #149

Re: [Pharo-project] Issue 3712 in pharo: Still CustomMenu references in Pharo 1.2 dev

Updates: Status: Closed Comment #6 on issue 3712 by marcus.d...@gmail.com: Still CustomMenu references in Pharo 1.2 dev http://code.google.com/p/pharo/issues/detail?id=3712 fixed as of #149

[Pharo-project] [TODO 1.2] Issues to fix before Release

http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage ... with the most pressing being the failing build. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3730 in pharo: #KedamaFloatArray is referenced in WordArray

Updates: Status: Closed Comment #2 on issue 3730 by marcus.d...@gmail.com: #KedamaFloatArray is referenced in WordArray http://code.google.com/p/pharo/issues/detail?id=3730 fixed, validated in #149

Re: [Pharo-project] Issue 3729 in pharo: Failing test: CollectionsTests.Arrayed.FloatArrayTest.testArithmeticCoercion

Updates: Status: Closed Comment #4 on issue 3729 by marcus.d...@gmail.com: Failing test: CollectionsTests.Arrayed.FloatArrayTest.testArithmeticCoercion http://code.google.com/p/pharo/issues/detail?id=3729 fixed, verified in build #149

Re: [Pharo-project] Issue 3579 in pharo: "declare temp" adds the variable twice

Updates: Status: Closed Comment #14 on issue 3579 by marcus.d...@gmail.com: "declare temp" adds the variable twice http://code.google.com/p/pharo/issues/detail?id=3579 verified in #149

Re: [Pharo-project] Issue 3731 in pharo: default browser size bigger

Updates: Status: Closed Comment #1 on issue 3731 by marcus.d...@gmail.com: default browser size bigger http://code.google.com/p/pharo/issues/detail?id=3731 The core browser size looks good to me

[Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

Status: Accepted Owner: marcus.d...@gmail.com Labels: Milestone-1.2-DevImage Importance-High New issue 3757 by marcus.d...@gmail.com: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 1.2 build is broken due to XML package

Re: [Pharo-project] Issue 3652 in pharo: [Failing Test] MocketryTests.Actions.MockActionAcceptanceTests.testWillProcessBlocking

Comment #4 on issue 3652 by marcus.d...@gmail.com: [Failing Test] MocketryTests.Actions.MockActionAcceptanceTests.testWillProcessBlocking http://code.google.com/p/pharo/issues/detail?id=3652 We should remove this package from 1.2

[Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

Markus wrote: >The XML package breaks the build? So let's remove it completely. Let's ship >>1.2, but without all the packages that are problematic. It's not that the package is problematic - the Configs are problematic Laurent wrote: >For XML I can fix this tonight if Otto don't want / can do i

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

Comment #4 on issue 3581 by marcus.d...@gmail.com: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 We should remove this package from 1.2

Re: [Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

Comment #1 on issue 3757 by marcus.d...@gmail.com: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 We should remove the XML package

[Pharo-project] Issue 3758 in pharo: Metacello has 12 failing tests in 1.2

Status: Accepted Owner: marcus.d...@gmail.com Labels: Milestone-1.2-DevImage Importance-High New issue 3758 by marcus.d...@gmail.com: Metacello has 12 failing tests in 1.2 http://code.google.com/p/pharo/issues/detail?id=3758 Metacello.TestsMC.MetacelloCurrentVersionTest.testFoo40Loaded1Packag

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

On Fri, Feb 25, 2011 at 2:10 PM, Torsten Bergmann wrote: > Markus wrote: > >The XML package breaks the build? So let's remove it completely. Let's > ship >1.2, but without all the packages that are problematic. > > It's not that the package is problematic - the Configs are problematic > > Laurent

Re: [Pharo-project] Issue 3707 in pharo: Syntax highlighting looks strange

Comment #5 on issue 3707 by marcus.d...@gmail.com: Syntax highlighting looks strange http://code.google.com/p/pharo/issues/detail?id=3707 Why don't we just change it back to how it used to be? We are *frozen* and want to release 1.2 ASAP (that is, 2 month ago). Yet, someone changed compel

[Pharo-project] [OT] Why PHP is better than Ruby

My friend gave me a fun post.. http://najafali.com/php-is-better-than-ruby.html rofl... -- Best regards, Igor Stasenko AKA sig.

Re: [Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

Comment #2 on issue 3757 by torsten@astares.de: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 nonsense, we should just fix the configs

Re: [Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

Updates: Cc: laurent.laffont Comment #3 on issue 3757 by torsten@astares.de: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 currently "project: 'XMLSupport' with: '1.1.6'." is referenced in ConfigurationOfPharo and THIS IS A WORKI

Re: [Pharo-project] Pharo Sources Google Hit Ratio

Some students at annecy started to produce yard but in pharo for pharo. I do not know where they are: herve verjus is their supervisors. > we are close... > - full smalltalk sources formatter for seaside > - http://rubydoc.info/docs/yard/0.6.4/frames like interface > > todo: > -

Re: [Pharo-project] Fwd: [ANN] pharo focused sprint - bern, feb 26

> I'll be there. > > From what I have done this week so far, I would like to work on extending the > IDE and reduce the amount of clicks / keystrokes to browse things... yes I would love to have a fly by help in method body. Stef > > m(o_o)m > camillo > > On 2011-02-21, at 19:42, Tudor Girba

Re: [Pharo-project] SilverSmalltalk

does it run on your machine? If people pay for it then there is a market for pharo too. > You're probably aware of it. I found it impressive > http://www.silversmalltalk.com/ > > Cheers, > Alexandre > --

Re: [Pharo-project] [squeak-dev] Re: SqueakSource down... again

> Stef, > > I believe that the source is on SqueakSource in the squeaksource3 repository. > This is a port of SqueakSource to Seaside3.0 that was done by Philippe, > Tobias and James Foster... Thanks!. > Tobias mentioned that he was getting close t finishing things up in an > earlier message.

Re: [Pharo-project] FileSystem. Possible FSReference rename

Hi denis > I think FSLocator and FSReference are same objects: > FSReference = fileSystem + path > FSLocator = "some origin object" + path. > > I think "some origin object" can be implemented as special > FSRelativeFileSystem. And fileLocator became fileReference. > > Now in "FSLocator vmDirect

Re: [Pharo-project] Is repository down for Magma?

In pharoTaskForces :) On Feb 23, 2011, at 5:17 PM, Miguel Cobá wrote: > Unfortunately for all us, Chris deleted without notice, the versions > from Magma repository that were used by the Metacello configuration to > install Magma. So Magma isn't installable with Metacello anymore. > > Last weeke

Re: [Pharo-project] Is repository down for Magma?

BTW this is why I would like to have a copy of all the packages when we publish a configuration. So that the world can explode and the user does not get impacted. Stef > Unfortunately for all us, Chris deleted without notice, the versions > from Magma repository that were used by the Metacello

Re: [Pharo-project] Is repository down for Magma?

> > To incorporate this into Pharo, see the changes in Squeak between: > >Collections-ul.403 and Collections-cmm.404. > > The changes are very simple. Basically, we simply allow the > OrderedCollection's internal 'array' to be specified by its > #arrayType, instead of being hard-coded to an

Re: [Pharo-project] SilverSmalltalk

Yes, it runs pretty well. I used Safari Alexandre On 25 Feb 2011, at 09:30, Stéphane Ducasse wrote: > does it run on your machine? > If people pay for it then there is a market for pharo too. > >> You're probably aware of it. I found it impressive >> http://www.silversmalltalk.com/ >> >> Cheer

Re: [Pharo-project] Issue 3756 in pharo: Browser title

Updates: Status: Closed Comment #2 on issue 3756 by stephane...@gmail.com: Browser title http://code.google.com/p/pharo/issues/detail?id=3756 in 13065

Re: [Pharo-project] Issue 3755 in pharo: HelpTopicListItemWrapper has it's own highlighting color

Updates: Status: closed Comment #2 on issue 3755 by stephane...@gmail.com: HelpTopicListItemWrapper has it's own highlighting color http://code.google.com/p/pharo/issues/detail?id=3755 in 13065

Re: [Pharo-project] [OT] Why PHP is better than Ruby

brilliant! Especially the ! first ! comment to the post... unbelievable On 25.02.2011, at 14:36, Igor Stasenko wrote: > My friend gave me a fun post.. > > http://najafali.com/php-is-better-than-ruby.html > > rofl... > > -- > Best regards, > Igor Stasenko AKA sig. >

[Pharo-project] [update 1.3] #13065

13065 - Issue 3755: help browser list highlight Issue 3756: browser title Alain (my first update)

Re: [Pharo-project] [update 1.3] #13065

On Fri, Feb 25, 2011 at 3:39 PM, Alain Plantec wrote: > 13065 > - > > Issue 3755: help browser list highlight > Issue 3756: browser title > > Alain (my first update) > yeepee one more integrator ! Laurent.

[Pharo-project] Issue 3759 in pharo: Stragger -> stagger

Status: Fixed Owner: stephane...@gmail.com Labels: Milestone-1.3 New issue 3759 by stephane...@gmail.com: Stragger -> stagger http://code.google.com/p/pharo/issues/detail?id=3759 straggerFor: aView initialExtent: initialExtent world: aWorld -> staggerFor: aView initialExtent: initialExtent worl

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

btw... 1.1.9 loaded well for me in 1.1.1 (while 1.1.8 was failing) El 25/02/2011, a las 10:23a.m., laurent laffont escribió: > On Fri, Feb 25, 2011 at 2:10 PM, Torsten Bergmann wrote: > Markus wrote: > >The XML package breaks the build? So let's remove it completely. Let's ship > >>1.2, but wit

Re: [Pharo-project] Issue 3759 in pharo: Stragger -> stagger

Updates: Status: Closed Comment #1 on issue 3759 by aplan...@gmail.com: Stragger -> stagger http://code.google.com/p/pharo/issues/detail?id=3759 in 13066

Re: [Pharo-project] Issue 3743 in pharo: Fix Finder UI (add shortcuts and more commands)

Updates: Status: Accepted Comment #8 on issue 3743 by stephane...@gmail.com: Fix Finder UI (add shortcuts and more commands) http://code.google.com/p/pharo/issues/detail?id=3743 so ben the idea is that you should resolve the conflicts because we do not know how to resolve them but I

[Pharo-project] Could we clean/remove some of the old themes?

I would suggest to remove/package in a separate package StandardSqueak to remove the Pro theme (because the fonts are broken) to rename softSqueak into Colorful Stef

[Pharo-project] About UIManager and UITheme for MenuMorph

Hi gary I was reading http://code.google.com/p/pharo/issues/detail?id=3728 which converts MenuMorph new -> UIManager default menuClass And I was wondering: - UIManager regulate coarse grained interaction - UITheme takes into account settings Now UIManager does n

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

> - For XML I can fix this tonight if Otto don't want / can do it. 1.1.9 was blessed as #development and 1.1.8 as #release. I changed the blessing 1.1.9 to #released. I do believe that the 1.1.9 version works well. 1.1.8 is now #broken. Sorry about that. Thanks for the help. I'm doing a load in

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

On Fri, Feb 25, 2011 at 4:53 PM, Otto Behrens wrote: > > - For XML I can fix this tonight if Otto don't want / can do it. > > 1.1.9 was blessed as #development and 1.1.8 as #release. I changed the > blessing 1.1.9 to #released. I do believe that the 1.1.9 version works > well. 1.1.8 is now #broke

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

I've downloaded the PharoOneClick1.2.zip file and am evaluating (ConfigurationOfPharo project version: '1.2-beta2') load now. This is the best "entry point" that I could determine from the console output. Please let me know if this is OK. My bandwidth is not amazing, but it's running. On Fri, F

Re: [Pharo-project] Is repository down for Magma?

El vie, 25-02-2011 a las 13:40 +0100, Stéphane Ducasse escribió: > BTW this is why I would like to have a copy of all the packages when we > publish a configuration. > So that the world can explode and the user does not get impacted. + 1 > > Stef > > > > Unfortunately for all us, Chris delet

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

Marcus I would not add XML in dev. just dev tools no extra package. So yes let us remove XML package. I already asked for that. Now the problem encountered reveal something deeper. STef On Feb 25, 2011, at 1:18 PM, Marcus Denker wrote: > I personally thing if we ever want to release 1.2, we n

Re: [Pharo-project] About UIManager and UITheme for MenuMorph

Not sure what you mean but I'd expect high-level interactions to not ask for a menuClass. Still, in headless case, with this, it is possible to provide a suitable replacement. Regards, Gary - Original Message - From: "Stéphane Ducasse" To: "pharo Development" Sent: Friday, February

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

It loaded and XML-Tests-Parser reports: 361 run, 361 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes Running all tests now (11240) ... On Fri, Feb 25, 2011 at 6:04 PM, Otto Behrens wrote: > I've downloaded the PharoOneClick1.2.zip file and am evaluating > >  (Configuratio

Re: [Pharo-project] Issue 3743 in pharo: Fix Finder UI (add shortcuts and more commands)

Comment #9 on issue 3743 by benjamin...@gmail.com: Fix Finder UI (add shortcuts and more commands) http://code.google.com/p/pharo/issues/detail?id=3743 Merge done in Finder-BenjaminVanRyseghem.26 in PharoInbox

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote: > Markus wrote: >> The XML package breaks the build? So let's remove it completely. Let's ship >> >1.2, but without all the packages that are problematic. > > It's not that the package is problematic - the Configs are problematic Exact But

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

Hi otto no stress. :) There is no problem. Doing something implies that we can do it wrong (I do all the times mistakes and I hope that I learn to improve myself). I prefer having a community of people doing some wrong actions than just talking. Stef On Feb 25, 2011, at 4:53 PM, Otto Behrens

Re: [Pharo-project] About UIManager and UITheme for MenuMorph

Gary What I mean is that there are a lot of places where MenuMorph is hardcoded and the UIManager does not have a chance to take control. I imagine that this is for this reason that guillermo proposed this change. Stef > Not sure what you mean but I'd expect high-level interactions to not as

Re: [Pharo-project] Could we clean/remove some of the old themes?

Go for it (or was that Gofer ;-) ) Regards, Gary - Original Message - From: "stephane ducasse" To: "pharo Development" Sent: Friday, February 25, 2011 3:30 PM Subject: [Pharo-project] Could we clean/remove some of the old themes? I would suggest to remove/package in a separate pac

Re: [Pharo-project] About UIManager and UITheme for MenuMorph

Indeed, a step forward. UIManager is a quite focussed facade. Perhaps the "unusual" usages of MenuMorph can be analysed as to their main intent. Regards, Gary - Original Message - From: "Stéphane Ducasse" To: Sent: Friday, February 25, 2011 4:27 PM Subject: Re: [Pharo-project] Abou

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

+1 El 25/02/2011, a las 1:09p.m., Stéphane Ducasse escribió: > Marcus > > I would not add XML in dev. just dev tools no extra package. > So yes let us remove XML package. I already asked for that. > Now the problem encountered reveal something deeper. > > > STef > > On Feb 25, 2011, at 1:18

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

On Fri, Feb 25, 2011 at 5:11 PM, Stéphane Ducasse wrote: > > On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote: > > > Markus wrote: > >> The XML package breaks the build? So let's remove it completely. Let's > ship >1.2, but without all the packages that are problematic. > > > > It's not that t

Re: [Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

Updates: Status: Closed Comment #4 on issue 3757 by marcus.d...@gmail.com: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 Now this is fixed, and the build fails due to another reason. (We will *never* release 1.2, this is my prediction)

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

On Feb 25, 2011, at 5:42 PM, laurent laffont wrote: > On Fri, Feb 25, 2011 at 5:11 PM, Stéphane Ducasse > wrote: > > On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote: > > > Markus wrote: > >> The XML package breaks the build? So let's remove it completely. Let's > >> ship >1.2, but withou

[Pharo-project] [update 1.3] #13066

Issue 3759: Stragger -> stagger Issue 3742: MorphTreeMorph keyStroke: send Event object instead of Character Alain

[Pharo-project] Issue 3760 in pharo: Build 1.2 Fails due to Mock package

Status: Accepted Owner: marcus.d...@gmail.com Labels: Milestone-1.2-DevImage Importance-High New issue 3760 by marcus.d...@gmail.com: Build 1.2 Fails due to Mock package http://code.google.com/p/pharo/issues/detail?id=3760 Solution: Remove the package that is the problem. THERE_BE_DRAGONS_HER

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

On 25.02.2011, at 17:48, Marcus Denker wrote: > > On Feb 25, 2011, at 5:42 PM, laurent laffont wrote: > >> On Fri, Feb 25, 2011 at 5:11 PM, Stéphane Ducasse >> wrote: >> >> On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote: >> >> > Markus wrote: >> >> The XML package breaks the build? So

Re: [Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

Comment #5 on issue 3757 by torsten@astares.de: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 When I load it manually it works for me (didnt clear package cache).

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

I think the build will become unstable with every package update... So maybe we should update every ConfigurationOf used by pharo, and put symbolic versions into it Guille On Fri, Feb 25, 2011 at 1:50 PM, Norbert Hartl wrote: > > On 25.02.2011, at 17:48, Marcus Denker wrote: > > > On Feb 25,

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

I didn't try it yet, but using metacello browser, and letting it have a project description, will do the work for us ;). On Fri, Feb 25, 2011 at 1:09 PM, Stéphane Ducasse wrote: > Marcus > > I would not add XML in dev. just dev tools no extra package. > So yes let us remove XML package. I alread

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

On Feb 25, 2011, at 6:14 PM, Guillermo Polito wrote: > I think the build will become unstable with every package update... So maybe > we should update every ConfigurationOf used by pharo, and put symbolic > versions into it > The 1.1 build is broken, too. So even for 1.1, we somhow load new

Re: [Pharo-project] Issue 3743 in pharo: Fix Finder UI (add shortcuts and more commands)

Comment #10 on issue 3743 by aplan...@gmail.com: Fix Finder UI (add shortcuts and more commands) http://code.google.com/p/pharo/issues/detail?id=3743 Hi Benjamin! I've found two problems: 1) Since keyStroke: is sent with the event as argument, now you have to get the character from the eve

Re: [Pharo-project] Issue 3728 in pharo: Changed MenuMorph references to go through UIManager default menuClass

Updates: Status: Accepted Comment #5 on issue 3728 by stephane...@gmail.com: Changed MenuMorph references to go through UIManager default menuClass http://code.google.com/p/pharo/issues/detail?id=3728 fernando I started to do something a bit better :) but we cannot attach anything a

[Pharo-project] we cannot add attachment anymore on the bug tracker

Hi guys does anybody know how we can fix that? Stef

Re: [Pharo-project] we cannot add attachment anymore on the bug tracker

On 25 February 2011 18:54, Stéphane Ducasse wrote: > Hi guys > > does anybody know how we can fix that? > whaaat? that's really bad :( > Stef > > > -- Best regards, Igor Stasenko AKA sig.

[Pharo-project] about Issue 3728: Changed MenuMorph references to go through UIManager default menuClass

Hi fernando here are my own changes. Please have a look and let me know what you think. Stef MenuMorph.1.cs Description: Binary data Stef

Re: [Pharo-project] [OT] Why PHP is better than Ruby

:-) Funny yes Alexandre On 25 Feb 2011, at 11:35, Max Leske wrote: > brilliant! Especially the ! first ! comment to the post... unbelievable > > > On 25.02.2011, at 14:36, Igor Stasenko wrote: > >> My friend gave me a fun post.. >> >> http://najafali.com/php-is-better-than-ruby.html >> >>

Re: [Pharo-project] Issue 3760 in pharo: Build 1.2 Fails due to Mock package

Updates: Status: Closed Comment #1 on issue 3760 by marcus.d...@gmail.com: Build 1.2 Fails due to Mock package http://code.google.com/p/pharo/issues/detail?id=3760 fixed by removing Mock package

Re: [Pharo-project] Issue 3652 in pharo: [Failing Test] MocketryTests.Actions.MockActionAcceptanceTests.testWillProcessBlocking

Updates: Status: Closed Comment #5 on issue 3652 by marcus.d...@gmail.com: [Failing Test] MocketryTests.Actions.MockActionAcceptanceTests.testWillProcessBlocking http://code.google.com/p/pharo/issues/detail?id=3652 fixed in #157 by removing Mocketry

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

On Feb 25, 2011, at 5:48 PM, Marcus Denker wrote: >> >> Exact >> But still can't Pharo Dev focuses on tools and not frameworks that we should >> load by ourselves. >> Because else why not loading, cassandra, coucdb, opendbx, magma >> >> Because many more people are manipulating XML every

Re: [Pharo-project] Issue 3760 in pharo: Build 1.2 Fails due to Mock package

Comment #2 on issue 3760 by dionisiy...@gmail.com: Build 1.2 Fails due to Mock package http://code.google.com/p/pharo/issues/detail?id=3760 Latest ConfigurationOfMocketry version fix problem

Re: [Pharo-project] Issue 3652 in pharo: [Failing Test] MocketryTests.Actions.MockActionAcceptanceTests.testWillProcessBlocking

Comment #6 on issue 3652 by dionisiy...@gmail.com: [Failing Test] MocketryTests.Actions.MockActionAcceptanceTests.testWillProcessBlocking http://code.google.com/p/pharo/issues/detail?id=3652 Latest ConfigurationOfMocketry version fix problem

[Pharo-project] Metacello feature: Can Metacello do this?

Can i test the configuration (with all dependencies), that every version of packages it going to load are specified explicitly, i.e. there is not 'load latest version from that branch'. This is to ensure that given configuration will continue to work and load same packages no matter of what new fu

Re: [Pharo-project] Metacello feature: Can Metacello do this?

I do not think there is such possibility out of the box. I think that a clean solution is to be able to define a visitor that run over the graph of dependencies. Cheers, Alexandre On 25 Feb 2011, at 16:03, Igor Stasenko wrote: > Can i test the configuration (with all dependencies), > that eve

Re: [Pharo-project] Metacello feature: Can Metacello do this?

On 25 February 2011 20:10, Alexandre Bergel wrote: > I do not think there is such possibility out of the box. I think that a clean > solution is to be able to define a visitor that run over the graph of > dependencies. > I heard about new tool which checks mc configs.. maybe it can do this? >

  1   2   >