June 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Smalltalk Programming Competition

by horrido

Alan Kay contributed to my campaign!!!!! This is so frickin' amazing! Can we spell S-T-A-R P-O-W-E-R, boys and girls? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 23, 2018

Re: [Pharo-users] OmniBase for Pharo 6

by PBKResearch

Matias Thanks. I have made this change, but it does not affect the tests I have run. I have focused on getting the test suite in OmniBaseTests to run. So far I still have 5 greens, 7 reds and one orange. The greens are all the first five test methods in the browser list; it seems it half fails on the sixth one (TestEquality), hence the orange, and then red for all the rest. One problem is that the test database is created at the start of the test suite, and then not removed at the end. This seems to mess up the next attempt to run the tests. I tried to run the OmniBaseTests>>#tearDown manually, but it fails, so I have to exit Pharo and delete the test database in Windows. I intend to continue running the test suite, but I shall run the tests individually, and put breakpoints in those that fail. I shall report here if I make any progress. Best wishes Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Matias Maretto Sent: 23 June 2018 01:37 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] OmniBase for Pharo 6 Peter: I think I found the problem. On ODBFileStream class >> accessModeReadOnly the "o" on "only" is not capital. It is ^#accessModeReadonly when should be ^#accessModeReadOnly ; so on the ODBWin32FileStream >> createOn: createMode: accessMode: shareMode: cacheMode: this part fails: accessMode = #accessModeReadOnly ifTrue: [acMode := 2147483648 "GENERIC_READ"]. So it cant open the users file for read. I have fix it and at least for now I didn't get any "block" error. _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de PBKResearch <peter(a)pbkresearch.co.uk <mailto:peter@pbkresearch.co.uk> > Enviado: viernes, 22 de junio de 2018 10:39 p. m. Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] OmniBase for Pharo 6 Matias Thanks for the hints. I now have 5 greens, but all the rest are red. I am still getting the 'File cannot be locked' message. Are you doing better than that? I may try a few trials using it for real, rather than the test suite. Thanks again Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > On Behalf Of Matias Maretto Sent: 22 June 2018 22:54 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Subject: Re: [Pharo-users] OmniBase for Pharo 6 Hi Peter, yes I had the same error at the beginning. I have done 2 minor changes. Now it seems to be working fine (Although I am still running more tests). Here: ODBWin32FileStream >> closeHandle: aHandle "Close an open Win32 object handle, freeing any resources held by it. Once closed a handle is no longer valid. Answer whether the function succeeds. See Win32 SDK help for more information. BOOL CloseHandle( HANDLE hObject // handle of object to close );" "<apicall: ulong 'CloseHandle' (long) module:'kernel32.dll'>" ^ self ffiCall: #(ulong CloseHandle(long aHandle)) ODBWin32FileStream >> lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength lengthHigh: hiLength "<apicall: long 'LockFile' (long ulong ulong ulong ulong) module: 'kernel32.dll'>" ^ self ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong loLength , ulong hiLength)) _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de PBKResearch <peter(a)pbkresearch.co.uk <mailto:peter@pbkresearch.co.uk> > Enviado: viernes, 22 de junio de 2018 09:45 p. m. Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] OmniBase for Pharo 6 Matias I have just loaded Esteban's package in a new Pharo 6.1 under Windows 10. I get an error message saying 'File cannot be locked. Try again?'. When I select 'no', all tests are run and give red. Are you still running on win 7? If so, I must be doing something wrong. Can you give more details of the FFI corrections you made, please? Many thanks Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > On Behalf Of Matias Maretto Sent: 22 June 2018 21:07 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Subject: Re: [Pharo-users] OmniBase for Pharo 6 Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls and now everithing seems to be working fine. For What I saw with Voyage-UnqLite only String Objects can be used to searilize; Omnibase allow to persist almost any kind of objects, thats the part I like about it. _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com> > Enviado: jueves, 21 de junio de 2018 08:19 p. m. Para: Any question about pharo is welcome Asunto: Re: [Pharo-users] OmniBase for Pharo 6 I did it manually and I took like 5 min :P but this was really easy, just a bunch of FFI calls. Esteban > On 21 Jun 2018, at 15:31, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com> > wrote: > > EstebanLM wrote >> I just made a "blind port". migrated the old FFI to new UFFI > > Did you do this manually or use some migration tool? How long did it take? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> Smalltalk - Pharo Smalltalk Users | Mailing List Archive forum.world.st Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum >

June 23, 2018

Re: [Pharo-users] Workflow aka Aare status?

by CÃ©drick BÃ©ler

Hi Paul, I did nothing more since what was discussed in this thread. This is still something Iâm interested in but itâs not a priority at the moment. The work done since Max published it was to make it work (itâs was mainly about the removal of Omnibase dependancies). BTW, removing was Â« easy Â» but Rare was relying a lot on logging action/activity (Omnibase) and generating Seaside web UI (through Magritte) we do not have that anymore. The actual state/limitation for me if I remember well, is : - there is Â« only Â» a Â« manual Â» completion of tasks (someone has to declare a task completed). To me, it needs to be able to declare Â« software tasks Â». - manual completion was achieved through Web UI (anActivation complete). I think we need a more generic UI mechanism (Annoucement?) - I also would need delegated subtasks (to other images ). - I think it would need some kind of scheduler/orchestrator. For what purposes you need Workflow ? HTH, CÃ©drick > Le 22 juin 2018 Ã 20:48, PAUL DEBRUICKER <pdebruic(a)gmail.com> a Ã©crit : > > I read this thread: > > > http://forum.world.st/Aare-questions-td5063745.html > > > And it seems a lot of work has been done since Max/NetStyle posted the code here: > > https://github.com/Netstyle/Workflow > > > In Stef's repo here: > > https://github.com/Ducasse/Workflow > > > Is anyone else working on it / publishing code for it? > > > Thanks > > Paul

June 23, 2018

Re: [Pharo-users] [ANN] GNU Dr. Geo release 18.06

by Hilaire

Hi Ben, They call it Dynabook in the old time... Not yet there 40 years later, we are damn slow. As an educator, I am all days frustrated with the computed tools we have, and the lack of integration. Anyones crazy enough to work on this challenge? Hilaire Le 23/06/2018 Ã 02:03, Ben Coman a Ã©critÂ : > So now we need a DrGeo inside a live document providing a curriculum > for teachers... ;) ? > > cheers -ben > -- Dr. Geo http://drgeo.eu

June 23, 2018

Re: [Pharo-users] OmniBase for Pharo 6

by Matias Maretto

Peter: I think I found the problem. On ODBFileStream class >> accessModeReadOnly the "o" on "only" is not capital. It is ^#accessModeReadonly when should be ^#accessModeReadOnly ; so on the ODBWin32FileStream >> createOn: createMode: accessMode: shareMode: cacheMode: this part fails: accessMode = #accessModeReadOnly ifTrue: [acMode := 2147483648 "GENERIC_READ"]. So it cant open the users file for read. I have fix it and at least for now I didn't get any "block" error. ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org> en nombre de PBKResearch <peter(a)pbkresearch.co.uk> Enviado: viernes, 22 de junio de 2018 10:39 p. m. Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] OmniBase for Pharo 6 Matias Thanks for the hints. I now have 5 greens, but all the rest are red. I am still getting the âFile cannot be lockedâ message. Are you doing better than that? I may try a few trials using it for real, rather than the test suite. Thanks again Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Matias Maretto Sent: 22 June 2018 22:54 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] OmniBase for Pharo 6 Hi Peter, yes I had the same error at the beginning. I have done 2 minor changes. Now it seems to be working fine (Although I am still running more tests). Here: ODBWin32FileStream >> closeHandle: aHandle "Close an open Win32 object handle, freeing any resources held by it. Once closed a handle is no longer valid. Answer whether the function succeeds. See Win32 SDK help for more information. BOOL CloseHandle( HANDLE hObject // handle of object to close );" "<apicall: ulong 'CloseHandle' (long) module:'kernel32.dll'>" ^ self ffiCall: #(ulong CloseHandle(long aHandle)) ODBWin32FileStream >> lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength lengthHigh: hiLength "<apicall: long 'LockFile' (long ulong ulong ulong ulong) module: 'kernel32.dll'>" ^ self ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong loLength , ulong hiLength)) ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de PBKResearch <peter(a)pbkresearch.co.uk<mailto:peter@pbkresearch.co.uk>> Enviado: viernes, 22 de junio de 2018 09:45 p. m. Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] OmniBase for Pharo 6 Matias I have just loaded Estebanâs package in a new Pharo 6.1 under Windows 10. I get an error message saying âFile cannot be locked. Try again?â. When I select ânoâ, all tests are run and give red. Are you still running on win 7? If so, I must be doing something wrong. Can you give more details of the FFI corrections you made, please? Many thanks Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> On Behalf Of Matias Maretto Sent: 22 June 2018 21:07 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: Re: [Pharo-users] OmniBase for Pharo 6 Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls and now everithing seems to be working fine. For What I saw with Voyage-UnqLite only String Objects can be used to searilize; Omnibase allow to persist almost any kind of objects, thats the part I like about it. ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de Esteban Lorenzano <estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>> Enviado: jueves, 21 de junio de 2018 08:19 p. m. Para: Any question about pharo is welcome Asunto: Re: [Pharo-users] OmniBase for Pharo 6 I did it manually and I took like 5 min :P but this was really easy, just a bunch of FFI calls. Esteban > On 21 Jun 2018, at 15:31, Sean P. DeNigris <sean(a)clipperadams.com<mailto:sean@clipperadams.com>> wrote: > > EstebanLM wrote >> I just made a âblind portââ¦ migrated the old FFI to new UFFI > > Did you do this manually or use some migration tool? How long did it take? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html Smalltalk - Pharo Smalltalk Users | Mailing List Archive<http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> forum.world.st Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum >

June 23, 2018

Re: [Pharo-users] [ANN] GNU Dr. Geo release 18.06

by Ben Coman

On 23 June 2018 at 06:22, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Congrats, > > This was a big jump between platforms (3 to 7) and is good to know that > children (from 8 to 100) will be able to enjoy geometry, Pharo and live > coding with all the upcoming goodness. > So now we need a DrGeo inside a live document providing a curriculum for teachers... ;) ? cheers -ben > Cheers, > > Offray > > On 22/06/18 05:16, Hilaire wrote: > > We are please to announce the Dr. Geo release 18.06. It follows the > release 17.07 in July 2017. > A large part of the effort was to port Dr. Geo from the Pharo 3 to Pharo 7 > Smalltalk development environment. > In addition to usual bug fixes several features were added. > > > > *Mini changelog:* > - Dedicated Script browser > - Inspector on Smalltalk Sketch > - Positioning zoom > - Unit tests based on Smalltalk sketch > - Lan share > - Graphic user interface theme > - Fullscreen option > - Lots of bug fixes > > Read the complete announcement <http://www.drgeo.eu/news/drgeorelease1806> > > Dr. Geo is always looking for volunteers to translate > <http://www.drgeo.eu/news/weneedyou> its user interface. > > Hilaire Fernandes > > -- > Dr. Geohttp://drgeo.eu > > >

June 23, 2018

Re: [Pharo-users] OmniBase for Pharo 6

by Matias Maretto

Peter: when I run code like this example: db := OmniBase createOn: 'C:\temp\testOmni'. aTrans := db newTransaction. aTrans root at: 'Hello' put: (OrderedCollection with: 1 with: 2 with: 3). aTrans commit. db close. db := OmniBase openOn: 'C:\temp\testOmni'. aTrans := db newTransaction. (aTrans root at: 'Hello') size Everything is fine, but sometimes when I close an reopen the base I get the "lock" error, but even when I get the error the base is still opened and transactions run fine. I will take a closer look to the lockFIle method. I will tell you if I find a solution. (I am using Win 7). ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org> en nombre de PBKResearch <peter(a)pbkresearch.co.uk> Enviado: viernes, 22 de junio de 2018 10:39 p. m. Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] OmniBase for Pharo 6 Matias Thanks for the hints. I now have 5 greens, but all the rest are red. I am still getting the âFile cannot be lockedâ message. Are you doing better than that? I may try a few trials using it for real, rather than the test suite. Thanks again Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Matias Maretto Sent: 22 June 2018 22:54 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] OmniBase for Pharo 6 Hi Peter, yes I had the same error at the beginning. I have done 2 minor changes. Now it seems to be working fine (Although I am still running more tests). Here: ODBWin32FileStream >> closeHandle: aHandle "Close an open Win32 object handle, freeing any resources held by it. Once closed a handle is no longer valid. Answer whether the function succeeds. See Win32 SDK help for more information. BOOL CloseHandle( HANDLE hObject // handle of object to close );" "<apicall: ulong 'CloseHandle' (long) module:'kernel32.dll'>" ^ self ffiCall: #(ulong CloseHandle(long aHandle)) ODBWin32FileStream >> lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength lengthHigh: hiLength "<apicall: long 'LockFile' (long ulong ulong ulong ulong) module: 'kernel32.dll'>" ^ self ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong loLength , ulong hiLength)) ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de PBKResearch <peter(a)pbkresearch.co.uk<mailto:peter@pbkresearch.co.uk>> Enviado: viernes, 22 de junio de 2018 09:45 p. m. Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] OmniBase for Pharo 6 Matias I have just loaded Estebanâs package in a new Pharo 6.1 under Windows 10. I get an error message saying âFile cannot be locked. Try again?â. When I select ânoâ, all tests are run and give red. Are you still running on win 7? If so, I must be doing something wrong. Can you give more details of the FFI corrections you made, please? Many thanks Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> On Behalf Of Matias Maretto Sent: 22 June 2018 21:07 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: Re: [Pharo-users] OmniBase for Pharo 6 Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls and now everithing seems to be working fine. For What I saw with Voyage-UnqLite only String Objects can be used to searilize; Omnibase allow to persist almost any kind of objects, thats the part I like about it. ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de Esteban Lorenzano <estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>> Enviado: jueves, 21 de junio de 2018 08:19 p. m. Para: Any question about pharo is welcome Asunto: Re: [Pharo-users] OmniBase for Pharo 6 I did it manually and I took like 5 min :P but this was really easy, just a bunch of FFI calls. Esteban > On 21 Jun 2018, at 15:31, Sean P. DeNigris <sean(a)clipperadams.com<mailto:sean@clipperadams.com>> wrote: > > EstebanLM wrote >> I just made a âblind portââ¦ migrated the old FFI to new UFFI > > Did you do this manually or use some migration tool? How long did it take? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html Smalltalk - Pharo Smalltalk Users | Mailing List Archive<http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> forum.world.st Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum >

June 22, 2018

Re: [Pharo-users] OmniBase for Pharo 6

by PBKResearch

Matias Thanks for the hints. I now have 5 greens, but all the rest are red. I am still getting the 'File cannot be locked' message. Are you doing better than that? I may try a few trials using it for real, rather than the test suite. Thanks again Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Matias Maretto Sent: 22 June 2018 22:54 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] OmniBase for Pharo 6 Hi Peter, yes I had the same error at the beginning. I have done 2 minor changes. Now it seems to be working fine (Although I am still running more tests). Here: ODBWin32FileStream >> closeHandle: aHandle "Close an open Win32 object handle, freeing any resources held by it. Once closed a handle is no longer valid. Answer whether the function succeeds. See Win32 SDK help for more information. BOOL CloseHandle( HANDLE hObject // handle of object to close );" "<apicall: ulong 'CloseHandle' (long) module:'kernel32.dll'>" ^ self ffiCall: #(ulong CloseHandle(long aHandle)) ODBWin32FileStream >> lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength lengthHigh: hiLength "<apicall: long 'LockFile' (long ulong ulong ulong ulong) module: 'kernel32.dll'>" ^ self ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong loLength , ulong hiLength)) _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de PBKResearch <peter(a)pbkresearch.co.uk <mailto:peter@pbkresearch.co.uk> > Enviado: viernes, 22 de junio de 2018 09:45 p. m. Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] OmniBase for Pharo 6 Matias I have just loaded Esteban's package in a new Pharo 6.1 under Windows 10. I get an error message saying 'File cannot be locked. Try again?'. When I select 'no', all tests are run and give red. Are you still running on win 7? If so, I must be doing something wrong. Can you give more details of the FFI corrections you made, please? Many thanks Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > On Behalf Of Matias Maretto Sent: 22 June 2018 21:07 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Subject: Re: [Pharo-users] OmniBase for Pharo 6 Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls and now everithing seems to be working fine. For What I saw with Voyage-UnqLite only String Objects can be used to searilize; Omnibase allow to persist almost any kind of objects, thats the part I like about it. _____ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> > en nombre de Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com> > Enviado: jueves, 21 de junio de 2018 08:19 p. m. Para: Any question about pharo is welcome Asunto: Re: [Pharo-users] OmniBase for Pharo 6 I did it manually and I took like 5 min :P but this was really easy, just a bunch of FFI calls. Esteban > On 21 Jun 2018, at 15:31, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com> > wrote: > > EstebanLM wrote >> I just made a "blind port". migrated the old FFI to new UFFI > > Did you do this manually or use some migration tool? How long did it take? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> Smalltalk - Pharo Smalltalk Users | Mailing List Archive forum.world.st Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum >

June 22, 2018

Re: [Pharo-users] [ANN] GNU Dr. Geo release 18.06

by Offray Vladimir Luna CÃ¡rdenas

Congrats, This was a big jump between platforms (3 to 7) and is good to know that children (from 8 to 100)Â will be able to enjoy geometry, Pharo and live coding with all the upcoming goodness. Cheers, Offray On 22/06/18 05:16, Hilaire wrote: > We are please to announce the Dr. Geo release 18.06. It follows the > release 17.07 in July 2017. > A large part of the effort was to port Dr. Geo from the Pharo 3 to > Pharo 7 Smalltalk development environment. > In addition to usual bug fixes several features were added. > > > > *Mini changelog:* > - Dedicated Script browser > - Inspector on Smalltalk Sketch > - Positioning zoom > - Unit tests based on Smalltalk sketch > - Lan share > - Graphic user interface theme > - Fullscreen option > - Lots of bug fixes > > Read the complete announcement <http://www.drgeo.eu/news/drgeorelease1806> > > Dr. Geo is always looking for volunteers to translate > <http://www.drgeo.eu/news/weneedyou> its user interface. > > Hilaire FernandesÂ > -- > Dr. Geo > http://drgeo.eu

June 22, 2018

Re: [Pharo-users] OmniBase for Pharo 6

by Matias Maretto

Hi Peter, yes I had the same error at the beginning. I have done 2 minor changes. Now it seems to be working fine (Although I am still running more tests). Here: ODBWin32FileStream >> closeHandle: aHandle "Close an open Win32 object handle, freeing any resources held by it. Once closed a handle is no longer valid. Answer whether the function succeeds. See Win32 SDK help for more information. BOOL CloseHandle( HANDLE hObject // handle of object to close );" "<apicall: ulong 'CloseHandle' (long) module:'kernel32.dll'>" ^ self ffiCall: #(ulong CloseHandle(long aHandle)) ODBWin32FileStream >> lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength lengthHigh: hiLength "<apicall: long 'LockFile' (long ulong ulong ulong ulong) module: 'kernel32.dll'>" ^ self ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong loLength , ulong hiLength)) ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org> en nombre de PBKResearch <peter(a)pbkresearch.co.uk> Enviado: viernes, 22 de junio de 2018 09:45 p. m. Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] OmniBase for Pharo 6 Matias I have just loaded Estebanâs package in a new Pharo 6.1 under Windows 10. I get an error message saying âFile cannot be locked. Try again?â. When I select ânoâ, all tests are run and give red. Are you still running on win 7? If so, I must be doing something wrong. Can you give more details of the FFI corrections you made, please? Many thanks Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Matias Maretto Sent: 22 June 2018 21:07 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] OmniBase for Pharo 6 Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls and now everithing seems to be working fine. For What I saw with Voyage-UnqLite only String Objects can be used to searilize; Omnibase allow to persist almost any kind of objects, thats the part I like about it. ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de Esteban Lorenzano <estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>> Enviado: jueves, 21 de junio de 2018 08:19 p. m. Para: Any question about pharo is welcome Asunto: Re: [Pharo-users] OmniBase for Pharo 6 I did it manually and I took like 5 min :P but this was really easy, just a bunch of FFI calls. Esteban > On 21 Jun 2018, at 15:31, Sean P. DeNigris <sean(a)clipperadams.com<mailto:sean@clipperadams.com>> wrote: > > EstebanLM wrote >> I just made a âblind portââ¦ migrated the old FFI to new UFFI > > Did you do this manually or use some migration tool? How long did it take? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html Smalltalk - Pharo Smalltalk Users | Mailing List Archive<http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> forum.world.st Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum >

June 22, 2018