- Pharo-users - lists.pharo.org

Re: [Pharo-users] SDL2 and fork

by Sean P. DeNigris

EstebanLM wrote > I just committed my prototype/experiment for windows with OSWindow, SDL2 > and Athens. I got an error because my VM (via Launcher 0.2.4 - I can't upgrade due to a previously-reported error) doesn't have SDL2. I guess Launcher is using stable from 9/2014. How stable is VM latest? If I inject it into my current Launcher, will it be okay for general use? ----- Cheers, Sean -- View this message in context: http://forum.world.st/SDL2-and-fork-tp4818623p4820732.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 21, 2015

Re: [Pharo-users] SDL2 and fork

by Nicolai Hess

2015-04-20 14:20 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > I just committed my prototype/experiment for windows with OSWindow, SDL2 > and Athens. > to check them: > > Gofer it > smalltalkhubUser: 'Pharo' project: 'OSWindow'; > package: 'OSWindow-Core'; > package: 'OSWindow-SDL2'; > package: 'OSWindow-SDL2-Canvases'; > load. > > and check the examples at: > > OSSDLAthensWindow > OSSDLMorphWindow > Great! Although the VM crashes sometimes (after closing the SDL-Window) And I know found out why the window is partly out of the screen (on Windows7, don't think this happens on linux/mac): If you open a SDL window with SDL createWindow: title x: 0 y: 0 .... The window opens at 0@0 but this is the upper left corner of the window rectangle *without* window decoration. If you open the window with SDL createWindow: title x: SDL_WINDOWPOS_UNDEFINED .... -> the full window is visible nicolai > > cheers, > Esteban > > On 20 Apr 2015, at 13:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-04-20 13:13 GMT+02:00 <merwanouddane(a)gmail.com>: > >> Hello, >> >> We donât lose all keystroke events, but they are replaced by keydown >> events. >> > > Yes, KeyDown/KeyUp are working and instead of a keystroke event another > keydown is sent. > This is strange, I don't know exactly how the SDL event processing can > influence the main window events. > Maybe this has something to do how we look for new events in the > SDL2DisplayPlugin. > For me the call to SDL_PumpEvents looks unnecessary, maybe this is the > cause? > > > nicolai > > > >> >> Merwan >> >> >> *De :* Nicolai Hess >> *EnvoyÃ© :* âlundiâ â20â âavrilâ â2015 â09â:â36 >> *Ã :* Any question about pharo is welcome; Esteban Lorenzano >> >> >> >> 2015-04-20 8:38 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: >> >>> Hello, >>> >>> Thanks for your answers ! I have multiple remarks here : >>> >>> 1) I know that SDL2 should not be used "as is" in Pharo and I should use >>> OSWindow instead, that's why I won't use SDL2 directly anymore. >>> >> >> On windows there is currently an issue if you use OSWindow instead of >> directly use SDL. >> If you create a window with OSWindow, (like in the SDL2Example>>osWindow) >> you will loose all "keystroke" events in the main pharo window. >> I don't know yet why this happens. >> >> nicolai >> > > >

April 20, 2015

Re: [Pharo-users] SDL2 and fork

by Nicolai Hess

2015-04-20 16:56 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > I see the point, but SDL seems to be pretty stable isnât it? > Only two versions are reported on their website (1.2 and 2.0). Maybe it > would be better to directly talk to SDL. Just wondering... > > Alexandre > If you use SDL directly -> you will have to create your own event loop (and other stuff) If you use the OSWindow layer -> you will get a nice API that is already integrated with the main window / main window eventloop.

April 20, 2015

Re: [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages

by Laurent

Fixed. Laurent Le lun. 20 avril 2015 Ã 14:25, Markus Schlager <m.slg(a)gmx.de> a Ã©crit : > Hi Laurent, > > There's again a 404 file not found with > PharoLauncher-user-stable-2015.04.18.zip. > > Markus > > ------------------------------------------------ > > ==> Erstelle Paket: pharo-launcher 4.0-1 (Mo 20. Apr 14:19:39 CEST > 2015) > ==> PrÃ¼fe Laufzeit-AbhÃ¤ngigkeiten... > ==> PrÃ¼fe Buildtime-AbhÃ¤ngigkeiten... > ==> Empfange Quellen... > -> Lade icon-lighthouse-128x128.png herunter... > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total Spent > Left Speed > 100 8219 100 8219 0 0 32276 0 --:--:-- --:--:-- > --:--:-- 32231 > -> Lade PharoLauncher-user-stable-2015.04.18.zip herunter... > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total Spent > Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > --:--:-- 0curl: (22) The requested URL returned error: 404 Not Found > ==> FEHLER: Fehler beim Download von > PharoLauncher-user-stable-2015.04.18.zip > Breche ab...

April 20, 2015

Re: [Pharo-users] SDL2 and fork

by Nicolai Hess

2015-04-20 13:55 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-04-20 13:13 GMT+02:00 <merwanouddane(a)gmail.com>: > >> Hello, >> >> We donât lose all keystroke events, but they are replaced by keydown >> events. >> > > Yes, KeyDown/KeyUp are working and instead of a keystroke event another > keydown is sent. > This is strange, I don't know exactly how the SDL event processing can > influence the main window events. > Maybe this has something to do how we look for new events in the > SDL2DisplayPlugin. > For me the call to SDL_PumpEvents looks unnecessary, maybe this is the > cause? > > So, I removed the call to SDL_PumpEvents, and now keystroke events are still working in the main window after opening an OSWindow. @Esteban Can you check if this is working on other platforms too. > > nicolai > > > >> >> Merwan >> >> >> *De :* Nicolai Hess >> *EnvoyÃ© :* âlundiâ â20â âavrilâ â2015 â09â:â36 >> *Ã :* Any question about pharo is welcome; Esteban Lorenzano >> >> >> >> 2015-04-20 8:38 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: >> >>> Hello, >>> >>> Thanks for your answers ! I have multiple remarks here : >>> >>> 1) I know that SDL2 should not be used "as is" in Pharo and I should use >>> OSWindow instead, that's why I won't use SDL2 directly anymore. >>> >> >> On windows there is currently an issue if you use OSWindow instead of >> directly use SDL. >> If you create a window with OSWindow, (like in the SDL2Example>>osWindow) >> you will loose all "keystroke" events in the main pharo window. >> I don't know yet why this happens. >> >> nicolai >> > >

April 20, 2015

Re: [Pharo-users] SDL2 and fork

by Alexandre Bergel

I see the point, but SDL seems to be pretty stable isnât it? Only two versions are reported on their website (1.2 and 2.0). Maybe it would be better to directly talk to SDL. Just wondering... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Apr 20, 2015, at 4:18 AM, stepharo <stepharo(a)free.fr> wrote: > > Alex > Just to make sure we are clear on this: > pay attention NOBODY should directly use SDL. > OSWindow is the API, SDL is a BACKEND. > > Athens is the API, CAIRO a BACKEND > > Stef > > Le 20/4/15 02:57, Alexandre Bergel a Ã©crit : >> Hi Matthieu, >> >> This is important: Binding SDL with Pharo will help Roassal to get better. >> Please, let us know how it goes >> >> Alexandre >> >> >>> On Apr 9, 2015, at 12:54 PM, Matthieu Lacaton <matthieu.lacaton(a)gmail.com> wrote: >>> >>> Hello everyone, >>> >>> I tried to use the SDL2 binding to Pharo to create a very basic 2D application (just some sprites and events) and it worked great. >>> The issue I have is that when I start my application, as long as I have an active SDL window, I can't use my Pharo image anymore (it freezes). >>> To solve this problem I tried opening my application in another thread by doing so : >>> [ (MyApplication new) start. ] forkAt: Processor lowestPriority. (If I don't chose a low priority it changes nothing) >>> >>> The problem is that even if it kind of works, it is really slow and it slows my whole operating system as well (I use windows XP) >>> >>> How can I fork more efficiently or open a SDL window without losing control of my image ? >>> >>> Thanks, >>> >>> Matthieu > >

April 20, 2015

Re: [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages

by Markus Schlager

Hi Laurent, There's again a 404 file not found with PharoLauncher-user-stable-2015.04.18.zip. Markus ------------------------------------------------ ==> Erstelle Paket: pharo-launcher 4.0-1 (Mo 20. Apr 14:19:39 CEST 2015) ==> PrÃ¼fe Laufzeit-AbhÃ¤ngigkeiten... ==> PrÃ¼fe Buildtime-AbhÃ¤ngigkeiten... ==> Empfange Quellen... -> Lade icon-lighthouse-128x128.png herunter... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 8219 100 8219 0 0 32276 0 --:--:-- --:--:-- --:--:-- 32231 -> Lade PharoLauncher-user-stable-2015.04.18.zip herunter... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (22) The requested URL returned error: 404 Not Found ==> FEHLER: Fehler beim Download von PharoLauncher-user-stable-2015.04.18.zip Breche ab...

April 20, 2015

Re: [Pharo-users] SDL2 and fork

by Esteban Lorenzano

Hi, I just committed my prototype/experiment for windows with OSWindow, SDL2 and Athens. to check them: Gofer it smalltalkhubUser: 'Pharo' project: 'OSWindow'; package: 'OSWindow-Core'; package: 'OSWindow-SDL2'; package: 'OSWindow-SDL2-Canvases'; load. and check the examples at: OSSDLAthensWindow OSSDLMorphWindow cheers, Esteban > On 20 Apr 2015, at 13:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-04-20 13:13 GMT+02:00 <merwanouddane(a)gmail.com <mailto:merwanouddane@gmail.com>>: > Hello, > > We donât lose all keystroke events, but they are replaced by keydown events. > > Yes, KeyDown/KeyUp are working and instead of a keystroke event another keydown is sent. > This is strange, I don't know exactly how the SDL event processing can influence the main window events. > Maybe this has something to do how we look for new events in the SDL2DisplayPlugin. > For me the call to SDL_PumpEvents looks unnecessary, maybe this is the cause? > > > nicolai > > > > Merwan > > > De : Nicolai Hess > EnvoyÃ© : âlundiâ â20â âavrilâ â2015 â09â:â36 > Ã : Any question about pharo is welcome; Esteban Lorenzano > > > > 2015-04-20 8:38 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com <mailto:matthieu.lacaton@gmail.com>>: > Hello, > > Thanks for your answers ! I have multiple remarks here : > > 1) I know that SDL2 should not be used "as is" in Pharo and I should use OSWindow instead, that's why I won't use SDL2 directly anymore. > > On windows there is currently an issue if you use OSWindow instead of directly use SDL. > If you create a window with OSWindow, (like in the SDL2Example>>osWindow) you will loose all "keystroke" events in the main pharo window. > I don't know yet why this happens. > > nicolai >

April 20, 2015

Re: [Pharo-users] Pillar used directly from Pharo

by Damien Cassou

Hi Jan, the following complements Cyril's answers. You can have a look at all the unit-tests, they do a lot of things like what you want. Jan ValÃ¡Å¡ek <valasja7(a)fit.cvut.cz> writes: > header := pillarHeaderObject new. //creating pillar objects directly header := PRHeader new level: 2; add: (PRText content: 'foo'); yourself. > aPillarDocument add: header. //adding them to the whole document document := PRDocument new. document add: header. > aPillarDocument exportToLatex. //export the document to only export the body of the document: PRLaTeXWriter write: document > or I can just write the text in the pillar notation to "myTextObject" > and then call something like-> > ------- > pillarParseAndExportToLatex: myTextObject. document := PRDocumentParser parse: '!!foo'. PRLaTeXWriter write: document. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 20, 2015

Re: [Pharo-users] SDL2 and fork

by Nicolai Hess

2015-04-20 13:13 GMT+02:00 <merwanouddane(a)gmail.com>: > Hello, > > We donât lose all keystroke events, but they are replaced by keydown > events. > Yes, KeyDown/KeyUp are working and instead of a keystroke event another keydown is sent. This is strange, I don't know exactly how the SDL event processing can influence the main window events. Maybe this has something to do how we look for new events in the SDL2DisplayPlugin. For me the call to SDL_PumpEvents looks unnecessary, maybe this is the cause? nicolai > > Merwan > > > *De :* Nicolai Hess > *EnvoyÃ© :* âlundiâ â20â âavrilâ â2015 â09â:â36 > *Ã :* Any question about pharo is welcome; Esteban Lorenzano > > > > 2015-04-20 8:38 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: > >> Hello, >> >> Thanks for your answers ! I have multiple remarks here : >> >> 1) I know that SDL2 should not be used "as is" in Pharo and I should use >> OSWindow instead, that's why I won't use SDL2 directly anymore. >> > > On windows there is currently an issue if you use OSWindow instead of > directly use SDL. > If you create a window with OSWindow, (like in the SDL2Example>>osWindow) > you will loose all "keystroke" events in the main pharo window. > I don't know yet why this happens. > > nicolai >

April 20, 2015