April 2014 - Pharo-users - lists.pharo.org

Use of FileDialogWindow : getting the result

by Thomas Bany

Hi ! I'm trying to fit a GUI in full screen mode, that uses a FileDialogWindow at some point. I'm able to recover the answer from FileDialogWindow when I it is opened modaly. However, since I would like to open it fullscreen with the selector #openFullScreen, the calling block does not wait and immediatly gets a nil answer. I was thinking of hacking my way out of it and subclassing FileDialogWindow to overide a method somewhere to call a block of my choosing but I really does not feel right. Has anyone a clue ? Thanks in advance for your time ! Thomas.

April 7, 2014

Re: [Pharo-users] [ANN] JNIPort for Pharo 3.0 alpha

by Tudor Girba

Hi Joachim, Thanks for the explanations. It looks complicated but I am very happy it is possible! I will give a try next week and get back to you. Cheers, Doru On Sat, Apr 5, 2014 at 2:32 PM, Joachim Geidel <joachim.geidel(a)onlinehome.de > wrote: > Am 31.03.2014 um 21:25 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Now, the next question. I saw that it is possible to enable callbacks, > but I could not find an example of how it works. > > > > For example, could we model this: > > > > - in a JavaClassOriginator class we have a method like > > execute(JavaClassTargetInterface target) { target.m() } > > - In Pharo we create PharoClassTargetImplementation as an implementation > of JavaClassTargetInterface > > - passing an instance of PharoClassTargetImplementation to > JavaClassOriginator results in calling PharoClassTargetImplementation>>m > > > > ? > > > > > > Cheers, > > Doru > > Hi Doru, > > it's not completely straightforward, but also not really complicated. > Chris Uppal's JNIPort documentation contains examples, and you can also get > some information from the test cases for callbacks. You will need the > jniport.jar file which can be downloaded from > http://jniport.wikispaces.com/Downloads (it is contained in > JNIPort_Extras.zip). The Java classes needed for callback support have > names starting with "Dolphin" - they come directly from Chris' > implementation for Dolphin Smalltalk. > > A simple example: To set up sending a simple notification without > parameters to a Smalltalk object, you need a Java class similar to the > following: > > ----------------- > package my.package; > import org.metagnostic.jniport.*; > public class MyClass > { > private static final Object notifyTag = new > String("MyClass.sendNotification()"); > public static Object notifyTag () { return notifyTag; } > public void sendNotification() > throws RequestNotHandedException > { > new DolphinNotification(notifyTag, this).send(); > } > } > ----------------- > > You have to install the callback in Smalltalk: > > ----------------- > NotificationHandler := ... "the object which receives the notifications" > classStatic := jvm findClass: 'my.package.MyClass'. > jvm callbackRegistry > setCallback: classStatic notifyTag "the tag can be an arbitrary > String" > handler: [:this :param | NotificationHandler > handleNotificationFor: this]. > ----------------- > > When you send sendNotification() to an instance of MyClass, > NotificationHandler should receive the message #handleNotificationFor:. > > In the example code, the tag is a static variable in MyClass. Of course, > you can also give every instance of MyClass its own tag. In this case, you > have to set up a callback in Smalltalk for every tag which is used. > > The example is a short version of the test code for handling notifications > in JNIPortCallbackNotificationsTest and the corresponding Java class > org.metagnostic.jniport.test.regression.Notifications. The source code of > this Java class is in the archive JNIPort-Tests.zip which is contained in > JNIPort_Extras.zip. > > If you need an example for a notification which has parameters and where > the Smalltalk code returns a result, have a look at > JNIPortCallbackRequestsTest>>testCallbackWithOneParameterAndReturn and the > corresponding Java class org.metagnostic.jniport.test.regression.Callbacks. > > In the Java class, you need something like this (copied from Callbacks and > simplified) which enables a callback taking an int parameter and returning > an instance of the Java class Integer: > > private static final Object callbackTag = new String("callback > with parameters"), > > // callback with return value > public int callbackAndReturn(int i) > throws Throwable > { > Object returnValue = new DolphinRequest(callbackTag, this, > i).value(); > return ((Integer) returnValue).intValue(); > } > > A DolphinRequest is created with the tag which identifies the callback in > Smalltalk, the object sending the callback (this), and an arbitrary number > of parameters. For example, the following creates a DolphinRequest with two > parameters: > > DolphinRequest dr = new DolphinRequest( > s_callbackTag, > this, > new Integer(i), > new Double(d)); > > Calling the value() method of the DolphinRequest sends the request to > VisualWorks and returns the result of the Smalltalk callback block. > > In Smalltalk, you can create callbacks accepting parameters like this (see > JNIPortCallbackRequestsTest): > > "No parameters" > jvm callbackRegistry setCallback: classStatic callbackTag > handler: [:this :param | self handleCallbackFor: > this]. > > "One parameter" > jvm callbackRegistry setCallback: classStatic callbackTag > handler: [:this :param | self handleCallbackFor: > this with: param]. > > "Arbitrary number of parameters" > jvm callbackRegistry setCallback: classStatic callbackTag > handler: [:this :params | self handleCallbackFor: > this withArguments: params asArray]. > > If the callback has a result which should be passed from Smalltalk to > Java, it must be a Java object. Here is an example from the test class > (callbacksStatus is just an instance variable of > JNIPortCallbackRequestsTest): > > handleCallbackFor: aJavaObject with: anotherJavaObject > > | jliClass | > > jliClass := jvm findClass: #'java.lang.Integer'. > > callbacksStatus addLast: (aJavaObject = instance). "identity > test on the Java object" > callbacksStatus addLast: ((anotherJavaObject static = jliClass) > and: [anotherJavaObject intValue = 1]). > > ^ jliClass new_int: 15. "Do not return a Smalltalk Integer. It > must be a Java Integer" > > Johan Brichau's JavaConnect had a more direct way of creating callbacks, > using Java's dynamic proxies. However, it had an open issue, as it relied > on different Java objects having different identity hashes, which is not > true in all cases. JNIPort's implementation is relatively complicated > because it had to take into account that the callbacks can be triggered > from a different thread than the Smalltalk thread. In VisualWorks, that's > not a problem, as the VM handles this, and Pharo simply does not support > callbacks from foreign threads. So, it could be simplified in JNIPort as > well. > > Does this help? > Joachim > > > -- www.tudorgirba.com "Every thing has its own flow"

April 7, 2014

Re: [Pharo-users] Compiler evaluate: -> Smalltalk evaluate:

by Sergi Reyner

2014-04-07 11:51 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > In 4.0, we will remove the old compiler and then we can see how to make > the API perfect. > Will it be able to decompile by then? Cheers, Sergi

April 7, 2014

Re: [Pharo-users] free learnig book

by Roelof Wobben

April 7, 2014

Re: [Pharo-users] Compiler evaluate: -> Smalltalk evaluate:

by Marcus Denker

On 07 Apr 2014, at 12:15, Andre Hora <andrehoraa(a)gmail.com> wrote: > Hello, > > Recently in Pharo there was some tendency to replace Compiler evaluate: by Smalltalk evaluate:. > Stef does not seem to agree with that. > My question is which one is the correct convention to call #evaluate: ? > The problem is that Compiler is the old Compiler. There is Compiler and OpalCompiler. If you now hard-code Compiler, then the old compiler is used. Yes, this is not beautiful, but is is *very* hard to move a system to a new compiler and new API without some ugliness while doing so. In 4.0, we will remove the old compiler and then we can see how to make the API perfect. Marcus

April 7, 2014

Re: [Pharo-users] Drag and drop items between list views

by MartinW

Benjamin Van Ryseghem (Pharo) wrote > Out of this thread, I have made this post: > http://spec.st/docs/drag_n_drop/ > With a small change in the Spec code base (to not sort by default, but > only when a sorting block is specified), > it gives an example of how to do what you want :) Cool. Thank you. Still the fact that the passenger does only know the object's string representation is a problem. Because in a real application i would not display strings and integers in the lists, but my domain objects. And already with this example it does not work: you convert the string to an integer when it leaves list1 - but of course a user might drag it back from list2 to list1 - and here you can no longer convert it as you do not know if the dragged object is a string or an integerâ¦ Why does the passenger only know an object's string representation? Can this be changed? -- View this message in context: http://forum.world.st/Drag-and-drop-items-between-list-views-tp4752285p4753… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 7, 2014

Compiler evaluate: -> Smalltalk evaluate:

by Andre Hora

Hello, Recently in Pharo there was some tendency to replace Compiler evaluate: by Smalltalk evaluate:. Stef does not seem to agree with that. My question is which one is the correct convention to call #evaluate: ? thanks in advance, -- Andre Hora

April 7, 2014

Re: [Pharo-users] Drag and drop items between list views

by Benjamin

Sorry for the delay, I turn off my emails during the week end :) Out of this thread, I have made this post: http://spec.st/docs/drag_n_drop/ With a small change in the Spec code base (to not sort by default, but only when a sorting block is specified), it gives an example of how to do what you want :) (since it is not a crucial change, I do not think it will be introduced in 3.0, but the latest Spec image can be found here: http://benjamin.is-a-geek.com:9095/job/Spec/lastSuccessfulBuild/artifact/) Hope it helps, Ben On 04 Apr 2014, at 12:18, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 04/04/2014 12:04, MartinW a Ã©crit : >> Goubier Thierry wrote >>> By the way, any chance of having your code as an example for Spec? I >>> went through the spec documentation and I couldn't see anything similar, >>> and, from our difficulties to get that to work, I would guess a bit of >>> work on Spec drag and drop support could be a good thing. >> >> I just start investigating my ui possibilities with pharo for a new >> application. The code examples in this thread are all there is at the >> moment. > > Ok. Still, they offer a good working base for a specific use case. > >> Goubier Thierry wrote >>>> Are there other possibilities if i do not use Spec? >>> >>> Yes. Drag and drop code in Morphic is fairly similar. The Morphic code >>> for opening windows is certainly longer, however. >> >> Yes, there are more possibilities if i do it in pure Mophic/Polymorph? â or >> possibilites are quite similar? :) > > You get better control over what drag and drop means (including the ability to control per-item if you will accept the target, or what to carry when the drag starts), but the framework takes time to get into. > > Thierry > -- > 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 >

April 7, 2014

Re: [Pharo-users] [ANN] WIP iStoa

by Bernat Romagosa

Very nice, Hilarie! Just FYI, I had to replace the shipped vm and plugins by the latest ones to get it to work on my Debian Wheezy machine. Congrats! 2014-04-05 18:20 GMT+02:00 Hilaire Fernandes <hilaire.fernandes(a)gmail.com>: > Hello, > > For those who want to give a try to work in progress iStoa on Linux, an > Interactive math exercises book. > > https://launchpad.net/istoa/alpha/14.04/+download/iStoa.app-14.04a.zip > > Hilaire > > -- > Dr. Geo http://drgeo.eu > > > -- Bernat Romagosa.

April 7, 2014

Re: [Pharo-users] free learnig book

by Jean Baptiste Arnaud

Steph keeps some treasure: http://stephane.ducasse.free.fr/FreeBooks.html On 07 Apr 2014, at 08:43, Roelof Wobben <r.wobben(a)home.nl> wrote: > Hello, > > I wonder if there is a free book with a lot of exercises so I can practice and learn a lot about Smalltalk. > > Roelof > >

April 7, 2014