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

Re: [Pharo-project] FS and binary files

by Lukas Renggli

I thought it was adopted as part of Pharo 1.4? Or maybe it is just used as part of Coral? No clue ... Lukas On 11 November 2011 08:09, Johannes Rasche <johannesrasche(a)mac.com> wrote: > Thx Lukas, > > I'll try it ... > > anyway I'm wondering about that - > > as FS appeared, I had the impression, that this would be the long awaited > replacement of FileDirectory, > > but it doesn't seem so, because it's not part of the official Pharo up to > now (1.3), > > or is there another alternative to FileDirectory I've overseen? > > and what do you mean by "Pharo forked the original implementation"? up to > 1.3 I cannot see FS > > Johannes > > Am 10.11.11 18:06, schrieb Lukas Renggli: > > 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> <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 > > > > -- > Johannes Rasche *Hagelberger Str. 56 10965 Berlin mail > johannesrasche(a)mac.com mobile +49 1577 175 04 75* > -- Lukas Renggli www.lukas-renggli.ch

Nov. 11, 2011

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

by Milan Mimica

On 10 November 2011 17:09, Igor Stasenko <siguctua(a)gmail.com> wrote: > Because if there's nobody who wants to fix it, why we should keep it > listed? > Eh, because it's a bug. If you accept it as a bug, then it is a bug. "Nobody bothers to fix it" is not a valid issue resolution. It should stay there forever until you can think of a good enough reason not to fix it, or you actually fix it. -- Milan Mimica http://sparklet.sf.net

Nov. 11, 2011

Re: [Pharo-project] FS and binary files

by Johannes Rasche

Thx Lukas, I'll try it ... anyway I'm wondering about that - as FS appeared, I had the impression, that this would be the long awaited replacement of FileDirectory, but it doesn't seem so, because it's not part of the official Pharo up to now (1.3), or is there another alternative to FileDirectory I've overseen? and what do you mean by "Pharo forked the original implementation"? up to 1.3 I cannot see FS Johannes Am 10.11.11 18:06, schrieb Lukas Renggli: > 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 > <mailto:johannesrasche@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> > <mailto:johannesrasche@mac.com> > Antwort an: Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr> > An: pharo-project(a)lists.gforge.inria.fr > <mailto:pharo-project@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 <http://www.lukas-renggli.ch> -- Johannes Rasche /Hagelberger Str. 56 10965 Berlin mail johannesrasche(a)mac.com mobile +49 1577 175 04 75/

Nov. 11, 2011

Re: [Pharo-project] deprecation process

by Bernardo Ezequiel Contreras

I've asked a similar question http://forum.world.st/How-to-deprecate-a-Class-td3710441.html and I've done it manually. maybe what it's needed is a description of the process. here's an attempt http://code.google.com/p/pharo/wiki/DeprecationProcess (seems outdated) On Thu, Nov 10, 2011 at 8:29 PM, Alain Plantec <alain.plantec(a)yahoo.com>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. 10, 2011

[Pharo-project] deprecation process

by Alain Plantec

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. 10, 2011

Re: [Pharo-project] Monticello Browser Feedback - additional window pane for description

by Guido Stepken

Should'nt every Smalltalk object know, where it can find its source?? Monticello as interim solution towards full OO-ish thinking? Have fun, Guido Stepken Am 10.11.2011 um 22:25 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > The manifesto of the Mondrian-Core package is called ManifestoMondrianCore, and is a subclass of Object. > Maybe on some point we could have a class Manifesto in Pharo, but this is another story. > > Alexandre > > > On 10 Nov 2011, at 08:35, Igor Stasenko wrote: > >> On 10 November 2011 16:50, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Hi Ben! >>> >>> I agree with you! We are currently working on a manifesto browser that will include this information per package, and much more (e.g,. List of authors, associated lint rules) >>> >>> You can have a look at it if you wish. It is ManifestoBrowser from the ss3.gemstone.com forge >>> >> >> My main question is where such information will be stored in monticello package. >> Because right now, we don't have any formal defined rules for keeping >> such information. >> And of course it is useful, especially to people who only getting started. >> >>> Cheers, >>> Alexandre >>> >>> >>> >>> Le 10 nov. 2011 Ã 07:36, Ben Coman <btc(a)openInWorld.com> a Ã©crit : >>> >>>> greetings all, >>>> >>>> Some hopefully constructive feedback as from a newbie perusing Monticello Browser in Pharo 1.3. >>>> On the left-side there are a of packages listed and I don't know what any of them do. On the right-side is list a few repositories with a lot of white space beneath. What do you think of splitting the right-side horizontally to include a description of the package? >>>> This could include: >>>> 1. a textual description >>>> 2. a link to a web page for the package, which could be an authors home page or a wiki page >>>> 3. display of the linked web page within the Monticello Browser >>>> >>>> This is just something I would find useful as I explored the system. Actually, it just occurred to me that the listed packages are delivered as an integral part of Pharo 1.3 system. I see that some of them are marked with a star and I wonder what that means. I did read the PBE Monticello chapter a while ago but its been awhile since I used Pharo and it didn't stick. It is a pain searching for the description in PBE again - and a scan of this escription seems more about using Monticello as a developer than a newbie exploring the system. I want to get familiar with the system by exploring it and my feeling of confidence depends on easily understanding the questions that arise as I am flipping through thing. >>>> >>>> Any thoughts for having a help button on the Monticello Browser with "user" oriented information? >>>> >>>> cheers, >>>> BenComan >>>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

Nov. 10, 2011

Re: [Pharo-project] Monticello Browser Feedback - additional window pane for description

by Alexandre Bergel

The manifesto of the Mondrian-Core package is called ManifestoMondrianCore, and is a subclass of Object. Maybe on some point we could have a class Manifesto in Pharo, but this is another story. Alexandre On 10 Nov 2011, at 08:35, Igor Stasenko wrote: > On 10 November 2011 16:50, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi Ben! >> >> I agree with you! We are currently working on a manifesto browser that will include this information per package, and much more (e.g,. List of authors, associated lint rules) >> >> You can have a look at it if you wish. It is ManifestoBrowser from the ss3.gemstone.com forge >> > > My main question is where such information will be stored in monticello package. > Because right now, we don't have any formal defined rules for keeping > such information. > And of course it is useful, especially to people who only getting started. > >> Cheers, >> Alexandre >> >> >> >> Le 10 nov. 2011 Ã 07:36, Ben Coman <btc(a)openInWorld.com> a Ã©crit : >> >>> greetings all, >>> >>> Some hopefully constructive feedback as from a newbie perusing Monticello Browser in Pharo 1.3. >>> On the left-side there are a of packages listed and I don't know what any of them do. On the right-side is list a few repositories with a lot of white space beneath. What do you think of splitting the right-side horizontally to include a description of the package? >>> This could include: >>> 1. a textual description >>> 2. a link to a web page for the package, which could be an authors home page or a wiki page >>> 3. display of the linked web page within the Monticello Browser >>> >>> This is just something I would find useful as I explored the system. Actually, it just occurred to me that the listed packages are delivered as an integral part of Pharo 1.3 system. I see that some of them are marked with a star and I wonder what that means. I did read the PBE Monticello chapter a while ago but its been awhile since I used Pharo and it didn't stick. It is a pain searching for the description in PBE again - and a scan of this escription seems more about using Monticello as a developer than a newbie exploring the system. I want to get familiar with the system by exploring it and my feeling of confidence depends on easily understanding the questions that arise as I am flipping through thing. >>> >>> Any thoughts for having a help button on the Monticello Browser with "user" oriented information? >>> >>> cheers, >>> BenComan >>> >> >> > > > > -- > Best regards, > Igor Stasenko. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 10, 2011

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

by Guido Stepken

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. 10, 2011

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

by csrabak＠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. 10, 2011

Re: [Pharo-project] Headless PetitParser

by Alberto Bacchelli

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. 10, 2011