- Pharo-dev - lists.pharo.org

[Pharo-project] just help :)

by Sebastian Nozzi

> 2012/11/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > just help :) This is what I would like to get involved in. Hopefully it can benefit the project. In order of personal interest: == 1) Positioning Pharo as THE language to learn programming. With a "fun" touch. Smalltalk is still an excellent language/environment to learn programming and I think: if it can be learnt while having fun, the better! My idea is to write simple game-programming tutorials (board games, puzzles, etc. like this - http://inventwithpython.com/ - but cooler). I already started working on this, that's why I bugged you guys with Morphic questions in the past. What I would like to offer is the knowledge and tools to use Pharo as a post-Scratch (http://scratch.mit.edu/) for creative projects (games, animations, stories, etc.). Conceptually similar to: http://www.greenfoot.org/home - only it would be it would be Smalltalk based ;-D. I also would love to write educational software (disclaimer: I'm not a school teacher or anything similar - although I imagine getting involved in the area). >From the spirit I know that maybe Squeak is more the place to go... And also that Pharo aims to be more enterprise/research oriented. I don't discard my code running in Squeak, but I just happen to find Pharo easier to use / develop in. == 2) Writing small (but attractive/useful) sample apps ... to be useful for people/small companies and get devs hooked (return-on-investment might be low?). Examples: a TestLink clone, a time-tracker, a corporate contact-database, a room reservation system, etc. The idea is to use these apps as "troyan horses", and get devs interested in Smalltalk/Pharo (the apps would be free and open-source, to guarantee usage/adoption). Maybe to extend / customize them for their needs. Increase mind-share (I assure you, it's needed! None of my past/current colleagues knew what Smalltalk was, some confused it with Lisp). But I'm sure this won't happen without... == 3) Writing (documenting) Pharo >From an "enterprise" point of view (how can I do X, because I need this for a real-life project asap?). I think there is a lot of work to be done here also. Documenting classes, working on external documentation. Like how to interact with OS processes/io, databases, deployment strategies, persistence strategies, how to work in a team, etc. For this I would like to collaborate in the "collaborative book". I already have a list of things that could be added/improved, and I think I would also learn a lot in the process. The only thing that worries me is me not being a native English speaker (writer). == Some work involved in these areas overlap. Ideally I would combine all three. So, these are the areas I would like to get involved in. It would be great if it could benefit the project at large :-) Best regards, Sebastian

Nov. 27, 2012

Re: [Pharo-project] Athens OpenGL backend - what does it mean?

by Sebastian Nozzi

2012/11/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > May be you did not see it but adding polymorph was the first things we did > even if the code was not perfect. No no, I realized the addition of Polymorph. Although it is only now that I am starting to get active in open-source Smalltalk, I have been following it since the days of Squeak 3.X (maybe earlier - I heard about Smalltalk for the first time in 1998). I lived through the announcement of Pharo (without understanding, at that time, why all the fuzz). In my head I kept coming and going to/from Smalltalk, never being able to give it up ;-) No matter how hard I tried, or how disappointed I sometimes was, I was also hooked. I knew somewhere that there is something true and unique to it. My heart was/is somehow tied to Smalltalk, I guess, even if I'm painfully aware of many of its (current) shortcomings... But I digress... Yes, I noticed about Polymorph. > I often said to my students if you want to faint or vomit when you open > Squeak (at that time I was maintaining squeak3.8or9) then this is normal > we are working on it and one day it will be cool. Hahaha! Well, it definitely looks ahem... different... than anything out there. But Squeak also took notice and somehow improved its looks a little bit in the last versions (since 4.2 or so). It took a lot of "faith", I guess. To look it to the face and in spite of the visual shortcomings say: but it will look cool in the future. Sometimes I think it would be awesome to be able to attract great designers. So many people designing great web-widgets, or Gnome/KDE skins, or even Winamp Skins... The visual aspect must not be underestimated. Fortunately Pharo right now has, for me, reached the state where I "can live with it" (visually). One thing I would like to investigate is how easy (or not) is to write new Polymorph-aware widgets. > So these is years that I want to get a vector graphics based ui and a lot more :) That's great :-) > just help :) > There are a lot of little tasks that can help us. > Like checking if a bug is still a bug in the current version. > I'm still learning a lot by trying (and I fail often) to fix something but I nearly always learn something. Since you mention "helping" I would like to take this opportunity to mention what my plans for Smalltalk/Pharo are, and see if it can be beneficial to the project. For this, I better create a new topic...

Nov. 27, 2012

[Pharo-project] Halo fly by help broken: an analysis -> MorphicEventHandler is not initialized

by StÃ©phane Ducasse

Nov. 27, 2012

Re: [Pharo-project] Getting started with Athens

by Esteban Lorenzano

be sure to install the 32bits version On Nov 27, 2012, at 5:37 PM, Sebastian Nozzi <sebnozzi(a)gmail.com> wrote: > Hello Araya, > > you might still need to install the library for your host operating system. > > See here: > > http://www.pharocasts.com/2012/06/athens-and-native-boost-at-work.html > > For Debian/Ubuntu systems you would need to do: > > apt-get install libcairo2 # as root in Debian > > Or: > > sudo apt-get install libcairo2 # as non-root in Ubuntu > > Hope this helps! > > Sebastian > > P.S. Future versions of Pharo, if I'm not mistaken, will include this > dependency... ? > > > 2012/11/27 Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com>: >> Hi, >> >> I'm trying to get started with Athens but I'm having the following errors: >> >> Pharo 1.4, loaded last version configurationOfAthens: >> 'failed to get a symbol address: cairo_image_surface_create' >> >> I also tried in this in a 2.0 image and I got the same error. >> >> I'm trying with this VM: >> >> https://ci.lille.inria.fr/pharo/view/Cog/job/NativeBoost-Cog-VM/Architectur… >> >> Any help, please? :) >> >> Thanks, >> Vanessa. >

Nov. 27, 2012

Re: [Pharo-project] Getting started with Athens

by Sebastian Nozzi

Sorry... I meant "Hello Vanessa" ;-) 2012/11/27 Sebastian Nozzi <sebnozzi(a)gmail.com>: > Hello Araya,

Nov. 27, 2012

Re: [Pharo-project] Getting started with Athens

by Sebastian Nozzi

Hello Araya, you might still need to install the library for your host operating system. See here: http://www.pharocasts.com/2012/06/athens-and-native-boost-at-work.html For Debian/Ubuntu systems you would need to do: apt-get install libcairo2 # as root in Debian Or: sudo apt-get install libcairo2 # as non-root in Ubuntu Hope this helps! Sebastian P.S. Future versions of Pharo, if I'm not mistaken, will include this dependency... ? 2012/11/27 Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com>: > Hi, > > I'm trying to get started with Athens but I'm having the following errors: > > Pharo 1.4, loaded last version configurationOfAthens: > 'failed to get a symbol address: cairo_image_surface_create' > > I also tried in this in a 2.0 image and I got the same error. > > I'm trying with this VM: > > https://ci.lille.inria.fr/pharo/view/Cog/job/NativeBoost-Cog-VM/Architectur… > > Any help, please? :) > > Thanks, > Vanessa.

Nov. 27, 2012

[Pharo-project] Getting started with Athens

by Vanessa PeÃ±a Araya

Hi, I'm trying to get started with Athens but I'm having the following errors:<https://ci.lille.inria.fr/pharo/view/Cog/job/NativeBoost-Cog-VM/Architectur…> Pharo 1.4, loaded last version configurationOfAthens: 'failed to get a symbol address: cairo_image_surface_create' I also tried in this in a 2.0 image and I got the same error. I'm trying with this VM: https://ci.lille.inria.fr/pharo/view/Cog/job/NativeBoost-Cog-VM/Architectur… Any help, please? :) Thanks, Vanessa.

Nov. 27, 2012

Re: [Pharo-project] Got our first pharo consortium contract :)

by Sophie Perin

ok Just a little precision: PHARO consortium starts with 2013 calendar year. it is the reason why there is not a real pro rata for 2012 (you have signed on november 2012 but you pay only the global amount for calendar year 2013) But the generals rules starting fron 2013 is : the pro rata amount due for a calendar year is calculated by Inria from the date of signature of the membership agreement. Sophie ----- Mail original ----- > De: "Norbert Hartl" <norbert(a)hartl.name> > Ã: "Sophie Perin" <sophie.perin(a)inria.fr> > Cc: Pharo-project(a)lists.gforge.inria.fr > EnvoyÃ©: Mardi 27 Novembre 2012 12:34:19 > Objet: Re: [Pharo-project] Got our first pharo consortium contract :) > > > Am 27.11.2012 um 11:51 schrieb Sophie Perin <sophie.perin(a)inria.fr>: > > > Dear Norbert > > > > You can pay now but you pay for 2013 calendar year. > > > > the pro-rata apply and it is calculated only when a compagny joins > > the consortium during the calendar year (for example, if a > > compagny sign the membership agreement on june 2013) > > > > Hope it is clear now for you ? > > > Yes, thank you. Memberships are adjusted to the calendar year. In > this case it is the same for us regardless when we pay (tax wise). > So I just wait for you to settle things. > > thanks again, > > Norbert > > > ----- Mail original ----- > >> De: "Norbert Hartl" <norbert(a)hartl.name> > >> Ã: Pharo-project(a)lists.gforge.inria.fr > >> Cc: "Sophie Perin" <sophie.perin(a)inria.fr> > >> EnvoyÃ©: Mardi 27 Novembre 2012 11:42:17 > >> Objet: Re: [Pharo-project] Got our first pharo consortium contract > >> :) > >> > >> > >> Am 27.11.2012 um 10:35 schrieb StÃ©phane Ducasse > >> <stephane.ducasse(a)inria.fr>: > >> > >>> Norbert > >>> > >>>>> Great!. And being the first is always something special :) Do > >>>>> you > >>>>> think the fees can be transferred already this year? > >>> > >>> We decided to do a pro-rata so that people do not think that we > >>> are > >>> trying to steal them and also to make sure that > >>> everybody can join at any time without thinking too much. > >>> So it would mean 1 month so it will be probably for january. Now > >>> if > >>> you want to pay the full > >>> price we can do it :). > >>> > >> I'm not sure I understand. My assumption was that whenever I join > >> the > >> consortium I pay an annual fee and be member for one year. Or do > >> you > >> arrange the membership payment with the calendar year? So to be > >> clear do you state paying for this year will be one month (for > >> december) and it starts all over again in 2013? Or will I be able > >> to > >> pay now for one year (until Nov '13)? > >> For us it would be best to pay a year of membership within 2012. > >> > >> Norbert > >> > >> > >> > >

Nov. 27, 2012

Re: [Pharo-project] New Change System

by Ezequiel Lamonica

On 27 November 2012 12:22, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > On 11/27/2012 11:32 AM, Ezequiel Lamonica wrote: > >> Hi Goran, >> >> We use your idea about "previous" and "post" states of the system for >> every change at the moment that was done. >> Also,the possibility of do redo and undo of every kind of change. >> > > Does your changes have the ability to produce their "anti change"? And > does in that case a "remove class X"-change produce an anti-change that is > in fact a composite change that has 1 class create change + x method add > changes? > > Yes, and also the variables. In fact, an anti-change is an undo change which knows the change undone. > Hmmm, I really should take a look because I have tons of things I would > like to investigate :) > > regards, GÃ¶ran > > PS. I tracked changes using the SystemChangeNotification (or what it was > called) which is the equivalent of the new announcements I guess. > >

Nov. 27, 2012

Re: [Pharo-project] Got our first pharo consortium contract :)

by Norbert Hartl

Am 27.11.2012 um 11:51 schrieb Sophie Perin <sophie.perin(a)inria.fr>: > Dear Norbert > > You can pay now but you pay for 2013 calendar year. > > the pro-rata apply and it is calculated only when a compagny joins the consortium during the calendar year (for example, if a compagny sign the membership agreement on june 2013) > > Hope it is clear now for you ? > Yes, thank you. Memberships are adjusted to the calendar year. In this case it is the same for us regardless when we pay (tax wise). So I just wait for you to settle things. thanks again, Norbert > ----- Mail original ----- >> De: "Norbert Hartl" <norbert(a)hartl.name> >> Ã: Pharo-project(a)lists.gforge.inria.fr >> Cc: "Sophie Perin" <sophie.perin(a)inria.fr> >> EnvoyÃ©: Mardi 27 Novembre 2012 11:42:17 >> Objet: Re: [Pharo-project] Got our first pharo consortium contract :) >> >> >> Am 27.11.2012 um 10:35 schrieb StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr>: >> >>> Norbert >>> >>>>> Great!. And being the first is always something special :) Do you >>>>> think the fees can be transferred already this year? >>> >>> We decided to do a pro-rata so that people do not think that we are >>> trying to steal them and also to make sure that >>> everybody can join at any time without thinking too much. >>> So it would mean 1 month so it will be probably for january. Now if >>> you want to pay the full >>> price we can do it :). >>> >> I'm not sure I understand. My assumption was that whenever I join the >> consortium I pay an annual fee and be member for one year. Or do you >> arrange the membership payment with the calendar year? So to be >> clear do you state paying for this year will be one month (for >> december) and it starts all over again in 2013? Or will I be able to >> pay now for one year (until Nov '13)? >> For us it would be best to pay a year of membership within 2012. >> >> Norbert >> >> >>

Nov. 27, 2012