- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Some Object methods that could be removed ?

by Henrik Sperre Johansen

On 04.12.2012 17:54, Camillo Bruni wrote: > On the same topic. > > Do we have a VM that marks methods as they are executed? > > We should really do a cleaning session by running an image for a week or so > and remove all methods that are unused! > That's an ... overly optimistic view :) http://www.youtube.com/watch?feature=player_detailpage&v=yxqkzSbKhF8#t=270s If the same holds true for the % of objects that are methods, you would probably remove around 90% depending on usage pattern during that particular week. I'd imaging the influx of #doesNotUnderstand issues in the tracker would be quite impressive though :P Cheers, Henry

Dec. 5, 2012

Re: [Pharo-project] Vim Keys?

by Goubier Thierry

Le 03/12/2012 23:17, Sean P. DeNigris a Ã©crit : > Goubier Thierry wrote >> the removal of the global, class-linked maps (it was rejected)... >> This is the only step missing for your vim shortcuts to work. > > Yes!!! That's exactly what was holding me up... From > http://forum.world.st/Keymapping-Class-vs-Instance-Targets-tp4639863p464022… > : What I introduced is kind of what you are asking : - An initialization method in a Morph which adds default maps to the KMDispatcher instance, called #initializeShortcuts:. Its called when the KMDispatcher instance is created. It is used by the focus navigation, which loads the #MorphFocusCtrlNavigation category. But I didn't remember that conversation when I did it :( Thierry > Sean P. DeNigris wrote >> >> Guillermo Polito wrote >>> - static shortcuts (per class) >>> - dynamic category shortcuts ( you build a category and attach it to an >>> instance) >> The thing is that these two conflict. If I add a category to a class in >> the "static shortcuts" (which I consider to be "default shortcuts" - I >> think that's more useful), and then I want to remove that category for an >> instance, I can't. >> >> What I want is: each instance gets its own copy of all its maps. If the >> morph instance doesn't have any per-instance customizations, this can >> point to the class defaults to save space (but I think this would be >> premature optimization). However, as soon as the instance differs at all >> from the class defaults, it /must/ have it's own local copy of all the >> maps. I don't want to have to override each shortcut of a category >> attached to the class. I want to detach the category /for just this >> instance/. > > > > > > -- > View this message in context: http://forum.world.st/Re-Vim-Keys-tp4657381p4657920.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Dec. 5, 2012

Re: [Pharo-project] The monkey is back in town

by Goubier Thierry

Le 05/12/2012 04:43, Camillo Bruni a Ã©crit : > I had a sudden urge to program something so I revived the monkey (partly) > > - full smalltalk implementation (no more ruby) > - basic command line handler (could be better but works..) > - using OSProcess with FileSystem-Legacy in 2.0 So that would be the way to have OSProcess in 2.0? Thierry > the only thing missing are the couple of changes I proposed for the main image: > > - http://code.google.com/p/pharo/issues/detail?id=7097 > - http://code.google.com/p/pharo/issues/detail?id=7096 > - http://code.google.com/p/pharo/issues/detail?id=7095 > > once they are in, we're ready to roll > cami on fernet > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Dec. 5, 2012

Re: [Pharo-project] The monkey is back in town

by Pavel Krivanek

Cool, where can we found source code of the monkey? -- Pavel On Wed, Dec 5, 2012 at 4:43 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I had a sudden urge to program something so I revived the monkey (partly) > > - full smalltalk implementation (no more ruby) > - basic command line handler (could be better but works..) > - using OSProcess with FileSystem-Legacy in 2.0 > > the only thing missing are the couple of changes I proposed for the main image: > > - http://code.google.com/p/pharo/issues/detail?id=7097 > - http://code.google.com/p/pharo/issues/detail?id=7096 > - http://code.google.com/p/pharo/issues/detail?id=7095 > > once they are in, we're ready to roll > cami on fernet

Dec. 5, 2012

Re: [Pharo-project] An excellent news

by Jordi Delgado

Great!! Bests, Jordi > Hi guys > > We mentioned it in the past but now this is really official. To support the consortium, Inria is paying one full year > to Igor Stasenko. > > We want to thank Inria for its continuous support. > > Stef

Dec. 5, 2012

Re: [Pharo-project] An excellent news

by Sven Van Caekenberghe

On 05 Dec 2012, at 09:43, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Excellent news! > > Doru +100 Indeed, very good news. Thank you, INRIA. > On Wed, Dec 5, 2012 at 9:41 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > We mentioned it in the past but now this is really official. To support the consortium, Inria is paying one full year > to Igor Stasenko. > > We want to thank Inria for its continuous support. > > Stef > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 5, 2012

[Pharo-project] PharoConf 2013 @ Bern?

by StÃ©phane Ducasse

Hello Pharoers The software composition group of the university of Bern proposed to organize the next pharo conf at berne during the week of 2-3 of April 2013. We are really happy of this proposal. Now we would like to know what you think about it before committing to the date and location. The Pharo board and crew

Dec. 5, 2012

Re: [Pharo-project] An excellent news

by Tudor Girba

Excellent news! Doru On Wed, Dec 5, 2012 at 9:41 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi guys > > We mentioned it in the past but now this is really official. To support > the consortium, Inria is paying one full year > to Igor Stasenko. > > We want to thank Inria for its continuous support. > > Stef > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 5, 2012

[Pharo-project] An excellent news

by StÃ©phane Ducasse

Hi guys We mentioned it in the past but now this is really official. To support the consortium, Inria is paying one full year to Igor Stasenko. We want to thank Inria for its continuous support. Stef

Dec. 5, 2012

Re: [Pharo-project] NBFFICallback fnSpec

by Max Leske

On 05.12.2012, at 07:15, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: > On 12/4/2012 8:48 PM, Igor Stasenko wrote: >> On 5 December 2012 03:22, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >>> Hello, >>> >>> I am working through implementing NativeBoost interface to a C wrapper dll. >>> >>> I have 8 callback functions to call in this interface. I am subclassing >>> NBFFICallback as stated in the documentation. I am also implementing the >>> fnSpec method based on the code in the header file. >>> >>> fnSpec >>> >>> ^#( void (NBExternalString rowID, Row rowData)) >>> >>> This is the code in the header: >>> >>> typedef void (*TABLE_ROW_CALLBACK)(const char *rowID, FXCHandle rowData); >>> >>> >>> Should I leave the return type as void or should I use NBVoid? >>> >> Either will work. >> As long as >> NBFFICallout new resolveType: 'void' >> and >> NBFFICallout new resolveType: 'NBVoid' >> returning same object(s). >> >>> I do not know C at all. Is the NBExternalString suitable for the const char >>> *rowID? >> NBExternalString is a coverter which takes a pointer and turns it into >> ByteString instance. >> >> But you can use just 'String' as a type qualifier, which is alias for >> NBExternalString: >> >> String class>>asNBExternalType: gen >> >> ^ gen resolveType: #NBExternalString >> >>> The documentation says you can use it for char*, but I don't know what >>> difference const makes. >>> >> The const modifier matters for C compiler that guarantees that no >> attempts to write at pointer location >> will be made.. which is of course get lost when you cross language >> boundaries and therefore doesn't makes sense specifying in function >> signature. >> >> NBExternalString takes a pointer as input and then creates an instance >> of ByteString object >> and copies contents of C string in newly created object. >> From that perspective it fits well with 'const char *' type, because >> at language side you never obtain a >> real pointer to the string, but just a copy with string contents, and >> even if you will try to modify that string, you will be modifying a >> copy, but not original. >> >> P.S. if you load NativeBoost-Help package, there is a page describing >> in detail how type system >> and type resolution works. >> >> You can read help using >> NBHelp open >> >> or just open a help browser.. >> >> There could be some glitches loading markdown parser (which i had few >> days ago).. so if it will fail to work, then you can read from sources >> here: >> NBHelpOnFFI class>>types / types2 > Thanks for the help and information. > I wasn't expecting an answer quite so quickly. I can't tell if you sleep? :) > > I haven't been able to get the NBHelp to work yet. > In a freshly downloaded NBCog-VM and Pharo-2.0.image after installing NB and NBHelp. > When I do, NBHelp open. It starts installing but can't get past petitmarkdown. > There's a new thread on the list about the configuration of PetitParser being broken. This is probably what trips up loading the NB help ("ConfigurationOfPetitParser has broken #'common' section"). Cheers, Max > I don't know if it is a momentary SS3 problem or what. I'll try again in the morning after I get some sleep. > > Again, thanks. > > Jimmie >

Dec. 5, 2012