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

Re: [Pharo-dev] REMEMBER: Tomorrow 28/02 16h UTC TechTalk: Reflectivity

by Ben Coman

Can we have a link and a countdown? cheers -ben On Mon, Feb 27, 2017 at 10:59 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > It will be handled by Marcus who will present current status of > Reflectivity integration. > > Esteban > > >

Feb. 28, 2017

[pharo-project/pharo-core] 4e8d88: 60417

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4e8d884ef5ef34a144070b758d44988be1e3f468 https://github.com/pharo-project/pharo-core/commit/4e8d884ef5ef34a144070b75… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-28 (Tue, 28 Feb 2017) Changed paths: M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/lookup/lookupVar_inContext_.st A OpalCompiler-Core.package/OCBlockScope.class/instance/lookup/nextOuterScopeContextOf_.st M OpalCompiler-Core.package/OCBlockScope.class/instance/lookup/outerScopeLookupVar_inContext_.st A OpalCompiler-Core.package/OCOptimizedBlockScope.class/instance/lookup/nextOuterScopeContextOf_.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/fetchArgFromOptimizedBlockInsideFullBlock_extraArg_.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingArgOfOuterBlockFromAnotherDeepBlock.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingMethodArgFromOptimizedBlockContext.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60416.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60417.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60416.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60417.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI-Tests.package/FFIExternalStructurePlatformTests.class/instance/tests/testStructureHasCorrectOffsets32bits.st M UnifiedFFI-Tests.package/FFIExternalStructurePlatformTests.class/instance/tests/testStructureHasCorrectOffsets64bits.st Log Message: ----------- 60417 19770 FFIExternalStructurePlatformTests>>#testStructureHasCorrectOffsets32bits is failing on the bootstrapped image https://pharo.fogbugz.com/f/cases/19770 19761 Debugger wrong temp var value after multiple step through block https://pharo.fogbugz.com/f/cases/19761 http://files.pharo.org/image/60/60417.zip

Feb. 28, 2017

[pharo-project/pharo-core]

by GitHub

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

Feb. 28, 2017

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

by Dimitris Chloupis

The first thing is to be very precise in what you want. I thought you wanted a window manager now you mention a full blow GUI API. Frankly if you want to ovehaul Pharo GUI API , personally I think hands down a Pharo QT project will be far more valuable. Windows may have an overwhelming market of 90% of OS users but the same is not true for developers. Developers are far more attracted to other platforms like MacOS and Linux. MacOS especially has a very loyal and quite large developer crowd. So a WIN API solution will not be as attractive as cross platform QT. QT not only work on Win, Mac and Linux , it also work inside Web pages , iOS and Android. If we take into account that mobile is the most rapidly growing market you can imagine why QT is so much loved by devs. I also recommend to get your hands dirty and learn C. Yes there are easier solutions out there, much easier, but knowing C does not open a door it opens a multiverse of possibilities. Its a huge bonus to have in your coding arsenal. C and C++ may not be as loved as Pharo but its a necessary evil none the less. There is also the .NET options which provided the native gui on widnows and recently it open sourced and gained support from Microsoft for other platforms. Basically M$ bought Xamarin , the company responsible for MONO , a .NET that can run on pretty much any platform with support for C#, Python, Delphi, J#, F# and many other langauges. But personally I do not trust Microsoft. In any case using an existing GUI API will make your life eaiser. Both QT and Winforms (.NET GUI API) are very well designed but Win API (especially MFC) are a monstrosity. Another solution is to get your hands dirty and help with Bloc, the new replacement for Morphic which is the standard Pharo GUI API. I am sure Bloc devs would love your assistance and Bloc already works well so it will be eaiser for you too. You can instead focus on features you care the most and bring those features inside Bloc or as a separate Pharo library depending on Bloc. This will be extremely valuable for your Pharo user because we will be moving to Bloc slowly next year and thus they wont have to learn a new GUI API. Hence why I said that you need to define a precise strategy. Pitch your ideas , discuss them here, see if there devs already working on similar features. You will be surprised how much "buried" Pharo code there is out there. People make it for personal use and never both to advertise it or even mention it. Coders are generally terrible at 3 things 1) GUIs 2) Code design 3) Promotion On Tue, Feb 28, 2017 at 3:17 PM lw1990 <lukewallace1990(a)gmail.com> wrote: > Thank you all for the excellent replies > I will be rereading them, here are my thoughts/responses for now: > > There exists a windows scripting language called autohotkey > (autohotkey.com) similar to autoit, which does everything I want, I > merely > wanted to make similar functionality in Pharo so I could use Pharo - it > will > be better for large and ambitious windows projects. > > AutoHotkey is open source and the source of the language is in C. > > So, most or all of the necessary C code is hopefully already available, I > will just have to figure out how to put it into Pharo. It will not be as > ambitious as Autohotkey itself because Pharo has most of the functionality > required by default - all that is needed is DllCall's for the Windows API > to > get/set values, hooks to be aware of Windows Messages, and perhaps one day > an API to create native windows gui's using Pharo syntax. That is at least > all of the main stuff I can think of that would be useful to most business > people that want to automate their windows OS. > > Pharo offers a very good IDE/debugger and programming environment, and > natural language syntax which Autohotkey lacks. Autohotkey is the best > there > is right now, but I believe Pharo could surpass it quickly once some of > this > functionality is implemented. The number one reason Autohotkey is easy to > use is because the community is extremely responsive and helpful, and Pharo > seems to be this way too :-) > > > > -- > View this message in context: > http://forum.world.st/How-to-listen-for-microsoft-os-windows-messages-WM-ME… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Feb. 28, 2017

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

by lw1990

Thank you all for the excellent replies I will be rereading them, here are my thoughts/responses for now: There exists a windows scripting language called autohotkey (autohotkey.com) similar to autoit, which does everything I want, I merely wanted to make similar functionality in Pharo so I could use Pharo - it will be better for large and ambitious windows projects. AutoHotkey is open source and the source of the language is in C. So, most or all of the necessary C code is hopefully already available, I will just have to figure out how to put it into Pharo. It will not be as ambitious as Autohotkey itself because Pharo has most of the functionality required by default - all that is needed is DllCall's for the Windows API to get/set values, hooks to be aware of Windows Messages, and perhaps one day an API to create native windows gui's using Pharo syntax. That is at least all of the main stuff I can think of that would be useful to most business people that want to automate their windows OS. Pharo offers a very good IDE/debugger and programming environment, and natural language syntax which Autohotkey lacks. Autohotkey is the best there is right now, but I believe Pharo could surpass it quickly once some of this functionality is implemented. The number one reason Autohotkey is easy to use is because the community is extremely responsive and helpful, and Pharo seems to be this way too :-) -- View this message in context: http://forum.world.st/How-to-listen-for-microsoft-os-windows-messages-WM-ME… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 28, 2017

Re: [Pharo-dev] Pharo bootstrap with Ring and Calypso

by Guillermo Polito

Hi, yes this is cool :) There is also a new smart student that will work on this infrastructure a bit to make it "normal developer friendly", you know, hiding some implementation details, making maybe a UI for the process and so on. Now, about the questions: - And how much smaller could the image get if the class builder was removed? Well, as Pavel says, you can get for example 10K. You can get even less if you tweak it manually. Around 10k is the minimal required by the VM to run a full featured image (at least in cog 32 bits, I did not measure it in Spur). Imagine that the VM requires at least: * one process scheduler * one process in that scheduler * one context on that process * one method on that context Then, the VM requires some information to interact with the runtime, e.g., * what is the selector used for doesNotUnderstand: (yes, we can change it!) * what are the first 256 character objects in the Character flyweight * what is the class of SmallInteger immediate instances * some special/optimized selectors My automatic process generated a somewhat 10k of objects required for this VM/image interaction. Of course this list changes a bit with Spur, and could be reduced (for example, if you don't use characters, you wouldn't need the character flyweight and so on...) - Is it future approach for bootstrap? (with respect to the 10k image) Well, if you read my thesis, what I'm doing there is to lazily pick what classes and methods will go inside an image. While this is nice to experiment, I do not think It's a good approach for bootstrapping: * you need to exercise/execute all possible cases your image needs to support * and that means you need to know all those cases in advance * and that you have to be careful with side effects Otherwise, code not executed is not taken in the resulting image. Also take the fact that changing a little line of code may result in bootstrapping an image a couple of times bigger because of a wrong dependency. All these points make this approach less reproducible and a bit more complicated. I prefer an explicit list of packages to bootstrap, that we can control and really test the output :) Also, as Igor says, we could be able to generate an image without a class builder, as we are able to generate an image without a compiler. But we do not want to. Because that is an image that we cannot almost interact with. We cannot load code inside. So the more interesting question is where is the balance between space and functionality. BTW Pavel, this approach may need to be updated but I think we could make it run on top of the simulator also ;). - How faster or slower bootstrap process with it? They are not really comparable. They do not use the same infrastructure, nor the same process, and they do not generate the same results. The 10k image is of course generated in a matter of seconds, but a 600k image containing the seaside counter may take half an hour. In our current approach, the speed of bootstrap is directly related to the number of classes and methods inside the result. There are two ways to speed up the process: - by speeding up the ast interpreter (or replacing it by a compiled version of it) - and by cleaning the kernel Guille On Fri, Feb 24, 2017 at 9:15 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > On 24 February 2017 at 21:01, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> >> 2017-02-24 17:17 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> >>> >>> 2017-02-24 16:36 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >>> >>>> The "guest" object memory runs in a special virtual machine simulator >>>> during the bootstrapping. That simulator uses AST Interpreter to execute >>>> the code inside the guest environment before it is installed for real. It >>>> uses own special kind of proxies and tricks to do it. The current bootstrap >>>> cannot run without class builder in the guest environment, but... >>>> >>>> >>>>> And how much smaller could the image get if the class builder was >>>>> removed. >>>>> >>>> >>>> ...Guille in his thesis tried different approaches and he was able to >>>> produce extremely small images (~10 KiB) that did for example only a sum >>>> of two numbers. >>>> >>> >>> Is it future approach for bootstrap? >>> How faster or slower bootstrap process with it? >>> >> >> That's more question for Guille, but I do not think we will adopt this >> approach of bootstrapping in near future because it needs to be updated for >> the Spur format and it needs a special VM modifications. And the question >> is how much is it really needed because if you want to do something with >> the image, you will anyway need most of methods needed for the class >> builder like basic strings and collections support. >> >> > I think, you can shrink image even more, by running something after > booting it to remove ClassBuilder & co, if you don't need to create classes > etc. > > -- > Best regards, > Igor Stasenko. >

Feb. 28, 2017

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

by Dimitris Chloupis

> 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 :-) > First of all Torsten gave you an excellent answer. If read it once, go reread it 10 times and bookmark it. Second of all I cannot answer precisely what code you will need because I have not done this before. I did have a recent experience with UFFI. Apart from some of the basics of UFFI that you need to be aware of , everything else is pretty straightforward. I did work with shared memory mapped files which is an extremely low level functionality of an OS, so low level that is included in the OS kernel and forms the basic of OS memory management. I expected to be insanely hard and I was suprised how simple it was. It started as a joke (how to make Pharo controll C++ applications) it turned out into a serious Pharo library (CPP). The main reason for this is the fact that UFFI keeps the C syntax almost intact when it comes to function signatures. But the big catch here is that you need to be familiar with C and the libraries you are going to use. It will be super easy to use them from Pharo but the task itself may not. Pharo maybe be a higher level language but C is not. C is not low level but still you need to know how to do manual memory management and also OS APIs tend to be quite technical too. The general idea is that Pharo will follow the C approach to the letter even when it comes to manual memory management. So if you do not know C , drop anything you do and go learn it NOW. My advice is to NOT i repeat DO NOT do this in Pharo. First do this in C. Why ? First of all you will find tons of example code online, so all you have to do is copy paste and modify accordingly. So getting the code to work is suprisingly easy but understanding the code and why when you made changes started crashing for no apparent reason is a lot more difficult. Second of all Pharo IDE may be awesome but is made to be used with Pharo not with C libraries. A C debugger and generally a C ide , in case of windows Visual Studio is free and very efficient will help you deal with bugs a lot easier. When a bug happens in Pharo , the IDE practically takes you by the hand and helps you find it and correct it. When a bug happens in C code , even C code run from inside Pharo via UFFI it will crash your C executable or Pharo itself and no error will be displayed apart from extremely limited information. However this comparison is unfair because Pharo comes with an IDE , C usually does not. But C with Visual Studio or other IDEs will help you get very close to Pharo experience. Obviously not the same , but quite close none the less. Generally my approach was to start with prints , printing values and information to track exactly what went wrong with my C code . Then when prints became too many I used Visual Studio debugger breakpoints, that stop execution so you can examine what code is actually executed and fails and watchpoints which basically keep track of data inside variables so you can find bugs that are more tricky to find than executing the wrong code. Also find a C forum and ask question. You wont get much help here because even though UFFI is very important the vast majority of Pharo coders prefer to stay away from C coding because C coding is not Pharo coding. If you figure out how to do this in C it will take you literally minutes to port it to Pharo , its pretty much the exactly same process and exactly same code. Well almost. The process is the same for any C library and C code called from Pharo, the rest is just techncial documentation which you will find a ton online. Thats one of the advantages of using a popular language like C. So go and do this in C and make sure it works in C then try to port it to Pharo. If Pharo gives you any problems you can always copy paste your code here, or preferably using an online code snippet service like pastebin or gist and we will guide you through how to fix your errors since the process is the same for all C code.

Feb. 28, 2017

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

by phil＠highoctane.be

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. 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/plat… 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/PharoBookWorkInProgre… > > 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).… > > 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. > > > > >

Feb. 28, 2017

[pharo-project/pharo-core] 17e26d: 60416

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 17e26d8fd2926a817bf37b64aaab0eb9ec522fe7 https://github.com/pharo-project/pharo-core/commit/17e26d8fd2926a817bf37b64… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-28 (Tue, 28 Feb 2017) Changed paths: M BaselineOfIDE.package/BaselineOfIDE.class/instance/actions/additionalInitialization.st M BaselineOfIDE.package/BaselineOfIDE.class/instance/baseline/baseline_.st M BaselineOfIDE.package/BaselineOfIDE.class/instance/baseline/groups_.st M PharoBootstrap-Initialization.package/PharoBootstrapInitialization.class/class/public api/initializeCommandLineHandlerAndErrorHandling.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60415.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60416.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60415.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60416.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60416 19732 Reenable Catalog loading in Spotter and fix confusing/hidden setting for it https://pharo.fogbugz.com/f/cases/19732 19769 BaselineOfIDE needs update https://pharo.fogbugz.com/f/cases/19769 19771 remove debugging "Alive" report during the bootstrap initialization https://pharo.fogbugz.com/f/cases/19771 http://files.pharo.org/image/60/60416.zip

Feb. 28, 2017

[pharo-project/pharo-core]

by GitHub

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

Feb. 28, 2017