May 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub May 29, 2015

May 29, 2015

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

1 0

[pharo-project/pharo-core]
by GitHub May 29, 2015

May 29, 2015

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

1 0

[pharo-project/pharo-core] 2e9129: 50073
by GitHub May 29, 2015

May 29, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 2e9129f2ce3dc4e686385980a3f0841e56a6ea30 https://github.com/pharo-project/pharo-core/commit/2e9129f2ce3dc4e686385980… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-29 (Fri, 29 May 2015) Changed paths: A AST-Core.package/RBBlockNode.class/instance/initialization/initialize.st A EmbeddedFreeType.package/LucidaGrandeRegular.class/README.md A EmbeddedFreeType.package/LucidaGrandeRegular.class/class/accessing/fontContents.st A EmbeddedFreeType.package/LucidaGrandeRegular.class/class/accessing/fontDirectory.st A EmbeddedFreeType.package/LucidaGrandeRegular.class/class/accessing/fontReference.st A EmbeddedFreeType.package/LucidaGrandeRegular.class/class/accessing/installFontsIn_.st A EmbeddedFreeType.package/LucidaGrandeRegular.class/class/accessing/originalFileName.st A EmbeddedFreeType.package/LucidaGrandeRegular.class/class/class initialization/initialize.st A EmbeddedFreeType.package/LucidaGrandeRegular.class/definition.st M Keymapping-Tools-Spec.package/KMDescription.class/instance/initialization/initializeWidgets.st M Morphic-Base.package/ToggleMenuItemMorph.class/instance/drawing-private/drawKeyTextOn_.st M Morphic-Base.package/ToggleMenuItemMorph.class/instance/layout/minWidth.st A Morphic-Base.package/ToggleMenuItemMorph.class/instance/private/keyTextExpanded.st A Morphic-Base.package/ToggleMenuItemShortcut.class/README.md A Morphic-Base.package/ToggleMenuItemShortcut.class/class/instance creation/new.st A Morphic-Base.package/ToggleMenuItemShortcut.class/class/instance creation/owner_keyText_.st A Morphic-Base.package/ToggleMenuItemShortcut.class/class/private/expandCondensedStyle_.st A Morphic-Base.package/ToggleMenuItemShortcut.class/class/private/expandFullStyle_.st A Morphic-Base.package/ToggleMenuItemShortcut.class/class/private/expand_.st A Morphic-Base.package/ToggleMenuItemShortcut.class/class/private/keyTextShortcuts.st A Morphic-Base.package/ToggleMenuItemShortcut.class/class/private/shortcutClass.st A Morphic-Base.package/ToggleMenuItemShortcut.class/definition.st A Morphic-Base.package/ToggleMenuItemShortcut.class/instance/accessing/keyText.st A Morphic-Base.package/ToggleMenuItemShortcut.class/instance/accessing/owner.st A Morphic-Base.package/ToggleMenuItemShortcut.class/instance/drawing/drawOn_.st A Morphic-Base.package/ToggleMenuItemShortcut.class/instance/initialization/initializeOwner_keyText_.st A Morphic-Base.package/ToggleMenuItemShortcut.class/instance/private/boundsForKeyText_font_.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/README.md A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/class/accessing/symbolFont.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/class/accessing/symbolTable.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/class/accessing/symbolTableAt_ifAbsent_.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/class/private/createSymbolFont.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/class/private/createSymbolTable.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/class/testing/canBeUsed.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/definition.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/instance/drawing/drawOn_.st A Morphic-Base.package/ToggleMenuItemShortcutWithText.class/README.md A Morphic-Base.package/ToggleMenuItemShortcutWithText.class/definition.st A Morphic-Base.package/ToggleMenuItemShortcutWithText.class/instance/drawing/drawOn_.st M Morphic-Core.package/WorldState.class/class/world menu items/mostUsedToolsOn_.st M Morphic-Core.package/WorldState.class/class/world menu items/quitItemsOn_.st M NautilusRefactoring.package/extension/TClassDescription/instance/sourceCodeRefactoringMenu_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50072.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50073.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50072.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50073.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Platforms.package/MacOSPlatform.class/instance/accessing/menuShortcutString.st A System-Platforms.package/OSPlatform.class/instance/accessing/menuShortcutString.st A System-Platforms.package/UnixPlatform.class/instance/accessing/menuShortcutString.st A System-Platforms.package/Win32Platform.class/instance/accessing/menuShortcutString.st Log Message: ----------- 50073 15626 SHRBStyle dnu for incomplete block nodes https://pharo.fogbugz.com/f/cases/15626 15628 Remove ComposableModel>>#instantiateModels:s senders in Keymapping-Tools-Spec https://pharo.fogbugz.com/f/cases/15628 15621 show complete menu modifiers https://pharo.fogbugz.com/f/cases/15621 http://files.pharo.org/image/50/50073.zip

1 0

OSWindow + X Server problem ?
by Matthieu Lacaton May 29, 2015

May 29, 2015

Hello everyone, I think I found a bug with OSWindow when using the X11 server : Everytime you open an OSWindow (it doesn't matter what you do with it, you can even close it you just need to have opened an OSWindow once) when you want to quit your image you get a segmentation fault on the "quitPrimitive". Or sometimes you can have a error: "double free or corruption (out)". To reproduce it you just have to open an empty OSWindow with "OSWindow new." then close it and close your image. It is not a big problem because the image is still saved and closed and nothing bad happens when you reopen it but it is just frustrating to have a segfault everytime you close your image. I've been able to get a C stack backtrace : /home/matthieu/Documents/Pharo5/pharo-vm/pharo[0x80a3352] > /home/matthieu/Documents/Pharo5/pharo-vm/pharo[0x80a36a3] > [0xf772a410] > /lib/i386-linux-gnu/libpthread.so.0(__pthread_mutex_lock+0x16)[0xf76a5036] > /usr/lib/i386-linux-gnu/libX11.so.6(+0x23f0d)[0xf710df0d] > /usr/lib/i386-linux-gnu/libX11.so.6(XrmDestroyDatabase+0x2d)[0xf712888d] > > /usr/lib/i386-linux-gnu/libX11.so.6(_XFreeDisplayStructure+0x473)[0xf710fbf3] > /usr/lib/i386-linux-gnu/libX11.so.6(XCloseDisplay+0xd9)[0xf70fd0f9] > > /home/matthieu/Documents/Pharo5/pharo-vm/vm-display-X11(disconnectXDisplay+0xcf)[0xf771dd3f] > > /home/matthieu/Documents/Pharo5/pharo-vm/vm-display-X11(+0x11d74)[0xf771dd74] > > /home/matthieu/Documents/Pharo5/pharo-vm/pharo(ioExitWithErrorCode+0x20)[0x80a3990] > /home/matthieu/Documents/Pharo5/pharo-vm/pharo[0x807551f] > /home/matthieu/Documents/Pharo5/pharo-vm/pharo(interpret+0x234c)[0x80973cc] > > /home/matthieu/Documents/Pharo5/pharo-vm/pharo(enterSmalltalkExecutiveImplementation+0x59)[0x809a5c9] > /home/matthieu/Documents/Pharo5/pharo-vm/pharo(interpret+0x1ee)[0x809526e] > /home/matthieu/Documents/Pharo5/pharo-vm/pharo(main+0x2b2)[0x805ba82] > /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xf7507a83] > /home/matthieu/Documents/Pharo5/pharo-vm/pharo[0x805bda1] > By digging up a bit I think I may have a hint about why this happens : When you initialize the X11 server you need to make a choice about calling XInitThreads() or not. Here is a part of the man of XInitThreads() : *The XInitThreads function initializes Xlib support for concurrent threads. > This function must be the first Xlib function a multi-threaded program > calls, and it must complete before any other Xlib call is made. This > function returns a nonzero status if initialization was successful; > otherwise, it returns zero. On systems that do not support threads, this > function always returns zero. * > > *It is only necessary to call this function if multiple threads might use > Xlib concurrently. If all calls to Xlib functions are protected by some > other access mechanism (for example, a mutual exclusion lock in a toolkit > or through explicit client programming), Xlib thread initialization is not > required. It is recommended that single-threaded programs not call this > function.* > I've searched a bit in the Pharo VM code and I have not found any call to XInitThreads() and it seems normal because it only opens one window in a single thread. Now the problem is that SDL makes a call to XinitThreads() in the file "SDL_x11video.c" in the function : "X11_CreateDevice(int devindex)" because SDL needs it. This means basically that the XinitThreads() function is called from the same process than the VM one after the first Xlib calls have been made. So to sum up, the VM initializes the X server in single thread mode. Then SDL changes it to multi thread mode so the X server probably creates a mutex to handle everything. Now when we try to close the VM the main window that was opened in single thread mode makes the mutex crash and it results in a segfault. If I am right it means that adding a call to XInitThreads() in the initialization of the X11 server in the VM code could maybe solve this problem. What do you think about it ? Cheers, Matthieu

3 4

Re: [Pharo-dev] [Pharo-users] [Pre-ANN][Job] We are looking for a "Engineer R&D"
by Marcus Denker May 29, 2015

May 29, 2015

> On 29 May 2015, at 10:28, Martin BÃ¤hr <mbaehr(a)email.archlab.tuwien.ac.at> wrote: > > Excerpts from Marcus Denker's message of 2015-05-29 10:17:24 +0200: >> Hi, >> >> Good news: the job is not constraint by the â2 years after universityâ condition, but instead it is a >> so called âExperienced Engineerâ position: >> >> http://www.inria.fr/en/institute/recruitment/offers/find-a-position?nPostin… > > that link does not work for me, is it this one? > http://www.inria.fr/en/institute/recruitment/offers/find-a-position/%28view… > Yes! Marcus

1 0

[Pre-ANN][Job] We are looking for a "Engineer R&D"
by Marcus Denker May 29, 2015

May 29, 2015

Hi, We will put the official announce online later this weekâ¦ we are looking to fill a a âyoung engineer positionâ. This is for recent graduates who finished their degree 2013/2014/2015. The topic is to work for 2 years on improving âremoteâ debugging for cases like server deployment, typical cloud scenarios and when using embedded Pharo images (e.g. for robotics). If you are interested (or know someone who might), please contact me. (official announcement will be online later this week). Marcus

1 2

does recent changes broke playground with dark theme?
by Esteban Lorenzano May 29, 2015

May 29, 2015

Iâm having some forced black fonts there. Can you confirm it? Esteban

2 1

OSWindow and OSWindowDriver
by Matthieu Lacaton May 29, 2015

May 29, 2015

Hello everyone, I'm writing here because I would like some insight about the OSWindowDriver. As you may know, the OSWindowDriver (via OSSDL2Driver) is responsible for many things in OSWindow such as setting up the event loop, creating the SDL window, etc. My first question is : How are you supposed to access the driver ? Currently you can do a "OSWindowDriver current" and it should return you the "most suited driver". It is the way the driver is picked if you don't specify a preferable driver in the OSWindow attributes. I see two problems with this : - If you don't have the SDL plugin it returns you an OSWindowNullDriver and you cannot do anything with it even if you have the SDL library. - Let's say that SDL does not meet my requirements and I create another binding to another library. I now have the possibility to use OSWindow with two different back-ends. How does the OSWindowDriver discriminates between the twos ? Now if I want to specify a driver I can do it by setting "preferableDriver" in the OSWindowAttributes. But if I want an OSSDL2Driver, the only way I see for the moment is to call "OSSDL2Driver new". But by doing so I am creating an instance of the driver per window created whereas with "OSWindowDriver current" I am only using one instance of the driver for all windows. I think something is not coherent here. So should all specific drivers be singletons ? Should they all implement their own version of the "current" method returning the only instance of them ? I have another remark too : The driver needs to keep a map of all active windows to be able to dispatch events to the correct one. But when a window is destroyed, it needs to be removed from the map so there is no mess in the events and so the garbage collector can free it. Currently the window map is a class variable of OSSDL2Driver. But I think the map should be common to all drivers because they would probably all need one. So I'd like to move the WindowMap class variable to the "OSWindowDriver" class directly

2 2

OSWindow and OSWindowDriver questions
by Matthieu Lacaton May 29, 2015

May 29, 2015

Hello everyone, I'm writing here because I would like some insight about the OSWindowDriver. As you may know, the OSWindowDriver (via OSSDL2Driver) is responsible for many things in OSWindow such as setting up the event loop, creating the SDL window, etc. My first question is : How are you supposed to access the driver ? Currently you can do a "OSWindowDriver current" and it should return you the "most suited driver". It is the way the driver is picked if you don't specify a preferable driver in the OSWindow attributes. I see two problems with this : - If you don't have the SDL plugin it returns you an OSWindowNullDriver and you cannot do anything with it even if you have the SDL library. - Let's say that SDL does not meet my requirements and I create another binding to another library. I now have the possibility to use OSWindow with two different back-ends. How does the OSWindowDriver discriminates between the twos ? Now if I want to specify a driver I can do it by setting "preferableDriver" in the OSWindowAttributes. But if I want an OSSDL2Driver, the only way I see for the moment is to call "OSSDL2Driver new". But by doing so I am creating an instance of the driver per window created whereas with "OSWindowDriver current" I am only using one instance of the driver for all windows. I think something is not coherent here. So should all specific drivers be singletons ? Should they all implement their own version of the "current" method returning the only instance of them ? I have another remark too : The driver needs to keep a map of all active windows to be able to dispatch events to the correct one. But when a window is destroyed, it needs to be removed from the map so there is no mess in the events and so the garbage collector can free it. Currently the window map is a class variable of OSSDL2Driver. But I think the map should be common to all drivers because they would probably all need one. So I'd like to move the WindowMap class variable to the "OSWindowDriver" class directly with a class method to remove the selected window from it. That way when a window is destroyed, we just have to call this class method and it is easy. What do you think about it ? I hope I was clear enough for you to understand. I would just like to know the best way to "fix" these things. And If I am totally wrong and there is a precise way to deal with this, please let me know :) Thanks a lot, Matthieu

2 1

Beyond RPackages: RPackageTag and DynamicGroup
by Sergio Fedi May 28, 2015

May 28, 2015

Hi list! As we are adding comments to Packages in Pharo, we stumbled upon the fact that there are other creatures present in the package list. These are: RPackageTag, which models the tags under the package DynamicGroup, which model the dynamic categories of LastModifiedClasses, MostViewedClasses and Work Objects of these classes WILL have to understand the accessor #comment 1 - *How do we want RPackageTag and DynamicGroup to handle #comment and #comment: ?* 2 - *Are there any other classes present in that list we are not aware of?* Some options we can consider: a - Hardcode in an generic answer to #comment, do nothing on #comment, leave them be for now b - Have the object behave as a RPackage, it can have a persistent comment. In this case, where do we save that data? Since the Package Comments case is taking so long, and to keep the scope of the case in check, we are incline to handle both classes with option a. But we wanted to check with the list first, just in case. Ok, now let's hear you feedback.

6 7