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

Re: [Pharo-project] [NB] Speaking about callbacks

by Marten Feldtmann

Me too. Marten Am 16.09.2012 20:42, schrieb StÃ©phane Ducasse: > > for what it is worth I like the 3rd form. Now I'm not sure on: is the right selector. > > >

Sept. 16, 2012

Re: [Pharo-project] [NB] Speaking about callbacks

by StÃ©phane Ducasse

On Sep 16, 2012, at 7:17 PM, Igor Stasenko wrote: > Hello, there > > i am happy to say that during last week, i found a cure for my > callback code, and so finally callbacks are now working without > crashing the VM. :) > But before releasing it to public, first, i need to update VMs for > that, because of additional callback support code in VM. > > Right now, i'd like to discuss about different ways of > defining/creating callbacks. And i need more input from people, > because i think > the way how i implemented it is good for get started, but it looks > like there could be more convenient forms :) > > So, the existing implementation, for creating a callback, you must > make a subclass of NBFFICallback, overide #fnSpec method > and then instantiate it by using: > > callback := MyCallBack on: [:... some block ] > > and then you must pass it somewhere (to some external function), and > so, when callback get called, your block will handle it. > > In objective-C, however it would be much nicer to have a smalltalk > objects act as a Obj-C objects (so implementing a methods > for it will naturally map them as a callbacks ). > > For instance imagine that i wanna make own subclass of NSFoo obj-C class > and wanna override the #bar method. > And then i passing it as an obj-c instance around and each time ,Obj-C > #bar message is sent to it , i got a #bar message sent to my smalltalk > instance. > That would be really cool, isnt? Despite it is only applicable to > obj-c because of similar object model :) > > I imagine it could be done as following: > in #bar method you putting a special pragma: > > MyClass>>bar > <objCMethod: 'int ()'> > ^ 5 > > that's it, you telling the compiler that given method can be called > from Objective-C.. and you don't have to manually instantiate > callbacks etc.. > > In fact, same form can be used for non-objC callbacks , you must just > tell something like: > > callback := (MyClass>>#bar) asCallbackFor: myObject. > > here, you instantiating a callback, which when called, the object > 'myObject' will receive #bar message. But unlike from Obj-C this > callback > won't work for all instances of MyClass, but just for specific one. > > And third form is a variation of original one, instead of subclassing > the NBFFICallback, actually i can change implementation to use special > factory class(es) for it, so to create a callback you will do > something like: > > callbackFactory := NBFFICallback withSignature: #( int (int x, void * bar)). > > callback := callbackFactory on: [:x :bar | .... ]. > > So, i'd like to hear your input, which one you like, and which ones > you prefer to have > > 1. requires creating a subclass of NBFFICallback, overriding it's > fnSpec method. Takes a block closure as a callback. > 2. first you must create a factory object by specifying a callback > signature, then you can instantiate new callbacks by passing a block > closure to that factory > 3. to create a callback you must specify it's signature in one of the > compiled methods, and specify an object which will receive a message > when callback will be called. for what it is worth I like the 3rd form. Now I'm not sure on: is the right selector.

Sept. 16, 2012

Re: [Pharo-project] pharo on ipad3 -- tiny image shown only

by phil＠highoctane.be

In another application, I do have this thing that helps in rescaling (the class is a XXXView) // Enable retina display if( CFG_IOS_RETINA_ENABLED ){ if( [self respondsToSelector:@selector(contentScaleFactor)] ){ float scaleFactor=[[UIScreen mainScreen] scale]; [self setContentScaleFactor:scaleFactor]; } } This is a quickfix that will look ugly but... worth trying. Add that into the SqueakUIView.m file inside this: - (id)initWithFrame:(CGRect) aFrame { self = [super initWithFrame: aFrame]; self.autoresizingMask = UIViewAutoresizingFlexibleRightMargin|UIViewAutoresizingFlexibleBottomMargin|UIViewAutoresizingFlexibleHeight|UIViewAutoresizingFlexibleWidth; colorspace = CGColorSpaceCreateDeviceRGB(); return self; } I suspect that self.autoresizingMask is the culprit... Hope it helps. Phil 2012/9/16 Igor Stasenko <siguctua(a)gmail.com>: > On 16 September 2012 18:14, Johan Brichau <johan(a)inceptive.be> wrote: >> Hi everyone, >> >> After some very friendly help of Nick and Igor at ESUG, I managed to get the iStackVM running on my iPad again, thanks a lot guys! >> >> However, the image now shows up on only a very small portion of the screen. >> Is that a known issue? > > yes. this is a "retina display" issue. :) > I am not sure what is the status, however i can assure you that we > (especially Esteban) is well aware of it. > >> >> btw: the problem I experienced to compile the vm correctly was eventually a package-loading problem (i.e. I did not get the correct packages). This is because there is a bug in the version-method generation of Metacello. Together with Dale, we discussed that issue and Dale just solved it last friday. >> >> Johan > > > > -- > Best regards, > Igor Stasenko. >

Sept. 16, 2012

Re: [Pharo-project] pharo on ipad3 -- tiny image shown only

by phil＠highoctane.be

It works fine on my iPad2. Dunno about the 3. What happens when you rotate the screen? Phil 2012/9/16 Johan Brichau <johan(a)inceptive.be>: > Hi everyone, > > After some very friendly help of Nick and Igor at ESUG, I managed to get the iStackVM running on my iPad again, thanks a lot guys! > > However, the image now shows up on only a very small portion of the screen. > Is that a known issue? > > btw: the problem I experienced to compile the vm correctly was eventually a package-loading problem (i.e. I did not get the correct packages). This is because there is a bug in the version-method generation of Metacello. Together with Dale, we discussed that issue and Dale just solved it last friday. > > Johan

Sept. 16, 2012

[Pharo-project] [NB] Speaking about callbacks

by Igor Stasenko

Hello, there i am happy to say that during last week, i found a cure for my callback code, and so finally callbacks are now working without crashing the VM. :) But before releasing it to public, first, i need to update VMs for that, because of additional callback support code in VM. Right now, i'd like to discuss about different ways of defining/creating callbacks. And i need more input from people, because i think the way how i implemented it is good for get started, but it looks like there could be more convenient forms :) So, the existing implementation, for creating a callback, you must make a subclass of NBFFICallback, overide #fnSpec method and then instantiate it by using: callback := MyCallBack on: [:... some block ] and then you must pass it somewhere (to some external function), and so, when callback get called, your block will handle it. In objective-C, however it would be much nicer to have a smalltalk objects act as a Obj-C objects (so implementing a methods for it will naturally map them as a callbacks ). For instance imagine that i wanna make own subclass of NSFoo obj-C class and wanna override the #bar method. And then i passing it as an obj-c instance around and each time ,Obj-C #bar message is sent to it , i got a #bar message sent to my smalltalk instance. That would be really cool, isnt? Despite it is only applicable to obj-c because of similar object model :) I imagine it could be done as following: in #bar method you putting a special pragma: MyClass>>bar <objCMethod: 'int ()'> ^ 5 that's it, you telling the compiler that given method can be called from Objective-C.. and you don't have to manually instantiate callbacks etc.. In fact, same form can be used for non-objC callbacks , you must just tell something like: callback := (MyClass>>#bar) asCallbackFor: myObject. here, you instantiating a callback, which when called, the object 'myObject' will receive #bar message. But unlike from Obj-C this callback won't work for all instances of MyClass, but just for specific one. And third form is a variation of original one, instead of subclassing the NBFFICallback, actually i can change implementation to use special factory class(es) for it, so to create a callback you will do something like: callbackFactory := NBFFICallback withSignature: #( int (int x, void * bar)). callback := callbackFactory on: [:x :bar | .... ]. So, i'd like to hear your input, which one you like, and which ones you prefer to have 1. requires creating a subclass of NBFFICallback, overriding it's fnSpec method. Takes a block closure as a callback. 2. first you must create a factory object by specifying a callback signature, then you can instantiate new callbacks by passing a block closure to that factory 3. to create a callback you must specify it's signature in one of the compiled methods, and specify an object which will receive a message when callback will be called. -- Best regards, Igor Stasenko.

Sept. 16, 2012

Re: [Pharo-project] pharo on ipad3 -- tiny image shown only

by Igor Stasenko

On 16 September 2012 18:14, Johan Brichau <johan(a)inceptive.be> wrote: > Hi everyone, > > After some very friendly help of Nick and Igor at ESUG, I managed to get the iStackVM running on my iPad again, thanks a lot guys! > > However, the image now shows up on only a very small portion of the screen. > Is that a known issue? yes. this is a "retina display" issue. :) I am not sure what is the status, however i can assure you that we (especially Esteban) is well aware of it. > > btw: the problem I experienced to compile the vm correctly was eventually a package-loading problem (i.e. I did not get the correct packages). This is because there is a bug in the version-method generation of Metacello. Together with Dale, we discussed that issue and Dale just solved it last friday. > > Johan -- Best regards, Igor Stasenko.

Sept. 16, 2012

[Pharo-project] pharo on ipad3 -- tiny image shown only

by Johan Brichau

Hi everyone, After some very friendly help of Nick and Igor at ESUG, I managed to get the iStackVM running on my iPad again, thanks a lot guys! However, the image now shows up on only a very small portion of the screen. Is that a known issue? btw: the problem I experienced to compile the vm correctly was eventually a package-loading problem (i.e. I did not get the correct packages). This is because there is a bug in the version-method generation of Metacello. Together with Dale, we discussed that issue and Dale just solved it last friday. Johan

Sept. 16, 2012

Re: [Pharo-project] [ANN] iPad Dr. Geo 12.10

by StÃ©phane Ducasse

yes I meet boris once and this is a nice person. Ask him if he want to release his code under MIT. On Sep 16, 2012, at 5:22 PM, Hilaire Fernandes wrote: > Ho Lorenzo, > > Philip wrote about simplex algorithm for DrGeo, but he did not gave > examples of use case. Right now I can not tell if I will use it for Dr. Geo. > But it is nice you asked. > > Something I will use for sure in Dr. Geo is a Computer Algebra System > (even a simple one) written in Smalltalk. > Btw, does any of you know Boris Gaertner, he worked in a CAS system in > Smalltalk ? > http://www.bgaertner.gmxhome.de/liouville.htm > > Thanks > > Hilaire > > Le 16/09/2012 17:04, Lorenzo Schiavina a Ã©crit : >> Hi Hilaire, >> >> I am going to download a simplex algorithm for linear programming from a VSE >> version I developed some years ago; are you (or some other people) >> interested to it, as I have found that the porting is more complex than I >> have imagined. >> >> Grazie >> >> Lorenzo >> > >

Sept. 16, 2012

Re: [Pharo-project] R: [ANN] iPad Dr. Geo 12.10

by Hilaire Fernandes

Ho Lorenzo, Philip wrote about simplex algorithm for DrGeo, but he did not gave examples of use case. Right now I can not tell if I will use it for Dr. Geo. But it is nice you asked. Something I will use for sure in Dr. Geo is a Computer Algebra System (even a simple one) written in Smalltalk. Btw, does any of you know Boris Gaertner, he worked in a CAS system in Smalltalk ? http://www.bgaertner.gmxhome.de/liouville.htm Thanks Hilaire Le 16/09/2012 17:04, Lorenzo Schiavina a Ã©crit : > Hi Hilaire, > > I am going to download a simplex algorithm for linear programming from a VSE > version I developed some years ago; are you (or some other people) > interested to it, as I have found that the porting is more complex than I > have imagined. > > Grazie > > Lorenzo >

Sept. 16, 2012

[Pharo-project] R: [ANN] iPad Dr. Geo 12.10

by Lorenzo Schiavina

Hi Hilaire, I am going to download a simplex algorithm for linear programming from a VSE version I developed some years ago; are you (or some other people) interested to it, as I have found that the porting is more complex than I have imagined. Grazie Lorenzo -----Messaggio originale----- Da: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] Per conto di Hilaire Fernandes Inviato: domenica 16 settembre 2012 10.30 A: pharo-project(a)lists.gforge.inria.fr Oggetto: [Pharo-project] [ANN] iPad Dr. Geo 12.10 Dr. Geo (aka Dr. Geometry) 12.10 for iPad is available on AppStore. It comes in two versions: gratis and paid. http://itunes.apple.com/us/app/dr.-geometry/id559858173?l=fr&ls=1&mt=8 Compare to the desktop versions, it is almost feature complete: only the script and programmed figure can not be created or edited with this version. However, sketches including scripts are interpreted and rendered correctly on the tablet. *Feedbacks* and *rating* are welcome and greatly appreciated! Thanks! http://drgeo.eu

Sept. 16, 2012