- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ann] beacon - a slim announcement-based logging engine

by stepharo

> > I had troubles myself seeing how this can contribute to SystemLogger. > It looks a lot like âI donât like yours here is mineâ. But if you > remember that is the same reason why you've started SystemLogger. no I started SystemLogger because - it should log objects - it should be the basis for the future logger. > So you should be fair here. Now it is the time to see how we can > benefit from each other. I see it as an advantage to have code to > compare because a lot of discussions are usual too theoretical to make > something of it. > I did not have the time to look at svens and dorus code. But I will > because I had the impression, too, in the beginning that the > dispatching of events would be better done with announcements. If you have an hammer everything looks like a nail. To me it just kills my fun. > We all should review the other implementations and all of us should be > open minded for any reason why the own implementation is probably > _not_ the way to go. > I wish we can find an agreement about an optimal implementation we > like to promote. > > Norbert > > >>> It is called Beacon, it is based entirely on Announcements, it has >>> ~200 lines of code, it has no tags or levels, and in my opinion it >>> is fully functional. >>> >>> You can see a detailed description here including some informal >>> comparisons with SystemLogger: >>> http://www.humane-assessment.com/blog/beacon >>> >>> Please let me know what you think. I would be happy to join forces >>> to reach a mature solution that is both versatile and that can show >>> how Pharo is different. >> So should we see it as a competitor to SystemLogger? >> (you will say of course not) but I do not understand. >> >> >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> >>> "Every thing has its own flow" >> >

June 17, 2014

ConfigurationOfSandstoneDB?

by Udo Schneider

All, I'm searching for an up-to-date version of ConfigurationOfSandstoneDB. In the past I used the MetacelloRepository on SS. However this doesn't seem to be updated anymore (as a side-effect of SS being made read-only). So can anybody point me to an updated version of ConfigurationOfSandstoneDB or even better to an "official" successor of MetacelloRepository? Thanks, Udo

June 17, 2014

Survey: outdated slices

by Martin Dias

Hello dear Pharo community, I'm looking for fogbugz issues where a slice that was ready to be integrated became outdated because of other issues that were integrated before. In other words: the author of a slice writes it in Pharo-30XXX. Then, a responsible of integration wants to merge it in a Pharo-30YYY (where YYY > XXX), and the slice is rejected because it is old. Note: the reason of rejection can be a merge conflict, but I'm particularly interested in more subtle cases, where the reason was not that clear. Regards, MartÃn

June 17, 2014

Re: [Pharo-dev] Where is the postcard with syntax?

by Sven Van Caekenberghe

On 17 Jun 2014, at 10:04, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Itâs hard for me to agree with you. Pharoâs compact syntax is one of main features for me. Because in all other languages there was a time when I encountered some unknown constructs even after a year of usage. In Pharo you just have to learn syntax from postcard, and then if you want to know how some thing woks you just read the source code. > > Maybe this is some special thing related to me. I am with you Yuriy and I disagree with Kilon: Pharo/Smalltalk syntax is really special, it is about as minimal as you can get for a messaging object system, without being too simple. It is also almost magically elegant, IMO. I can only think of Scheme being somewhat similar. Most dynamic/scripting style languages still have too much syntax in the name of convenience and too many special cases or weird semantics. Statically typed languages are off the scale in this regard. Yes, to work in any development environment, you need to learn how to use many libraries and frameworks, but this is independent of the core language. BTW, it would be even cooler if the postcard method would make real sense and actually do something, but that is a real challenge ;-) > On 17 Jun 2014, at 09:59, kilon alios <kilon.alios(a)gmail.com> wrote: > >> personally I don't like this postcard , it looks too much like "snake oil marketing" to me. >> >> It creates the illusion that Pharo is much simpler than other programming languages as a programming language while nothing can be further from the truth. The idea here is to prove to the viewer that Pharo is based on a very simple recipe and that is of course true. But if we have to be honest is should come with a disclaimer for the potential users that Pharo is no blue pill and there tons of things outside this postcard you need to learn if you want to create the simplest Pharo application. I will be frank , as a language I dont find Pharo any simpler than let's say python , which I am more familiar with. And the fact that there is this simple recipe gave me zero benefits to me so far. Its a cool trick that may come handy down the line if I want to shape the language more to my needs, but I dont see doing this to a day by day basis. >> >> Now a "living coding postcard" stating the workflow of Pharo and demonstrating the power of the debugger is much more honest and frankly better marketing for Pharo. You show something to a person that will benefit his workflow on a day by day basis. >> >> >> On Tue, Jun 17, 2014 at 10:32 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> Now, who is creative enough to add âdynamic arrayâ (one with curly braces) and temporaries in a block to the original thing: >> >> exampleWithNumber: x >> | y | >> true & false not & (nil isNil) ifFalse: [self halt]. >> y := self size + super size. >> #($a #a "a" 1 1.0) >> do: [ :each | >> Transcript show: (each class name); >> show: ' ']. >> ^x < y >> >> >> >> Uko >> >> On 16 Jun 2014, at 15:35, Oscar Nierstrasz <oscar.nierstrasz(a)gmail.com> wrote: >> >>> >>> I got it from Stef, who always said it came originally from Ralph Johnson. >>> >>> http://c2.com/cgi-bin/wiki?SmalltalkSyntaxInaPostcard >>> >>> Googling around finds various copies of this, but no original source. >>> >>> Oscar >>> >>> On 16 Jun 2014, at 10:58 , Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>>> I guess itâs here: http://files.pharo.org/media/flyer-cheat-sheet.pdf >>>> >>>> I think that it would be interesting to put the syntax on a postcard. It can work as a proof of concept, some addition cheat-sheet for newcomers and also as some king of souvenir. >>>> >>>> Uko >>>> >>>> On 16 Jun 2014, at 10:36, stepharo <stepharo(a)free.fr> wrote: >>>> >>>>> you have the flyer of Damien (no idea where it is) but no real postcard. >>>>> >>>>> Stef >>>>> >>>>> On 16/6/14 09:35, Yuriy Tymchuk wrote: >>>>>> Hi guys, >>>>>> >>>>>> we all are talking about the syntax fitting in a postcard, but was there any real postcard with Pharo syntax prototype? This would be really interesting. >>>>>> >>>>>> Uko >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >

June 17, 2014

Re: [Pharo-dev] [Moose-dev] CodeCity and Spec

by Benjamin

>From what I remember, it was something like: RoassalModel new script: [ :view :canvas | my roassal stuff ]; openWithSpec Or you can then embed it as any other spec model Ben On 17 Jun 2014, at 10:27, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Are there any examples how to use it? Iâm not a Spec guru, so any snipers are useful :) > > Uko > > On 13 Jun 2014, at 14:34, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > >> Hola, >> >> AFAIK there are no plans for that. Maybe there is an alternative: there is a Roassal2 adaptor for Spec, Roassal2Spec package, which should now come with Roassal2. It allows you to have any Roassal2 visualization as a Spec ComposableModel. >> >> On Jun 13, 2014, at 4:47 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >>> Hi all, >>> >>> are there any suggestions for integrating CodeCity into Spec? E.g. using CodeCity visualisation in a view build by Spec. >>> >>> Uko >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >> >> >> >> ---> Save our in-boxes! http://emailcharter.org <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry >> PLEIAD lab - Computer Science Department (DCC) - University of Chile >> >> > >

June 17, 2014

Re: [Pharo-dev] Where is the postcard with syntax?

by Yuriy Tymchuk

I think that this is an issue of auto changing quotes to open and close. And something was just copied :) On 17 Jun 2014, at 10:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > > 2014-06-17 10:07 GMT+02:00 Damien Cassou <damien.cassou(a)gmail.com>: > On Tue, Jun 17, 2014 at 9:32 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Now, who is creative enough to add "dynamic array" (one with curly braces) > > and temporaries in a block to the original thing: > > > the postcard on our Pharo slides has a bit more (see slide 34): > http://www.slideshare.net/pharoproject/pharo-tutorial-at-ecooptutorial > > > > Why are there different single quote characters? > > (`aÂ´ in the literal array and ` ` by the Trascript show) > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

June 17, 2014

Re: [Pharo-dev] Where is the postcard with syntax?

by Damien Cassou

On Tue, Jun 17, 2014 at 10:55 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Why are there different single quote characters? > > (`aÂ´ in the literal array and ` ` by the Trascript show) > bug in the slide, thank you :-) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 17, 2014

Swapping morph in MorphicGenericAdapter

by Yuriy Tymchuk

Hi, Iâm still trying to integrate CodeCity into Spec. I know how to get a Morph and I know that I can use asSpecAdapter on morph, but I need to change the morph dynamically once widget in displayed. I thought about instantiating MorphicGenericAdapter from scratch and then swapping itâs morph, but I donât know how to refresh the widget. Uko

June 17, 2014

Re: [Pharo-dev] Where is the postcard with syntax?

by Nicolai Hess

2014-06-17 10:07 GMT+02:00 Damien Cassou <damien.cassou(a)gmail.com>: > On Tue, Jun 17, 2014 at 9:32 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > > Now, who is creative enough to add "dynamic array" (one with curly > braces) > > and temporaries in a block to the original thing: > > > the postcard on our Pharo slides has a bit more (see slide 34): > http://www.slideshare.net/pharoproject/pharo-tutorial-at-ecooptutorial > > Why are there different single quote characters? (`aÂ´ in the literal array and ` ` by the Trascript show) > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

June 17, 2014

Re: [Pharo-dev] [Moose-dev] CodeCity and Spec

by Yuriy Tymchuk

Are there any examples how to use it? Iâm not a Spec guru, so any snipers are useful :) Uko On 13 Jun 2014, at 14:34, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Hola, > > AFAIK there are no plans for that. Maybe there is an alternative: there is a Roassal2 adaptor for Spec, Roassal2Spec package, which should now come with Roassal2. It allows you to have any Roassal2 visualization as a Spec ComposableModel. > > On Jun 13, 2014, at 4:47 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Hi all, >> >> are there any suggestions for integrating CodeCity into Spec? E.g. using CodeCity visualisation in a view build by Spec. >> >> Uko >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >

June 17, 2014