November 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] NativeBoost Dev

by Luc Fabresse

Hi all, 2012/11/6 Igor Stasenko <siguctua(a)gmail.com> > On 2 November 2012 06:05, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Igor, > > > > in Win32 often one passes NULL as argument > > (for instance if a function has an argument "handle to a window", then > > a hWnd of NULL can be given). > > > > For instance when I have > > > > shellExecute: hwnd operation: lpOperation file: lpFile parameters: > lpParameters directory: lpDirectory show: nShowCmd > > <primitive: #primitiveNativeCall module: > #NativeBoostPlugin> > > > > ^ self nbCall: #( > > HINSTANCE ShellExecuteA( > > HWND hwnd, > > LPCTSTR lpOperation, > > LPCTSTR lpFile, > > LPCTSTR lpParameters, > > LPCTSTR lpDirectory, > > INT nShowCmd)) module: 'Shell32.dll' > > > > usually it controlled by options for code generator > like #optCoerceNilToNull > which will allow you to pass nil as valid argument. > > What is missing, is that in your case you passing an instance of > NBExternalObject, > and NBExternalObjectType converter does not honors that option. > This is easy to fix. I will add it as time allows me to do a pass on > NativeBoost. > > > > > The NBFFICallout class(NBNativeCodeGen > class)>>handleFailureIn:nativeCode: > > tells me that "an instance of NBWin32Window" is expected. > > > right, so what you can do is to synthesize an instance of > NBWin32Window with handle value == 0. > This will effectively behave as if you passed null argument. Sure it > is not nearly elegant, so i mentioning it > just for protocol :) > > > > So currently I have to pass "NBWin32Window getFocus" as first > > argument. But often this is not necessary. > > > Another way of doing this is use convenience methods. Like with your > function, > you could have two methods for it, one which takes window argument, > and another which doesn't: > > > shellExecute: lpOperation file: lpFile parameters: lpParameters > directory: lpDirectory show: nShowCmd > > ^ self nbCall: #( > HINSTANCE ShellExecuteA( > 0, > LPCTSTR lpOperation, > LPCTSTR lpFile, > LPCTSTR lpParameters, > LPCTSTR lpDirectory, > INT nShowCmd)) module: 'Shell32.dll' > yes I like this NB feature of directly put real values in external call definitions. But, having a NULL constant could also makes sense: ^ self nbCall: #( HINSTANCE ShellExecuteA( NULL, LPCTSTR lpOperation, LPCTSTR lpFile, LPCTSTR lpParameters, LPCTSTR lpDirectory, INT nShowCmd)) module: 'Shell32.dll' perhaps NULL is already there somewhere, I never look for it ;-) Luc > like that, you exposed API in proper way, i.e. without forcing users > to pass meaningless nils every time :) > and of course, in a second form (one which takes window handle as > argument), you would expect a valid window handle, but not > nil/null/whatever. That way it makes things less error prone. > > > I also havent found a constant pool with NULL or an accessor. > > Whats the prefered way to deal with NULL in NB? > > > > > > Can you also please add me as a developer > > to http://www.squeaksource.com/NativeBoost > > My initials are "tbn" > > > done. > > I would like to add several API functions for > > Win32 (ShellExecute, OutputDebugString, ...) > > > go ahead :) > > > Thx > > Torsten > > > > -- > Best regards, > Igor Stasenko. > >

Nov. 6, 2012

[Pharo-project] Manifest integration update failing

by Camillo Bruni

how did the 20382 update work on the build server? If I try to update an older image I get a warning when ((Smalltalk at: #ConfigurationOfManifest) project version: #stable) load. is evaluated: "No version found for #stable of ConfigurationOfRefactoringBrowser"? best cami

Nov. 6, 2012

[Pharo-project] [ANN] Pharo Online Help 1.0

by Torsten Bergmann

Hi, a little story: As you may know I wrote the current "Pharo help" implementation which you can access from the Help menu or via HelpBrowser open I'm still not satisfied with it. Some projects like NativeBoost, Metacello and others already provide an appropriate help package - but still beginners help and documentation is not where I would like to see it. The HelpBrowser is only usable within the image and other nice docu (blog posts, videos, ...) for Pharo is available online. You have to know about these pages after downloading Pharo to find the tips and tricks and nice features of the Smalltalk world. There is also no central "docu" point for someone who just downloaded Pharo and want a "Quick start". Also I dislike that we are limited with the in-image presentation style (text only) and that content is not visible to Google, Bing, etc. That made me think about web/HTML/Internet like documentation again and the image as the central place beginners have downloaded already. After many years of private research I now noticed that HTML is nothing more than a structured String - so I started coding... :) Packaging Seaside with the default Pharo image to serve help content would be overkill - but there is always a leaner way. Since Pharo 2.0 we have Zinc HTTP components within the image (thanks Sven!) and I played a little bit with it. It is really easy to setup/startup a webserver from Smalltalk now. So I wrote a basic "HelpServer" and wrapped the nice "twitter bootstrap" library. Code may be ugly and require some refactoring ... but it is currently more a prove of concept. Attached is a screenshot of the result running in a webbrowser. What is it: the idea is that we server the documentation from within the image but use the local webbrowser to display it. Since we soon integrate NativeBoost in Pharo 2.0 it is also easy to open the browser as soon as "Help" is requested from a menu. Serving for the web would also mean we could easily setup an image online that displays the docu online for indexing by search engines etc. Where is the code: http://ss3.gemstone.com/ss/PharoOnlineHelp.html (Read/Write) If you want to play with it yourself then start a Pharo 2.0 image, go to "Tools" -> "ConfigurationBrowser", select "PharoOnlineHelp" and select "Install configuration (stable version)" from the context menu. After that evaluate HelpServer start and point your browser to http://localhost:8080 If you like scripting you can also evaluate in a Pharo 2.0 image: -------------------------------------------------------------------------------- Gofer it squeaksource3: 'PharoOnlineHelp'; package: 'ConfigurationOfPharoOnlineHelp'; load. ((Smalltalk at: #ConfigurationOfPharoOnlineHelp) project version: #stable) load. (Smalltalk at: #HelpServer) start -------------------------------------------------------------------------------- Next steps: =========== 1. Lets discuss how we want to fill the "API help" section. I know that there once was a project that generated static API help (http://magaloma.seasidehosting.st) but we can now directly serve from the live image. My current implementation allows to navigate from classes to subclasses and superclasses - just to give you an idea. Maybe we want to display only class comments or provide a real Smalltalk browser within the webbrowser (similar to http://www.Amber-lang.net) 2. The section "Intro" is only a mock. I would like to see that people can find short "Quick start" like tutorials here to start with basic things like Smalltalk, Metacello, ... Maybe we can integrate a live and running ProfStef similar to http://amber-lang.net/learn.html that is adopted to Pharo. 3. Lets discuss how we want to describe the content "in-image" for "serving on the web". Maybe with a "Markup to HTML translator" - or a "WikiStyle to HTML" like help My wish to Santa would be that Pharo 2.0 comes with a better and nicer out-of-the-box documentation. For each package/project we should have a common way to define/load/browse docu and tutorials so people can just load and quick start without much hazzle. The code repo is open for read and write - I would appreciate comments, code contributions, help/tutorial content and ideas. Thanks Torsten

Nov. 6, 2012

Re: [Pharo-project] [NativeBoost] pass an array of args to external function

by Igor Stasenko

On 6 November 2012 17:57, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > This is clearly something to add to the documentation of NativeBoost. > Igor can you do it? I already have a description of memory management API for NB in docs. And telling how manage external memory is... ahem.. not really fits into docs :) Maybe a tutor or something. -- Best regards, Igor Stasenko.

Nov. 6, 2012

Re: [Pharo-project] Unable to use Monticello in last images from Jenkins

by Camillo Bruni

well let's debug it together in 10 days ;) that's going to be easier ;) On 2012-11-06, at 14:00, Guido Chari <charig(a)gmail.com> wrote: > Sorry for the late answer. > > > 2012/11/2 Camillo Bruni <camillobruni(a)gmail.com> > >> >> On 2012-11-01, at 15:58, Guido Chari <charig(a)gmail.com> wrote: >> >>> Both tests succeed. >> >> grml, maybe squeaksource falls under the argentinian import restriction >> as some sort of luxury goods :P >> > > Jeje. I don't think so, but.... > > > >> >> Ok so another try with zinc? >> >> ZnClient new >> systemPolicy; >> url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main'; >> setAcceptEncodingGzip; >> beOneShot; >> get >> > > Failed. > > >> >> >> could there be a problem with zip support in your image/vm? >> Can you run all the Compression tests? >> >> > Have only zip tests and they are green. > > >> thanks >> cami >> >> > I'm starting to think this may be something strange proxy blocking for gzip > content but it would be extremely strange. > > Guido > > > >>> I couldn't read at home so i couldn't test it without the proxy but i'm >>> "almost sure" the proxy is not explaining the issue. >>> >>> >>> >>> 2012/11/1 Camillo Bruni <camillobruni(a)gmail.com> >>> >>>> could you try the following "benchmarks" >>>> >>>> >>>> >> http://dev.nuclearrooster.com/2009/11/08/checking-gzipdeflate-server-respon… >>>> >>>> with the following urls (just 2 projects): >>>> http://smalltalkhub.com/mc/estebanlm/Voyage/main >>>> http://squeaksource.com/NativeBoost/ >>>> >>>> both support gzip answers without problems. >>>> >>>> On 2012-10-31, at 23:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> Would it be possible to test without the transparant proxy ? >>>>> From another location, like from home ? >>>>> If this would fail for everyone, we would have heard about it much >>>> sooner. >>>>> >>>>> On 31 Oct 2012, at 22:27, Guido Chari <charig(a)gmail.com> wrote: >>>>> >>>>>> Yes, since a couple of weeks i can't. I'm on a Unix now behind a >>>> transparent proxy. Same Vm, on same machine, behind the same proxy, no >>>> problem if strip out the gzip header from the packet. >>>>>> >>>>>> I'm using a custom personalized VM. But the only thing that is >>>> generating the error is the gzip header option on the http packet. Is >> that >>>> option deeply related or coupled to the vm? BTW, the error is a 400 from >>>> the server so i don't believe so. >>>>>> >>>>>> No one else experimenting the same as me? >>>>>> >>>>>> >>>>>> >>>>>> 2012/10/31 Camillo Bruni <camillobruni(a)gmail.com> >>>>>> You say you cannot download from squeaksource in the latest 2.0 image? >>>>>> >>>>>> We use that regularly, for instance for the NativeBoost build, >>>>>> and everything works fine (win / linux / mac) >>>>>> >>>>>> That leaves me quite puzzled about the real cause of this bug... >>>>>> >>>>>> >>>>>> On 2012-10-31, at 21:47, Guido Chari <charig(a)gmail.com> wrote: >>>>>>> Hi, >>>>>>> >>>>>>> Since a couple of weeks i'm have not been able to download packages >>>> with >>>>>>> Metacello on last image versions from Jenkins. >>>>>>> >>>>>>> Today i found that if i revert changes on httpClient method from >>>>>>> MCHttpRepository everything works fine again. >>>>>>> >>>>>>> I haven't research deeply on why, i'm not an expert on Zinc, but the >>>>>>> message that is breaking everything and making my image to receive a >>>> 400 >>>>>>> error from squeaksource is setAcceptEncodingGzip that is addinng the >>>> gzip >>>>>>> header to the requests. >>>>>>> >>>>>>> As i said, i haven't going to deep with this but as i am the only one >>>> who >>>>>>> is watching this behavior perhaps is something only for squeaksource. >>>>>>> >>>>>>> If this is actually an issue and not some fault from myself, and >>>> someone >>>>>>> give me some help, i can help with the solution. >>>>>>> >>>>>>> Cheers, >>>>>>> Guido. >>>>> >>>>> -- >>>>> Sven Van Caekenberghe >>>>> http://stfx.eu >>>>> Smalltalk is the Red Pill >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >> >> >>

Nov. 6, 2012

Re: [Pharo-project] Fixing the StackInterpreterSimulator for Pharo 1.4

by StÃ©phane Ducasse

> Hi: > > The attached change set fixes bit rot in the StackInterpreterSimulator and related classes. > > Here a brief summary: > > - VMClass>>#doOrDefer: now uses ProcessBrowser>>#isUIProcess: instead of Project > - it replaces the use of #asDisplayText with StringMorph>>#contents:. > - use of ThreadStream>>#on: is replaced with ThreadSafeTranscript>>#new > - Utilities is replaced by UIManager>>#default > - and #primitiveGetAttribute now uses the non-depricated `Smalltalk vm getSystemAttribute: attr` > > For the last change, I wonder whether that's going to work, because that code is going to be translated to C, right? > > > Is anyone interest in these changes? yes! > Should I also fix the other simulators? it would be great! > With them, I can load a Pharo 1.2.1 image in the simulator, I wasn't patient enough to wait for a 1.4 image to complete loading. > > | sim | > InterpreterStackPage initialize. > sim := StackInterpreterSimulator new. > sim openOn: '/.../Downloads/Pharo-1.2.1-11.04.03/Pharo-1.2.1.image'. > sim openAsMorph. > [ sim run ] fork. > > Best regards > Stefan > > > <Fix simulator.1.cs> > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 >

Nov. 6, 2012

Re: [Pharo-project] [Pharo-users] Pharo consortium agreement

by Tudor Girba

This is excellent work. Congratulations for pulling it through! Doru On 6 Nov 2012, at 19:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Very good that there is progress on this front ! > > Even better news about Igor ;-) > > Indeed: thank you INRIA for sponsoring Pharo. > > I will read the document this evening. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > On 06 Nov 2012, at 17:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Dear Pharoers >> >> Here is the result of the work we did around the consortium for Pharo for about 2 years. We took into account all your remarks over the years >> and we think that the result is good and corresponds to what the community can support. >> This consortium is important for Pharo's future and it will help us to deliver a system to help you making business. >> Our goal is to be able to collect fundings to pay at least one full time engineer. >> >> The idea is that all the consortium members will sign the same agreement. We will not handle modifications per partners. >> Now since we are starting the process if you spot some glitches on the form let us know. We can discuss and fully stabilize one version. >> >> We suggest to read the document. >> - If you agree to sign it and send it to us (in two copies if you do it by surface mail at >> INRIA - S. Ducasse - Pharo, 40, avenue Halley, Parc Scientifique de la Haute Borne, >> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.), so that we sign it too. >> - Don't forget to complete your legal mention on first page and your contact details on article 14 before signing. :) >> >> We will launch soon two web sites: >> - one for the Pharo user association and >> - one for the Pharo consortium. >> >> >> A side note: we will communicate about it later and separately but Inria decided to support the consortium by paying one extra year to Igor Stasenko. >> This is around 60 Keuros in addition to the year of Esteban Lorenzano and previous years of Igor. >> >> I really want to thank Inria for the constant support and the work of S. Karpf, P. Moreau and S. Perin. >> >> Stef >> >> <2012-11-06-consortium PHARO.pdf> >> >> >> >> >> ------------------------ >> Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) >> INRIA - USTL - CNRS UMR 8022 >> stephane.ducasse(a)inria.fr >> http://stephane.ducasse.free.fr >> http://rmod.lille.inria.fr/ >> **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 >> >> 40, avenue Halley, Parc Scientifique de la Haute Borne, >> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France. >> >> >> >> >> >> >> > > -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

Nov. 6, 2012

Re: [Pharo-project] [NativeBoost] pass an array of args to external function

by StÃ©phane Ducasse

This is clearly something to add to the documentation of NativeBoost. Igor can you do it? Stef On Nov 6, 2012, at 6:34 PM, Igor Stasenko wrote: > On 6 November 2012 11:23, Max Leske <maxleske(a)gmail.com> wrote: >> Thanks Igor. >> >> I meant a pointer to an array, sorry. Here's the function prototype: >> >> int run_command(const char *command, char *argv[]); >> >> I could then simply pass this to execve like so: >> >> status = execve(command, argv, envp); >> > so, like i said, prepare a buffer which will hold strings, i.e. > > buffer := NativeBoost allocate: (numArgs * 4). > arg1ptr := NativeBoost allocate: arg1 size+1. > > NativeBoost memcopy: arg1 to: arg1ptr size: arg1 size. > arg1ptr nbUInt8At: arg1 size put: 0. "terminating null char" > > buffer nbUInt32At: 0 put: (arg1ptr value). > > something like that. > (and then , of course free memory after you no longer need it :) > >> >> >> On 06.11.2012, at 15:12, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> well, you have to decompose it to >>> fn(arg1, arg2, arg3 ... ) >>> >>> because NB does not supports vararg functions. >>> >>> But if function takes a pointer to array, then you can just use >>> external memory buffer and fill it with >>> anything you want. >>> What exactly function you wanna use? >>> >>> On 6 November 2012 11:06, Max Leske <maxleske(a)gmail.com> wrote: >>>> Hi >>>> >>>> Working with NativeBoost I'm trying to figure out if there is a way I can pass an array of arguments to a function like so: >>>> >>>> MyExample run: 'echo' args: { 'foo' }. >>>> >>>> >>>> nbRun: str args: args >>>> <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode > >>>> ^ self nbCall: #( int run_command (String str, Array args) ) module: 'librunner.dylib' >>>> >>>> The intention is of course to be able to pass arguments to execve() (for example). >>>> I guess I could simply parse a string on the C-side but I'd rather not. >>>> >>>> Any suggestions? >>>> >>>> Cheers, >>>> Max >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> > > > > -- > Best regards, > Igor Stasenko. >

Nov. 6, 2012

Re: [Pharo-project] now that squeaksource is back...

by StÃ©phane Ducasse

you can find Gofer scripts in the Gofer chapter. Stef >> Hi, >> >> I strongly recommend all of you to move your projects into one of the alternatives: >> >> http://smalltalkhub.com >> http://ss3.gemstone.com > > I would appreciate some guidance as to which of these is intended to > serve as the long term replacement for SqueakSource, and how specifically > I should go about migrating an existing project from SqueakSource to the > replacement system. > > Thanks, > Dave > >

Nov. 6, 2012

Re: [Pharo-project] Pharo 2.0 and Metacello preview

by Frank Shearar

On 6 November 2012 19:07, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 6 November 2012 16:00, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> On 6 November 2012 18:07, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> Basically, what is needed is: >>> VMs with OSProcess installed by default >>> Image(s) with OSProcess >>> >>> then Metacello Preview will be functional. >>> >>> The reason why , i personally want that, is >>> to be able to use git for monticello. and be able to store C sources >>> and smalltalk sources (VMMaker) in a single git repo. >> >> Igor, I assume then that neither Filetree nor Gitocello meet your >> needs? (Both map Monticello repositories to git.) >> > Well, one of the reasons why i want a preview is to figure that out: > does it fits or not, > and what/how it can be used. Right, I've jumped the gun then. You want Metacello Preview precisely so you can try out either/both/something else! frank >> frank >> > > -- > Best regards, > Igor Stasenko. >

Nov. 6, 2012