Tx ronie. On Thu, Oct 19, 2017 at 7:48 PM, Ronie Salgado <roniesalg@gmail.com> wrote:
Hi Clément,
Last night I was checking again the VM. If I remove the hack in the ioProcessEvents, I can receive the events with SDL2, but as soon as I type on the main Pharo window I get a crash in an objective-c message send by SDL2. I still need to debug SDL2 itself with debugging symbols.
I am not sure whether I will be able to fix the problem without modifying SDL2. In the worst case escenario, we will have to move to the minheadless vm.
Best regards, Ronie
2017-10-18 4:49 GMT-03:00 Clément Bera <bera.clement@gmail.com>:
Hi again,
I made many more attempts since those mails: I wrote this page showing how to deploy my game in native app at 50fps on Linux, Mac and Windows.
Currently I deploy with: Ubuntu 64 bits: Pharo61-64 (Pharo61-32 also works with the right lib installed) Mac OS X 64 bits: Pharo5Alpha-32 (On Pharo61 the keyboard events do not work correctly) Windows 64 bits: Pharo61-32 (There are bugs with the SDL2 window, the top bar is not displayed, but the game work. Reportedly it would work better with Pharo61-64 but the default Pharo64 VM on Windows still does not feature the JIT, once the default VM does, I will update).
My goal is to deploy on all platforms with Pharo61-64 (and later Pharo7-64).
I wrote this mail since maybe you are interested in knowing that with Pharo5Alpha-32 and the set-up described on the page of my game the keyboard events work fine on Mac, so it may be possible to write a fix for Pharo61/Pharo7 based on that.
Best,
On Fri, Sep 29, 2017 at 8:56 PM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Tx ronie!
On Fri, Sep 29, 2017 at 1:42 PM, Ronie Salgado <roniesalg@gmail.com> wrote:
Hi Clément,
I just checked on my machine and it is also not working. It seems to be a VM bug. It will take me some time to debug it. I have some suspicious on ioProcessEvents .
Best regards, Ronie
2017-09-29 10:39 GMT+02:00 Clément Bera <bera.clement@gmail.com>:
On Fri, Sep 29, 2017 at 10:29 AM, Hilaire <hilaire@drgeo.eu> wrote:
Hi,
IMHO, it will make Pharo much more robust if core libraries as sdl, cairo, etc will be shipped with each plateform dependent virtual machine and the image modified accordingly to use these core libraries.
That's how it is now but some of it is not working (Here SDL events and there are 2 SDL2 libs by default).
I think we should still have a minimal image starting with a minimal UI without using FFI/SDL/Cairo or whatever lib. Else when we start on a platform where one of this thing is not properly supported yet (See the problem on the raspberry pie with some Pharo alpha version) it is too hard to understand what is going on.
The delivery of Pharo application to end users is an issue because of these recuring problem.
Honestly I was trying to write a doc on how to deploy Pharo client app with SDL2 and Cairo but I have only a version working in Pharo 4 on Mac and Linux, while in theory I could have it working in Windows/Mac/Linux in the latest Pharo.
Hilaire
Le 28/09/2017 à 15:02, Clément Bera a écrit :
Btw for some reason in the one-click version of Pharo 32 bits on Mac there is 2 SDL plugins (libSDL2-2.0.0 and libSDL2), which leads to conflicts (the VM use randomly one lib or the other). I randomly chose one that I use and deleted the other one, do you have advises on which one I should prefer ? Maybe the events are working only with the other one ?
-- Dr. Geo http://drgeo.eu
-- Clément Béra Pharo consortium engineer https://clementbera.wordpress.com/ Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq