February 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing

by Schwab,Wilhelm K

That does always seem to be the case. But "boring" is our problem, assuming the thing works as advertised, others might bore themselves to success of which we can only dream - we should be careful about passing judgments. Scalable is a needed element, and I am not at all convinced that many "enterprise" systems deliver on this point any more than we could (can?) w/ load balancing. Inelegant is probably a key feature of most "enterprise" *code* that gets copy/pasted/tweaked vs. truly engineered for reuse. How's that? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Marcus Denker [marcus.denker(a)inria.fr] Sent: Tuesday, February 21, 2012 2:32 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing On Feb 21, 2012, at 3:11 AM, Krishsmalltalk wrote: > Yes, > > Do not emphasize on one or few keywords. Malleable is better than plastic (can be off putting for any environment conscious) > > Adopt the Pharo motto: > > "Pharo shall be one of the best enterprise platform in 3 years." Isn't "Enterprise Plattform" another word for "boring and complicated" ?? Marcus -- Marcus Denker -- http://marcusdenker.de

Feb. 21, 2012

Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing

by Marcus Denker

On Feb 21, 2012, at 3:11 AM, Krishsmalltalk wrote: > Yes, > > Do not emphasize on one or few keywords. Malleable is better than plastic (can be off putting for any environment conscious) > > Adopt the Pharo motto: > > "Pharo shall be one of the best enterprise platform in 3 years." Isn't "Enterprise Plattform" another word for "boring and complicated" ?? Marcus -- Marcus Denker -- http://marcusdenker.de

Feb. 21, 2012

Re: [Pharo-project] Nautilus Refactorings

by StÃ©phane Ducasse

On Feb 20, 2012, at 11:33 PM, Mariano Martinez Peck wrote: > One last thing: when you type the name of a class somewhere and you do a cmd+b I think it would be much better if Nautilus open the "normal" browser and not "hierarchy" one. having cmd+h for hierarchy would be great :) Ben we should produce a configuration because this is important. What you can do is at least load the baseline and snapshot only when you will release on version for 1.4 and 1.5 > > > On Mon, Feb 20, 2012 at 8:38 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > To be honest, if it works, I do not want to lose my time on Configuration > > > It shouldn't be done by hand, but generated by a tool :) > > > Ben > > On Feb 20, 2012, at 8:06 PM, Mariano Martinez Peck wrote: > >> >> >> On Tue, Feb 14, 2012 at 6:39 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> Hello guys, >> >> I know a some of you are waiting for the integration of the RB engine into Nautilus. >> >> Some of them are already implemented, so if you wanna test them, here is the gofer script >> >> Gofer new >> url: 'http://ss3.gemstone.com/ss/Nautilus'; >> package: 'ConfigurationOfNautilus'; >> load. >> >> (Smalltalk at: #ConfigurationOfNautilusRefactoring) perform: #loadDefault >> >> >> >> >> So...that's the way of loading Nautilus with refactorings? Wouldn't it be better to include RB dependencis in ConfigurationOfNautilus and have a specific group there. So you can do for example >> >> ConfigurationOfNautilus project stableVersion load: 'WithRefactorings'. >> >> ? >> >> BTW, I checked the ConfigurationOfNautilusRefactoring and it looks you miss a critical feature of Metacello: project references :) From ConfigurationOfNautilusRefactoring you can directly depend on ConfigurationOfRB or ConfigurationOfNautilus rather than duplicating everything in there. Don't tell Stef you didn't read the chapter hahahaha >> >> >> >> It loads everything. >> >> For now I have only done some refactorings for classes, so if you popup the menu on a class, a new item named Refactoring should appear :) >> >> Moreover, the 'rename class' method is replaced by the RB one :) >> >> >> Thanks in advance for your feedback, and if you want to participate, you are more than welcome :) >> >> >> Ben >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Feb. 21, 2012

Re: [Pharo-project] how can I use Nautilus with OCompletion?

by StÃ©phane Ducasse

About Ocompletion we discussed with the workshop at bern that OCompletion breaks ECompletion so that it would be better to only use ECompletion and see how OCompletion could be made working without breaking ECompletion so that people can use the one they like. I like graphically ECompletion but functionally I prefer OCompletion. Now I understand that people prefer the inverse so it would be good to investigate this problem. Any taker? Stef

Feb. 21, 2012

Re: [Pharo-project] Script for building 1-click images

by StÃ©phane Ducasse

excellent news!! Thanks christophe! On Feb 20, 2012, at 4:33 PM, Marcus Denker wrote: > > On Feb 20, 2012, at 4:27 PM, StÃ©phane Ducasse wrote: > >> >> On Feb 20, 2012, at 11:03 AM, Martin Sandiford wrote: >> >>> On Monday, February 20, 2012, Sven Van Caekenberghe wrote: >>> But I believe the general feeling is that the VM included in the 1.3 One-Click is not the most up to date one, maybe someone else can give a definitive answer of what should be done best to make the most up to date One-Click. >>> >>> The script fetches the latest successful CogVM build from Jenkins for Linux and MacOS. If there is a better source, then it should not be too hard to change. >>> >>> Would also appreciate any info on the best source for a Windows VM tooâ¦ >> >> we have some problems of stability with the Windows jenkins slave. > > > But lots of progress lately... thanks to Christophe. > > 32 win slave is up and connected to > > https://ci.lille.inria.fr/pharo/computer/pharo-build-732.lille.inria.fr/ > > Next steps: > > -> Win VM Build setup there > -> Pharo setup so we can run the tests. > > After that: > -> Win 64bit slave > -> Linux 64bit slave > > -- > Marcus Denker -- http://marcusdenker.de > >

Feb. 21, 2012

Re: [Pharo-project] error trying to upload to ss3

by Nicolas Cellier

Agree with Igor, legacy streams suck. I think that Colin purpose was to produce a cleaner FSStream, but maybe now he is thinking of using Xtreams. Otherwise, it is too tempting to bring the mud back for very noble compatibility reasons. Nicolas Le 21 fÃ©vrier 2012 01:40, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > On 20 February 2012 17:11, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> This is silly, because Zinc also only works with or needs binary streams. >> >> But I have to know what kind of stream comes in, so I think it would not hurt to implement >> >> isBinary >> Â Â Â Â "I am always binary" >> >> Â Â Â Â ^ true >> > > I would love to have streams at some day, which don't trouble > themselves about being bivalent. > Imo all i/o streams should be inherently binary, and only wrapper > streams which can allow reading/writing text into them. > > its clear that in modern times it is not enough to have just two > modes: text or binary. > a 'text' is very vague term today, because next question is what its > encoding, what is line ending convention etc etc.. the whole bunch of > variations which is better to implement by using wrappers. > > Btw, Sven > > isBinary > Â Â Â Â ^ binary isNil > Â Â Â Â Â Â Â Â ifTrue: [ stream isBinary ] > Â Â Â Â Â Â Â Â ifFalse: [ binary ] > > can be written as: > > isBinary > Â Â Â Â ^ binary ifNil: [ stream isBinary ] > > or you doing it on purpose? > >> Sven >> >> On 20 Feb 2012, at 16:53, StÃ©phane Ducasse wrote: >> >>> camillo >>> >>> I'm trying your script with the latest image. >>> >>> >>> | f files| >>> f := FSFilesystem disk workingDirectory / 'www.squeaksource.com' / 'Kozen'. >>> files := f glob: [ :each| each basename endsWith: '.mcz']. >>> >>> files do: [ :file ||entity stream| >>> Â Â Â stream := file readStream. >>> Â Â Â (entity := ZnStreamingEntity type: ZnMimeType applicationOctetStream) >>> Â Â Â Â Â Â Â stream: stream; >>> Â Â Â Â Â Â Â contentLength: stream size. >>> Â Â Â Transcript show: file; cr. >>> Â Â Â "upload the version to gemstone" >>> Â Â Â ZnClient new >>> Â Â Â Â Â Â Â systemPolicy; >>> Â Â Â Â Â Â Â beOneShot; >>> Â Â Â Â Â Â Â signalProgress: true; >>> Â Â Â Â Â Â Â ifFail: [ :exception | Transcript show: file basename; show: ' '; print: exception ]; >>> Â Â Â Â Â Â Â username: 'sd' password: 'sn00py_'; >>> Â Â Â Â Â Â Â entity: entity; >>> Â Â Â Â Â Â Â url: ( 'http://ss3.gemstone.com/ss/Kozen/', file basename); >>> Â Â Â Â Â Â Â put ] >>> Â Â Â displayingProgress: 'Uploading mcz' >>> >>> >>> apparently FSReadStream does not know isBinary >>> >>> >>> >>> streamFrom: inputStream to: outputStream size: totalSize >>> Â Â Â | bufferSize buffer leftToRead | >>> Â Â Â bufferSize := 4096 min: totalSize. >>> Â Â Â buffer := (inputStream isBinary ifTrue: [ ByteArray ] ifFalse: [ String ]) new: bufferSize. >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^^^^^^^^^^ >>> Â Â Â leftToRead := totalSize. >>> Â Â Â [ leftToRead > 0 ] >>> Â Â Â Â Â Â Â whileTrue: [ | readCount | >>> Â Â Â Â Â Â Â Â Â Â Â readCount := bufferSize min: leftToRead. >>> Â Â Â Â Â Â Â Â Â Â Â inputStream next: readCount into: buffer. >>> Â Â Â Â Â Â Â Â Â Â Â leftToRead := leftToRead - readCount. >>> Â Â Â Â Â Â Â Â Â Â Â outputStream next: readCount putAll: buffer startingAt: 1 ] >> >> > > > > -- > Best regards, > Igor Stasenko. >

Feb. 21, 2012

[Pharo-project] How to cook Mr Popatoe Process?

by StÃ©phane Ducasse

Hi guys we have practically two solutions to cook a troll: - either I remove his email address from the list (2 min) a bit rude and unfriendly but this is a troll after all ;) - or we all create a nice rule: as Read I suggest you all to do 2 and keep you good energy for helping and not arguing endless with Mr Potatoe Process. Did you count the amount of time we all spent already on that? Have fun. Stef (I have my rule and I do not read such mail anymore).

Feb. 21, 2012

Re: [Pharo-project] "Do not feed the trolls"

by Schwab,Wilhelm K

+10. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Stuart Herring [st-lists(a)stuartherring.com] Sent: Monday, February 20, 2012 9:29 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] "Do not feed the trolls" > > Develop the development process! > You keep saying this, but you don't explain what you mean. You think Pharo's development process is flawed. Ok, we get that. But what exactly do you suggest be done about it? To be clear - I am _not_ asking to hear what's _wrong_ with it. I want to hear a positive suggestion of something that can be done. Something practical and possible. Once given that, Stephane and the others can either use the information, or not. But either way you will have said your piece and there will be no need to say any more.

Feb. 21, 2012

Re: [Pharo-project] syntax error in StartupLoader script

by Ben Coman

I loaded SLICE-Issue-5290 onto a freshly unzipped Pharo-1.4-14341 + cogwin_r2522.zip This caused a problem with the debugger as follows. In workspace I execute... self halt. x := 1. y := 2. z := x+y. I click the second line of the stack "UndefinedObject>>DoIt" which now shows "halt" highlighted. I click <Into> and " := 1" is now highlighted. I click <Into> again and nothing happens. There is no further response from any of the debugger buttons, although <Full Stack> causes the window to flash once. I can temporarily fix this misbehaviour by forcing #isPostMortem to always return false. Camillo Bruni wrote: > you can try to load > > SLICE-Issue-5290-Cleanup-Startup-Error-Handling-CamilloBruni.2 > > from the pharoInbox which will significantly improve the error responses during startup. > > best > cami > > > On 2012-02-18, at 00:19, Ben Coman wrote: > > >> When using the following StartupLoader script >> >> StartupLoader default executeAtomicItems: { >> StartupAction name: 'Shared Package Cache' code: [ MCCacheRepository default directory setPathName: 'C:\Apps\Smalltalk\!Shared-Package-Cache'.]. >> }. >> >> I was getting a "syntax error in startup" that I could not identify (is it obvious to others?) >> This was due to the debugger not opening at the point of error since SmalltalkImage>>executeDeferredStartupActions catches the errors. So I hacked this as follows... >> deferredStartupActions do: [:each | >> [ each cull: resuming ] value. >> "btcdebug >> on: Halt >> do: [ :err| >> Smalltalk >> logError: '==== Startup Error: ', err description >> inContext: err signalerContext. >> errors add: err]"]. >> >> and then after a quit and restart the dialog "Syntax error: Unmatched string quote" appeared with... >> StartupLoader default executeAtomicItems: { >> StartupAction name: 'Shared Package Cache' code: [ MCCacheRepository default directory setPathName: _Unmatched string quote_ -> 'C:\Apps\Smalltalk\ >> >> So after removing "!" from the folder name the syntax error went away. >> >> So now a few questions... >> >> 1. Is there a simpler way to debug the startup scripts that I have missed? >> If not, can a StartupLoader>>test or similar be implemented which runs the same as at image start time but without the error catching in executeDeferredStartupActions, rather than needing to hack executeDeferredStartupActions as I did. >> >> 2. Is it reasonable to set a shared package cache in the startup like I have? Or are there some obvious problems with this that I don't see? >> I would like to avoid downloading all packages every time unzip a fresh image for testing. >> >> 3. Is the invalid "!" fixable (though of course I've worked around it)? >> >> I'll open any required bug entries. This was with Pharo-14333 / cogwin_r2522.zip / Windows 7. >> >> cheers, -ben >> >> >> >> > > > >

Feb. 21, 2012

Re: [Pharo-project] "Do not feed the trolls"

by Stuart Herring

> > Develop the development process! > You keep saying this, but you don't explain what you mean. You think Pharo's development process is flawed. Ok, we get that. But what exactly do you suggest be done about it? To be clear - I am _not_ asking to hear what's _wrong_ with it. I want to hear a positive suggestion of something that can be done. Something practical and possible. Once given that, Stephane and the others can either use the information, or not. But either way you will have said your piece and there will be no need to say any more.

Feb. 21, 2012