May 2014 - Pharo-dev - lists.pharo.org

Getting access to the _whole_ smalltalkhub?

by Alexandre Bergel

Hi! As you know, the moose team is full of passionated and happy people willing to analyze software. We have great platforms to carry out analysis that are robust enough to compete with state-of-the-Art software analysis platforms out there. It would be great to have software to feed our wonderful tools. There are 123 873 packages on Smalltalkhub (!). Can we have easily access to them? I mean, a big big big .zip file would be fantastic with all the public software. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 23, 2014

Re: [Pharo-dev] Coral is green

by Stephan Eggermont

Thanks, David. Where do I find a precompiled cog vm with the changes to test with? (preferably mac, but linux will do). build.squeak.org doesn't seem to have a recent green build. Stephan

May 23, 2014

Re: [Pharo-dev] NativeBoost and WKHTML

by Henrik Johansen

On 23 May 2014, at 2:52 , Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On 23 May 2014, at 2:36 , Torsten Bergmann <astares(a)gmx.de> wrote: > >> Hi, >> >> as there was no responded so far I tried to track the problem deeper and did a short test >> client in C/C++ to verify if I can call WKHTMLTOPDF there and generate a PDF and to >> compare to the Pharo/NativeBoost client. >> >> Attached is the according CPP file which works and results in a PDF with the google >> homepage. >> >> I also additionally implemented the callback functions in the Pharo wrapper and >> using the error handling I noticed that the component returns "Failed loading page http:// ..." >> >> >> With that info I compared the C/C++ calls to the Pharo/NativeBoost calls more deeply and >> found out that in C/C++ the following call for an object setting works (by returning 1): >> >> >> // this returns 1 in C/C++ which is OK >> int a = wkhtmltopdf_set_object_setting(os, "page", "http://www.google.de"); >> printf("object set %i",a); >> >> >> while in Pharo the same call fails (by returning 0): >> >> "The following call failed and returns 0 instead of 1" >> self setObjectSetting: 'page' to: 'http://www.google.de' in: os. > > With argument type char * , NB does not 0-terminate your strings, but passes in the argument you provided raw. > ByteStrings have an internal representation size a multiplum of 4, thus âpageâ will have no accidentally terminating 0, while âoutâ does, and the call fails since whatever garbage bytes are in the image after the string instance (âpageâ) leads to the it not being recognized as a valid property name. > > Change the call definitions to use String as argument type instead, and NB will convert the args to zero-terminated strings for you: > > NBFFICallout stdcall: #(int wkhtmltopdf_set_object_setting(wkhtmltopdf_object_settings* settings, String aName, String value)) module: 'wkhtmltox.dll' > > Alternatively, you need to provide null-terminated strings yourself: > > x := self setObjectSetting: ('page' , (Character value: 0) asString) to: 'http://www.google.de', (Character value: 0) asString) in: os. > > Which also returns makes it return 1. > > Cheers, > Henry To test it then *actually* worked, I implemented: getObjectSetting: aName in: settings into: value ofSize: vs <primitive: #primitiveNativeCall module: #NativeBoostPlugin> ^NBFFICallout stdcall: #(int wkhtmltopdf_get_object_setting(wkhtmltopdf_object_settings* settings, String aName, char* value, int vs)) module: 'wkhtmltox.dll' Note, you *cannot* use String for a parameter being written to, while NB in that case would pass along a zero-terminated copy for you, it does *not* copy the contents back into the actual string instance @ end of call. Itâs also easy to spot garbage characters added when value was // 4 = 0 (using char * definition): x := self setObjectSetting: (âpage' , Character null asString) to: 'http://www.google.de' in: os. "http://www.google.de size = 20" Transcript show: x. buffer := String new: 40. x := self getObjectSetting: ('page' , Character null asString) in: os into: buffer ofSize: buffer size. (buffer indexOf:Character null) > 21 "Probably true..." Cheers, Henry PS: Thatâs a glorious getter APIâ¦ It returns 1 even if your buffer is shorter than the actual parameter, so your only way to be sure youâve fetched all of it, is to test that the result give contains a null character, and if not, retry with a larger bufferâ¦ (The sane thing to do would be allowing you to query the parameter length, either through a * int parameter, or a separate function).

May 23, 2014

Re: [Pharo-dev] NativeBoost and WKHTML

by Henrik Johansen

On 23 May 2014, at 2:36 , Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > as there was no responded so far I tried to track the problem deeper and did a short test > client in C/C++ to verify if I can call WKHTMLTOPDF there and generate a PDF and to > compare to the Pharo/NativeBoost client. > > Attached is the according CPP file which works and results in a PDF with the google > homepage. > > I also additionally implemented the callback functions in the Pharo wrapper and > using the error handling I noticed that the component returns "Failed loading page http:// ..." > > > With that info I compared the C/C++ calls to the Pharo/NativeBoost calls more deeply and > found out that in C/C++ the following call for an object setting works (by returning 1): > > > // this returns 1 in C/C++ which is OK > int a = wkhtmltopdf_set_object_setting(os, "page", "http://www.google.de"); > printf("object set %i",a); > > > while in Pharo the same call fails (by returning 0): > > "The following call failed and returns 0 instead of 1" > self setObjectSetting: 'page' to: 'http://www.google.de' in: os. With argument type char * , NB does not 0-terminate your strings, but passes in the argument you provided raw. ByteStrings have an internal representation size a multiplum of 4, thus âpageâ will have no accidentally terminating 0, while âoutâ does, and the call fails since whatever garbage bytes are in the image after the string instance (âpageâ) leads to the it not being recognized as a valid property name. Change the call definitions to use String as argument type instead, and NB will convert the args to zero-terminated strings for you: NBFFICallout stdcall: #(int wkhtmltopdf_set_object_setting(wkhtmltopdf_object_settings* settings, String aName, String value)) module: 'wkhtmltox.dll' Alternatively, you need to provide null-terminated strings yourself: x := self setObjectSetting: ('page' , (Character value: 0) asString) to: 'http://www.google.de', (Character value: 0) asString) in: os. Which also returns makes it return 1. Cheers, Henry

May 23, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Sergi Reyner

2014-05-22 6:56 GMT+01:00 Freemail <nicolaihess(a)web.de>: > Are we talking about the update menu item > in the system menu? > Yes. > I don't understand this discussion, I always use > this menu item for updating the image. > I thought this is the nomal way. > So did I when I first discovered Pharo. > And I never had any problems with that . > You are a very lucky person :D (maybe it works because I use it regulary) > Even if that was a solution, itÂ´s not good enough.. > How do you keep the image up to date? > I would answer "by using the system update, which, sadly, may or may not work for you at any particular point in time with any particular image". Somebody else may answer "make configurations for your packages and set up a CI job to create images for you". Which is *not* updating the image at all. Cheers, Sergi

May 23, 2014

Re: [Pharo-dev] NativeBoost and WKHTML

by Markus Fritsche

On 23.05.2014 02:36, Torsten Bergmann wrote: > With that info I compared the C/C++ calls to the Pharo/NativeBoost calls more deeply and > found out that in C/C++ the following call for an object setting works (by returning 1): > while in Pharo the same call fails (by returning 0): > I tried to use another DLL which required me to change "stackAlignment" on Windows to answer 16 instead of 1; running on Win7 64 Bit. Could your problem be caused by something like that? (Just a shot in the dark). Best regards, Markus

May 23, 2014

Re: [Pharo-dev] Wanna to browse your code as a Disneyland ride?

by Serge Stinckwich

Always inspiring ! I had the same idea with Calder: https://www.youtube.com/watch?v=SE1vuCy8q44 be able to switch from one view showing the agents in a spatial environment to another one more focus on the network communication. I made a short demo if you remember during last MOOSEDAY in Lille. Regards, On Thu, May 22, 2014 at 5:37 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Here is an early preview of what we are working on... > https://vimeo.com/96091089 > > To be announced at ESUG... > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 23, 2014

Re: [Pharo-dev] NativeBoost and WKHTML

by Torsten Bergmann

Hi Jan, I did not compile the WKHTML component, just used the predefined DLL from the website. I know that there is no C++ interfering as the DLL has a normal C interface. So no C++ calling convention stuff/name mangling etc. is involved, no SWIG required or additional C wrapper. One can download and use the DLL as a usual C DLL like many others. So C/C++ was only involved because after the mentioned single Pharo/NB call failed and I could not see the reason in my code I wanted a Pharo independent non-smalltalk calling example to prove that the DLL is working. Could have used any other language (Java, VB, ...) to call the WKHTML DLL. So I use the DLL as a black box, similar like any other API where you do not have the source code. Debugging the DLL or modifying its source code by adding debug outputs would mean to go through all the hazzle of compiling WKHTML myself. According to the website this would also additionally require many tools (Perly, Python, Windows SDK, VisualStudio, ...) which I do not have installed. Way too much effort as I only thought it would be a nice idea if we could provide a Pharo binding to print something easily from Pharo using HTML -> PDF. As you see on the calling example WKHTML is simple and straightforward with an init, put some settings (file/URL) and calling the conversion. I also think that the route to debugging the DLL would be questionable - my simple non-Smalltalk calling example proves that the DLL is properly working as the website states. So according to this the problem must be on the Pharo wrapper or NativeBoost side who calls the component. Therefore I looked at my wrapper code again and again - nothing suspicious. Thats why I asked: either I'm blind to "not see the forest because of the all the trees" or there is still some bug left in NB. Maybe there is also an easy way to check/compare the calls. Thanks T. > Gesendet: Freitag, 23. Mai 2014 um 12:11 Uhr > Von: "Jan Vrany" <jan.vrany(a)fit.cvut.cz> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] NativeBoost and WKHTML > > Hi, > > If I were to debug this, I would: > > 1 ) make sure there's no C++ interfering, try to compile using C > compiler (not C++, I guess you run Windows and MSVC, I think > there's command line option to process file as C). > If not possible, wrap all methods you want to call form St > in extern "C" {} block. Does it work? If not, then C++ compiler > is doing it's magic which NB doesn't. > > > 2 ) If it does, run whole thing under debugger, set breakpoint to > the faulty function and check that arguments are correct > and what's return value. > If args are incorrect, then the problem is in either yours or > NB's code. > If return value is correct, then the problem is also in > either yours or NB's code. > If the return value is incorrect, well then the problem could be > either in the library or some sort of GC thing as GC moves stuff > around, which most of C/C++ libraries don't like much. > > In that case, I learned, the only way us to read library's code > and single-step through it to see that the code actually does with > data you pass down. > > HTH, Jan > > > > On 23/05/14 10:51, Torsten Bergmann wrote: > > Hi Jean, > > > > thanks for answering. I dont think that the convention is an issue here: internally > > it is written in C++, but it exposes the API as simple C functions. The calls with NB > > work (even the callbacks). > > > > What confuses me most is that the call to "wkhtmltopdf_set_global_setting" > > works while the "wkhtmltopdf_set_object_setting" does not. They have exactly > > the same signature and are called one after the other. First one returns proper int 1 (success) > > as in the non-Smalltalk example, the other one 0 which means it failed. > > > > There is no magic in the Pharo code, just simple calls. Also the non-Smalltalk example > > proves that the component is working. Maybe a side effect of NativeBoost itself? > > > > Looks like so far I'm lost without the help of Igor here... > > > > Thx > > T. > > > > > > > > Gesendet: Freitag, 23. Mai 2014 um 11:31 Uhr > > Von: "Jean Baptiste Arnaud" <jbaptiste.arnaud(a)gmail.com> > > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Betreff: Re: [Pharo-dev] NativeBoost and WKHTML > > > > I think this is because it is a C++ lib. > > NativeBoost cannot be used with C++ lib. > > It is a problem of call convention that is not the same from C to C++. > > As I discuss with some people it seems be a complexe problem, each C++ compiler seems have it own convention. > > But Igor can maybe be more accurate about that. > > A C wrapper to call C++, which should work. > > > > > > > > On 23 May 2014, at 02:36, Torsten Bergmann <astares(a)gmx.de> wrote: Hi, > > > > as there was no responded so far I tried to track the problem deeper and did a short test > > client in C/C++ to verify if I can call WKHTMLTOPDF there and generate a PDF and to > > compare to the Pharo/NativeBoost client. > > > > Attached is the according CPP file which works and results in a PDF with the google > > homepage. > > > > I also additionally implemented the callback functions in the Pharo wrapper and > > using the error handling I noticed that the component returns "Failed loading page http:// ..." > > > > > > With that info I compared the C/C++ calls to the Pharo/NativeBoost calls more deeply and > > found out that in C/C++ the following call for an object setting works (by returning 1): > > > > > > // this returns 1 in C/C++ which is OK > > int a = wkhtmltopdf_set_object_setting(os, "page", "http://www.google.de[http://www.google.de]"); > > printf("object set %i",a); > > > > > > while in Pharo the same call fails (by returning 0): > > > > "The following call failed and returns 0 instead of 1" > > self setObjectSetting: 'page' to: 'http://www.google.de'[http://www.google.de'] in: os. > > > > I checked how I wrapped this API call again and again - it is fine from my side: > > > > setObjectSetting: aName to: value in: settings > > > > <primitive: #primitiveNativeCall module: #NativeBoostPlugin> > > > > ^NBFFICallout stdcall: #(int wkhtmltopdf_set_object_setting(wkhtmltopdf_object_settings* settings, char* aName, char* value)) module: 'wkhtmltox.dll' > > > > and I still have no idea why it fails. > > > > Especially because "wkhtmltopdf_set_object_setting" function is not different from "wkhtmltopdf_set_global_setting" which is exactly the same way wrapped, works > > and returns 1 in exactly the same example. > > > > I would really appreciate if someone could have a second look... > > > > To reproduce on Windows: > > > > 1. Download the 32 bit version of WKHTML from http://wkhtmltopdf.org[http://wkhtmltopdf.org] and install it > > 2. Copy the "wkhtmltox.dll" to either the folder of the VM executable > > or the Windows directory so it can be found > > 3. Load the package WKHTML2PDF-Core-TorstenBergmann.7 > > from http://smalltalkhub.com/#!/~TorstenBergmann/WKHTML2PDF[http://smalltalkhub.… into Pharo 3.0#30848 > > 4. Check the Transcript while evaluating: > > > > WKPDFLibrary example > > > > One can see that within this code #setObjectSetting:to:in: fails while #setGlobalSetting:to:in: > > works. > > > > Maybe I just do not see the obvious. Help is appreciated. Thanks in advance! > > > > bye > > T. > > > > > > <main.cpp> > > > > Best Regards > > Jean Baptiste Arnaud > > jbaptiste.arnaud@gmail.com[jbaptiste.arnaud@gmail.com] > > > > > > > > > > >

May 23, 2014

Re: [Pharo-dev] OSProcess tests (was: Coral is green)

by David T. Lewis

On Fri, May 23, 2014 at 11:20:18AM +0200, phil(a)highoctane.be wrote: > On Fri, May 23, 2014 at 5:12 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: > > > On Wed, May 21, 2014 at 04:35:33PM +0200, Stephan Eggermont wrote: > > > PetitParser 1.6 instead of 1.5. > > > Tests only work when no Nautilus browser is open. Some notification > > problem when creating classes. > > > > > > OSProcess ci has lots of failing tests, so we don't know if it actually > > works??? > > > > > > Diego & Stephan > > > > The tests for OSProcess require VM support. Until recently, an interpreter > > VM was > > required to run the full OSProcess test suite because it relies heavily on > > #forkSqueak > > to generate cooperating VM processes for the tests. > > > > Eliot has recently added an enhancement to Cog that provides the required > > support. When > > that change is added to the Pharo VM, the tests will run. > > > > The changes are in SVN in branches/Cog/platforms/unix/vm/ and the commit > > notice is at: > > > > > > http://lists.squeakfoundation.org/pipermail/vm-dev/2014-March/014964.html > > > I experienced that PipeableOSProcess broke after calling in for a given > amount of invocations. > > Having a solid OSProcess thing in Pharo is really a must have... > > Are those changes only in a plugin? That I can integrate. > Hi Phil, No, the change I am referring to is part of the main VM, not OSProcess or OSProcessPlugin. Can you describe the problem that you had with PipeableOSProcess? I am guessing that you may have been doing something that resulted in unclosed file handles, which eventually will cause a failure when the OS resource limits are exceeded. Dave

May 23, 2014

Re: [Pharo-dev] Clarifications with small lint rules

by Yuriy Tymchuk

Ha, Iâve found the solution. Something around this lines: checker := SmalllintManifestChecker new rule: rules; environment: env; run. (rules leaves collect: [ :rule | rule -> (checker criticsOf: rule) ] thenReject: [ :assoc | assoc value isEmpty ]) asDictionary Uko On 22 May 2014, at 17:27, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > No. not really. > > There are just 4 implementors only, in RBBasicLintRule, RBTransformationRule and RBCompositeLintRule. > > Maybe I've added something to environment, I don't really remember, it's a long time ago when worked on this and since then it just works :-) > > If you'd like more convenient way to browse the code, you may want to > download and run St/X and look at it in browser: > > https://swing.fit.cvut.cz/projects/stx-jv/wiki/Download > > SmallLint is pre-loaded. > > Jan > > > On 22/05/14 16:18, Yuriy Tymchuk wrote: >> Hi Jan, >> >> in #failedMethods: you use #failedMethodsInto: which is abstract. So the idea is that in each rule gets methods from itâs result? >> >> Uko >> >> >> On 22 May 2014, at 17:03, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: >> >>> Yeah, >>> >>> all the refatory stuff has weird API and SmallLint ones are of the weirdest. The design is bit unfortunate. >>> You may want to have a look how I did it: >>> >>> RBLintRule>>failedMethods, RBLintRule>>failedClasses >>> >>> source code's here: >>> http://www.exept.de/cgi-bin/viewvc.cgi/stx/goodies/refactoryBrowser/lint/RB… >>> >>> Best, Jan >>> >>> >>> On 22/05/14 15:49, Yuriy Tymchuk wrote: >>>> Hi guys, >>>> >>>> so Iâm experimenting with rules, and I have one simple question: how do I get a collection of items from some environment which violate some rule? >>>> >>>> i know that I can send #runOnEnvironment: to the rule itself and then it will use a checker to run the rule on the environment. But later I end up with the rule itself. I know that I can get all atomic rules from composite rule by sending #leaves, and there is #result method that returns environment. But there is no single way to get items from environment, and all accessors are environment-specific. Am I doing something wrong? Because Iâve spent half of a day to find out how to run a rule and get violations :). >>>> >>>> Cheers. >>>> Uko >>>> >>> >>> >> >> >> > >

May 23, 2014