- Pharo-dev - lists.pharo.org

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

by Eliot Miranda

Hi Luke, On Tue, Feb 28, 2017 at 5:11 AM, 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 :-) > There is a complete integration of the Windows event loop in Newspeak, written by Vassili Bykov. It is implemented above the same Alien callbacks we have in Pharo and Squeak, which use slightly different, but mostly common versions of the same VM. If you're looking to integrate with Windows events I suggest contacting the newspeaklanguage group and asking there for assistance in porting the code to Pharo. -- > View this message in context: http://forum.world.st/How-to- > listen-for-microsoft-os-windows-messages-WM-MESSAGE-s- > tp4936285p4936388.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > _,,,^..^,,,_ best, Eliot

March 14, 2017

Re: [Pharo-dev] [ANN] threaded heartbeat VMs added to zeroconf

by Ben Coman

Good discussion here... http://forum.world.st/Unix-heartbeat-thread-vs-itimer-td4928943.html#a49289… cheers -ben On Tue, Mar 14, 2017 at 2:44 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Can you explain what a Threaded Heartbeat VM is? > I can do some inference based on the name, but I'll probably be wrong. > > Regards! > Esteban A. Maringolo > > > 2017-03-13 14:38 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hello, > > > > Following recent talks, I added threaded heartbeats VMs to zeroconf. > > Is weird because is not anymore âzeroâ conf: you need to configure the > > machine to accept this VMâ¦ but well, this is like that :P > > > > The links to use are this: > > > > http://get.pharo.org/vmT60 > > http://get.pharo.org/vmTLatest60 > > http://get.pharo.org/alpha+vmT > > http://get.pharo.org/alpha+vmTLatest > > http://get.pharo.org/60+vmTLatest > > > > (they are listed at http://get.pharo.org, as usual) > > > > cheers, > > Esteban > > > >

March 13, 2017

Re: [Pharo-dev] [ANN] threaded heartbeat VMs added to zeroconf

by Esteban A. Maringolo

Can you explain what a Threaded Heartbeat VM is? I can do some inference based on the name, but I'll probably be wrong. Regards! Esteban A. Maringolo 2017-03-13 14:38 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hello, > > Following recent talks, I added threaded heartbeats VMs to zeroconf. > Is weird because is not anymore âzeroâ conf: you need to configure the > machine to accept this VMâ¦ but well, this is like that :P > > The links to use are this: > > http://get.pharo.org/vmT60 > http://get.pharo.org/vmTLatest60 > http://get.pharo.org/alpha+vmT > http://get.pharo.org/alpha+vmTLatest > http://get.pharo.org/60+vmTLatest > > (they are listed at http://get.pharo.org, as usual) > > cheers, > Esteban >

March 13, 2017

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

by Esteban A. Maringolo

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 13, 2017

Re: [Pharo-dev] [ANN] threaded heartbeat VMs added to zeroconf

by Thierry Goubier

Thanks Esteban! (well, on Linux, the 32 bits VM were not zero-conf either, far from it) Thierry Le 13/03/2017 Ã 18:38, Esteban Lorenzano a Ã©crit : > Hello, > > Following recent talks, I added threaded heartbeats VMs to zeroconf. > Is weird because is not anymore âzeroâ conf: you need to configure the > machine to accept this VMâ¦ but well, this is like that :P > > The links to use are this: > > http://get.pharo.org/vmT60 > http://get.pharo.org/vmTLatest60 > http://get.pharo.org/alpha+vmT > http://get.pharo.org/alpha+vmTLatest > http://get.pharo.org/60+vmTLatest > > (they are listed at http://get.pharo.org, as usual) > > cheers, > Esteban >

March 13, 2017

[ANN] threaded heartbeat VMs added to zeroconf

by Esteban Lorenzano

Hello, Following recent talks, I added threaded heartbeats VMs to zeroconf. Is weird because is not anymore âzeroâ conf: you need to configure the machine to accept this VMâ¦ but well, this is like that :P The links to use are this: http://get.pharo.org/vmT60 http://get.pharo.org/vmTLatest60 http://get.pharo.org/alpha+vmT http://get.pharo.org/alpha+vmTLatest http://get.pharo.org/60+vmTLatest <http://get.pharo.org/60+vmTLatest> (they are listed at http://get.pharo.org <http://get.pharo.org/>, as usual) cheers, Esteban

March 13, 2017

Pharo6 supported syntax regression

by Peter Uhnak

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). Peter

March 13, 2017

Google App Engine allows whatever runtime.

by phil＠highoctane.be

And Pharo should of course run there :-) https://techcrunch.com/2017/03/09/new-version-of-google-app-engine-supports… With Google Cloud functions, maybe this will make sense for the initiative of starting lots of VM superfast, Phil

March 13, 2017

[ANN] Fog - Ethereum driver

by Santiago Bragagnolo

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 <https://github.com/sbragagnolo/Fog#rhash>RHash sudo apt-get install rhash <https://github.com/sbragagnolo/Fog#solidity>Solidity npm install solc <https://github.com/sbragagnolo/Fog#download-code>Download code <https://github.com/sbragagnolo/Fog#iceberg--baseline>Iceberg / Baseline Metacello new baseline: 'Fog'; repository: 'github://sbragagnolo/Fog:v0.1.1.1/src'; load. <https://github.com/sbragagnolo/Fog#by-hand>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 13, 2017

Re: [Pharo-dev] Esteban's ChangeLog week of 6 March 2017

by Esteban Lorenzano

> On 13 Mar 2017, at 10:31, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 13 March 2017 at 09:00, <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hello! > > This is my weekly ChangeLog, from 6 March 2017 to 12 March 2017. > You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=6/3/2017&to=12/3/2017 <http://log.smallworks.eu/web/search?from=6/3/2017&to=12/3/2017> > > ChangeLog > ========= > > 10 March 2017: > -------------- > > * === libgit2(ssh) and linux > An update on the libgit2 (and consequently iceberg) problem on linux: SSH will not work on ITIMER VM (which > is the zeroconf default, at least for now). > > Here the reason: > > ITIMER sends an signal to the VM thread using +pthread_kill(tickerThread, TICKER_SIGNAL)+ and that aborts > system calls, which are used by +libssh2+, producing a 'wait for packet' to fail answering a timeout ( > even if that timeout does not happens for real). > > Here is an interesting comment from +sqUnixITimerTickerHeartbeat.c+ : > > ---- > /* While we use SA_RESTART to ensure system calls are restarted, this is > * not universally effective. In particular, connect calls can abort if > * a system call is made in the signal handler, i.e. the pthread_kill in > * prodHighPriorityThread. So we avoid this if possible by not prodding > * the high-priority thread unless there are high-priority tickees as > * indicated by numAsyncTickees > 0. > */ > ---- > > ... and sadly, as +OSSubprocess+, +libssh2+ calls falls under the category of "not universally effective" > (they are connect calls... once disconnected, you cannot connect again 'as is'). > > So, the only workaround possible (at least for now), is to use the threaded version of VM... I improved the > error message it throws when this fails, now looks like this: > > ---- > This VM uses a thread heartbeat who requires a special configuration to work. > You need to allow it to run higher priority threads (real time), to allow clock to work properly > You need to add a conf file to /etc/security/limits.d, executing this: > > sudo cat >/etc/security/limits.d/%s.conf <<END\n", VMNAME); > * hard rtprio 2 > * soft rtprio 2 > END > > You need to log out and log back in for the limits to take effect. > For more information read https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/r3732#linux <https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/r3732#linux> > ---- > > which at least shows what's happens and how you can easily fix it. > > Now, I think this is a *sad solution*. Needing to touch system configuration in order to run a VM > does not feels "professional". I would like to have some time to find a fix. > > No, it does feels right, according to common *nix lifestyle :) > No, seriously, it is not an issue for linux to set up configs for installed software , that would require root privileges. > VM is quite a beast, and this is not a surprise, that it requires fine tuning & deep & broader interfacing with OS, comparing to regular software. > Of course, the sad moment is that you need to write down an installation package and put this .conf file there which will install it, > in comparison to usual "download and run" style, this surely looks like a drawback. > But we can do smarter: - add small script to bundle with big letters "RUN ME" , that will do what is should to copy/concat .conf file > for VM binary located at given folder or wherever it does.. and everyone's happy :) hehehâ¦ I was in fact modifying zeroconf to add threaded download and I was adding a file INSTALL with this ;) Esteban > > > > 9 March 2017: > ------------- > > * I spent last two days again fighting with linux dependencies, because what I thought was fixed (the > loading of +libgit2.so+), actually was not working in all conditions. > > Now, I think I finally arrived to a working solution (that involved add an +rpath+ to Pharo, not > to dependent libraries). > > There is a new +vmLatest60+, let's see how it works... > > > 6 March 2017: > ------------- > > * I spent time fixing libgit2 (and dependents) compilation, both for linux and windows. > > As a result, now windows is working again (there was problems after version 0.26)... but linux, who seemed > working last friday, is now again not working properly :( > > > cheers! > Esteban > > > > > -- > Best regards, > Igor Stasenko.

March 13, 2017