December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Why was the old Editor Functionality Removed?

by Lukas Renggli

No, don't waste time on reverting. I almost got it working. My comment was ment for the future :-) Lukas On 10 December 2010 13:02, Alain Plantec <alain.plantec(a)free.fr> wrote: > so, concerning the new editor changes, I would like to help because this > messy situation is partly my fault. > would it be helpful if I rename current TextEditor as TextEditor2, (give me > another name please ...), > current SmalltalkEditor as SmalltalkEditor2 and reintroduce the previous > implementation > for TextEditor and SmalltalkEditor ? > Cheers > Alain > > Le 10/12/2010 00:32, Lukas Renggli a Ã©crit : >>> >>> I said it before: just give the variable a different name. For example, >>> textStyle. That would solve all loading problems. >> >> I said it before: This doesn't solve anything at all. In fact it is >> much easier to remove the variable and fork the code. Renaming causes >> a ripple effect to lots of methods and makes it impossible to merge >> the forks in the future. >> >> The style variable is just one example of the problem. I am suggesting >> that the next time the editor framework is replaced the old code is >> left untouched, then deprecated, and different class names are chosen >> for the new implementation. Like this both frameworks can coexist for >> a while making it much easier to migrate the code. >> >> The current situation comes from the fact that some existing classes >> changed their class layout and API completely making migration really >> difficult. >> >> Lukas >> > > > -- Lukas Renggli www.lukas-renggli.ch

Dec. 10, 2010

Re: [Pharo-project] A suggestion.

by Diogenes Moreira

One data more... may be, can be definied un ChronologyConstants class On Fri, Dec 10, 2010 at 9:27 AM, Diogenes Moreira < diogenes.moreira(a)gmail.com> wrote: > Hi folks. > > First make a question, in this list. > > String>>asDate message assume(harcode way) english date format.. may be.. > may be better if the date format to take it to a context variable as with > the names of the months? > > Best.. >

Dec. 10, 2010

[Pharo-project] A suggestion.

by Diogenes Moreira

Hi folks. First make a question, in this list. String>>asDate message assume(harcode way) english date format.. may be.. may be better if the date format to take it to a context variable as with the names of the months? Best..

Dec. 10, 2010

Re: [Pharo-project] Why was the old Editor Functionality Removed?

by Alain Plantec

so, concerning the new editor changes, I would like to help because this messy situation is partly my fault. would it be helpful if I rename current TextEditor as TextEditor2, (give me another name please ...), current SmalltalkEditor as SmalltalkEditor2 and reintroduce the previous implementation for TextEditor and SmalltalkEditor ? Cheers Alain Le 10/12/2010 00:32, Lukas Renggli a Ã©crit : >> I said it before: just give the variable a different name. For example, textStyle. That would solve all loading problems. > I said it before: This doesn't solve anything at all. In fact it is > much easier to remove the variable and fork the code. Renaming causes > a ripple effect to lots of methods and makes it impossible to merge > the forks in the future. > > The style variable is just one example of the problem. I am suggesting > that the next time the editor framework is replaced the old code is > left untouched, then deprecated, and different class names are chosen > for the new implementation. Like this both frameworks can coexist for > a while making it much easier to migrate the code. > > The current situation comes from the fact that some existing classes > changed their class layout and API completely making migration really > difficult. > > Lukas >

Dec. 10, 2010

Re: [Pharo-project] about cloud in pharo

by GermÃ¡n Arduino

2010/12/10 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> In summary, I'm sure that cloud is the way to go, and count me in to >> any idea related with some sort of business/startup/entrepreneural >> initiative around Pharo on the cloud. > > I would be interested to hear about simple solutions for hosting seaside and other apps > > Well, I agree that the first thing we need (talking here in terms of Seaside (Pharo or Squeak)) is an easy and affordable way to host Seaside solutions. As I can saw on all this time developing customer solutions in Seaside, the main problem is host them and not, VPS is not the solution.

Dec. 10, 2010

[Pharo-project] Linux VM with IA32ABI plugin (Alien)

by Luc Fabresse

Hi all, I know that someone already manage to compile linux (squeak or cog) VM with Alien support (plugin I32ABI). Could someone, send me an already compiled VM? ;-) BTW, why the compiled linux VM available for download does not include this plugin? Thanks, #Luc

Dec. 10, 2010

Re: [Pharo-project] [squeak-dev] Cog+NativeBoost @ Mac OS

by Michael Haupt

Hi Igor, OK, so those are "expected failures". :-) On 9 December 2010 19:31, Igor Stasenko <siguctua(a)gmail.com> wrote: > Currently the Mac NB code using mostly the linux code, and sure thing > it could be different in some places specific to mac. Are there any larger bodies of example code that could be used to identify those places? Best, Michael

Dec. 10, 2010

[Pharo-project] Issue 3398 in pharo: SystemNavigation and SourcedMethodReference

by pharo＠googlecode.com

Status: Accepted Owner: luc.fabresse Labels: Milestone-1.2 Type-FailingTest New issue 3398 by luc.fabresse: SystemNavigation and SourcedMethodReference http://code.google.com/p/pharo/issues/detail?id=3398 6 tests in SystemNavigationTest and SystemNavigationOnNewlyCreatedEnvironementTest are failing in 1.2-12272 This is because of the introduction of SourcedMethodReference. I already speak about this problem here: http://forum.world.st/About-SourcedMethodReference-td3035187.html SourcedMethodReference>>= must not be based on identity (==) because it prevents to have multiple SourcedMethodReference pointing to the same CompiledMethod. And we need that because each tools will use different SourcedMethodReference. IMHO, SourcedMethodReference are just proxies and we don't care of their identity. I attach a cs that make these 6 tests pass. I replace MethodReference by SourcedMethodReference in SystemNavigationTest and al... And I modified the equality method of SourcedMethodReference: SourcedMethodReference>>= anotherMethodReference ^ (super = anotherMethodReference) and: [ (self timeStamp = self timeStamp) and: [ self sourceCode = self sourceCode ]] I have no idea of the impact of this change for the SourcedMethodReference stuff point of view. Attachments: FixFailingSystemNavigationTests.1.cs 3.6 KB

Dec. 10, 2010

[Pharo-project] Some Tests failing in 1.2

by Luc Fabresse

Hi all, 6 tests in SystemNavigationTest and SystemNavigationOnNewlyCreatedEnvironementTest are failing in 1.2 This is because of the introduction of SourcedMethodReference. I already speak about this problem here: http://forum.world.st/About-SourcedMethodReference-td3035187.html SourcedMethodReference>>= must not be based on identity (==) because it prevents to have multiple SourcedMethodReference pointing to the same CompiledMethod. And we need that because each tools will use different SourcedMethodReference. IMHO, SourcedMethodReference are just proxies and we don't care of their identity. I made these 6 tests pass by: -replacing MethodReference by SourcedMethodReference in SystemNavigationTest and al... -modifying the equality method of SourcedMethodReference: SourcedMethodReference>>= anotherMethodReference ^ (super = anotherMethodReference) and: [ (self timeStamp = self timeStamp) and: [ self sourceCode = self sourceCode ]] I have no idea of the impact of this change for the SourcedMethodReference stuff point of view. Written here: http://code.google.com/p/pharo/issues/detail?id=3398 #Luc

Dec. 10, 2010

Re: [Pharo-project] Issue 3397 in pharo: Behaviour>> #adoptInstance:

by pharo＠googlecode.com

Updates: Labels: Type-RequestForEnhancement Comment #2 on issue 3397 by rydier: Behaviour>> #adoptInstance: http://code.google.com/p/pharo/issues/detail?id=3397 (No comment was entered for this change.)

Dec. 10, 2010