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

Re: [Pharo-project] [Pharo-users] OCompletion configuration for 1.4

by Mariano Martinez Peck

Thanks Guille. It works perfect. I have just commited a small fix in Ocompletion-MarianoMartinezPeck.114 ;) cheers On Fri, Jan 13, 2012 at 10:34 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 13 January 2012 17:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > Thanks a lot!!!! > > > yeah, i just checked and it works out of the box. good job! > > > Stef > > > > On Jan 13, 2012, at 3:53 PM, Guillermo Polito wrote: > > > >> I've written a new version of OCompletion for 1.4 with several fixes > and compatibility additions for Pharo 1.4 > >> > >> Gofer it > >> squeaksource: 'MetacelloRepository'; > >> package: 'ConfigurationOfOCompletion'; > >> load. > >> > >> ConfigurationOfOCompletion loadStable > >> > >> If someone wants to try it :). > >> > >> Guille > > > > > > > > -- > Best regards, > Igor Stasenko. > > -- Mariano http://marianopeck.wordpress.com

Jan. 13, 2012

Re: [Pharo-project] [Pharo-users] OCompletion configuration for 1.4

by Igor Stasenko

On 13 January 2012 17:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks a lot!!!! > yeah, i just checked and it works out of the box. good job! > Stef > > On Jan 13, 2012, at 3:53 PM, Guillermo Polito wrote: > >> I've written a new version of OCompletion for 1.4 with several fixes and compatibility additions for Pharo 1.4 >> >> Gofer it >> Â Â squeaksource: 'MetacelloRepository'; >> Â Â package: 'ConfigurationOfOCompletion'; >> Â Â load. >> >> ConfigurationOfOCompletion loadStable >> >> If someone wants to try it :). >> >> Guille > > -- Best regards, Igor Stasenko.

Jan. 13, 2012

Re: [Pharo-project] What is the difference between ActionSequence and WeakActionSequence

by Guillermo Polito

On Fri, Jan 13, 2012 at 5:32 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > What is that? > ActionSequence? Who use that? > So far, OB :P > > > But they are both defined the same way! > > > > Array variableSubclass: #WeakActionSequence > > instanceVariableNames: '' > > classVariableNames: '' > > poolDictionaries: '' > > category: 'Kernel-Objects' > > > > The only reference to it's weakness it its name! :P > > > > On Fri, Jan 13, 2012 at 12:39 PM, Henrik Johansen < > henrik.s.johansen(a)veloxit.no> wrote: > > > > On Jan 13, 2012, at 4:33 23PM, Guillermo Polito wrote: > > > > > In 1.3 they look the same, in 1.4 ActionSequence is not there any > more... > > > > > > Is the second one replacing the first one? are there any differences > for the user? > > > > > > Thanks, > > > Guille > > > > > > ActionSequence was not referenced by the base system any more, not sure > why it was removed instead of deprecated. > > And yes, there is a difference for a user, the WeakActionSequence holds > actions weakly, while ActionSequence held them strongly. > > (WeakActionSequence automatically removes the actions when there are no > other references to the registrar, while ActionSequence did not, and you > had to unregister manually before it would stop executing them) > > > > Cheers, > > Henry > > > > >

Jan. 13, 2012

Re: [Pharo-project] CommentReference removed?

by Guillermo Polito

Yeap, I've already updated the reference from CommentReference to RGCommetnDefinition :) On Fri, Jan 13, 2012 at 5:30 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > > > I am trying to load OB in Pharo 1.4, but It seems CommentReference was > removed from the image... Shouldn't it go to a deprecated package? > > CommentReference should not work anymore because it was just a hack that > we introduced with johan and benjamin > waiting for Ring. > We could reintroduce it but I think that it should not work. > Now we have Ring and we can use it instead. > > > > > Should we reitroduce it with the proper deprecation? > > > > Guille > > >

Jan. 13, 2012

Re: [Pharo-project] Preparing 1.4 beta

by StÃ©phane Ducasse

On Jan 13, 2012, at 4:09 PM, Henrik Johansen wrote: > > On Jan 13, 2012, at 1:18 44PM, StÃ©phane Ducasse wrote: > >> thanks. May be I will add SystemAnnouncement and RPackage since this is stable. >> We will check if we can push or not in 1.4 the clean of the eventBuff. >> >> Stef > > See issue 5172 - 5174 for my comments. > > TLDR; I don't think it's a good idea to include in Core for 1.4, a more pervasive integration with the base system would be desirable, so one could remove the old event-based system at the same time. Up until here I agree. > (but have a backwards-compatible external package) I think that it will be difficult enough to swap the two events notification systems and that we will not make a backward compatible package. I think that for migrating the few users will just have to register to the new one. Now give me 10 full time engineers and we do it. At the end of the day, we should do some reality checks and put resources on the right items. Stef > > Cheers, > Henry

Jan. 13, 2012

Re: [Pharo-project] What is the difference between ActionSequence and WeakActionSequence

by StÃ©phane Ducasse

What is that? ActionSequence? Who use that? > But they are both defined the same way! > > Array variableSubclass: #WeakActionSequence > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Kernel-Objects' > > The only reference to it's weakness it its name! :P > > On Fri, Jan 13, 2012 at 12:39 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On Jan 13, 2012, at 4:33 23PM, Guillermo Polito wrote: > > > In 1.3 they look the same, in 1.4 ActionSequence is not there any more... > > > > Is the second one replacing the first one? are there any differences for the user? > > > > Thanks, > > Guille > > > ActionSequence was not referenced by the base system any more, not sure why it was removed instead of deprecated. > And yes, there is a difference for a user, the WeakActionSequence holds actions weakly, while ActionSequence held them strongly. > (WeakActionSequence automatically removes the actions when there are no other references to the registrar, while ActionSequence did not, and you had to unregister manually before it would stop executing them) > > Cheers, > Henry >

Jan. 13, 2012

Re: [Pharo-project] CommentReference removed?

by StÃ©phane Ducasse

> I am trying to load OB in Pharo 1.4, but It seems CommentReference was removed from the image... Shouldn't it go to a deprecated package? CommentReference should not work anymore because it was just a hack that we introduced with johan and benjamin waiting for Ring. We could reintroduce it but I think that it should not work. Now we have Ring and we can use it instead. > > Should we reitroduce it with the proper deprecation? > > Guille

Jan. 13, 2012

Re: [Pharo-project] [Seaside] 10 reasons why I'm using Smalltalk for airflowing

by Sven Van Caekenberghe

On 13 Jan 2012, at 19:41, Sebastian Sastre wrote: > in this essay I've published I talk about some of the reasons why Smalltalk made sense for me: > 10 reasons why I'm using Smalltalk for airflowing [1] > > Which of course mentions Seaside and has other useful Smalltalk related links > > comments (of any kind) most welcome > > hug, > > sebastian > > o/ > > [1] http://sebastianconcept.com/brandIt/10-reasons-why-im-using-smalltalk-for-a… Excellent writeup, Sebastian, I couldn't agree more. Inspiring for the new year, thanks ! Sven PS: forwaring to the Pharo list ;-)

Jan. 13, 2012

Re: [Pharo-project] [ANN] DBXTalk site and mailing list little news

by GastÃ³n Dall' Oglio

Congratulation for the team!!! A little comment, in the page of OpenDBX the name and link of DBXTalk are bad (SqueakDBX): http://www.linuxnetworks.de/doc/index.php/OpenDBX

Jan. 13, 2012

Re: [Pharo-project] New IDE alternative (was Misc. newbie questions)

by blake

Gaston, > This method is for manage the event, not for do something that is really > part of the model. A Form, no is part of the model. This is similar in VW: > you coded your event handler method in the AplicationModel, that is like a > Form in Delphi. > Delphi was a direct reaction to VB, which was eating Borland Pasal's lunch. MVC was nowhere to be seen. It was all about "look how easy it is to do [whatever]." Never "look how easy it is to re-use" or "look how easy it is to maintain". I'm not a Basic basher, but the atmosphere surrounding it has always been "Computer science is =haaaaarrd=. I just wanna program!" You CAN do it right. But here I am (right now!) looking at a guy who's encoded multi-hundred-line event handlers, that are massive if-then chains, with code duplicated like crazy between the events. Really, the "beauty" of the VB model is that you didn't HAVE to learn OO. (And, hey, reality bears out that code quality and profit are not strongly correlated.) > No. The IDE automaticaly define a global variable and create code for > create and assign a instance, but if you want more instances of same Form > you can easy declare local variables and create new instance (on initialize > of other instance or on the fly in accesor methods) and asign to. Same in > Smalltalk.... And you can delete this automaticaly created code. > Sure. You can do a lot of things right. The underlying weakness is in the static typing and poorly defined messaging. (I haven't tried FireMonkey yet, though, it may be different.) mmm no. Again, a Form is not part of model, idealy this is for write event > methods handlers. > I'm glad you're following the ideal. I started using Delphi on the beta in 1994, and in the past 18 years, I've seen about two instances of the ideal being properly followed in the real world (that I didn't write). > In the Buttons you can use Actions for delegate the handler method of the > click event. In general, you can assign method of a Form to events of > controls in another Form, but I do not do often that becouse I only write a > small code in the event handler in the Form for delegate to some model the > work (DataModules). > Point is: Buttons then become inflexible pass-throughs. In Smalltalk what you'd do is allow a component to be swapped for any other component if it had the right handlers. If you could lay out forms in Smalltalk and press a button to create a lean, deployable version, I'd only use Delphi for CPU intensive tasks. What'd be optimal is a Smalltalk (with some VA/Delphi influences) in a browser with an overall approach like that of OPA or maybe Morfik (not Morphic) so that front and back-end stuff was seamless. Smalltalk was born for that.

Jan. 13, 2012