November 2012 - Pharo-dev - lists.pharo.org

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

[Pharo-project] [update 2.0] #20420

by Marcus Denker

20420 ----- Issue 7055: Removing the last direct references to Debugger http://code.google.com/p/pharo/issues/detail?id=7055 Issue 7058: bug on compilation http://code.google.com/p/pharo/issues/detail?id=7058 Issue 7045: SystemNavigation>>#allUnimplementedNonPrimitiveCalls calls isFalse: http://code.google.com/p/pharo/issues/detail?id=7045 Issue 7053: improve AbsolutePath tests http://code.google.com/p/pharo/issues/detail?id=7053 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-MarcusDenker.991.diff http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.749.diff http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-MarcusDenker.738.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.379.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1258.diff http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-MarcusDenker.10.diff http://ss3.gemstone.com/ss/Pharo20/FileSystem-Tests-Core-MarcusDenker.39.di… -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Nov. 27, 2012

Re: [Pharo-project] Versioning external packages

by Fernando Olivero

Hi Roberto, in the first case you have to add the methods in a category named: '*MyPackage', then Monticello versions it as an method "extension", a method of you package which is in a class that doesn't belong to your package. OrderedCollection>>myMethodExtension " I'm in a method category starting with an asterisk *" self doSomething. In the second case, you should put the class in your package, so it would be versioned (and be part of), your package, but still accessible throughout the image. But, if you think your new Roassal Layout is cool enough, then you should tell the package maintainers to add it to Roassal. Saludos, Fernando On Tue, Nov 27, 2012 at 12:12 PM, roberto.minelli(a)usi.ch < roberto.minelli(a)usi.ch> wrote: > Hi all, > > I'm using Monticello to version my source code. > > Suppose this use case: I need to add a message to the OrderedCollection > class and I want my message to be versioned within my repository (i.e., > when an user downloads my package she also get the new message in the > OrderedCollection class. > > And another one, suppose I create a new Layout for Roassal that suits my > needs. I will create a class in the category 'Roassal-Layout' which is not > versioned in my repository. Is there a way to version it? > > Cheers, > Roberto >

Nov. 27, 2012

Re: [Pharo-project] New Change System

by GÃ¶ran Krampe

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? 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] Versioning external packages

by Sven Van Caekenberghe

Hi Roberto, Yes, of course you can do that. It is called an extension. You have to put such methods in a method category matching your package's name, starting with an asterix, *. You can see those all over the system. For example, String has methods #asZnUrl and #asZnMimeType in a category '*zinc-http' to place them in the Monticello package Zinc-HTTP. HTH, Sven On 27 Nov 2012, at 12:12, roberto.minelli(a)usi.ch wrote: > Hi all, > > I'm using Monticello to version my source code. > > Suppose this use case: I need to add a message to the OrderedCollection class and I want my message to be versioned within my repository (i.e., when an user downloads my package she also get the new message in the OrderedCollection class. > > And another one, suppose I create a new Layout for Roassal that suits my needs. I will create a class in the category 'Roassal-Layout' which is not versioned in my repository. Is there a way to version it? > > Cheers, > Roberto -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Nov. 27, 2012

[Pharo-project] Versioning external packages

by roberto.minelli＠usi.ch

Hi all, I'm using Monticello to version my source code. Suppose this use case: I need to add a message to the OrderedCollection class and I want my message to be versioned within my repository (i.e., when an user downloads my package she also get the new message in the OrderedCollection class. And another one, suppose I create a new Layout for Roassal that suits my needs. I will create a class in the category 'Roassal-Layout' which is not versioned in my repository. Is there a way to version it? Cheers, Roberto

Nov. 27, 2012

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

by Sophie Perin

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 ? Sophie ----- 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] Got our first pharo consortium contract :)

by Norbert Hartl

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