- Pharo-users - lists.pharo.org

Re: [Pharo-users] Code Completion Table with dead entries

by Volkert Barr

> that's because it does not has anything to do with the code completion, but with the fact that symbols are still there (they are not removed when you remove the method). OCompletion just shows you a bunch of *symbols* you used lately (sorted with some -not much- intelligence), not methods or classes or anything... Understand. So it shows the expected behaviour, even if it not nice one. > Of course that can be fixed (and should be, eventually)... but who can take it? The "in house pharo team" now is really busy stabilizing 2.0 to take another feature action right now. I have no expectations here that this should fixed/enhanced with the upcoming 2.0. In my eyes it was not clear, if it was a bug. Anyway i can open a feature request. ;-) > But I think I don't need to remember you that the "full pharo team" are not just us, it includes all of you too. Any help (implementing cool stuff, fixing bugs or just reporting them) is always welcome (and talking by myself, I welcome much more the first, "implementing cool stuff" ;) I just started with Pharo, so give me a few weeks (to implement cool stuff ;-)) Appreciate your work. > best, > Esteban > > On May 29, 2012, at 5:07 PM, Volkert Barr wrote: > >> >>>> Hello, >>>> >>>> i have a question. Why does the code completion offers methods that were removed? >>> >>> probably because it works at the symbol level and not method dictionary. >>> May be removing a method could unintern its selector from the symbol cache. >>> >>>> I have some >>>> cases where deleted methods still listed as "symbol (no implementors)". >>> >>> where? >>> In nautilus? >> In workspace, nautilus, ... the removed methods still listed in the code completion popup. >> >> I removed the messages with nautilus and also with the default system browser. Same effect. >> >> if this is an bug, i can open a ticket. >> >> Volkert >> >> >> > > -- www.nivoba.de www.software-wartung.net www.erlang-dach.org PGP-Key on request / PGP-SchlÃ¼ssel auf Anfrage

May 29, 2012

Re: [Pharo-users] Code Completion Table with dead entries

by Mariano Martinez Peck

On Tue, May 29, 2012 at 5:17 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi > > that's because it does not has anything to do with the code completion, > but with the fact that symbols are still there (they are not removed when > you remove the method). OCompletion just shows you a bunch of *symbols* you > used lately (sorted with some -not much- intelligence), not methods or > classes or anything... > I think there are to possible fixes: > 1) just remove the symbols (but that can lead to other problems, when you > remove a method but there are still references around), or > 2) iimplement a new-new ocompletion who actually sort method and classes, > not just symbols > > Of course that can be fixed (and should be, eventually)... but who can > take it? The "in house pharo team" now is really busy stabilizing 2.0 to > take another feature action right now. > But I think I don't need to remember you that the "full pharo team" are > not just us, it includes all of you too. Any help (implementing cool stuff, > fixing bugs or just reporting them) is always welcome (and talking by > myself, I welcome much more the first, "implementing cool stuff" ;) > > Maybe a Symbol compactSymbolTable "solves" the problem. What still, when to execute the compact? > best, > Esteban > > On May 29, 2012, at 5:07 PM, Volkert Barr wrote: > > > > >>> Hello, > >>> > >>> i have a question. Why does the code completion offers methods that > were removed? > >> > >> probably because it works at the symbol level and not method dictionary. > >> May be removing a method could unintern its selector from the symbol > cache. > >> > >>> I have some > >>> cases where deleted methods still listed as "symbol (no implementors)". > >> > >> where? > >> In nautilus? > > In workspace, nautilus, ... the removed methods still listed in the code > completion popup. > > > > I removed the messages with nautilus and also with the default system > browser. Same effect. > > > > if this is an bug, i can open a ticket. > > > > Volkert > > > > > > > > > -- Mariano http://marianopeck.wordpress.com

May 29, 2012

Re: [Pharo-users] Code Completion Table with dead entries

by Esteban Lorenzano

Hi that's because it does not has anything to do with the code completion, but with the fact that symbols are still there (they are not removed when you remove the method). OCompletion just shows you a bunch of *symbols* you used lately (sorted with some -not much- intelligence), not methods or classes or anything... I think there are to possible fixes: 1) just remove the symbols (but that can lead to other problems, when you remove a method but there are still references around), or 2) iimplement a new-new ocompletion who actually sort method and classes, not just symbols Of course that can be fixed (and should be, eventually)... but who can take it? The "in house pharo team" now is really busy stabilizing 2.0 to take another feature action right now. But I think I don't need to remember you that the "full pharo team" are not just us, it includes all of you too. Any help (implementing cool stuff, fixing bugs or just reporting them) is always welcome (and talking by myself, I welcome much more the first, "implementing cool stuff" ;) best, Esteban On May 29, 2012, at 5:07 PM, Volkert Barr wrote: > >>> Hello, >>> >>> i have a question. Why does the code completion offers methods that were removed? >> >> probably because it works at the symbol level and not method dictionary. >> May be removing a method could unintern its selector from the symbol cache. >> >>> I have some >>> cases where deleted methods still listed as "symbol (no implementors)". >> >> where? >> In nautilus? > In workspace, nautilus, ... the removed methods still listed in the code completion popup. > > I removed the messages with nautilus and also with the default system browser. Same effect. > > if this is an bug, i can open a ticket. > > Volkert > > >

May 29, 2012

Re: [Pharo-users] Code Completion Table with dead entries

by Volkert Barr

>> Hello, >> >> i have a question. Why does the code completion offers methods that were removed? > > probably because it works at the symbol level and not method dictionary. > May be removing a method could unintern its selector from the symbol cache. > >> I have some >> cases where deleted methods still listed as "symbol (no implementors)". > > where? > In nautilus? In workspace, nautilus, ... the removed methods still listed in the code completion popup. I removed the messages with nautilus and also with the default system browser. Same effect. if this is an bug, i can open a ticket. Volkert

May 29, 2012

Re: [Pharo-users] Code Completion Table with dead entries

by StÃ©phane Ducasse

On May 29, 2012, at 1:22 PM, Volkert Barr wrote: > Hello, > > i have a question. Why does the code completion offers methods that were removed? probably because it works at the symbol level and not method dictionary. May be removing a method could unintern its selector from the symbol cache. > I have some > cases where deleted methods still listed as "symbol (no implementors)". where? In nautilus? > I there a way to remove > them from the code completion table? > > Pharo-1.4, Nautilus, NOCController > > Volkert

May 29, 2012

Code Completion Table with dead entries

by Volkert Barr

Hello, i have a question. Why does the code completion offers methods that were removed? I have some cases where deleted methods still listed as "symbol (no implementors)". I there a way to remove them from the code completion table? Pharo-1.4, Nautilus, NOCController Volkert

May 29, 2012

Re: [Pharo-users] [ANN] Fuel Release Version 1.8

by HernÃ¡n Morales Durand

Hola Mariano, lo estamos usando para serializar clasificaciones poblacionales de estudios filogenÃ©ticos. Cuando tengamos la publicaciÃ³n te aviso. Un abrazo, HernÃ¡n 2012/5/27 Mariano Martinez Peck <marianopeck(a)gmail.com> > che para q estas usando Fuel vos? > avisanos si te podemos agregar acA: > http://rmod.lille.inria.fr/web/pier/software/Fuel/Software-using-Fuel? > ;) > > abrazo > > On Sun, May 27, 2012 at 8:19 PM, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >> Hi Martin, >> How do I get the old behavior to instantiate a serializer without >> serializing? >> >> FLSerializer on: aFileStream >> >> I want to have the serializer around stuck over a location. >> Cheers, >> >> HernÃ¡n >> >> >> 2012/5/26 Martin Dias <tinchodias(a)gmail.com> >> >>> Hi all, >>> >>> We are proud to announce Fuel 1.8 with a lot of new features and >>> documentation. Of course, we don't stop working but it was time to >>> freeze a stable version. >>> >>> Fuel is an open-source general-purpose object serialization framework >>> developed in Pharo Smalltalk environment. More information on our >>> website [1]. >>> >>> Fuel works out of the box in Pharo from 1.1 up to 2.0 (checked at >>> #20094). Please check our documentation [2] for complete installation >>> and use guides. >>> >>> Below, there are some remarkable changes. >>> >>> - Much more complete user guides. >>> - Improved API for customizing how graph is traced. >>> - FuelMetalevel: serialization of stuff like classes and compiled >>> methods moved to an optional package. >>> - Customize objects to be treated as globals. >>> - Migrations: declare at materialization time class and variables >>> renames. >>> - Weak references properly managed. Thanks to Juan Vuletich and Levente. >>> - Thanks Pavel for helping us improving FuelPackageLoader with >>> wonderful ideas and bug reports. >>> - Serialization speed up on large graphs by using specialized >>> collections. Thanks Levente. >>> - Encoder and Decoder: new reifications that clarify the design. >>> Thanks Colin Putney. >>> - Optimized serialization of "clean" BlockClosures, which don't need >>> the whole stack of contexts. Thanks Juan Vuletich and Eliot Miranda. >>> - Added a clear error hierarchy. >>> - Debug facilities, including graph visualization using Roassal. >>> Thanks Alexandre and Doru. >>> - Many more new tests. Including those from extension packages, we >>> have almost 600 tests. >>> - Repository moved from 'http://www.squeaksource.com/Fuel' to >>> 'http://ss3.gemstone.com/ss/Fuel'. >>> >>> If you are a Fuel user we are not aware of, please let us know! >>> >>> Best regards, >>> Martin and Mariano >>> >>> [1]: http://rmod.lille.inria.fr/web/pier/software/Fuel >>> [2]: >>> http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation >>> >>> >> >> >> -- >> HernÃ¡n Morales >> Institute of Veterinary Genetics. >> National Scientific and Technical Research Council (CONICET). >> La Plata (1900), Buenos Aires, Argentina. >> Telephone: +54 (0221) 421-1799. >> Internal: 422 >> Fax: 425-7980 or 421-1799. >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- HernÃ¡n Morales Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.

May 28, 2012

Re: [Pharo-users] [Pharo-project] [ANN] Fuel Release Version 1.8

by Martin Dias

> >> It has been long time since I looked into Pharo and licensing environment >> (revitalising my interest now...), so I may be asking obvious questions but >> what is the licencing model for Fuel? Â (skimmed the mail and the web site >> and only noted "open-sourced") >> > > Thanks. I have updated the site. Now it says: "An open-source (MIT license) > general-purpose object serialization framework developed in Pharo Smalltalk > environment." Thanks Jaroslaw, any feedback is welcome!

May 28, 2012

Re: [Pharo-users] [Pharo-project] [ANN] Fuel Release Version 1.8

by Mariano Martinez Peck

On Mon, May 28, 2012 at 7:44 PM, Jaroslaw Podgajny < jarek.x.podgajny(a)gmail.com> wrote: > Hi guys, > > It has been long time since I looked into Pharo and licensing environment > (revitalising my interest now...), so I may be asking obvious questions but > what is the licencing model for Fuel? (skimmed the mail and the web site > and only noted "open-sourced") > > Thanks. I have updated the site. Now it says: "An open-source (MIT license) general-purpose *object serialization* framework developed in Pharo Smalltalk environment <http://www.pharo-project.org>." > > Regards, Jaroslaw > > > On Sunday, May 27, 2012, Igor Stasenko wrote: > >> On 27 May 2012 21:23, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> > >> > >> > >> >> Fuel works out of the box in Pharo from 1.1 up to 2.0 (checked at >> >> #20094). Please check our documentation [2] for complete installation >> >> and use guides >> > >> > >> > >> > Martin told me something by private email that I think is worth to >> mention. >> > Not sure if you read it carefully, but Fuel is working from Pharo >> version >> > 1.1 up to 2.0!!! >> >> But he is mentioned that already in his announcement. :) >> This is nice, of course! >> >> >> > One of reasons is to help people migrate to new Pharo versions by using >> Fuel >> > as a way of moving data. >> > >> > Cheers >> > >> >> . >> >> >> >> Below, there are some remarkable changes. >> >> >> >> - Much more complete user guides. >> >> - Improved API for customizing how graph is traced. >> >> - FuelMetalevel: serialization of stuff like classes and compiled >> >> methods moved to an optional package. >> >> - Customize objects to be treated as globals. >> >> - Migrations: declare at materialization time class and variables >> renames. >> >> - Weak references properly managed. Thanks to Juan Vuletich and >> Levente. >> >> - Thanks Pavel for helping us improving FuelPackageLoader with >> >> wonderful ideas and bug reports. >> >> - Serialization speed up on large graphs by using specialized >> >> collections. Thanks Levente. >> >> - Encoder and Decoder: new reifications that clarify the design. >> >> Thanks Colin Putney. >> >> - Optimized serialization of "clean" BlockClosures, which don't need >> >> the whole stack of contexts. Thanks Juan Vuletich and Eliot Miranda. >> >> - Added a clear error hierarchy. >> >> - Debug facilities, including graph visualization using Roassal. >> >> Thanks Alexandre and Doru. >> >> - Many more new tests. Including those from extension packages, we >> >> have almost 600 tests. >> >> - Repository moved from 'http://www.squeaksource.com/Fuel' to >> >> 'http://ss3.gemstone.com/ss/Fuel'. >> >> >> >> If you are a Fuel user we are not aware of, please let us know! >> >> >> >> Best regards, >> >> Martin and Mariano >> >> >> >> [1]: http://rmod.lille.inria.fr/web/pier/software/Fuel >> >> [2]: >> >> >> http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation >> >> >> > >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >> -- Mariano http://marianopeck.wordpress.com

May 28, 2012

Re: [Pharo-users] [Pharo-project] [ANN] Fuel Release Version 1.8

by StÃ©phane Ducasse

On May 28, 2012, at 7:44 PM, Jaroslaw Podgajny wrote: > Hi guys, > > It has been long time since I looked into Pharo and licensing environment (revitalising my interest now...), so I may be asking obvious questions but what is the licencing model for Fuel? (skimmed the mail and the web site and only noted "open-sourced") good point. It is MIT as the complete pharo environment. Stef > > > > Regards, Jaroslaw > > > On Sunday, May 27, 2012, Igor Stasenko wrote: > On 27 May 2012 21:23, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > > > > >> Fuel works out of the box in Pharo from 1.1 up to 2.0 (checked at > >> #20094). Please check our documentation [2] for complete installation > >> and use guides > > > > > > > > Martin told me something by private email that I think is worth to mention. > > Not sure if you read it carefully, but Fuel is working from Pharo version > > 1.1 up to 2.0!!! > > But he is mentioned that already in his announcement. :) > This is nice, of course! > > > > One of reasons is to help people migrate to new Pharo versions by using Fuel > > as a way of moving data. > > > > Cheers > > > >> . > >> > >> Below, there are some remarkable changes. > >> > >> - Much more complete user guides. > >> - Improved API for customizing how graph is traced. > >> - FuelMetalevel: serialization of stuff like classes and compiled > >> methods moved to an optional package. > >> - Customize objects to be treated as globals. > >> - Migrations: declare at materialization time class and variables renames. > >> - Weak references properly managed. Thanks to Juan Vuletich and Levente. > >> - Thanks Pavel for helping us improving FuelPackageLoader with > >> wonderful ideas and bug reports. > >> - Serialization speed up on large graphs by using specialized > >> collections. Thanks Levente. > >> - Encoder and Decoder: new reifications that clarify the design. > >> Thanks Colin Putney. > >> - Optimized serialization of "clean" BlockClosures, which don't need > >> the whole stack of contexts. Thanks Juan Vuletich and Eliot Miranda. > >> - Added a clear error hierarchy. > >> - Debug facilities, including graph visualization using Roassal. > >> Thanks Alexandre and Doru. > >> - Many more new tests. Including those from extension packages, we > >> have almost 600 tests. > >> - Repository moved from 'http://www.squeaksource.com/Fuel' to > >> 'http://ss3.gemstone.com/ss/Fuel'. > >> > >> If you are a Fuel user we are not aware of, please let us know! > >> > >> Best regards, > >> Martin and Mariano > >> > >> [1]: http://rmod.lille.inria.fr/web/pier/software/Fuel > >> [2]: > >> http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation > >> > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- > Best regards, > Igor Stasenko. >

May 28, 2012