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

Bug in SmalltalkHub "delete package"

by Mariano Martinez Peck

Hi guys. I tried to remove a package from the "remove package" button in the website. The package is indeed removed from the website, but if you take a fresh image, add the repository and add it to monticello, you still can see and browse the removed package.... any idea how to solve it? I need to remove packages for real... thanks! -- Mariano http://marianopeck.wordpress.com

May 31, 2013

Re: [Pharo-dev] zeroconf --headless/-headless

by Camillo Bruni

yep we switched to --headless maybe we have to sit with esteban and add a compatibility option '-headless' again. The image-side of 2.0 and 3.0 are already prepared for that. Actually we changed all long options to use '--' like real unix commands :P On 2013-05-31, at 16:02, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > If I try to execute './pharo Pharo.image' after downloading the latest > Pharo Vm with the zero conf script it fails with the error: unknown option: > -headless. If I download the stable one it works. > > Cheers, > Andrei

May 31, 2013

Re: [Pharo-dev] Release Artefact 1.0, the PDF framework

by btc＠openinworld.com

Thats really great. I'll have to find some time to have a look at it. cheers -ben Guillaume Larcheveque wrote: > We are proud to announce that Artefact is available in 1.0 version. > > You can download it from: http://smalltalkhub.com/#!/~RMoD/Artefact > > Artefact is a framework to generate PDF documents. It is fully written in > Smalltalk and doesn't require any native library. Artefact is light, > platform independant and offer to users a high level of abstraction in > order to easily creating PDF documents. > > * completely written in Smalltalk (and only Smalltalk), > * complete freedom about the order of creation for pages, elements... (no > need to follow the document order) > * multi format and orientation for pages > * page composition based on reusables PDF elements, > * extensibility by offering a composition standard to create your own high > level elements > * styleSheet that can be reused in many documents and avoid wasting time > and place with duplication > * image support with the JPEG format > * pre-defined high level elements like datagrid > * support PDF compression to produce compact files > > A basic documentation is available in the help browser. Many examples are > implemented in the PDFDemos class. > >

May 31, 2013

Re: [Pharo-dev] Hosting your own SmalltlakHub: turning off/on the web

by Mariano Martinez Peck

Hi Nico, First, let me say that without a lot of pain, I have my own (actually, its for a client) SmalltalkHub instance running with Pharo 2.0, mongoDB, nginx and HTTPS :) Usually we need the web interface quite infrequently, that is, when we create a new user or a new project. So I would like to turn off the website for most of the time and just turn it on when I need something like that. Of course when I mean turn off the website I mean that: only the website. Monticello should continue working :) One "solution" I found is that since I have nginx listening in an SSL port and then this is forwarded to the port zinc is listening, I can just turn off nginx. That way noone can reach the website from outside... but maybe there is a better solution... Thanks! -- Mariano http://marianopeck.wordpress.com

May 31, 2013

Re: [Pharo-dev] Release Artefact 1.0, the PDF framework

by Max Leske

Awesome guys! I'll have to take a look soon. Max On 31.05.2013, at 16:00, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Images are automatically built by a continuous integration job: > https://ci.inria.fr/pharo-contribution/job/Artefact/. > > On Fri, May 31, 2013 at 3:30 PM, Guillaume Larcheveque > <guillaume.larcheveque(a)gmail.com> wrote: >> We are proud to announce that Artefact is available in 1.0 version. >> >> You can download it from: http://smalltalkhub.com/#!/~RMoD/Artefact >> >> Artefact is a framework to generate PDF documents. It is fully written in >> Smalltalk and doesn't require any native library. Artefact is light, >> platform independant and offer to users a high level of abstraction in order >> to easily creating PDF documents. >> >> * completely written in Smalltalk (and only Smalltalk), >> * complete freedom about the order of creation for pages, elements... (no >> need to follow the document order) >> * multi format and orientation for pages >> * page composition based on reusables PDF elements, >> * extensibility by offering a composition standard to create your own high >> level elements >> * styleSheet that can be reused in many documents and avoid wasting time >> and place with duplication >> * image support with the JPEG format >> * pre-defined high level elements like datagrid >> * support PDF compression to produce compact files >> >> A basic documentation is available in the help browser. Many examples are >> implemented in the PDFDemos class. >> >> -- >> Olivier Auverlot and Guillaume Larcheveque >> > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

May 31, 2013

[update 3.0] #30177

by Marcus Denker

30177 ----- 10718 More commands for Node Navigation https://pharo.fogbugz.com/f/cases/10718 10411 flush after nextChunkPut: https://pharo.fogbugz.com/f/cases/10411 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/NodeNavigation-MarcusDenker.3… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Streams-MarcusDen…

May 31, 2013

zeroconf --headless/-headless

by Andrei Vasile Chis

Hi, If I try to execute './pharo Pharo.image' after downloading the latest Pharo Vm with the zero conf script it fails with the error: unknown option: -headless. If I download the stable one it works. Cheers, Andrei

May 31, 2013

Re: [Pharo-dev] Release Artefact 1.0, the PDF framework

by Damien Cassou

Images are automatically built by a continuous integration job: https://ci.inria.fr/pharo-contribution/job/Artefact/. On Fri, May 31, 2013 at 3:30 PM, Guillaume Larcheveque <guillaume.larcheveque(a)gmail.com> wrote: > We are proud to announce that Artefact is available in 1.0 version. > > You can download it from: http://smalltalkhub.com/#!/~RMoD/Artefact > > Artefact is a framework to generate PDF documents. It is fully written in > Smalltalk and doesn't require any native library. Artefact is light, > platform independant and offer to users a high level of abstraction in order > to easily creating PDF documents. > > * completely written in Smalltalk (and only Smalltalk), > * complete freedom about the order of creation for pages, elements... (no > need to follow the document order) > * multi format and orientation for pages > * page composition based on reusables PDF elements, > * extensibility by offering a composition standard to create your own high > level elements > * styleSheet that can be reused in many documents and avoid wasting time > and place with duplication > * image support with the JPEG format > * pre-defined high level elements like datagrid > * support PDF compression to produce compact files > > A basic documentation is available in the help browser. Many examples are > implemented in the PDFDemos class. > > -- > Olivier Auverlot and Guillaume Larcheveque > -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

May 31, 2013

Re: [Pharo-dev] Running coverage breaks the VM

by Frank Shearar

I'll have to give this a try once I've upgraded my machine. I only have GLIBC_2.11 and this requires GLIBC_2.15. Excellent news though! frank On 31 May 2013 14:17, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > It is fixed in latest vm (which you can get from the zeroconf script > http://get.pharo.org/vmLatest) :). > > Guille > > > On Fri, May 31, 2013 at 1:25 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 31 May 2013 09:20, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> > Ahh, that's why the code in CoInterpreter I was looking didn't match the >> > C >> > code :D. Was looking at the wrong place, hehe. >> > >> > Igor, why do you say that this method should be reached only with >> > vanilla >> > compiled methods? From the comment I understand >> > >> > "For interpreter performance and to ease the objectAsMethod >> > implementation eagerly >> > evaluate the primtiive, i.e. if the method is cogged and has a >> > primitive /do not/ evaluate >> > the machine code primitive, just evaluate >> > primitiveFunctionPointer >> > directly." >> > >> >> Yes, my bad.. >> It is hard to see that in code: the logic to handle objects-as-method. >> So, yes, please fix executNewMethod and internalExecuteNewMethod with >> this additional check. >> >> > And in #addNewMethodToCache: there is as a first statement: >> > >> > [...] >> > (objectMemory isOopCompiledMethod: newMethod) >> > ifTrue: >> > [primitiveIndex := self primitiveIndexOf: newMethod. >> > primitiveFunctionPointer := self functionPointerFor: primitiveIndex >> > inClass: >> > class] >> > ifFalse: >> > [primitiveFunctionPointer := #primitiveInvokeObjectAsMethod]. >> > [...] >> > >> > So I'd say that both objects as methods and primitives are kind of >> > handled >> > in the same way after? >> > >> > >> > >> > On Fri, May 31, 2013 at 2:27 AM, Igor Stasenko <siguctua(a)gmail.com> >> > wrote: >> >> >> >> On 30 May 2013 20:06, Guillermo Polito <guillermopolito(a)gmail.com> >> >> wrote: >> >> > Ok, I was playing with flushing caches and stuff... Its still a bit >> >> > obsure >> >> > to me why the example in the workspace works and the code coverage >> >> > doesnot. >> >> > >> >> > However, I managed to hack the VM to make it work :). >> >> > >> >> > It looks like the VM is treating the objects as methods, as cog >> >> > methods. >> >> > So >> >> > I added the following validation in the commonSend: >> >> > >> >> > methodHeader2 = longAt((GIV(newMethod) + BaseHeaderSize) + >> >> > (HeaderIndex >> >> > << >> >> > ShiftForWord)); >> >> > >> >> > if (isCogMethodReference(methodHeader2) && >> >> > isCompiledMethodHeader(methodHeader2)) { >> >> > >> >> > /* begin externalizeIPandSP */ >> >> > >> >> > assert((((usqInt)localIP)) != (ceReturnToInterpreterPC())); >> >> > >> >> > GIV(instructionPointer) = oopForPointer(localIP); >> >> > >> >> > GIV(stackPointer) = localSP; >> >> > >> >> > GIV(framePointer) = localFP; >> >> > >> >> > executeCoggedNewMethodmethodHeader(1, methodHeader2); >> >> > >> >> > } >> >> > >> >> > >> >> > And it works :). >> >> > >> >> > I cc Eliot, so maybe he has an idea... >> >> > >> >> I touched this code. >> >> >> >> Original: >> >> >> >> CoInterpreter>>internalExecuteNewMethod >> >> <inline: true> >> >> "For interpreter performance and to ease the objectAsMethod >> >> implementation eagerly >> >> evaluate the primtiive, i.e. if the method is cogged and has a >> >> primitive /do not/ evaluate >> >> the machine code primitive, just evaluate >> >> primitiveFunctionPointer directly." >> >> primitiveFunctionPointer ~= 0 ifTrue: >> >> [| succeeded | >> >> self isPrimitiveFunctionPointerAnIndex ifTrue: >> >> [^self internalQuickPrimitiveResponse]. >> >> "slowPrimitiveResponse may of course context-switch. >> >> If >> >> so we must >> >> reenter the >> >> new process appropriately, returning only if we've >> >> found >> >> an >> >> interpreter frame." >> >> self externalizeIPandSP. >> >> succeeded := self slowPrimitiveResponse. >> >> instructionPointer = cogit ceReturnToInterpreterPC >> >> ifTrue: >> >> [instructionPointer := self iframeSavedIP: >> >> framePointer]. >> >> self internalizeIPandSP. >> >> succeeded ifTrue: >> >> [self return: self popStack toExecutive: true. >> >> self browserPluginReturnIfNeeded. >> >> ^nil]]. >> >> "if not primitive, or primitive failed, activate the method" >> >> (self methodHasCogMethod: newMethod) >> >> ifTrue: [self iframeSavedIP: localFP put: localIP >> >> asInteger. >> >> instructionPointer := cogit >> >> ceReturnToInterpreterPC. >> >> self externalizeFPandSP. >> >> self activateCoggedNewMethod: true. >> >> self internalizeIPandSP] >> >> ifFalse: [self internalActivateNewMethod] >> >> >> >> Now in subclass (NBCoInterpreter) >> >> i made this: >> >> >> >> internalExecuteNewMethod >> >> <inline: true> >> >> "For interpreter performance and to ease the objectAsMethod >> >> implementation eagerly >> >> evaluate the primtiive, i.e. if the method is cogged and has a >> >> primitive /do not/ evaluate >> >> the machine code primitive, just evaluate >> >> primitiveFunctionPointer directly." >> >> >> >> | methodHeader | >> >> >> >> methodHeader := self rawHeaderOf: newMethod. >> >> >> >> (self isCogMethodReference: methodHeader) ifTrue: [ >> >> self externalizeIPandSP. >> >> self executeCoggedNewMethod: true methodHeader: >> >> methodHeader. >> >> "we never reach here" >> >> ]. >> >> >> >> primitiveFunctionPointer ~= 0 ifTrue: >> >> [| succeeded | >> >> self isPrimitiveFunctionPointerAnIndex ifTrue: >> >> [^self internalQuickPrimitiveResponse]. >> >> "slowPrimitiveResponse may of course context-switch. >> >> If >> >> so we must >> >> reenter the >> >> new process appropriately, returning only if we've >> >> found >> >> an >> >> interpreter frame." >> >> self externalizeIPandSP. >> >> succeeded := self slowPrimitiveResponse. >> >> instructionPointer = cogit ceReturnToInterpreterPC >> >> ifTrue: >> >> [instructionPointer := self iframeSavedIP: >> >> framePointer]. >> >> self internalizeIPandSP. >> >> succeeded ifTrue: >> >> [self return: self popStack toExecutive: true. >> >> self browserPluginReturnIfNeeded. >> >> ^nil]]. >> >> "if not primitive, or primitive failed, activate the method" >> >> (self methodHasCogMethod: newMethod) >> >> ifTrue: [self iframeSavedIP: localFP put: localIP >> >> asInteger. >> >> instructionPointer := cogit >> >> ceReturnToInterpreterPC. >> >> self externalizeFPandSP. >> >> self activateCoggedNewMethod: true. >> >> self internalizeIPandSP] >> >> ifFalse: [self internalActivateNewMethod] >> >> >> >> === >> >> The intent of change was: >> >> - if method is cog method, execute it (the jited code takes care to >> >> call primitive, if it there) >> >> >> >> The old code logic was: >> >> - run primitive if it there >> >> - and only then, if no prim/or prim failed, try to run a jited code >> >> (but entry point is to the first bytecode of method, >> >> not to its start) >> >> >> >> This (old) logic prevents from using primitive 220 properly, because >> >> it is a "meta-primitive" - a marker >> >> that says that given method should: >> >> - always be jited >> >> - actual primitive is taken by copying machine code from compiled >> >> method trailer into CogMethod's primitive section. >> >> Therefore executing prim 220 (a C function) ~~ invoking method's >> >> primitive (a machine code generated by image). >> >> >> >> Still i cannot understand why code reaching this point, when a result >> >> of lookup is not a compiled method, but arbitrary object, because >> >> everything even in original code says: VM enters this method only if >> >> it found 100% vanilla guaranteed CompiledMethod, and not something >> >> which pretends to be it. >> >> As i understand , the logic to handle object-as-method is in method >> >> lookup.. but not in internalExecuteNewMethod, because VM can "execute" >> >> the only thing it knows, and it is CompiledMethod. >> >> >> >> Your test says, that Cog does something extra (some magic, which i >> >> failed to grasp) with object-as-method, >> >> like generating special kind of CogMethod which sends #run:as:in: >> >> message >> >> to it. >> >> >> >> I would like to hear Eliot's comments on this. >> >> >> >> >> >> >> >> -- >> >> Best regards, >> >> Igor Stasenko. >> >> >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >

May 31, 2013

Re: [Pharo-dev] Lowecase class names

by Marcus Denker

On May 31, 2013, at 1:32 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > Hi > > is there any reason why class builder does not allow lowercase > classnames? Underscore is allowed, though. > In the past people started too add check to make sure that we only use the naming that people are supposed to use. The place these checks where placed was the class builder. Over time it has shown that this is not good: it has do be done on a higher level. (we already removed certain checks, e.g. about variable capitalization). We should at some point introduce something that does these kinds of checks for the tools, but allows one to just do anything when needed at the lower levelâ¦ Marcus

May 31, 2013