- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] OsWindow tests

by Eric Le Pors

Hello Ronie, Thank you ! Events are "back" in the main Pharo Window ! But now, when i open and close brick window examples, a debugger opens because BlOsWindow try to call destroy method on OSSDL2Windowhandle. But OSSDL2Driver class >> current returns an instance of OSNullWindowDriver and this class does not have unregisterWindowWithId: method. this method is in OSSDL2Driver In order to be able to close SDL window i added a temporary fix : OSNullWindowDriver >> unregisterWindowWithId: OSWindowDriver current unregisterWindowWithId: windowId. It is not a good and long term solution... i know ! The VM is also unstable after openning SDL window... Thank you for you help. Can i help to solve OsWindow/SDL2 problems ? Eric. -- View this message in context: http://forum.world.st/OsWindow-tests-tp4918041p4918243.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 6, 2016

Re: [Pharo-dev] [ANN] New "DarkMetalTheme" for Pharo

by Norbert Hartl

You should call it Insomnia! Norbert > Am 06.10.2016 um 10:36 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, > > I took some time to extract the ==MUDDarkTheme== I made for my *MUDClient>https://github.com/estebanlm/MUDClient* <https://github.com/estebanlm/MUDClient*>, > repackage it, rebrand it and make it available for everybody. > > So behold, the new DarkMetalTheme ! > > https://github.com/estebanlm/themes <https://github.com/estebanlm/themes> > > <DarkMetalPharo.png>

Oct. 6, 2016

[ANN] New "DarkMetalTheme" for Pharo

by Esteban Lorenzano

Hi, I took some time to extract the ==MUDDarkTheme== I made for my *MUDClient>https://github.com/estebanlm/MUDClient*, repackage it, rebrand it and make it available for everybody. So behold, the new DarkMetalTheme ! https://github.com/estebanlm/themes <https://github.com/estebanlm/themes>

Oct. 6, 2016

Re: [Pharo-dev] Extending Pharo Debugger

by Matteo Marra

Hello Stephan, In the work for my thesis, I'm building a debugger for big data applications, that when a bug happens doesn't stop the computation but proceeds evaluating the next data. This opens a series of debuggers in separate threads, that are shown one by one. I added a button that allows me to restart and automatically proceed all the waiting debuggers from a certain point of the stack (assuming that the stack has the same "shape"), so basically after I fix a bug in the first debugger I can say to the others: ok, the bug is solved, restart yorself and proceed. The thing seems more or less to work, except some details that I still have to implement. Matteo 2016-10-06 7:40 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi matteo > > What do you want to add? > > Stef > > > Le 4/10/16 Ã 16:10, Matteo Marra a Ã©crit : > > Hello, >> >> I'm working on the Pharo debugger, and I wanted to add a button with new >> functionality just besides the buttons "Proceed" "restart" ... >> >> Is there an easy way to do it? Which is the class that I have to >> Modify/Extend in order to do that? >> >> I tried to look around the methods and I found where DebugSession is >> created, but I didn't see any clear reference to the UI or to how is >> constructed in it. >> >> Thank you in advance, >> Matteo >> > > >

Oct. 6, 2016

Re: [Pharo-dev] Extending Pharo Debugger

by stepharo

Hi matteo What do you want to add? Stef Le 4/10/16 Ã 16:10, Matteo Marra a Ã©crit : > Hello, > > I'm working on the Pharo debugger, and I wanted to add a button with > new functionality just besides the buttons "Proceed" "restart" ... > > Is there an easy way to do it? Which is the class that I have to > Modify/Extend in order to do that? > > I tried to look around the methods and I found where DebugSession is > created, but I didn't see any clear reference to the UI or to how is > constructed in it. > > Thank you in advance, > Matteo

Oct. 6, 2016

[off topic] Working overseas

by Ben Coman

I hope this is not out of line... Until recently I wasn't paying attention to employment opportunities on this list, but I've realised my current job is not challenging me and I'm starting to consider other options, including working overseas. So as well as trawling back through past mails, I thought I'd just put a shout out for opportunities. Ideally I could blend my interest and experience in electrical systems and Pharo, but all things considered. To keep the list noise down, please respond off-list. cheers -ben https://www.linkedin.com/in/bencoman

Oct. 5, 2016

Re: [Pharo-dev] OsWindow tests

by Ronie Salgado

Hello Eric, I am checking some problems with OSWindow in windows, and this is a problem with the SDL2DisplayPlugin in Windows. Until we fix the VM plugin in Windows, the current workaround is to just disable the plugin in Windows. For disabling this plugin, you have to the change the following method to always return false (by removing the primitive): OSSDL2Driver class >> hasPlugin ^ false When the plugin is not available, the OSWindow SDL2 driver will spawn a Pharo process for polling the SDL2 queue. The plugin installs a hooks in the VM heartbeat place, which checks if there are available SDL2 events. If there are, it signals a Pharo semaphore to wake up a Pharo process the consumes all of the events avaiable in the queue. Best regards, Ronie 2016-10-04 13:18 GMT-03:00 Eric Le Pors <eric.lepors(a)fr.thalesgroup.com>: > Hello, > > I try to execute OsWindow examples with Pharo 5 VM and Pharo-50761 or > Pharo-60251 images on Windows 7 > > Every time you open a SDL window, interact with Pharo main window is no > longer possible... > > When i execute : > SDL2AthensDrawingExample new open > > a "New window" is openned and you can draw something in the window, but... > the window does not close and the pharo main window is not clickable > (however some incorrect keystrokes events are transmitted to the pharo main > window) > > When i use the same images on Linux... no bug. > Is there a solution to this issue on Microsoft Windows ? > > Thank you in advance, > Eric > > > > -- > View this message in context: http://forum.world.st/ > OsWindow-tests-tp4918041.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Oct. 5, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60254 Home: https://github.com/pharo-project/pharo-core

Oct. 5, 2016

[pharo-project/pharo-core] bcd79c: 60254

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: bcd79c42eceb6ea1ca9ae4f30846d404a4ce7fe5 https://github.com/pharo-project/pharo-core/commit/bcd79c42eceb6ea1ca9ae4f3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-05 (Wed, 05 Oct 2016) Changed paths: M Morphic-Widgets-Tabs.package/TabBar.class/instance/protocol/selectLastTab.st M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/lookup/lookupVar_inContext_.st A OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/lookup/outerScopeLookupVar_inContext_.st A OpalCompiler-Core.package/OCBlockScope.class/instance/lookup/nextLexicalContextOf_.st A OpalCompiler-Core.package/OCBlockScope.class/instance/lookup/outerScopeLookupVar_inContext_.st R OpalCompiler-Core.package/OCOptimizedBlockScope.class/instance/accessing/lookupVar_inContext_.st A OpalCompiler-Core.package/OCOptimizedBlockScope.class/instance/lookup/nextLexicalContextOf_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60253.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60254.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60253.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60254.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60254 19178 TabBar selectLastTab is not working https://pharo.fogbugz.com/f/cases/19178 19180 Var lookup broken https://pharo.fogbugz.com/f/cases/19180 http://files.pharo.org/image/60/60254.zip

Oct. 5, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60253 Home: https://github.com/pharo-project/pharo-core

Oct. 5, 2016