September 2019 - Pharo-users

Re: [Pharo-users] Microsoft COM

by Vince Refiti

>>I'm very interested in COM implementation since I found Pharo to be very useful as a tool, and since I work in "windowed" environment the COM interaction is crucial to me. I decided to spent my free evenings working on the project finalization. I'm not sure of how long will it take though :-) Pablo, I hope that I can count on your help regarding the questions about the overall architecture that you set. Is anybody else interested in this? Maybe we can join our efforts. Have you checked out Dolphin Smalltalk's way of creating COM components? The Dolphin guys have a wizard to "automatically generate wrapper classes for all the interfaces defined in the type-library" (from the help file). Vince

Sept. 25, 2019

Re: [Pharo-users] Microsoft COM

by Esteban Lorenzano

Hi, This is very nice to hear :) Iâm sure Pablo will help in his capabilities, we want to improve windows interaction as much as possible :) Esteban > On 25 Sep 2019, at 22:28, eftomi <tomaz.turk(a)ef.uni-lj.si> wrote: > > Hi, > > I finally got some time to check Pablo's PharoCOM package closely. At first > I had problems with simple things, like making Word visible with > properyNamed:put: (it's frustrating when you see the app on the processes > list but you cannot control it :-)) but then I found the reason - it was a > tiny detail in Win32VariantBool>>#write:to:, and then - voila! > > Here's an example of opening Word for Windows, adding a blank document, > typing some text and getting this text back to Pharo: > > Ole32Lib uniqueInstance initLibrary. > wrd := COMDispatchInstance createInstanceByName: 'Word.Application'. > wrd propertyNamed: 'Visible' put: true. > > docs := wrd propertyNamed: 'Documents'. > docs dispatch: 'Add'. > > sel := wrd propertyNamed: 'Selection'. > sel dispatch: 'TypeText' withArguments: {'Hello from Pharo!'}. > > sel dispatch: 'WholeStory' . > Transcript show: (sel propertyNamed: 'Text'); cr. > > Another example is with Active Data Objects to get DB access: > > conn := COMDispatchInstance createInstanceByName: 'ADODB.Connection' . > conn dispatch: 'Open' withArguments: { 'DSN=this; Uid=that; Pwd=theOther;' } > . > conn propertyNamed: 'State' . --> true! > rst := (COMDispatchInstance createInstanceByName: 'ADODB.Recordset') . > rst dispatch: 'Open' withArguments: { 'SomeTableName' . conn . 3 . 1 }. > > The last line raises an exception because not all of the data types that > functions are reporting are implemented yet, as Pablo mentioned in his post. > > The package is really nicely prepared. The most impressive is it's > reflective capability. My "proof of concept" work with DispHelper library > that I mentioned in another forum topic was successful (I can get to the SQL > Server :-)), however it's a dead-end regarding the reflection. > > I'm very interested in COM implementation since I found Pharo to be very > useful as a tool, and since I work in "windowed" environment the COM > interaction is crucial to me. I decided to spent my free evenings working on > the project finalization. I'm not sure of how long will it take though :-) > Pablo, I hope that I can count on your help regarding the questions about > the overall architecture that you set. > > Is anybody else interested in this? Maybe we can join our efforts. > > Best wishes, > Tomaz > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Sept. 25, 2019

Re: [Pharo-users] Microsoft COM

by eftomi

Hi, I finally got some time to check Pablo's PharoCOM package closely. At first I had problems with simple things, like making Word visible with properyNamed:put: (it's frustrating when you see the app on the processes list but you cannot control it :-)) but then I found the reason - it was a tiny detail in Win32VariantBool>>#write:to:, and then - voila! Here's an example of opening Word for Windows, adding a blank document, typing some text and getting this text back to Pharo: Ole32Lib uniqueInstance initLibrary. wrd := COMDispatchInstance createInstanceByName: 'Word.Application'. wrd propertyNamed: 'Visible' put: true. docs := wrd propertyNamed: 'Documents'. docs dispatch: 'Add'. sel := wrd propertyNamed: 'Selection'. sel dispatch: 'TypeText' withArguments: {'Hello from Pharo!'}. sel dispatch: 'WholeStory' . Transcript show: (sel propertyNamed: 'Text'); cr. Another example is with Active Data Objects to get DB access: conn := COMDispatchInstance createInstanceByName: 'ADODB.Connection' . conn dispatch: 'Open' withArguments: { 'DSN=this; Uid=that; Pwd=theOther;' } . conn propertyNamed: 'State' . --> true! rst := (COMDispatchInstance createInstanceByName: 'ADODB.Recordset') . rst dispatch: 'Open' withArguments: { 'SomeTableName' . conn . 3 . 1 }. The last line raises an exception because not all of the data types that functions are reporting are implemented yet, as Pablo mentioned in his post. The package is really nicely prepared. The most impressive is it's reflective capability. My "proof of concept" work with DispHelper library that I mentioned in another forum topic was successful (I can get to the SQL Server :-)), however it's a dead-end regarding the reflection. I'm very interested in COM implementation since I found Pharo to be very useful as a tool, and since I work in "windowed" environment the COM interaction is crucial to me. I decided to spent my free evenings working on the project finalization. I'm not sure of how long will it take though :-) Pablo, I hope that I can count on your help regarding the questions about the overall architecture that you set. Is anybody else interested in this? Maybe we can join our efforts. Best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 25, 2019

Using Pharo for instrumentation & process control

by Brainstorms

Hi Ben, The ML didn't break out Guillermo's topic change into a new thread as I expected it to, so I'm "manually" starting this as a new one -- unless there's a better/easier way..?? I'll respond to your message more fully later today (and after I've checked out your links). In the meantime... https://www.linkedin.com/in/ted-brunzie-2931b5 <https://www.linkedin.com/in/ted-brunzie-2931b5> -Ted Ben Coman wrote > Cool! I'd be interested to track what you do in this space. > (I'm an electrical engineer and always thought Pharo would make a great > SCADA system. > https://www.linkedin.com/in/bencoman/ ) > > Btw, I haven't managed to bubble playing-with-this to the top of my queue, > but it may interest you... > https://github.com/jmari/StModbus > > cheers -ben -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 25, 2019

Re: [Pharo-users] [Pharo-dev] Pumping FFI documentation [WAS] FFI beginner question

by ducasse

> On 25 Sep 2019, at 15:22, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Wed, 25 Sep 2019 at 13:51, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > Hi > > Normally each time a PR is integrated in a book, the CI is generating the PDF. > https://github.com/SquareBracketAssociates/Booklet-uFFI/releases <https://github.com/SquareBracketAssociates/Booklet-uFFI/releases> > > So what you can do is to not bother and copy-edit and we fix the corresponding pillar > if you break it. > > Hey Stef :) > I'm guessing you mean to encourage Ted to "not worry" rather than "not bother" > https://www.phrasemix.com/phrases/not-bother-doing-something <https://www.phrasemix.com/phrases/not-bother-doing-something> Yes :) > > cheers -ben

Sept. 25, 2019

Re: [Pharo-users] [Pharo-dev] Pumping FFI documentation [WAS] FFI beginner question

by Ben Coman

On Wed, 25 Sep 2019 at 13:51, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > Normally each time a PR is integrated in a book, the CI is generating the > PDF. > https://github.com/SquareBracketAssociates/Booklet-uFFI/releases > > So what you can do is to not bother and copy-edit and we fix the > corresponding pillar > if you break it. > Hey Stef :) I'm guessing you mean to encourage Ted to "not worry" rather than "not bother" https://www.phrasemix.com/phrases/not-bother-doing-something cheers -ben

Sept. 25, 2019

Re: [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by Ben Coman

On Wed, 25 Sep 2019 at 08:35, Brainstorms <wild.ideas(a)gmail.com> wrote: > I automate instrumentation for data acquisition & process control; > we started using Lua as a scripting language to allow our end-users to > script the operation of compiled apps we produce. There's a potential to > also use Pharo to do this. I think Lua's well-designed FFI will make > "swapping out" Lua for Pharo achievable. > Cool! I'd be interested to track what you do in this space. (I'm an electrical engineer and always thought Pharo would make a great SCADA system. https://www.linkedin.com/in/bencoman/ ) Btw, I haven't managed to bubble playing-with-this to the top of my queue, but it may interest you... https://github.com/jmari/StModbus cheers -ben

Sept. 25, 2019

Test method auto-generation in Calypso

by HernÃ¡n Morales Durand

Hi, I have this idea of typing a method in a Browser and have another code area in the same browser where the method test is "automagically generated". This is, divide the current method pane in two: One for the method being written itself, and another for its test, where at least the method selector could be autogenerated by writing testXXXX Of course being able to jump to the method test would be super nice! (and with a keyboard shortcut). This reminds myself to write the method now instead of forget it forever. Any hints to make this happen in Calypso? Cheers, HernÃ¡n

Sept. 25, 2019

Re: [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by Brainstorms

Hi Guillermo, I obviously gave the impression that I was focused on the UFFI code/documentation, but actually I'm up for helping in this way for any/all elements of Pharo, not just this one. Reviewing & editing (for grammar, clarification, spelling & punctuation, et al.) is definitely something I can help with. That would apply to PDF booklets, code comments, web pages, etc. The English in Pharo is generally very good, yet there are places here & there that could use.. 'polishing', mostly to make Pharo's English prose look as professional as the tool it represents, of course. :^) So the question is (given that you have a fairly high & wide view of things), what elements could best use my talents & efforts? If you want to start with UFFI, that's fine with me. It *is* a subject of interest for me, and I have a long-term project idea that will require a good understanding of it. (I automate instrumentation for data acquisition & process control; we started using Lua as a scripting language to allow our end-users to script the operation of compiled apps we produce. There's a potential to also use Pharo to do this. I think Lua's well-designed FFI will make "swapping out" Lua for Pharo achievable.) I'll dig into Pillar/Pier, install everything, and get the process working... Thanks for the detailed how-to for setting these up! It will likely be next week at the earliest that I'll have that in place. I'll also study the latest rev of the UFFI booklet to pick up the details of how it works in Pharo, and run through the examples. I'll make notes of my impressions & questions for feedback "as a newcomer" (that won't be hard!) -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 25, 2019

Re: [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by eftomi

Hi Guille, Thanks for your efforts, we really appreciate it! I was intrigued by Stephan and tried to prepare something for the book, like a subtitle/small chapter "Exotic types", but then I noticed that you already put some additional content to the book on GitHub since the pdf at pharo.org was created last year - the text that cleared some of my challenges. I went through UFFI complexities over and over with the debugger, so I have relatively good picture of what is going on when a call is "converted" to bytecode, however I'm constantly finding new pearls inside. UFFI is really great and heavy package! Anyways, I don't think that I can add anything substantial to the content of the book, however I can help with the feedback and suggestions, I can also test the examples if you need. As for the "missing pieces & understandable", I will fire right away :-) Most of my FFI experiences are coming from fiddling with the "mysterious" Win32WideString implementation or wchar_t*, char16_t*, char32_t* â¦ family of wide strings on Windows. It seems to me that Win32WideString class is only half made, or maybe it was made before UFFI -> I'm just guessing, however it's a subclass of ExternalObject and not the subclass of FFIExternalObject. When you pass it through UFFI as an argument, everything is OK, however when it is returned from a function call it is not automagically treated as a proper Win32WideString - you have to "manually" convert the data at the ExternalAddress. And now my suggestions on the book :-) - I hardly found (on the net, Pharo books ...) any explanation on ExternalObject's handle, which is quite often used in FFIExternalObjects, too; what's the difference between a handle and a pointer, and what exactly the various implementations of #fromHandle: are supposed to do. #fromHandle is now mentioned in the book, based on this discussion <http://forum.world.st/UFFI-correct-way-to-cast-void-td5067008.html> about casting, however if you are dealing with an "exotic type" then it would be nice to have some guidelines about the purpuse of it. To illustrate, in Win32WideString the handle is implemented as a ByteArray with the data itself, in other objects that I know of it's normally an (external) address/pointer, huh? - When the UFFI call ends, and the return argument's value is put onto the stack right after the #send:invokeWithArguments:, what happens with that value - is there anything that can be done with it - can the "casting" be performed "automatically"? Of course one can always prepare a "wrapper" to do that, however â¦ I found FFIExternalType>>#emitReturnArgument:context: where "loader" gets onto the scene, but this leads to heavy lifting with bytecodes, is I understand :-) - In relation to that, there is a bit vague explanation in the book about objects under the title External Objects ("... But often, frameworks will allocate structures, pointers, etc. which actually represents âan objectâ (not in the same sense as a Smalltalk object, but can be interpreted like one) ..."). This "interpretation" is a kind of mysterious :-) A couple of suggestions about possible directions would be nice to have. - As far as I can see, the FFIExternalValueHolder is not mentioned in the book yet. It is nicely described in its comment, however the missing information is that the type (the resulting subclass of FFIExternalValueHolder) should be defined as a class variable - without that the signature parser cannot find it. The purpose of FFIExternalValueHolder is similar to FFIExternalType class>>#newBuffer. I hope you find these suggestions helpful. Best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 24, 2019