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

Re: [Pharo-project] Cluster analysis of Pharo source available?

by csrabak＠bol.com.br

Guido, Notwithstanding how useful would be to track these attributes you just mentioned, I cannot see how the graphs of the clusters shown in the earlier post can be either a representation of them nor even a summary of what you brought now in this comment. . . Regards, -- Cesar Rabak Em 10/11/2011 18:44, Guido Stepken < gstepken(a)googlemail.com > escreveu: Project managers directly can *see*, how much brainpower each programmer is investing and in how far he really cleans up code, defines clear and usable (and used by other coprogrammers) interfaces, or he is messing up the code, producing even more work and costs for others. You know - "lines not written" -> but they directly show up in the graphs! Should be standard everywhere, IMHO. Have fun! Guido Stepken Am 10.11.2011 um 21:25 schrieb csrabak(a)bol.com.br: > As the saying says: "Every person to its taste!", I will not delve in the liking or not of the graphs, but I think the question must be posed: > > What practical measures can be extracted of such representation and how can they be used to [help] fulfill the Pharo vision? > > -- > Cesar Rabak > > Em 09/11/2011 19:15, Guido Stepken < gstepken(a)googlemail.com > escreveu: > I like such things, like visualizing class dependencies with girvan newman algorithm: > > http://igraph.sourceforge.net/screenshots2.html > > or here: > > http://www.little-idiot.de/teambuilding/apache-structure.pdf > > Should be nice to see, how Pharo has changed over time. > > Are there such "reflective tools" available in Pharo? (Should be pretty easy to handover a list of Pharo class dependencies to igraph ...) > > Tnx, Guido Stepken > >

Nov. 13, 2011

Re: [Pharo-project] FS and binary files

by StÃ©phane Ducasse

I do not believe that what changed from colin implementation would impact the problem of johannes. Stef > Not really, Pharo forked the original implementation. > > In Colin's code you had to use the third supported stream type: not #readStream and not #writeStream (that are minimal ANSI compatible streams), but a third kind that I forgot the name of (it would return a RBBinaryReadWriteStream that works with most existing code). > > Lukas > > On 10 November 2011 16:25, Johannes Rasche <johannesrasche(a)mac.com> wrote: > Hi Lukas, > > you may not have realized the message below. > > I assume you might be the person who coud answer my question > > Cheers Johannes > > -------- Original-Nachricht -------- > Betreff: [Pharo-project] FS and binary files > Datum: Wed, 09 Nov 2011 15:36:16 +0100 > Von: Johannes Rasche <johannesrasche(a)mac.com> > Antwort an: Pharo-project(a)lists.gforge.inria.fr > An: pharo-project(a)lists.gforge.inria.fr > > > Hi folks, > > I just started to using FS instead of FileDirectory. > > On readStream sent to FSReference a FSAnsiiStream turns out, which is > not suitable for reading images ( for instance with PNGReadWriter). > > What did I wrong? > > Johannes > > > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch

Nov. 12, 2011

Re: [Pharo-project] Call for help for reviewing code

by StÃ©phane Ducasse

+1 On Nov 11, 2011, at 4:49 PM, Sean P. DeNigris wrote: > > mmimica wrote: >> >> "Nobody bothers to fix it" is not a valid issue resolution. > I agree. I sometimes find bugs that I can't fix because I don't understand > enough or just don't have time right then, even though the bug is very > annoying or disruptive. Over time, I gather info through using the system > that I can collect as comments in the issue. Also, every once in a while > (e.g. ESUG), I'll have a block of time that I can sit down and take down a > big issue, but months may go by before such a block comes up. > > Maybe a status called "old" or "stale" or something else so these can be > filtered? > > Sean > > -- > View this message in context: http://forum.world.st/Call-for-help-for-reviewing-code-tp3992746p4031712.ht… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Nov. 12, 2011

Re: [Pharo-project] deprecation process

by StÃ©phane Ducasse

normally we do it manually :). Stef On Nov 11, 2011, at 12:29 AM, Alain Plantec wrote: > Hi all, > I'm reviewing some fixes and I was just wondering: > Do we have to manually move a deprecated method to the > Deprecated14 package or is it done automatically ? > Thanks > Alain > >

Nov. 12, 2011

Re: [Pharo-project] Cluster analysis of Pharo source available?

by StÃ©phane Ducasse

On Nov 10, 2011, at 9:44 PM, Guido Stepken wrote: > Project managers directly can *see*, how much brainpower each programmer is investing and in how far he really cleans up code, defines clear and usable (and used by other coprogrammers) interfaces, or he is messing up the code, producing even more work and costs for others. > > You know - "lines not written" -> but they directly show up in the graphs! do you have an example? A web site because I'm interested for Moose. Stef > > Should be standard everywhere, IMHO. > > Have fun! > > Guido Stepken > > Am 10.11.2011 um 21:25 schrieb csrabak(a)bol.com.br: > >> As the saying says: "Every person to its taste!", I will not delve in the liking or not of the graphs, but I think the question must be posed: >> >> What practical measures can be extracted of such representation and how can they be used to [help] fulfill the Pharo vision? >> >> -- >> Cesar Rabak >> >> Em 09/11/2011 19:15, Guido Stepken < gstepken(a)googlemail.com > escreveu: >> I like such things, like visualizing class dependencies with girvan newman algorithm: >> >> http://igraph.sourceforge.net/screenshots2.html >> >> or here: >> >> http://www.little-idiot.de/teambuilding/apache-structure.pdf >> >> Should be nice to see, how Pharo has changed over time. >> >> Are there such "reflective tools" available in Pharo? (Should be pretty easy to handover a list of Pharo class dependencies to igraph ...) >> >> Tnx, Guido Stepken >> >> >

Nov. 12, 2011

Re: [Pharo-project] Headless PetitParser

by StÃ©phane Ducasse

Hi Alberto can you give an example so that people can learn too? Stef On Nov 10, 2011, at 6:16 PM, Alberto Bacchelli wrote: > Thank you everybody for your super-useful help! > I managed to create my first smalltalk script for headless Pharo (it's > pretty fun ;) ! > > Cheers, > Alberto > > -- > View this message in context: http://forum.world.st/Headless-PetitParser-tp3994446p4024397.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Nov. 12, 2011

Re: [Pharo-project] Instantiating from a Symbol

by StÃ©phane Ducasse

>> > > StÃ©ph, > > Nick is right. I guess the question is: how should normal client or user code that used to do something like > > Smalltalk at: #Point > > be written ? > > Should we just do > > Smalltalk globals > > or > > self environment. environment should be used in a method while Smalltalk globals more for scripts. Stef

Nov. 12, 2011

Re: [Pharo-project] NewTextMorph

by StÃ©phane Ducasse

Thanks! Stef On Nov 10, 2011, at 4:46 PM, Fernando Olivero wrote: > Done. > > Issue 4986: Removing NewTextMorph and related > > Fernando > On Thu, Nov 10, 2011 at 3:23 PM, Hilaire Fernandes > <hilaire.fernandes(a)gmail.com> wrote: >> Fernando, can you do it? I think you know better the related elements. >> >> Hilaire >> >> Le 10/11/2011 09:30, StÃ©phane Ducasse a Ã©crit : >>> Can you create a bug entry to remove these classes? >>> If they are not maintained we should remove them. >>> >>> Stef >>> >>> >>>> Hi Fernando, >>>> >>>> Thanks for the feedback. I also saw these classes were not used, so I >>>> sticked to TextMorph. >>>> >>>> >>>> Hilaire >>>> >>>> >>>> Le 09/11/2011 10:17, Fernando Olivero a Ã©crit : >>>>> Hi Hillary, the classes you mention were created by me when Pharo >>>>> wasnt using the CUIS editors, they allowed me to plug them into Pharo, >>>>> coming up with a text morph form scratch. >>>>> >>>>> Nobody used them since them, except me in Gaucho. So i've discontinued >>>>> maintaing them in Pharo. I would suggest you to use the other text >>>>> morphs classes (TextMorph, PluggableTextMorph, etcâ¦), which are >>>>> maintained and used currently in the system. >>>>> >>>>> I will create an issue to remove them from the system, because now is >>>>> confusing, to have more than one option. >>>>> >>>>> Fernando >>>>> >>>>> On Sat, Nov 5, 2011 at 4:20 PM, Hilaire Fernandes >>>>> <hilaire.fernandes(a)edu.ge.ch> wrote: >>>>>> I want to plug a multiple line text morph a DrGeo canvas. The morph >>>>>> should display the text (yes) and be editable on place when the user ask >>>>>> for. >>>>>> >>>>>> Which class should I use ? >>>>>> EditableTextMorph, EntryFieldMorph or NewTextMorph >>>>>> >>>>>> >>>>>> The comments of the class EntryFieldMorph wrote about example1 and >>>>>> example2 methods bit I dont see it (I am using Pharo 1.3) >>>>>> >>>>>> Hilaire >>>>>> >>>>>> >>>>>> -- >>>>>> Education 0.2 -- http://blog.ofset.org/hilaire >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Education 0.2 -- http://blog.ofset.org/hilaire >>>> >>>> >>> >>> >>> >> >> >> >

Nov. 12, 2011

Re: [Pharo-project] Latest Polymorph improvements

by StÃ©phane Ducasse

thanks http://code.google.com/p/pharo/issues/detail?id=4996 stef On Nov 10, 2011, at 5:32 PM, Gary Chambers wrote: > Time for another accumulated bunch of things ;-) > > Attached change set > > Summary: > > AlphaImageMorph > can now answer effective image bounds for a rectangle in display bounds > allows use of on-screen crop tools etc. to specify area in image terms with respect to layout/scaling etc. > CheckboxButtonMorph > always honour explicit click/move handlers > CheckboxMorph > extra property to facilitate taking keyboard focus on click (can be used in conjunction with text editors to accept on (keyboard) focus change) > shrink horizontally by default > update enablement on label change > DropListMorph > support wrapSelector on underlying list > FileDialogWindow > update file list when directories added/removed > ListModel > extra change/update aspect for list order (allows using a list model to reorder a list via drag/drop) > MorphicUIManager > openModel uses detected modal morph rather than blocking World by default > PSMCPatchOperationWrapper > use summary of definition (avoid MNU on #selector for reorganisation operations) > PluggableButtonMorph > extra property to facilitate taking keyboard focus on click > PluggableSliderMorph > avoid possible ZeroDivide on bad parameters > PluggableTextFieldMorph > minor performance, reuse already calculated string > ToggleMenuItemMorph > centre text when vertical extent more than minimum > UITheme > Use a PanelMorph for label groups (allows disablement of group... ideally would want a major rework for parent enablement dependency though) > > Regards, Gary > <PolymorphChanges.7.cs>

Nov. 12, 2011

Re: [Pharo-project] [Moose-dev] mooseentitystate

by StÃ©phane Ducasse

good idea. if you have a piece of code send it. Stef On Nov 9, 2011, at 9:32 AM, jannik.laval wrote: > Hi Stef, > > It is not so simple :) > Take this example from Moose: > > === > LANNode methodDictionary collect:[:e | e timeStamp ifNotEmpty: [:s | s subStrings first ]] > === > > LANNode has no author, so if you take the first substring you will have the date of creation. > I have not a good solution, but for my scripts, I test the first character of the substring: if it is a letter, this is an author, else, there is no author. > === > ((myString subStrings) first at:1) isLetter > === > > Cheers, > > On Nov 6, 2011, at 21:48 , StÃ©phane Ducasse wrote: > >> http://code.google.com/p/pharo/issues/detail?id=4971 >> >>> >>>> In moose ? because in pharo this is like that and the changes I added where just to make sure that all the clients do not have to deal with timestamp stupid parsing. >>>> >>> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > --- > Jannik Laval > >

Nov. 12, 2011