- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] WhatsUp from: 2014-02-17 until: 2014-02-28

by Max Leske

On 17.02.2014, at 07:00, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - Finished Fuel 1.9.3 (not published yet, so please wait with integrating. You should see an announcement in the next couple of days.) - Fuel can now be used with Squeak4.5 - We now have Fuel builds for Squeak4.4 and Squeak4.5, inlcluding test results - Finished proof of concept for Fuel configurations (script your Fuel :) ) > > ### What's next, until 2014-02-28 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - implement number of objects limit for Fuel (is necessary for MethodContext serialization) > > (*) we'll be expecting results by then ;) >

Feb. 17, 2014

Re: [Pharo-dev] [Vm-dev] Re: Mapping key Ctrl+M and Ctrl+Enter

by Guillermo Polito

Hi Nicolai! which event are you listening to? Which platform? :) Keyup and keypress behave indeed differently though they use the same data structure (the event buffer array) to send the event from the vm to the image. Some fields that are valid for keyup are not for keypress and vice-versa. Cheers, Guille On Mon, Feb 17, 2014 at 2:01 PM, <btc(a)openinworld.com> wrote: > > Nicolai Hess wrote: > > Someone knows(remembers) why Ctrl+Enter is mapped to keyvalue 13 > I would expect Ctrl+M to be mapped at this value. > > > Ctrl+l -> keyValue 12 > Ctrl+Enter -> keyValue 13 > Ctrl+n -> keyValue 14 > > I miss > Ctrl+M -> keyValue ???? > > (see Fogbugz issue 12103 <https://pharo.fogbugz.com/default.asp?12103> > shortcuts for tools) > > (I vagualy remember this is related to the VM and there was > a reason for doing so, but don't know it anymore) > > > > regards > nicolai > > > Probably more than you wanted to know... > http://answers.google.com/answers/threadview/id/267586.html > http://www.everything2.org/index.pl?node=control%20codes > cheers -ben > >

Feb. 17, 2014

[pharo-project/pharo-core] d26359: 30765

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: d26359d3c56eb14e6e532af0e60814f7a6ac2b18 https://github.com/pharo-project/pharo-core/commit/d26359d3c56eb14e6e532af0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-17 (Mon, 17 Feb 2014) Changed paths: M Morphic-Core.package/PasteUpMorph.class/instance/world menu/makeAScreenshot.st M Morphic-Core.package/WorldState.class/class/world menu items/screenShotCommandOn_.st M Polymorph-Widgets.package/UITheme.class/instance/services/centeredAlertIn_text_title_configure_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script418.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30765.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30765 12896 Screenshot tool: tell save location https://pharo.fogbugz.com/f/cases/12896 12895 #centeredAlert:title:configure dialog is not centered https://pharo.fogbugz.com/f/cases/12895 http://files.pharo.org/image/30/30765.zip

Feb. 17, 2014

[pharo-project/pharo-core]

by GitHub

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

Feb. 17, 2014

Re: [Pharo-dev] NB and ASMJit questions

by Igor Stasenko

Other solution, is to change NBFFIConst and be more forgiving about constants range (so if it sees large positive integer which don't fits into 32-bit signed integer range, assume it is unsigned 32-but integer and use proper immediate type during code generation). I know this could be 'least surprising behavior' , only because this is how C works by not caring about signed/unsigned value assignments. But when i was doing it i decided to be more strict, because implicit conversions have one big downside: - if there's a malfunction in your code, you often find yourself in a position to wonder, whether it breaks because implicit conversion _applied_ in a place where you didn't expected or it is because it is _not applied_ in a place where you actually expected. :) -- Best regards, Igor Stasenko.

Feb. 17, 2014

Re: [Pharo-dev] Mapping key Ctrl+M and Ctrl+Enter

by btc＠openinworld.com

Feb. 17, 2014

Re: [Pharo-dev] NB and ASMJit questions

by Igor Stasenko

On 16 February 2014 23:37, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > I'm trying to mimic the following C/C++ example in NativeBoots to allow > random number > generation on windows: > > https://gist.github.com/kbjorklu/6317361 > > When I combine the flags in Pharo using "|" in the same way like in the > first function call > of the example: > > acquireContextExample1 > NBFFICallout stdcall: #(BOOL CryptAcquireContextA(HCRYPTPROV self, 0, 0, > PROV_RSA_FULL, CRYPT_VERIFYCONTEXT | CRYPT_SILENT)) module: #advapi32 > > I get an error 'comma expected'. Looks like the NBFnSpecParser does not > allow > expression evaluation like CRYPT_VERIFYCONTEXT | CRYPT_SILENT. Will this > be possible > in future versions? > > Nonetheless I tried to continue and since I defined: > CRYPT_VERIFYCONTEXT := 16rF0000000. > CRYPT_SILENT := 16r00000040. > > I evaluated manually and tried to use the harcoded value directly: > > acquireContextExample2 > > "Retrieves information about the current console font." > <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> > > ^ NBFFICallout stdcall: #(BOOL CryptAcquireContextA(HCRYPTPROV > self, 0, 0, PROV_RSA_FULL, 16rF0000040)) module: #advapi32 > > > but this returns another error when converting using #asDWord: > > (16rF0000040 i4) exceeds doubleword (32bit) range > > in an AJImmediate but 16rF0000040. Looks like it is treated as unsiged > since > > 16rF0000040 asUImm32 asDWord > > works. How to specifiy the number directly but as unsigned? > > To reproduce: > - take a fresh Pharo3.0 Latest update: #30759 > - load "OSWindows" from config browser to get the core and other packages > - load "OS-Windows-Cryptography" package/mcz from > smalltalkhub.com/#!/~OS/OS-Windows > - evaluate WinCryptoProvider new acquireContextExample2 or > WinCryptoProvider new acquireContextExample1 > > Any helping hand in converting the example would be appreciated. > > Thx > T. > Yes, i am aware of this problem. (16rF0000040 i4) exceeds doubleword (32bit) range i4 means signed integer 4 bytes.. the mantissa 16rF0000040 , simply don't fits, because it is > 2^31-1, which is max for 32-bit integer. The class responsible for passing constants is NBFFIConst: Integer>>asNBExternalType: gen "integer value in callout argument description array are pushed directly on stack #( 100 ) - an integer value argument = 100 " ^ NBFFIConst value: (self ) the code generator, uses: emitPush: gen gen asm push: ((gen asm imm: value) size: 4) and #imm: sends #asImm to the value, which by default turns integer into a signed immediate: Integer>>asImm "Convert integer value into a signed immediate operand" ^ AJImmediate new ivalue: self unfortunately, there is no easy way to work around this: if you change it to unsigned (uvalue:), then you have another problem, but now with all negative integer constants (like -1). But you can work that around: use a 32-bit complement of unsigned 16rF0000040 to signed one, which ends up with identical 32-bit value: 16rF0000040 - 16r100000000 => -268435392 test: (16r100000000 - 268435392) hex '16rF0000040' -- Best regards, Igor Stasenko.

Feb. 17, 2014

Re: [Pharo-dev] Package for manage USB - RS232

by Sven Van Caekenberghe

Dario, On 17 Feb 2014, at 12:55, Dario Trussardi <dario.trussardi(a)tiscali.it> wrote: > > Thanks Sven, > >> You should #close the port when you are done, else it remains in use, I would guess. > > Of course, i used : > > > | srl | > srl := SerialPort new. > srl openPort: 'COM1'. > > srl nextPutAll: #[ 27 66 2 2 ] . > > srl close. > > But after the first time, when submit the same code the system answer: > > Error: Cannot open 'COM1' > > I don't unterstand because. Me neither. I have no experience working with serial ports (but I know some people on the list do), let alone on Windows, but from looking at the code #close should be enough. > I note what the sometimes SerialPort allInstances answer instance after the close method. > > Perhaps remain occupied some resources? They are still there because they are not yet garbage collected. If they are properly closed (check the printString in the inspector), the external resource should have been released. Sorry, but I can't help you any further. Sven > Ciao, > > Dario > >> Also, why do you #close before you start, seems strange to me ? >> >> On 17 Feb 2014, at 12:05, Dario Trussardi <dario.trussardi(a)tiscali.it> wrote: >> >>> Ciao, >>> >>> >>>> Hi, >>>> >>>> I'm also interested by an answer to that question. So far, what I have as status is: you need a plugin to handle communications with the serial port (either for direct RS232 or USB-to-Serial) and compiling the serial port plugin with the Pharo VM makes it unstable. >>> >>> I dont know " compiling " plugin area. ( i work with Windows 7 ) >>> >>>> The solution we used was: to compile the serial plugin for the squeak VM and work in Squeak (4.3) instead of Pharo. >>> >>> Can you explain more detail about it? >>> >>> >>> My test is : >>> >>> >>> I download the Pharo 2.0 #20628 and i use the SerialPort class. >>> >>> The first time i do the code: >>> >>> | srl | >>> >>> srl := SerialPort new. >>> srl close. >>> >>> srl openPort: 'COM1'. >>> >>> srl nextPutAll: #[ 27 66 2 2 ] . >>> >>> The RS232 device work fine. >>> >>> After the first time, when submit the same code the system answer: >>> >>> Error: Cannot open 'COM1' >>> >>> A this time i need to restart the Pharo environment. >>> >>> >>> Any considerations, suggestions ? >>> >>> >>> Thanks, >>> >>> Dario >>> >>> >>>> >>>> Thierry >>>> >>>> Le 16/02/2014 16:28, Dario Trussardi a Ã©crit : >>>>> Hi, >>>>> >>>>> >>>>> i work with: Pharo1.Latest update: #14445 ( or with: Pharo2.0 Latest update: #20628 ). >>>>> >>>>> >>>>> I'm interested to manage communications with USB or RS232 device. >>>>> >>>>> >>>>> I can find package which support this protocol? >>>>> >>>>> Thank for any considerations ? >>>>> >>>>> Dario >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> Thierry Goubier >>>> CEA list >>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>> 91191 Gif sur Yvette Cedex >>>> France >>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>> >>> >>> >> >> > >

Feb. 17, 2014

Re: [Pharo-dev] Package for manage USB - RS232

by Dario Trussardi

Thanks Sven, > You should #close the port when you are done, else it remains in use, I would guess. Of course, i used : | srl | srl := SerialPort new. srl openPort: 'COM1'. srl nextPutAll: #[ 27 66 2 2 ] . srl close. But after the first time, when submit the same code the system answer: Error: Cannot open 'COM1' I don't unterstand because. I note what the sometimes SerialPort allInstances answer instance after the close method. Perhaps remain occupied some resources? Ciao, Dario > Also, why do you #close before you start, seems strange to me ? > > On 17 Feb 2014, at 12:05, Dario Trussardi <dario.trussardi(a)tiscali.it> wrote: > >> Ciao, >> >> >>> Hi, >>> >>> I'm also interested by an answer to that question. So far, what I have as status is: you need a plugin to handle communications with the serial port (either for direct RS232 or USB-to-Serial) and compiling the serial port plugin with the Pharo VM makes it unstable. >> >> I dont know " compiling " plugin area. ( i work with Windows 7 ) >> >>> The solution we used was: to compile the serial plugin for the squeak VM and work in Squeak (4.3) instead of Pharo. >> >> Can you explain more detail about it? >> >> >> My test is : >> >> >> I download the Pharo 2.0 #20628 and i use the SerialPort class. >> >> The first time i do the code: >> >> | srl | >> >> srl := SerialPort new. >> srl close. >> >> srl openPort: 'COM1'. >> >> srl nextPutAll: #[ 27 66 2 2 ] . >> >> The RS232 device work fine. >> >> After the first time, when submit the same code the system answer: >> >> Error: Cannot open 'COM1' >> >> A this time i need to restart the Pharo environment. >> >> >> Any considerations, suggestions ? >> >> >> Thanks, >> >> Dario >> >> >>> >>> Thierry >>> >>> Le 16/02/2014 16:28, Dario Trussardi a Ã©crit : >>>> Hi, >>>> >>>> >>>> i work with: Pharo1.Latest update: #14445 ( or with: Pharo2.0 Latest update: #20628 ). >>>> >>>> >>>> I'm interested to manage communications with USB or RS232 device. >>>> >>>> >>>> I can find package which support this protocol? >>>> >>>> Thank for any considerations ? >>>> >>>> Dario >>>> >>>> >>>> >>>> >>>> >>> >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> >> > >

Feb. 17, 2014

Re: [Pharo-dev] Mapping key Ctrl+M and Ctrl+Enter

by Benjamin

13 is the magic key to give 'enterâ as input in terminals (if I remember correctly) Ben On 17 Feb 2014, at 11:54, Nicolai Hess <nicolaihess(a)web.de> wrote: > Someone knows(remembers) why Ctrl+Enter is mapped to keyvalue 13 > I would expect Ctrl+M to be mapped at this value. > > > Ctrl+l -> keyValue 12 > Ctrl+Enter -> keyValue 13 > Ctrl+n -> keyValue 14 > > I miss > Ctrl+M -> keyValue ???? > > (see Fogbugz issue 12103 shortcuts for tools) > > (I vagualy remember this is related to the VM and there was > a reason for doing so, but don't know it anymore) > > > > regards > nicolai >

Feb. 17, 2014