November 2016 - Pharo-users

Re: [Pharo-users] [UFFI] Dealing with Windows types

by Dimitris Chloupis

" reality check... http://utf8everywhere.org/ Sorry I don't remember enough of my Unicode research six months ago to be more help. Only enough to know there are traps and hunt down that article. cheers -ben" Really .... ??? So bad ??? Oh well good thing I did not intend to use Unicode. Very eye opening article thanks. "First read the general introduction https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… That should be more than enough (we got all basic covered in Pharo). If you want more, there is the Pharo Unicode project https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… But you most probably don't need that. I thought that Windows used UTF-16 internally <https://en.wikipedia.org/wiki/UTF-16#Usage>https://en.wikipedia.org/ <https://en.wikipedia.org/wiki/UTF-16#Usage>wiki/UTF-16#Usage" Yes Windoom uses UTF-16, I am amazed how the coding world managed to take another simple problem and make it so complex. In any case , I dont need Unicode . I made the decision to just chain string characters together in 2 byte unicode arrays , I wont be converting from or to Unicode anyway. For usual English characters the second byte of a Unicode character array on Win 10 is always 00 which is a waste of memory anyway. Unicode may come handy when I have to deal with translating the game to other languages , but this for now is a very low priority. As always I love your medium posts, clear, simple and to the point. Definitely bookmarked for future reference. Thanks

Nov. 21, 2016

Re: [Pharo-users] [UFFI] Dealing with Windows types

by Sven Van Caekenberghe

> On 21 Nov 2016, at 10:23, Ben Coman <btc(a)openinworld.com> wrote: > > On Sun, Nov 20, 2016 at 9:50 PM, Dimitris Chloupis > <kilon.alios(a)gmail.com> wrote: >> Once more I got lost in the the spaghetti called "Pharo code". I am >> referring to OSWindows. >> >> Ironically its easier to read Windows header files and disassemble memory >> than actually read pharo code :D >> >> Fortunately void pointers is not an issue since I already used them on Linux >> and Macos with UFFI without using FFIConstanthandle. >> >> By the way the comment in that class wonder whether handles in Linux and >> Macos are the same , they are not, in Window a handle is a void pointer , in >> Linux and Macos they are just regular integers (int). >> >> So far I have drawn the following conclusions >> >> Unicode means 2 bytes char , windows names it wchar_t , the equivelant on >> pharo must be long char , it stores unicode strings which VS C++ defines as >> L"my text", first byte is a hex number for the character itself, second byte >> in most cases is 0 except for special characters. >> >> Numbers 0-9 are 48 (hex: 30) to 57 (hex: 39) >> >> Characters A-Z are 65(hex: 41) to 90(hex: 5A) >> >> Characters a-z are 97(hex: 61) to 122(hex: 7A) >> >> So either I use Unicode as it is or use Unicode as a 1 byte char chaining 2 >> bytes together instead of 1 at a time. > >> Which will result in exact same >> memory value for all OS (Windows /Linux / Maco) > > reality check... > http://utf8everywhere.org/ > > Sorry I don't remember enough of my Unicode research six months ago to > be more help. > Only enough to know there are traps and hunt down that article. First read the general introduction https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… That should be more than enough (we got all basic covered in Pharo). If you want more, there is the Pharo Unicode project https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… But you most probably don't need that. I thought that Windows used UTF-16 internally https://en.wikipedia.org/wiki/UTF-16#Usage Sven > cheers -ben > >> >> either solution could work. >> >> windows PVOID(void pointer) and *wchar_t ( pointer to TCHAR [Unicode- 2 >> bytes]) are 4 bytes like Linux and MacOS equivalent pointers. >> >> So it seems the differences are not as massive as I feared , apart from >> Unicode text the rest appears to be more or less the same. >> >> But I will be sure as soon as I use UFFI to test these assumptions which I >> am about to do. >> >> On Sun, Nov 20, 2016 at 10:51 AM Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >>> >>> Hi, >>> >>>> On 20 Nov 2016, at 00:52, Mark Bestley <st(a)bestley.co.uk> wrote: >>>> >>>> >>>> Sorry I have not got a Windows machine here but MSDN should provide all >>>> the documentation you need. Some of these types are not translatable and >>>> have to be treated as opaque on the Smalltalk side ie just pass as data >>>> >>>> All are defined in Windows.h and MSDN provides documentation - for types >>>> see >>>> https://msdn.microsoft.com/en-us/library/windows/desktop/aa383751(v=vs.85).… >>>> >>>> Note the naming of many of these comes from Windows 2 or earlier so was >>>> used on 16 bit programs >>>> >>>> handle_t / HANDLE is a pseudo pointer that Windows has created and >>>> Windows system calls understand. They will dereference it to find something >>>> useful - This is similar to a POSIX file handle that you can only use as a >>>> parameter to system calls. >>> >>> and these are handled by UFFI by FFIConstantHandle (read the comment) >>> >>>> >>>> PVOID is a pointer to a void ie just a pointer to something >>>> >>>> LPCTSTR and TCHAR depend on Unicode >>> >>> yepâ¦ maybe you want to see OSWindows from Torsten, he already aliased many >>> of this types. >>> >>> Esteban >>> >>>> >>>> In Wnndows C API there are usually two forms of many systems call they >>>> either take 8 bit ANSI strings or 16 bit ones which MS says is Unicode >>>> (unfortuneatly for us now MS made the decision of 16 bit when all Unicode >>>> points fitted into 16 bits so not now a simple mapping. See >>>> https://msdn.microsoft.com/en-us/library/vs/alm/dd183415(v=vs.85).aspx and >>>> https://msdn.microsoft.com/en-us/library/2dax2h36.aspx >>>> >>>> I'll assume you want Unicode >>>> >>>> TCHAR is then a 16 bit Unicode character >>>> LPCTSTR is a const long pointer to a 16 bit Unicode string >>>> >>>> I would suggest finding a book or long tutorial :( and sorry I can't >>>> suggest any as I read this from Petzold books over 25 years ago >>>> >>>> Mark >>>> >>>> >>>> On 19/11/2016 18:51, Dimitris Chloupis wrote: >>>>> So now I need to port my CPPBridge to Windows and I have to deal with >>>>> this monster. And it would not be Windows if it did not make life a lot >>>>> harder , so it defines its own types. >>>>> >>>>> Such types are >>>>> >>>>> handle_t / HANDLE >>>>> TCHAR >>>>> LPCTSTR >>>>> PVOID >>>>> >>>>> also I will have to deal with Unicode , I have no clue how to proceed, >>>>> any help is greatly appreciated. >>>>> >>>> >>>> >>>> -- >>>> Mark >>>> >>>> >>> >>> >> >

Nov. 21, 2016

Re: [Pharo-users] [UFFI] Dealing with Windows types

by Ben Coman

On Sun, Nov 20, 2016 at 9:50 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Once more I got lost in the the spaghetti called "Pharo code". I am > referring to OSWindows. > > Ironically its easier to read Windows header files and disassemble memory > than actually read pharo code :D > > Fortunately void pointers is not an issue since I already used them on Linux > and Macos with UFFI without using FFIConstanthandle. > > By the way the comment in that class wonder whether handles in Linux and > Macos are the same , they are not, in Window a handle is a void pointer , in > Linux and Macos they are just regular integers (int). > > So far I have drawn the following conclusions > > Unicode means 2 bytes char , windows names it wchar_t , the equivelant on > pharo must be long char , it stores unicode strings which VS C++ defines as > L"my text", first byte is a hex number for the character itself, second byte > in most cases is 0 except for special characters. > > Numbers 0-9 are 48 (hex: 30) to 57 (hex: 39) > > Characters A-Z are 65(hex: 41) to 90(hex: 5A) > > Characters a-z are 97(hex: 61) to 122(hex: 7A) > > So either I use Unicode as it is or use Unicode as a 1 byte char chaining 2 > bytes together instead of 1 at a time. > Which will result in exact same > memory value for all OS (Windows /Linux / Maco) reality check... http://utf8everywhere.org/ Sorry I don't remember enough of my Unicode research six months ago to be more help. Only enough to know there are traps and hunt down that article. cheers -ben > > either solution could work. > > windows PVOID(void pointer) and *wchar_t ( pointer to TCHAR [Unicode- 2 > bytes]) are 4 bytes like Linux and MacOS equivalent pointers. > > So it seems the differences are not as massive as I feared , apart from > Unicode text the rest appears to be more or less the same. > > But I will be sure as soon as I use UFFI to test these assumptions which I > am about to do. > > On Sun, Nov 20, 2016 at 10:51 AM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> >> Hi, >> >> > On 20 Nov 2016, at 00:52, Mark Bestley <st(a)bestley.co.uk> wrote: >> > >> > >> > Sorry I have not got a Windows machine here but MSDN should provide all >> > the documentation you need. Some of these types are not translatable and >> > have to be treated as opaque on the Smalltalk side ie just pass as data >> > >> > All are defined in Windows.h and MSDN provides documentation - for types >> > see >> > https://msdn.microsoft.com/en-us/library/windows/desktop/aa383751(v=vs.85).… >> > >> > Note the naming of many of these comes from Windows 2 or earlier so was >> > used on 16 bit programs >> > >> > handle_t / HANDLE is a pseudo pointer that Windows has created and >> > Windows system calls understand. They will dereference it to find something >> > useful - This is similar to a POSIX file handle that you can only use as a >> > parameter to system calls. >> >> and these are handled by UFFI by FFIConstantHandle (read the comment) >> >> > >> > PVOID is a pointer to a void ie just a pointer to something >> > >> > LPCTSTR and TCHAR depend on Unicode >> >> yepâ¦ maybe you want to see OSWindows from Torsten, he already aliased many >> of this types. >> >> Esteban >> >> > >> > In Wnndows C API there are usually two forms of many systems call they >> > either take 8 bit ANSI strings or 16 bit ones which MS says is Unicode >> > (unfortuneatly for us now MS made the decision of 16 bit when all Unicode >> > points fitted into 16 bits so not now a simple mapping. See >> > https://msdn.microsoft.com/en-us/library/vs/alm/dd183415(v=vs.85).aspx and >> > https://msdn.microsoft.com/en-us/library/2dax2h36.aspx >> > >> > I'll assume you want Unicode >> > >> > TCHAR is then a 16 bit Unicode character >> > LPCTSTR is a const long pointer to a 16 bit Unicode string >> > >> > I would suggest finding a book or long tutorial :( and sorry I can't >> > suggest any as I read this from Petzold books over 25 years ago >> > >> > Mark >> > >> > >> > On 19/11/2016 18:51, Dimitris Chloupis wrote: >> >> So now I need to port my CPPBridge to Windows and I have to deal with >> >> this monster. And it would not be Windows if it did not make life a lot >> >> harder , so it defines its own types. >> >> >> >> Such types are >> >> >> >> handle_t / HANDLE >> >> TCHAR >> >> LPCTSTR >> >> PVOID >> >> >> >> also I will have to deal with Unicode , I have no clue how to proceed, >> >> any help is greatly appreciated. >> >> >> > >> > >> > -- >> > Mark >> > >> > >> >> >

Nov. 21, 2016

Re: [Pharo-users] Chip-8

by Henrik Nergaard

Keys are mapped to 1-4,q-r,a-f,z-v. For Pong key 1 and q controls the left player while 4 and r is the right. Best regards, Henrik From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of stepharo Sent: Monday, November 21, 2016 9:25 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Chip-8 I could not resist.... The keys are not working for me too. Stef Le 21/11/16 Ã 08:38, olivier auverlot a Ã©crit : Very cool !!! What are the used keys to move the player ? Olivier ;-) 2016-11-21 0:16 GMT+01:00 Henrik Nergaard <henrik.nergaard(a)uia.no<mailto:henrik.nergaard@uia.no>>: http://smalltalkhub.com/#!/~Latsabben/Chip8<http://smalltalkhub.com/#%21/%7ELatsabben/Chip8> From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>] On Behalf Of olivier auverlot Sent: Wednesday, November 16, 2016 11:22 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: [Pharo-users] Chip-8 Hi, I just read an fun article about Chip-8. Someone has worked on an emulator of this with Pharo? http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interp… http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ Best regards

Nov. 21, 2016

Re: [Pharo-users] Chip-8

by stepharo

I could not resist.... The keys are not working for me too. Stef Le 21/11/16 Ã 08:38, olivier auverlot a Ã©crit : > Very cool !!! > > What are the used keys to move the player ? > > Olivier ;-) > > 2016-11-21 0:16 GMT+01:00 Henrik Nergaard <henrik.nergaard(a)uia.no > <mailto:henrik.nergaard@uia.no>>: > > http://smalltalkhub.com/#!/~Latsabben/Chip8 > <http://smalltalkhub.com/#%21/%7ELatsabben/Chip8> > > *From:*Pharo-users [mailto:pharo-users-bounces@lists.pharo.org > <mailto:pharo-users-bounces@lists.pharo.org>] *On Behalf Of > *olivier auverlot > *Sent:* Wednesday, November 16, 2016 11:22 AM > *To:* Any question about pharo is welcome > <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> > *Subject:* [Pharo-users] Chip-8 > > Hi, > > I just read an fun article about Chip-8. Someone has worked on an > emulator of this with Pharo? > > http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interp… > <http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interp…> > > http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ > <http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/> > > Best regards > >

Nov. 21, 2016

Re: [Pharo-users] Chip-8

by stepharo

Hi henrik You are superfast...... :) Thanks a lot. I started to code it too in the train and a virus smashed me in my bed I will really have a look. I was implementing it to see if I can use as a project for a new book..... Le 21/11/16 Ã 00:16, Henrik Nergaard a Ã©crit : > > http://smalltalkhub.com/#!/~Latsabben/Chip8 > <http://smalltalkhub.com/#%21/%7ELatsabben/Chip8> > > *From:*Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *On > Behalf Of *olivier auverlot > *Sent:* Wednesday, November 16, 2016 11:22 AM > *To:* Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > *Subject:* [Pharo-users] Chip-8 > > Hi, > > I just read an fun article about Chip-8. Someone has worked on an > emulator of this with Pharo? > > http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interp… > > http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ > > Best regards >

Nov. 21, 2016

Re: [Pharo-users] Chip-8

by olivier auverlot

Very cool !!! What are the used keys to move the player ? Olivier ;-) 2016-11-21 0:16 GMT+01:00 Henrik Nergaard <henrik.nergaard(a)uia.no>: > http://smalltalkhub.com/#!/~Latsabben/Chip8 > > > > *From:* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *On > Behalf Of *olivier auverlot > *Sent:* Wednesday, November 16, 2016 11:22 AM > *To:* Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > *Subject:* [Pharo-users] Chip-8 > > > > Hi, > > > > I just read an fun article about Chip-8. Someone has worked on an emulator > of this with Pharo? > > > > http://www.multigesture.net/articles/how-to-write-an- > emulator-chip-8-interpreter/ > > http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ > > > > Best regards >

Nov. 21, 2016

Re: [Pharo-users] Chip-8

by Henrik Nergaard

http://smalltalkhub.com/#!/~Latsabben/Chip8 From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of olivier auverlot Sent: Wednesday, November 16, 2016 11:22 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Chip-8 Hi, I just read an fun article about Chip-8. Someone has worked on an emulator of this with Pharo? http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interp… http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ Best regards

Nov. 20, 2016

Re: [Pharo-users] Improving comments cool action

by Julien Delplanque

Great, I'll do it next time it happens to me. Julien On 20/11/16 18:36, stepharo wrote: > > > Le 20/11/16 Ã 17:36, Julien Delplanque a Ã©crit : >> Hello, >> >> I may be able to help, it already happens to me to see a >> comment that I could improve but I don't take the time... > Thanks this is important. >> >> If someone wants to help, how can he publish his modifications? >> Do he needs to open an issue and suggest a slice directly? > Yes >> >> Regards, >> >> Julien >> >> On 20/11/16 17:26, stepharo wrote: >>> Hi guys >>> >>> I would like to see how we could build a concerted action to improve >>> the class and method comments in Pharo. >>> >>> Now we have package comments :) so we should take also advantage of >>> them. >>> >>> I would love that a newbie is highlithed by class comments. >>> >>> So I would like to start to comment key core classes. >>> >>> I'm sure that if we all spend 30 min per week we can really have a >>> huge impact. >>> >>> I was planning to start with collection classes. >>> >>> Now let me know if you want to help. >>> >>> Stef >>> >>> >> >> >> > >

Nov. 20, 2016

Re: [Pharo-users] [Pharo-dev] Improving comments cool action

by Sven Van Caekenberghe

More and better documentation, I am all for it. > On 20 Nov 2016, at 17:26, stepharo <stepharo(a)free.fr> wrote: > > Now we have package comments :) so we should take also advantage of them. Stupid question, how exactly does one add package comments ? Can it only be done in the latest 6 ? Is it somehow compatible with older versions ?

Nov. 20, 2016