Re: [Pharo-project] Issue 3420 in pharo: ReleaseTest>>#testUndeclared is failing

Comment #1 on issue 3420 by guillermopolito: ReleaseTest>>#testUndeclared is failing http://code.google.com/p/pharo/issues/detail?id=3420 Marcus, what is the hudson build code you are talking about? :)

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

Comment #1 on issue 3514 by guillermopolito: Failing Test: NewTextMorphTests.testAcceptContents http://code.google.com/p/pharo/issues/detail?id=3514 This is because TextEditor>>accept does: accept "Save the current text of the text being edited as the current acceptable version for purpos

Re: [Pharo-project] About preloaded packages

+1 Doru On 8 Jan 2011, at 17:02, Stéphane Ducasse wrote: > > On Jan 8, 2011, at 4:42 PM, Schwab,Wilhelm K wrote: > >> Stef, >> >> I'm not sure I follow. I think we agree that loading all configurations and >> running tests is good. > > I meant that the configurations do not have to be loa

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken (ph...@googlecode.com)

2011/1/8 Stephan Eggermont : > Nicolas wrote: >>Then group the selectors (first, first: etc..), explain that they are >>extensions, and don't need a copy prefix, because anyway most messages >>will do a copy. > > You are aware first doesn't copy, do you? The explanation should be > that you always

[Pharo-project] cog 2343 fails smoke test on linux

On Fri, Jan 07, 2011 at 06:15:52PM -0800, Eliot Miranda wrote: > Hi All, > > find new VMs in > VM.r2342/ > (SimpleStackBasedCogit) > and VM.r2343/ ( > StackToRegisterMappingCogit). 2343 se

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken (ph...@googlecode.com)

Nicolas wrote: >Then group the selectors (first, first: etc..), explain that they are >extensions, and don't need a copy prefix, because anyway most messages >will do a copy. You are aware first doesn't copy, do you? The explanation should be that you always have to take a look at the implementati

Re: [Pharo-project] TODO 1.2

Thanks Marcus for the summary. We need people to help on this! mariano On Fri, Jan 7, 2011 at 3:04 PM, Marcus Denker wrote: > 1) Core: > >- Failing Tests: 8 > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompletedBuild/testReport/ >- Open Bug Tracker entrie

Re: [Pharo-project] Including Zinc HTTP Components in Pharo 1.2 Dev ?

On 7 January 2011 20:07, Sven Van Caekenberghe wrote: > I was in meeting all day, hence the late reply. > > On 07 Jan 2011, at 14:08, Stéphane Ducasse wrote: > >> Sven >> >> two questions: >>       - if we want to use zn for pharo to replace HTTPSocket, don't you >> think that Zinc-HTTP-Client-Se

Re: [Pharo-project] Basic rules of life in this team!

sorry this mail was for our team at lille. Stef On Jan 8, 2011, at 5:13 PM, Stéphane Ducasse wrote: > May be this is time to resend this email... sadly. > > >> Hi guys >> >> apparently gwenael is reading this mailing-list and you too, so could you >> tell >> him that I would appreciate that

Re: [Pharo-project] [squeak-dev] Announcements in core images?

On Jan 8, 2011, at 5:16 PM, Mariano Martinez Peck wrote: > > > 2011/1/7 Janko Mivšek > Hi both Squeakers and Pharoers, > > What is a status of Announcements package as part of core images? Are > they already there and, are they compatible, and if not, what are the > differences? > > Hi Janko

Re: [Pharo-project] [Seaside-dev] Seaside and exception behaviour

On Wed, Jan 5, 2011 at 8:15 AM, Paolo Bonzini wrote: > On 01/05/2011 04:58 PM, mkobe...@cincom.com wrote: >> >> > >  Here's maybe a bit more concise example. If you run the thing below >> > > in a workspace, >> > >  it returns 'Squeak' in Squeak and 'VW' in VW >> > > >> > >  [  [       [       sel

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

+1 If you accept a two phase approach (as I understood Seaside may be heavily impacted): 1) Let's add add copyFrom: in Sequenceable as self copyFrom: a to: self size; 1.1) Test for issues with Seaside/Mondrian, etc., i.e., all production environments, if they come green from this mod

Re: [Pharo-project] [squeak-dev] Announcements in core images?

2011/1/7 Janko Mivšek > Hi both Squeakers and Pharoers, > > What is a status of Announcements package as part of core images? Are > they already there and, are they compatible, and if not, what are the > differences? > Hi Janko. I don't know anything about announcments, but I can tell you they a

[Pharo-project] Basic rules of life in this team!

May be this is time to resend this email... sadly. > Hi guys > > apparently gwenael is reading this mailing-list and you too, so could you > tell > him that I would appreciate that he replies (not only by email but this is a > first step but) by actions > to my mails, if they are of any valu

Re: [Pharo-project] Issue 3262 in pharo: Debugger enhancement to open in a background process when the UI process is busy

Updates: Labels: Milestone-1.3 Comment #4 on issue 3262 by stephane.ducasse: Debugger enhancement to open in a background process when the UI process is busy http://code.google.com/p/pharo/issues/detail?id=3262 (No comment was entered for this change.)

Re: [Pharo-project] About preloaded packages

On Jan 8, 2011, at 4:42 PM, Schwab,Wilhelm K wrote: > Stef, > > I'm not sure I follow. I think we agree that loading all configurations and > running tests is good. I meant that the configurations do not have to be loaded in the image. > I understand why the web image went away when it took

Re: [Pharo-project] About preloaded packages

Stef, I'm not sure I follow. I think we agree that loading all configurations and running tests is good. I understand why the web image went away when it took somebody's time time build it, but the Hudson server can do that work now. It seems reasonable to leave a range of targets that might

Re: [Pharo-project] About preloaded packages

My concern about Metacello has always been that while it is terribly easy to use, it is very potentially difficult to know what to ask it to do. I *think* I have seen signs of improvement and increasing uniformity since I began playing with 1.2. The ConfigurationBrowser probably brought the co

Re: [Pharo-project] Issue 3224 in pharo: Migrating MethodReference to MethodReferenceWithSource

Comment #13 on issue 3224 by Benjamin.VanRyseghem.Pharo: Migrating MethodReference to MethodReferenceWithSource http://code.google.com/p/pharo/issues/detail?id=3224 Here are two new change set which fix a little bit the SourceReference API and fix some tests. The order matters. With tha

Re: [Pharo-project] About preloaded packages

> Because we have to fix bug of packages that we do not know, control, want to > fix... > Because been agile to load and having a good infrastructure for validating > packages is way more > important than preloading XML. If we spend our time on the infrastructure > (metacello publication, > conf

Re: [Pharo-project] About preloaded packages

On Sat, Jan 8, 2011 at 2:59 PM, Stéphane Ducasse wrote: > > On Jan 7, 2011, at 5:10 PM, Miguel Cobá wrote: > > > I concur with Mariano and wonder why Stéphane wants a smaller dev image? > > Because we have to fix bug of packages that we do not know, control, want > to fix... > Because been agile t

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

+100 :-D -- Cheers, Peter On Sat, Jan 8, 2011 at 3:22 PM, Stéphane Ducasse wrote: > What we will do is > >deprecate copyFrom: from Object -> copyStateFrom: >add copyFrom: in Sequenceable >as >self copyFrom: a to: self size > > Stef

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

What we will do is deprecate copyFrom: from Object -> copyStateFrom: add copyFrom: in Sequenceable as self copyFrom: a to: self size Stef

Re: [Pharo-project] wiki style help

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 '' ' ' '' '" everyti

Re: [Pharo-project] Including Zinc HTTP Components in Pharo 1.2 Dev ?

On Jan 7, 2011, at 8:10 PM, Sven Van Caekenberghe wrote: > > On 07 Jan 2011, at 13:58, Stéphane Ducasse wrote: > >> I was just reading the code with olivier auverlot. >> I would love to have a small if possible replacement to the HTTPSocket. > > There really is a lot of cleanup to do. Yes. A

Re: [Pharo-project] Including Zinc HTTP Components in Pharo 1.2 Dev ?

On Jan 7, 2011, at 8:07 PM, Sven Van Caekenberghe wrote: > I was in meeting all day, hence the late reply. > > On 07 Jan 2011, at 14:08, Stéphane Ducasse wrote: > >> Sven >> >> two questions: >> - if we want to use zn for pharo to replace HTTPSocket, don't you think >> that Zinc-HTTP-Cl

Re: [Pharo-project] Including Zinc HTTP Components in Pharo 1.2 Dev ?

On Jan 7, 2011, at 2:02 PM, Adrian Lienhard wrote: > Hi Sven, > > +1 for Pharo 1.2 (the dev image) > -1 for patching HTTPSocket (dev packages should not modify core code) > > For 1.3 we should think about integrating Zinc in PharoCore to replace > HTTPSocket. Yes! > > Cheers, > Adrian > >

Re: [Pharo-project] announcements and weak references

let us know. > Thanks. > > I will take a look. > > Cheers, > Doru > > > On 7 Jan 2011, at 18:08, Lukas Renggli wrote: > >> As far as I remember my announcement implementation uses ActionSequence to >> represent the actions of an event. You just have to replace these with >> WeakActionSeque

Re: [Pharo-project] announcements and weak references

Yes This is on our plateI would like igor to have a look at all the weak stuff and after Annoucements > Hi, > > Are there any plans to get Announcements use weak references? > > I saw that in the repository of Lukas, there is a WeakAnnouncer. However, > here the subscriptions are still he

Re: [Pharo-project] Origins [poll]

Sudhakar Krishnamachari|Tamil|Vannakam|India|Bangalore|Smalltalk, dynamic languages, Civil Architecture, enterprise computing, financial software

Re: [Pharo-project] About preloaded packages

> I would also be rather conservative with regard to adding packages that are > not developer tools. > > If we add XML we should probably also add XYZ. Wouldn't it make sense to add > Seaside too? The problem here is not primarily the larger image file size, > but the image becomes bloated in

Re: [Pharo-project] About preloaded packages

On Jan 7, 2011, at 5:10 PM, Miguel Cobá wrote: > I concur with Mariano and wonder why Stéphane wants a smaller dev image? Because we have to fix bug of packages that we do not know, control, want to fix... Because been agile to load and having a good infrastructure for validating packages is w

Re: [Pharo-project] Origins [poll]

Name|Native Language|Greeting in native lang|Born country|Writing from| interests Patrick Barroca | French | Salut | France | Annecy, France | Video games, OOP, Manga

Re: [Pharo-project] About preloaded packages

On Jan 7, 2011, at 10:51 AM, Mariano Martinez Peck wrote: > > > On Fri, Jan 7, 2011 at 9:16 AM, Torsten Bergmann wrote: > >I would favor push metacello so that in one click people can load what they > >>want. > > You already can. Push the config to the Metacello Repository for 1.2 on > squea

Re: [Pharo-project] About preloaded packages

> > > -1 > > Sorry, But I don't agree. Who cares the size of a development image? You are > not going to deploy it. But we have to do the "oh let us fix this bug" > The less effort for new comers to get what they want, the best. They can click and load. > I would let XMLSupport (and the res

Re: [Pharo-project] Announcements in core images?

From our side announcements are really important and should replaced a lot of events. On Jan 7, 2011, at 7:44 PM, Janko Mivšek wrote: > Hi both Squeakers and Pharoers, > > What is a status of Announcements package as part of core images? Are > they already there and, are they compatible, and if

Re: [Pharo-project] About using pragma for help like in setting

On Jan 7, 2011, at 5:22 PM, Torsten Bergmann wrote: > Dont confuse this, marking with does not > mean you mark a method that returns a string and it > magically appears in the system help. > > This pragma is used to mark "help types" that should be > included in the SystemHelp. Classes marked

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

2011/1/7 : > > I will take this as meaning "I agree that Object>>copyFrom: is ambiguous..." > > If I misunderstood you, please feel free to correct. > > OTHO, as it is not explicitly written, I would like to understand your > stance on having this method name as a shorcut to > copyFrom: start to:

Re: [Pharo-project] Adding hudson links from pharo webpage?

On Fri, Jan 7, 2011 at 10:41 PM, Schwab,Wilhelm K wrote: > I would not have thought to put it there, but it's a good idea. I think > there should also be a link on the download section?? > > Exactly. THis is why I didn't even check in Community. It would have a section under download or somethin

Re: [Pharo-project] wiki style help

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" fo