March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How to listen for windows messages?

by Eliot Miranda

Hi Phil, Hi All, On Tue, Feb 28, 2017 at 4:29 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Hi, > > Pharo is itself a Windows application (under Windows of course). > > So Window event loop is picking up the events and transforming them into > Pharo events. > Right, but this is *not good enough* :-) It is a fundamentally different architecture. The processing of Windows events in the Windows VM transforms *event callbacks* into an *event queue*. This is fine for events such as mouse clicks, keyboard presses, etc. But it is fundamentally broken for events such as those that ask an application to quit because the OS is about to exit, or events that try to obtain mouse feedback while moving a native window, etc, etc. So one either needs to extend the VM event queue so that one can install callbacks for certain kinds of events still providing a cross-platform interface), or, as Vassili did for Newspeak native windows (which was fully working in 2008, with the ability to switch a window between emulated (Morphic) and native at will or on image startup), interface to the native Windows event pump via callbacks. > You can check this in https://github.com/pharo-project/pharo-vm > > in opensmalltalk-vm\platforms\win32\vm\sqWin32Window.c > > https://github.com/pharo-project/pharo-vm/blob/master/ > opensmalltalk-vm/platforms/win32/vm/sqWin32Window.c > > Like L235... > > LRESULT CALLBACK MainWndProcW(HWND hwnd, > UINT message, > WPARAM wParam, > LPARAM lParam) > > You'll see that we stick a lot of stuff into evt->... in various ways. > > There is a default fallback at the end. > > default: > /* Unprocessed messages may be processed outside the current > module. If firstMessageHook is non-NULL and returns a non > zero value, the message has been successfully processed */ > if(firstMessageHook) > if((*firstMessageHook)(hwnd, message, wParam, lParam)) > return 1; > return DefWindowProcW(hwnd,message,wParam,lParam); > > { > > > So, if firstMessageHook exists, one can do whatever. > > Now, a Windows manager may need other stuff and so on. > What you are looking at is how to hook this VM side with more of the > general Windows system. > > These hooks are globals, so should be accessible. > > /*********************************************************** > *****************/ > /* Message Processing */ > /*********************************************************** > *****************/ > /* The last dispatched event. It is used for the event processing > mechanism. */ > MSG *lastMessage = NULL; > /* The entry to the message hooks called from the window procedure. > If another module requires to process messages by itself, it should > put its message procedure in this place. */ > messageHook firstMessageHook = 0; > /* The entry to a pre-message hook. Can be used to intercept any messages > to the squeak main window. Useful for modules that wish to be notified > about certain messages before they are processed. */ > messageHook preMessageHook = 0; > > Never played with these but any Windows integration is of interest to me. > > So, go ahead. Nothing would resist focused work. > > Be aware that there is another VM underway with a cleanup of all of this > but this is not released yet. > > Keep us posted. > Phil > > > > > On Tue, Feb 28, 2017 at 9:33 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > Hi, > > > > I guess what you want to achieve will not be an easy task for you if you > are new to programming. > > But it is always good to have a goal and if you have time to learn I'm > pretty sure you will master > > it. > > > > Even when OS-Windows inspire you for automizing tasks in other Windows > processes (like autoit) you > > should not start with my OS-Windows project directly as contributing to > it requires knowledge > > on your side on Smalltalk as well as Win32 C programming. > > > > First start with learning Smalltalk and Pharo > > - http://files.pharo.org/books/ > > - http://pharo.pharocloud.com/pharobooks > > - http://stephane.ducasse.free.fr/FreeBooks.html > > > > After having an idea about Smalltalk and Pharo you should try to learn > UFFI which > > is Pharos unified foreign function interface and ability to call C DLL's. > > > > https://ci.inria.fr/pharo-contribution/view/Books/job/ > PharoBookWorkInProgress/lastSuccessfulBuild/artifact/ > book-result/UnifiedFFI/ > > > > Sideways start learning about the Win32 API and C as this helps to > better understand > > how things are done on the Windows side. There are many, many tutorials > out there. > > Try to call or wrap some simple DLL functions on you own first. > > > > There is a nice and tiny C compiler if you want to try out some C samples > > http://www.pellesc.de/index.php?page=download&lang=en > > > > With this initial knowledge you can try to understand why and how > OS-Windows was done. > > I wrote many tests - just add a breakpoint and run them to debug through > the code to understand. > > Google for the API descriptions of the Win32 functions that are called > to get an understanding > > how Pharo and C get connected. > > > > Also check how you work with callbacks in UFFI (as this would be > required for a hook). > > > > If you are then still interested in interception windows messages you > should start reading here > > https://msdn.microsoft.com/en-us/library/windows/desktop/ > ms632589(v=vs.85).aspx > > > > Primarily one has to wrap SetWindowsHookEx API function and friends and > wrap a good API > > for them in Pharo. > > > > Hope that helps to get started. > > > > Regards > > Torsten > > > > > Gesendet: Dienstag, 28. Februar 2017 um 06:04 Uhr > > > Von: lw1990 <lukewallace1990(a)gmail.com> > > > An: pharo-dev(a)lists.pharo.org > > > Betreff: [Pharo-dev] How to listen for windows messages? > > > > > > In the OS-Windows package, there exists the ability to use the windows > api in > > > Pharo. > > > This is very powerful, and I intend to add more of the windows api > into it > > > (it's only partially implemented). > > > > > > This appears to all have been done with DllCalls (FFI calls) so far. > > > > > > A big part of interacting with windows is listening to/intercepting and > > > responding to windows messages. > > > For example, every time a user presses a key on the keyboard, a windows > > > message will happen in the background for that key. If Pharo was aware > of > > > these messages, then Pharo could do things in response to hotkeys > pressed on > > > Windows (outside of a pharo window). > > > > > > It would also make reacting to events potentially nicer. Like making a > > > windows-desktop-manager in Pharo that can tell when a new window is > created > > > by windows (maybe they opened notepad). It would certainly be better > than an > > > infinite loop or timer of 'get active window and compare to last active > > > window and see if it changed'. Instead it would be 'when receive the > > > WM_MESSAGE for new window created, notify Pharo so it can react'. > > > > > > How can I set up a windows message hook in Pharo? > > > Please keep in mind I'm very new to programming, but I work from home > and > > > have lots of time to learn :-) > > > > > > > > > > > > -- > > > View this message in context: http://forum.world.st/How-to- > listen-for-windows-messages-tp4936285.html > > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > > > > -- _,,,^..^,,,_ best, Eliot

March 14, 2017

Re: [Pharo-dev] How to listen for microsoft os windows messages (WM_MESSAGE's)?

by Esteban Lorenzano

you cannot use QT out of the box because is C++ I have some experiments with GTK3 that were working but event loop was kinda failing (no time to go back to it soon). It would be very interesting to have native windows support, I may take a look eventually :) Esteban > On 14 Mar 2017, at 13:37, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > > > There are other cross platform APIs e.g. wxWidgets and Gtk > > There used to be a version of squeak with wx bindings wxSqueak but the > code seems not to be on line now. > > > GTK is not a very good choice, it works well on Linux but on MacOS and Windows has many issues and a lot less developers bug fixing. > > wxWidgets is a nice GUI API but again it does not come remotely close to the feature set and stability of QT. Some of its areas also are abandoned or very much lagging behind. In my case a big turn off was the outdated python wrappers which sent me directly back to QT. > > When it comes to guis No1 is Native GUIs , No2 is QT. > > But QT needs a commercial license for developing pro applications. Its free license is GLP which limits the usage on commercial projects. > > It does however offer a free LGPL version with more limited features. LGPL allows to close code as long as the code is distributed via dynamically linked libraries. > > Still it may be tricky to balance on the LGPL without falling down. Which is why many like us prefer MIT over LGPL. > > There are a ton of open source GUI APIs out there, but most of them are immature, limited or plain abandoned. So you have plenty of choice, but I think you will have little reason to prefer something that is not QT, especially if we are talking about commercial projects that need to run on many platforms.

March 14, 2017

[pharo-project/pharo-core]

by GitHub

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

March 14, 2017

[pharo-project/pharo-core] 1c5d63: 60441

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 1c5d63f507942e5be41af0c31d02a5064f56bb7f https://github.com/pharo-project/pharo-core/commit/1c5d63f507942e5be41af0c3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-14 (Tue, 14 Mar 2017) Changed paths: M Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/private/calculateStartIndexWhenShowing_.st M Nautilus.package/NautilusUI.class/instance/accessing/showHierarchy_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60440.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60441.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60440.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60441.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60441 19826 Off by one error in FTTableContainerMorph>>#calculateStartIndexWhenShowing: https://pharo.fogbugz.com/f/cases/19826 19828 Class side methods + hierarchy selection eats the selected class. https://pharo.fogbugz.com/f/cases/19828 http://files.pharo.org/image/60/60441.zip

March 14, 2017

Re: [Pharo-dev] How to listen for microsoft os windows messages (WM_MESSAGE's)?

by Dimitris Chloupis

> > There are other cross platform APIs e.g. wxWidgets and Gtk > > There used to be a version of squeak with wx bindings wxSqueak but the > code seems not to be on line now. > > GTK is not a very good choice, it works well on Linux but on MacOS and Windows has many issues and a lot less developers bug fixing. wxWidgets is a nice GUI API but again it does not come remotely close to the feature set and stability of QT. Some of its areas also are abandoned or very much lagging behind. In my case a big turn off was the outdated python wrappers which sent me directly back to QT. When it comes to guis No1 is Native GUIs , No2 is QT. But QT needs a commercial license for developing pro applications. Its free license is GLP which limits the usage on commercial projects. It does however offer a free LGPL version with more limited features. LGPL allows to close code as long as the code is distributed via dynamically linked libraries. Still it may be tricky to balance on the LGPL without falling down. Which is why many like us prefer MIT over LGPL. There are a ton of open source GUI APIs out there, but most of them are immature, limited or plain abandoned. So you have plenty of choice, but I think you will have little reason to prefer something that is not QT, especially if we are talking about commercial projects that need to run on many platforms.

March 14, 2017

Re: [Pharo-dev] Mini Pharo -> JavaScript translator?

by Dimitris Chloupis

A potential solution would be Pharo -> Slang -> C -> Javascript Slang converts pharo code to C and Emacscripten converts C to Javascript. This approach also should produce minimal JS code but it wont be readable. This C to Js approach also has the advantage of being able to utilize webassembly and asm.js to provide high performance JS code something that other approaches that go directly from Pharo to JS will struggle with. The reason being that tools that support these approaches tend to more heavily optimize the generated JS code. The catch here is that you will have to understand both C and JS to iron out potential issues. So this means this is definitely not a "simple way to translate Pharo code into JS" as you requested.

March 14, 2017

Re: [Pharo-dev] Pharo6 supported syntax regression

by Nicolai Hess

2017-03-13 16:47 GMT+01:00 Peter Uhnak <i.uhnak(a)gmail.com>: > Hi, > > apparently in Pharo 6 pragma attributes can no longer be symbols without > hash? > > In Pharo5 I could do > > method > <attr: Something> > > and it would compile it as symbol > > In Pharo6 this is syntax error. > > I am not asking for resolution either direction (although I guess > #Something should be canonical), it is just odd to me that the syntax would > change (and maybe some code where people like me forgot to add hash sign > will break). > Actually, I think the behavior in Pharo5 was broken, it should not compile, and we fixed it for Pharo 6. > > Peter > >

March 14, 2017

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

by Santiago Bragagnolo

You are welcome :). We are doing some experiments for looking some research branches on it. So, writing some Dapps but not really productive. or not yet. Any way, we still using solidity as language for the contracts. Santiago On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Very Nice! Thank you for building it. > > I started a similar project for the Bitcoin blockchain, but then I > drifted away and never got back to it. > > Are you writing DAPPs? > > Best regards, > > Esteban A. Maringolo > > > 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > Hi all. Im happy to announce a pre release of the Fog ethereum driver > that > > we develop in the space of an Inria project. > > > > It still not complete but is already usable for some experiments and > simple > > projects. > > > > You can downloadit from > > https://github.com/sbragagnolo/Fog/ > > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1) > > > > Dependencies > > > > RHash > > > > sudo apt-get install rhash > > > > Solidity > > > > npm install solc > > > > Download code > > > > Iceberg / Baseline > > > > Metacello > > new > > baseline: 'Fog'; > > repository: 'github://sbragagnolo/Fog:v0.1.1.1/src'; > > load. > > > > By hand > > > > You may want to use this version for having access to some scripts and > > contracts samples. > > > > git checkout git@github.com:sbragagnolo/Fog.git > > > > git checkout v0.1.1.1 > > > > Metacello > > new > > baseline: 'Fog'; > > repository: 'filetree:///path/to/git-repository/Fog/src';; > > load. > > > > > > It's based on the standar API for javascript > > (https://github.com/ethereum/wiki/wiki/JavaScript-API) . > > > > It provides interaction with remote contracts, it do as well provides a > way > > for navigating the architecture objects: blocks, transactions, accounts > and > > contracts. > > > > I hope you find it useful. > > > > Feel free to fill the github issue tracker with anything you find :). > > > > > > I will come to you with some new exciting news about ethereum soon :) > > > > Santiago. > > > > > > > > > > > > > >

March 14, 2017

[pharo-project/pharo-core]

by GitHub

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

March 14, 2017

[pharo-project/pharo-core] c5a89d: 60440

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: c5a89df18cc0e39d613a3855daa1e0c57a4b396e https://github.com/pharo-project/pharo-core/commit/c5a89df18cc0e39d613a3855… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-14 (Tue, 14 Mar 2017) Changed paths: M MonticelloFileTree-Core.package/MCFileTreeStCypressWriter.class/instance/private/fileNameMapFor_.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/packageSelection.st M Polymorph-Widgets.package/UITheme.class/instance/morph creation/scrollBarDownButtonBoundsFor_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60439.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60440.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60439.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60440.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Catalog.package/CatalogProvider.class/instance/actions/reset.st M Tool-Catalog.package/CatalogProvider.class/instance/private/loadProjects.st Log Message: ----------- 60440 19834 Error in horizontal scrollbar https://pharo.fogbugz.com/f/cases/19834 19831 catalog refresh retrieves an empty collection https://pharo.fogbugz.com/f/cases/19831 19823 exported source of the package MonticelloFileTree-Core in pharo-core repository contains strange extension https://pharo.fogbugz.com/f/cases/19823 http://files.pharo.org/image/60/60440.zip

March 14, 2017