March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] in anybody out there? who uses 2.0?

by Norbert Hartl

Am 27.03.2013 um 15:24 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > Here in Pharo headquarters we are shock that there are just 10 new bugs reported for 2.0 after the release... > So... I wonder... is that because we made a really cool release, or just because nobody is using it? > Most of my stuff is still on 1.4. As there is no big reason to move, I don't move because it takes time I can't spend at the moment. It will take some time to get used to the new environment, too. That means I need to figure out how to reestablish most of the 1.4 behavior (keyboard shortcuts, etc..) first. I will move on a project by project basis to 2.0 and for the time I need to work in a mixed environment I'm not ready to use two different UI/keyboard/mouse/whatever systems. So mimicking 1.4 behavior in 2.0 is first and getting used to the new ways comes after. Getting used to new things does not include keyboard shortcuts. I don't like them and I fear the day the support for 1.x shortcuts will be treated as legacy burden. It's just that there are people that hate emacs and everything that is like it :) But I'm in progress to move a project to 2.0. We'll see! Norbert

March 27, 2013

Re: [Pharo-project] Suggestion about Phexample and StateSpecs(Mocketry) integration

by Denis Kudriashov

2013/3/27 Tudor Girba <tudor(a)tudorgirba.com> > Perhaps Mocketry would be a good topic for a "Show us your projects" > session. Then we can try to go into a couple of more details. > > Unfortunately I can't participate conference this year > Cheers, > Doru > > > On Mar 27, 2013, at 12:42 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > Sounds good to me. > > > > On 26 Ð±ÐµÑ. 2013, at 23:00, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > > >> > >> On 2013-03-26, at 19:45, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > >> > >>> 2013/3/26 Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > >>> > >>>> Ok, and what if we will change behavior a bit so if no definitions > were > >>>> found it will send the incoming message to enclosed object? This way > it > >>>> will work like phexample but will also allow to define some fancy DSL. > >>>> > >>> > >>> We can copy all phexample syntax methods into single class inside > >>> StateSpecs package but replace implementation with pragmas approach. So > >>> anybody can browse implementors like usual and it will not required any > >>> special cases. > >>> > >>> How I can influence your interest, guys? I can provide cleaning, > comments, > >>> improvements to StateSpecs. I opened for your requirements. > >>> Phexample become quite popular and can be part of Pharo sometimes. > >>> Mocketry/StateSpecs used by people too. > >>> It would be bad if this packages can't be used together. > >> > >> sorry for starting the whole rant :) I am veery busy at least until > tomorrow > >> > >> Yuriy we can discuss that after tomorrow? > >> I would as well appreciate some common solution to avoid the selector > clash. > >> > >> > >> > >>>> On 26 Ð±ÐµÑ. 2013, at 07:46, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >>>> > >>>> Hello > >>>> 2013/3/26 Camillo Bruni <camillobruni(a)gmail.com> > >>>> > >>>>> Definitely StateSpec looks more mature and can be used in a more > flexible > >>>>> way. > >>>>> But I am not a big fan of the pragma magic. Why? > >>>>> It breaks all tools for me :/. If I see a message send I want to be > able > >>>>> to: > >>>>> - browse it, so I can see who implements it? > >>>>> - debug it directly to get to the real method. > >>>>> > >>>>> SateSpec does indeed help writing readable code by allowing almost > >>>>> grammatically > >>>>> correct sentences. However I don't think this is the way to program. > I am > >>>>> a big > >>>>> fan of stupid english: > >>>>> > >>>>> `foo should isKindOf: Bar` vs. `foo should be an instance of: Bar` > >>>>> > >>>>> If I want to figure out how the first one works, I can simply browse > the > >>>>> implementors of #should and/or #isKindOf: where is the StateSpec > version > >>>>> I am > >>>>> lost. I have to rely on "contains string literal" to get the > sources, for > >>>>> me > >>>>> that is very strange. > >>>>> > >>>> > >>>> I think main thing you want is easilly explore all available should > >>>> syntax. And StateSpecs can be easilly adopted for such task. We can > just > >>>> move all methods with syntax pragmas to single class. So you can open > this > >>>> class and see what available. > >>>> > >>>> To get implementors of some "should expression" you should use senders > >>>> search of syntax words instead of implementors. Syntax words in > StateSpecs > >>>> is just method literals ( <syntax: #(be an instance of:)>, #() is just > >>>> array of symbols). > >>>> > >>>> Interesting that StateSpecs has more explicit syntax system. How you > can > >>>> explore in Phexample expression: > >>>> > >>>> object should be true > >>>> ? > >>>> > >>>> You have separate PheMatcher>>be and PheMatcher>>true methods and > there is > >>>> no places in code where you can see that this messages can and should > be > >>>> used together. > >>>> But with StateSpecs you should put pragma with explicit expression > like: > >>>> > >>>> Equal>>true: anObject > >>>> <syntax: #(be true)> > >>>> ^self return: (IdentitySpec pattern: true) > >>>> > >>>> So with StateSpecs you have full syntax expression at one place which > can > >>>> be easy explored. > >>>> And for example to support Phexample mesage #beTrue you should just > add > >>>> another pragma: > >>>> > >>>> Equal>>true: anObject > >>>> <syntax: #(be true)> > >>>> <syntax: #(beTrue)> > >>>> ^self return: (IdentitySpec pattern: true) > >>>> > >>>> So with Phexample you can browse implementors of "single word should > >>>> expressions". But with Phexample if you browse implementors of #be > like > >>>> messages you have no idea how it can be used. > >>>> In StateSpecs you should use senders. And with StateSpecs if you > browse > >>>> "any syntax word implementors" by senders seach you will see all > possible > >>>> usage cases. And if I move all methods with syntax pragmas to single > class > >>>> you can easilly see all possible expressions in one place. > >>>> > >>>> `foo should isKindOf: Bar` vs. `foo should be an instance of: Bar` > >>>>> > >>>> > >>>> With StateSpecs it should be > >>>> > >>>> foo should be a kind of: Bar > >>>> > >>>> And as I said before It is simple task to support all Phexample > >>>> expressions by StateSpecs pragmas > >>>> > >>>> Best regards, > >>>> Denis > >>>> > >>>> > >>>> > >> > >> > > > > > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > >

March 27, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by Stephan Eggermont

Stef wrote: >we would like to use seaside to validate the VM and also make sure that Seaside31. works perfectly in Pharo2.0. >I saw that some of you have a working configuration. Where can we find it because we would like to publish it in the >MetaRepoForPharo20. We have it working, but it does not have the Seaside Panel (& browser). At last Esug Seaside sprint I started redoing them in Spec, but never managed to spend more time on them. They are in the Seaside31 repository on squeaksource: Seaside-Pharo-Tools-Spec (might need renaming to Pharo20). Stephan

March 27, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by Esteban A. Maringolo

2013/3/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Wed, Mar 27, 2013 at 2:11 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> Hi guys >> >> we would like to use seaside to validate the VM and also make sure that >> Seaside31. works perfectly in Pharo2.0. >> I saw that some of you have a working configuration. Where can we find it >> because we would like to publish it in the >> MetaRepoForPharo20. > > > +9999. I would love to have working confs for Seaside 3.1, Pier 2 and > Magritte 2. And speaking of latest versions why not Magritte 3? ;-) Esteban A. Maringolo

March 27, 2013

Re: [Pharo-project] in anybody out there? who uses 2.0?

by Sebastian Sastre

I don't use it yet. But you can bet you'll hear about it:D Let things come to you and keep the great work. sebastian o/ On Mar 27, 2013, at 11:24 AM, Esteban Lorenzano wrote: > Hi, > > Here in Pharo headquarters we are shock that there are just 10 new bugs reported for 2.0 after the release... > So... I wonder... is that because we made a really cool release, or just because nobody is using it? > > Cheers, > Esteban > >

March 27, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by Mariano Martinez Peck

On Wed, Mar 27, 2013 at 2:11 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > we would like to use seaside to validate the VM and also make sure that > Seaside31. works perfectly in Pharo2.0. > I saw that some of you have a working configuration. Where can we find it > because we would like to publish it in the > MetaRepoForPharo20. > +9999. I would love to have working confs for Seaside 3.1, Pier 2 and Magritte 2. Cheers, -- Mariano http://marianopeck.wordpress.com

March 27, 2013

[Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by StÃ©phane Ducasse

Hi guys we would like to use seaside to validate the VM and also make sure that Seaside31. works perfectly in Pharo2.0. I saw that some of you have a working configuration. Where can we find it because we would like to publish it in the MetaRepoForPharo20. Stef

March 27, 2013

Re: [Pharo-project] in anybody out there? who uses 2.0?

by stephane ducasse

Thanks! STef > Esteban wrote: >> Here in Pharo headquarters we are shock that there are just 10 new bugs reported for 2.0 after the release... >> So... I wonder... is that because we made a really cool release, or just because nobody is using it? > > It is a cool release and we are using it. > > Sorry about the lack of issues, I just added 10158 for you. > > We have been mostly doing a lot of work making our stuff work on Pharo 2.0. > That mostly involves changing our code, not Pharo 2.0. So I'd say it is stable enough. > Just keep up the speed. > > Cheers, > Stephan > >

March 27, 2013

Re: [Pharo-project] in anybody out there? who uses 2.0?

by Stephan Eggermont

Esteban wrote: >Here in Pharo headquarters we are shock that there are just 10 new bugs reported for 2.0 after the release... >So... I wonder... is that because we made a really cool release, or just because nobody is using it? It is a cool release and we are using it. Sorry about the lack of issues, I just added 10158 for you. We have been mostly doing a lot of work making our stuff work on Pharo 2.0. That mostly involves changing our code, not Pharo 2.0. So I'd say it is stable enough. Just keep up the speed. Cheers, Stephan

March 27, 2013

Re: [Pharo-project] More GSoC ideas wanted, 3 days left ....

by Serge Stinckwich

One more idea about SciSmalltalk! Title: SciSmalltalk - Solving Ordinary Differential Equations in Smalltalk Level: (intermediate) Possible mentor: Serge Stinckwich Possible second mentor: ? Description SciSmalltalk is a new Smalltalk project, similar to existing scientific libraries like NumPy, SciPy for Python or SciRuby for Ruby. SciSmalltalk already provide basic functionalities under MIT licence: complex and quaternions extensions, random number generator, fuzzy algorithms, LAPACK linear algebra package, Didier Besset's numerical methods, ... We want to extend SciSmalltalk to solve ODE (Ordinary Differential Equations). SciSmalltalk is available here: https://github.com/SergeStinckwich/SciSmalltalk Technical Details The development of this project is to be done in Pharo Smalltalk, but the code could be portable to other Smalltalk flavors. We want to build a library of ODE solvers that take care about performance without sacryifing flexibility. OdeInt could be used as an example to develop a Smalltalk library: http://headmyshoulder.github.com/odeint-v2/index.html The student will need to have basic knowledge about differential equations and numerical algorithms. Units tests should also be provided. Benefits to the Student The student will help the Smalltalk community in a very concrete way. The student will learn to design well-designed code with tests. Benefits to the Community Having a basic ODE library is very important if we want to develop Smalltalk in new domains like robotics, high performance computing, computer vision, bio-computing, .... The lack of numeric librairies hamper the use of the Smalltalk in a scientific context at the moment. Regards, On Tue, Mar 26, 2013 at 12:36 PM, Janko MivÅ¡ek <janko.mivsek(a)eranova.si> wrote: > Dear Pharoers, > > Ideas are slowly coming, 14 so far, but this is way below the 30+ in > previous years. So, stretch your brain, come with some more ideas, which > will be interesting for potential students and of course useful for our > community. Students you are again welcome to propose such idea by your > own. One student idea for now! > > Ideas so far: http://gsoc2013.esug.org/ideas > > To propose an idea just respond to this post by fulfilling this idea > template: > > Title: > > Level: (beginner, intermediate, advanced) > > Possible mentor: (if already known) > > Possible second mentor: (if already known) > > Description > > Technical Details > > Benefits to the Student > > Benefits to the Community > > Best regards > Serge and Janko, > your this year GSoC admins > > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://doesnotunderstand.org/

March 27, 2013