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

Re: [Pharo-project] #and:and:and: deprecated on 1.1, why?

by Alexandre Bergel

> Yup. Another argument to kill and:and:and: > It reminds me > isKindOf:orOf: Ah ah ah! #isKindOf:orOf: Woooaaaa.... Your email made me laugh. Thanks Igor :-) Cheers, Alexandre > >>> But then which is the equivalence to #and:and:and: when I have many >>> conditions? >> >> a and: [b] and: [c] >> >> if a and c do not have side effect that may change the condition are equivalent >> to >> a and: [ b and: [c]] >> >> so you have express what you want >> >>> Perhaps I will say a stupidity... but , not is valid the implementation of >>> #&& and #|| messages instead of #and:... #or: .....? >> >> >> & and | are executing all their arguments while >> true & error -> error >> true and: [error] -> true but it is more costly >> >> >>> >>> ( aCondition1 && aCondition2 && aCondition3 ) ifTrue: [ <something> ] >>> >>> >>> Regards >>> -- >>> View this message in context: http://forum.world.st/and-and-and-deprecated-on-1-1-why-tp2230786p2231486.h… >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 26, 2010

Re: [Pharo-project] =nil to isNil rewrite part 1 in inbox

by Mariano Abel Coca

Issue 1594 is related to this. Cheers, Mariano. 2010/5/26 Mariano Martinez Peck <marianopeck(a)gmail.com> > Gabriel, is there an issue in the bug tracker for that? If not, please do > it! > > Thanks > > Mariano > > 2010/5/26 Gabriel Cotelli <g.cotelli(a)gmail.com> > >> >> SLICE-RewriteEqualsNilToIsNil-GabrielOmarCotelli.2 >> >> >> Rewrite = nil to isNil in Pharo Core code. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 26, 2010

Re: [Pharo-project] Image Lockdown/Deployment mode

by Gary Chambers

Mostly done via #disableProgrammerFacilities, though I note it is now deprecated in Pharo... Also, deactivating ProjectLauncher takes care of the startup script thing. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, May 26, 2010 3:02 PM Subject: Re: [Pharo-project] Image Lockdown/Deployment mode Good question we need that!!!! We were thinking about that with noury for 1.0 and got distracted. This is really important. Any step in that direction is really welcome > Does Pharo currently provide support for a deployment mode/image > locking mode? > > I think of the following scenario: > ================================== > If one builds a rich (client) app for a customer based on Pharo > (I mean a real app, no Smalltalk tool - for instance a game or > a commercial app) he may want to: > > - lock the image so nobody is able to hit Cmd-. > - exchange the Walkback to display a custom dialog instead > of proving debugger access to the end user. Do we provide a > hook already? > - replace world menu with a custom menu. Do we provide a > hook already? > - wants to disable code evaluation in edit fields using > * menus (no doIt, printIt, inspectIt just cut, copy, paste) > * keyboard (Cmd-d, ...) > - wants to disable Halos > - prevent reading scripts/projects at startup so nobody is > able to hijack the image and get access to the code > - disable the dependency on source and changes file > > Maybe this locking facility can be reenabled after entering a > password so a developer can still debug in the customers environment. > (I remember Andreas said that they protect the Teleplace > image and save the password hashed in image). > > Maybe Gary can share his experience to lock the "Pinesoft â MBagger" > image or others how they lock down their image. > > Either we provide such a (switchable) mode in the default image > or give a guide in the pharo book on how to restrict end user > access to the Smalltalk environment in deployed applications. > > Yes - we provide a #cleanUpForProduction method - but this is > more to reduce size. > > Maybe the old "Lockdown" package could be a start: > http://wiki.squeak.org/squeak/518 > > I think of a loadable package "ImageLocker" with a class > that can set/unset the appropriate preferences and provide > alternative error handlers, menues, ... > > Any comments? > > Thx > T. > > BTW: I remember having a hard time with the "deployment step" in most > commercial environments due to "striping" the image. Now this > is partly adressed by building images bottom to top using > Metacello now. One could load his app based on a core without > the extended dev-tools. > > But Pharo should really care to also easily disable developer > facilities so developers may use it as the platform for > their next project. > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 26, 2010

[Pharo-project] ReferenceStream, tree or graph?

by Mariano Martinez Peck

Hi folks. I have a question. Reading http://wiki.squeak.org/squeak/2318 it says: "This is a way of serializing a tree of objects into disk file. A ReferenceStream can store one or more objects in a persistent form, including sharing and cycles." I am confused. If it has cycles, shouldn't it be a graph instead of a tree? I know this is subtle, but it is important for me. I want to know if ReferenceStream supports a graph of objects, NOT only a tree. Does someone know? Thanks Mariano

May 26, 2010

Re: [Pharo-project] difference between Sequenceable and Ordered

by Schwab,Wilhelm K

Tristan, SequenceableCollection abstracts using integers to index a collection; from there, subclasses (OrderedCollection is one of them) specialize the behavior to create growable and non-growable collections, collections specific to certain types of objects, etc. The Squeak/Pharo hierarchy browsers are **terrible** which greatly complicates building an understanding of such things. If you use or have access to Windows, you might grab the Community Edition of Dolphin Smalltalk if only to use their class hierarchy browser to look around the collections hierarchy. Dolphin has the best IDE in the business. Another question you might be asking is which collection class to use? The workhorses include Dictionary, Bag, SortedCollection, OrderedCollection, and sometimes Array; String and ByteArray count too, though they and things like FloatArray hold only specific types of objects for speed, gc efficiency, external calls, etc.. For reasons completely inscrutable to me after more than 15 years of Smalltalk use, streams like to work with and grow an Array far more than an OrderedCollection. Some things are best tolerate than understood :) Does that help? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Tristan Bourgois [tr.bourgois(a)laposte.net] Sent: Wednesday, May 26, 2010 10:19 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] difference between Sequenceable and Ordered Does anybody can explain the difference between a Sequenceable Collection and an Ordered Collection? Thanks. Tristan Bourgois. -- View this message in context: http://forum.world.st/difference-between-Sequenceable-and-Ordered-tp2231718… Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 26, 2010

Re: [Pharo-project] #and:and:and: deprecated on 1.1, why?

by Igor Stasenko

On 26 May 2010 15:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > In general (but it often does not work :)) having a lot of conditions in OOP > means that you are missing class to dispatch on then. > Yup. Another argument to kill and:and:and: It reminds me isKindOf:orOf: >> But then which is the equivalence to #and:and:and: when I have many >> conditions? > > a and: [b] and: [c] > > if a and c do not have side effect that may change the condition are equivalent > to > a and: [ b and: [c]] > > so you have express what you want > >> Perhaps I will say a stupidity... but , not is valid the implementation of >> #&& and #|| messages instead of #and:... Â #or: .....? > > > & and | are executing all their arguments while > Â Â Â Â true & error -> error > Â Â Â Â true and: [error] -> true but it is more costly > > >> >> ( aCondition1 && aCondition2 && aCondition3 ) ifTrue: [ <something> ] >> >> >> Regards >> -- >> View this message in context: http://forum.world.st/and-and-and-deprecated-on-1-1-why-tp2230786p2231486.h… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

May 26, 2010

Re: [Pharo-project] #and:and:and: deprecated on 1.1, why?

by Lukas Renggli

>> - The exact semantics of #and:and:and: is not clear without knowing >> how it is implemented. >> >> - There are subtle semantic differences between "a and: [ b ] and: [ c >> ] and: [ d ]" and "a and: [ b and: [ c and: [ d ] ] ]" if the >> conditions have side-effects. > > That's not true. Both #and: and #and:and:and: (and friends) are > short-circuit, so they'll cause exactly the same side effects. I know that and this is *not* what I am talking about. What you point out is already discussed above, it is absolutely unclear what #and:and:and: does without looking at the implementation. The point is that blocks that are lexically nested "a and: [ b and: [ c ] ]" and blocks that are in a lexical sequence "a and: [ b ] and: [ c ]" do not have the same expressive power (temps, state) and do not necessarily behave the same. Lukas -- Lukas Renggli www.lukas-renggli.ch

May 26, 2010

Re: [Pharo-project] plan for 1.1

by Guillermo Polito

Where can I read something about Alien? I can give a little hand for the windows part :). On Wed, May 26, 2010 at 11:12 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Stef, > > I am more concerned about Alien on Linux, which is not working. Beyond > that, I want to learn more about how to make calls using Alien; the more I > read, the more I have my doubts about its ease of use. I will gladly eat > those words if it's easy to use. > > 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, May 26, 2010 10:04 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] plan for 1.1 > > yes this is good point. > I would like to have alien or ffi in 1.1. Now I do not know the status of > Alien on windows. > > On May 26, 2010, at 2:52 PM, Schwab,Wilhelm K wrote: > > > Stef, > > > > My initial reaction to 1.1's approaching release was "where are the > callbacks/aliens?" Sig appears to be offering some competition to Alien. > If he/we can provide a comprehensive and convenient way to make calls, do > callbacks, additionally put calls onto other OS threads, and do all of this > on the three major platforms, then it could easily turn out the best option > for external interfacing. > > > > I am happy to see us take time to get it right. My only concern would be > that we not fall into a pattern of leaving out the difficult things that we > set out to accomplish with a given release. Since 1.1 is approaching > releasable form and FFI/Alien/NB is unclear at present, a release makes > sense. > > > > Short answer: sure, whatever you say :) > > > > 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, May 26, 2010 4:20 AM > > To: Pharo Development > > Subject: [Pharo-project] plan for 1.1 > > > > Hi guys > > > > we were discussing how we can handle 1.1 and the flux of good changes. > > Here is the proposal: > > we take two or three weeks to let people try their code in 1.1 > beta > > we integrate fixes that are important or easy > > then we wait one week > > then we launch 1.1 rc and 1.2 unstable > > > > does this plan look ok for you? > > The key point is that we want to avoid to have a pile of changes pending > because they can rot easily. > > > > Stef > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 26, 2010

[Pharo-project] difference between Sequenceable and Ordered

by Tristan Bourgois

Does anybody can explain the difference between a Sequenceable Collection and an Ordered Collection? Thanks. Tristan Bourgois. -- View this message in context: http://forum.world.st/difference-between-Sequenceable-and-Ordered-tp2231718… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 26, 2010

Re: [Pharo-project] plan for 1.1

by Schwab,Wilhelm K

Stef, I am more concerned about Alien on Linux, which is not working. Beyond that, I want to learn more about how to make calls using Alien; the more I read, the more I have my doubts about its ease of use. I will gladly eat those words if it's easy to use. 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, May 26, 2010 10:04 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] plan for 1.1 yes this is good point. I would like to have alien or ffi in 1.1. Now I do not know the status of Alien on windows. On May 26, 2010, at 2:52 PM, Schwab,Wilhelm K wrote: > Stef, > > My initial reaction to 1.1's approaching release was "where are the callbacks/aliens?" Sig appears to be offering some competition to Alien. If he/we can provide a comprehensive and convenient way to make calls, do callbacks, additionally put calls onto other OS threads, and do all of this on the three major platforms, then it could easily turn out the best option for external interfacing. > > I am happy to see us take time to get it right. My only concern would be that we not fall into a pattern of leaving out the difficult things that we set out to accomplish with a given release. Since 1.1 is approaching releasable form and FFI/Alien/NB is unclear at present, a release makes sense. > > Short answer: sure, whatever you say :) > > 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, May 26, 2010 4:20 AM > To: Pharo Development > Subject: [Pharo-project] plan for 1.1 > > Hi guys > > we were discussing how we can handle 1.1 and the flux of good changes. > Here is the proposal: > we take two or three weeks to let people try their code in 1.1 beta > we integrate fixes that are important or easy > then we wait one week > then we launch 1.1 rc and 1.2 unstable > > does this plan look ok for you? > The key point is that we want to avoid to have a pile of changes pending because they can rot easily. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 26, 2010