March 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] new link to query all projects in smalltalkhub

by Martin BÃ¤hr

Excerpts from Merwan Ouddane's message of 2015-03-23 21:22:23 +0100: > I don't know if you want to spend some time on it, but what would be > great is for the projects to choose if they want to appear or not in > this list, there is already a distinction between public and private projects. as far as i could tell, private projects are not in the list. at least i could not find mine. > and have a little description of the project on mouse over :) please let the description be right next to the title, not hidden with mouseover. there are way to many projects to me mousing over each one to read them. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

March 24, 2015

choose event in Bern on March 31: alain plantec on Bloc + working session on Pharo IDE

by Tudor Girba

Hi, On March 31, we will have a one day of Pharo in Bern: 10:15 - 11:00 Talk by Alain Plantec on Bloc: Reinventing Morphic Registration: https://www.eventbrite.com/e/bloc-reinventing-morphic-choose-talk-tickets-5… 11:00 - 17:00 Working session on the Pharo IDE Registration: https://www.eventbrite.com/e/pharo-ide-choose-working-session-tickets-16283… The event will be held at the Software Composition Group: SchÃ¼tzenmattstrasse 14, Room 107, Bern The event is sponsored by CHOOSE a subgroup of the Swiss Informatics Society and hosted by the Software Composition Group at the University of Bern. They are primarily organized for CHOOSE and SI members, but the events are open for other students and professionals as well. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

March 23, 2015

Re: [Pharo-users] Collection with memory?

by Sven Van Caekenberghe

Stef, Like Denis said, there is no #next: in Xtreams, AFIACT. There are XTReadStream>>#get "Read an object from self. If there aren't any elements left in the stream, the Incomplete exception is raised." and XTReadStream>>#read: anInteger "Read anInteger's worth of elements from self and return them in a collection. If full anInteger number of elements cannot be read from the source, the Incomplete exception is raised." Like I said, these selector names were chosen to prevent confusion, on purpose. I think that is good. I also think that a lot of though went into the design. #++ could be aliased to #seekForward: and #-- to #seekBackward: I guess. I also do not really like the look of them. BTW, I think that the compatibility layer/wrapper is not good (I would be very surprised if it could hide all the semantic differences). What is the point to switch to a new stream API if you hide it ? Also, the current stream API is 'too wide', there are too many methods, too much is expected from streams. To change that, the users must be changed. Sven > On 23 Mar 2015, at 22:06, stepharo <stepharo(a)free.fr> wrote: > > >>>>> Yes but with >>>>> r next. >>>>> r next >>>> The choice for different selector names was intentional, by design. To avoid confusion, because #next and #get are not 100% identical (semantically). This is an important point. >>> No I asked martin personally. This is the real reason. There were also experimenting to offer an API closer to other language. >>> So that we have >>> r get. >>> r next: 4 >> IIRC, one difference between #get and #next is that >> >> get cannot return nil and will throw an Incomplete exception when EOF >> next can return nil and might throws an Exception >> >> Changing the meaning of an existing selector will cause many problems and discussions. People will think they do not have to change anything and they will be wrong. > Indeed now this is still not a nice API. > So what would be a nice name for get > > I do not get it. I'm probably too tired > > get so it is named get and not next. > get cannot return nil and will throw an Incomplete exception when EOF > but > next: that could be confused with next > can return nil and might throws an Exception (because it should follow next) :) > No stupid stef. > next: is from xtreams so it should follow get > get cannot return nil and will throw an Incomplete exception when EOF > Ahhhhhhhh this is probably clear. > > So could we be consistent > > nextItem > nextItems: > putItem: > > > Now since in anyways people will have to revisit they wrapping of next calls > which should probably wraped into and Exception. > I do not see the problem. It is because there is a wrapper that would turn an Xstream stream into a old API (then again I do not understand > because since the wrapper is another class it can have a next method that delegates to the correct wrapped xstream which may have or not the same api. > So what is the point? > > I mean once xtream will replace the old one it will be for about 10 years so > I'm sorry but we should get the api right (and yes I know that ++ -= are correct smalltalk still they SUCK). > > Stef > > >

March 23, 2015

Re: [Pharo-users] Package dependencies

by Thierry Goubier

Le 23/03/2015 22:19, Laura Risani a Ã©crit : > Didn't thought of it, then i should write a Configuration. How does > Configuration Browser get to know about all the configurations it lists? As soon as the configuration is saved into the right repository, such as MetaRepoForPharo40 on smalltalkhub, then the configuration will appear in the configuration browser. Thierry

March 23, 2015

Re: [Pharo-users] Package dependencies

by Laura Risani

(i want to know what i should do to make my project available through it) On Mon, Mar 23, 2015 at 6:19 PM, Laura Risani <laura.risani(a)gmail.com> wrote: > Didn't thought of it, then i should write a Configuration. How does > Configuration Browser get to know about all the configurations it lists? > > On Mon, Mar 23, 2015 at 5:55 PM, stepharo <stepharo(a)free.fr> wrote: > >> Mmmm, since the project is just one package and the additional packages >> are examples, i'm writing for the moment a Gofer script instead. >> >> this means that it will not be loadable from the MetacelloBrowser, that >> it will not appear in the catalog..... >> >> Stef >> >> Thank you! >> >> On Sun, Mar 22, 2015 at 1:53 PM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> Le 22/03/2015 17:41, stepharo a Ã©crit : >>> >>>> Defining a configuration for your project. >>>> >>> >>> Even easier: define a BaselineOf for your project (a configuration will >>> have you write a baseline anyway). And use Metacello to load it. >>> >>> Thierry >>> >>> >>> You can have a look for example in the Mines configuration it depends on >>>> LedMorph >>>> >>>> Le 22/3/15 16:25, Laura Risani a Ã©crit : >>>> >>>>> Hi all, >>>>> >>>>> What's the easiest way at the moment to make a package when downloaded >>>>> from a repo automatically download others (which depend only on core >>>>> system classes)? >>>>> >>>>> Best, >>>>> Laura >>>>> >>>> >>>> >>>> >>>> >>> >>> >> >> >

March 23, 2015

Re: [Pharo-users] Package dependencies

by Laura Risani

Didn't thought of it, then i should write a Configuration. How does Configuration Browser get to know about all the configurations it lists? On Mon, Mar 23, 2015 at 5:55 PM, stepharo <stepharo(a)free.fr> wrote: > Mmmm, since the project is just one package and the additional packages > are examples, i'm writing for the moment a Gofer script instead. > > this means that it will not be loadable from the MetacelloBrowser, that it > will not appear in the catalog..... > > Stef > > Thank you! > > On Sun, Mar 22, 2015 at 1:53 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Le 22/03/2015 17:41, stepharo a Ã©crit : >> >>> Defining a configuration for your project. >>> >> >> Even easier: define a BaselineOf for your project (a configuration will >> have you write a baseline anyway). And use Metacello to load it. >> >> Thierry >> >> >> You can have a look for example in the Mines configuration it depends on >>> LedMorph >>> >>> Le 22/3/15 16:25, Laura Risani a Ã©crit : >>> >>>> Hi all, >>>> >>>> What's the easiest way at the moment to make a package when downloaded >>>> from a repo automatically download others (which depend only on core >>>> system classes)? >>>> >>>> Best, >>>> Laura >>>> >>> >>> >>> >>> >> >> > >

March 23, 2015

Using Google service discovery API's with Pharo Smalltalk by Richard J. Prinz

by Sven Van Caekenberghe

I hadn't seen this posted on the mailing list, but this is really cool stuff. Using Google service discovery API's with Pharo Smalltalk by Richard J. Prinz > http://www.min.at/prinz/?x=entry:entry150318-104537 <http://www.min.at/prinz/?x=entry:entry150318-104537;comments:1#comments> Nice work, Richard ! Sven

March 23, 2015

Re: [Pharo-users] Collection with memory?

by stepharo

>>>> Yes but with >>>> r next. >>>> r next >>> The choice for different selector names was intentional, by design. To avoid confusion, because #next and #get are not 100% identical (semantically). This is an important point. >> No I asked martin personally. This is the real reason. There were also experimenting to offer an API closer to other language. >> So that we have >> r get. >> r next: 4 > IIRC, one difference between #get and #next is that > > get cannot return nil and will throw an Incomplete exception when EOF > next can return nil and might throws an Exception > > Changing the meaning of an existing selector will cause many problems and discussions. People will think they do not have to change anything and they will be wrong. Indeed now this is still not a nice API. So what would be a nice name for get I do not get it. I'm probably too tired get so it is named get and not next. get cannot return nil and will throw an Incomplete exception when EOF but next: that could be confused with next can return nil and might throws an Exception (because it should follow next) :) No stupid stef. next: is from xtreams so it should follow get get cannot return nil and will throw an Incomplete exception when EOF Ahhhhhhhh this is probably clear. So could we be consistent nextItem nextItems: putItem: Now since in anyways people will have to revisit they wrapping of next calls which should probably wraped into and Exception. I do not see the problem. It is because there is a wrapper that would turn an Xstream stream into a old API (then again I do not understand because since the wrapper is another class it can have a next method that delegates to the correct wrapped xstream which may have or not the same api. So what is the point? I mean once xtream will replace the old one it will be for about 10 years so I'm sorry but we should get the api right (and yes I know that ++ -= are correct smalltalk still they SUCK). Stef

March 23, 2015

Re: [Pharo-users] Collection with memory?

by stepharo

The problem is that - we do not want to open alone another subproject - we would like to remove the old stream (make them loadable) - we should not get the system with two stream libraries. Stef Le 23/3/15 10:06, Denis Kudriashov a Ã©crit : > > 2015-03-23 0:40 GMT+03:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Le 22/3/15 22:05, Sven Van Caekenberghe a Ã©crit : > > On 22 Mar 2015, at 21:44, Denis Kudriashov > <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: > > Hi > > It is another perfect task for XStreams: > > r := #('a12' 'b12' 'a13' 'a14' 'c23' 'a16') reading > selecting: [:each | each first = $a]. > r get > a12 > r get > a13 > > Beautiful ! > > > Yes but with > r next. > r next > > I was reading the XTreams API recently but this is forbidden for > me to open another project before finishing > what I started. Now if somebody else would like to help pushing > Xtreams in Pharo 50. > > > > I think it is important to have XStreams in pharo by default. Because > current streams (from Smalltalk 80) are too powerfull. And when > XStreams not in image or can't be loaded easilly people can prefer to > use existed streams solution. I was such man when I was need quickly > solve some parsing and analizing data task but I can't load XStreams. > And I was solve my task with classic streams. It was simple solution. > But with XStreams it will be much compact and intuitive implementation. >

March 23, 2015

Re: [Pharo-users] Collection with memory?

by stepharo

>> No I asked martin personally. This is the real reason. There were also experimenting to offer an API closer to other language. >> So that we have >> r get. >> r next: 4 > IIRC, one difference between #get and #next is that > > get cannot return nil and will throw an Incomplete exception when EOF > next can return nil and might throws an Exception > > Changing the meaning of an existing selector will cause many problems and discussions. People will think they do not have to change anything and they will be wrong. > >> superb inconsistencet >>>> I was reading the XTreams API recently but this is forbidden for me to open another project before finishing >>>> what I started. Now if somebody else would like to help pushing Xtreams in Pharo 50. >>>> :) >>> Well, it does/did load OK in Pharo 3 and probably will in 4 too. >>> >>> https://ci.inria.fr/pharo-contribution/job/Xtreams/ >> Yes loading is just a part of the story :) >> We should remove the old ones. >> >> And we should revise the API because >> I **hate ++, -=, += > Yeah, but is not because it looks a bit like C++ that it is no longer Smalltalk, these are still normal messages. > > But yes, some API discussions are possible.

March 23, 2015