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

[Pharo4] Properties for classes

by Marcus Denker

Hi, Methods, AST Nodes and all Ring Definitions can store properties. Now in Pharo4 update 307, Yuriy Tymchuk extended this idea to Behaviors. They are not stored when saving code (filing out or MC), as this would be on top (as are the Pragmas on Methods build on top of properties). TODO -> unify API across RB/CompiledMethod/Ring -> add properties to the Variable meta-objects (there is already a proof-of-concept in class LinkWrapper for one special kind of property) -> For sure there are bugs (while writing this I had one idea of one alreadyâ¦ need to check) This will not be used by the system itself for now, therefore we opted to store them not in an ivar but a classVar dictionary, so they do not take any space when not used (like CompiledMethod properties where realised in the beginning, too). Marcus

Oct. 15, 2014

Re: [Pharo-dev] creating custom browsers out of GTInspector extensions

by Hilaire

Le 14/10/2014 23:26, Tudor Girba a Ã©crit : > Now, that more people are playing with the GTInspector, I would like to > raise another point that might otherwise go unnoticed: The inspector > extensions do not only work in the inspector, but can also be combined > in other browsers as well. > It really looks intersting! I can imagine some good use of it to navigate in geometric objects. Thanks Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Oct. 15, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40307 Home: https://github.com/pharo-project/pharo-core

Oct. 15, 2014

[pharo-project/pharo-core] 436ad6: 40307

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 436ad6373a606492b003f3a2aa13db8772dc9d85 https://github.com/pharo-project/pharo-core/commit/436ad6373a606492b003f3a2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-15 (Wed, 15 Oct 2014) Changed paths: M Kernel.package/Behavior.class/class/class initialization/initialize.st A Kernel.package/Behavior.class/class/class initialization/initializeClassProperties.st M Kernel.package/Behavior.class/definition.st A Kernel.package/Behavior.class/instance/accessing-properties/properties.st A Kernel.package/Behavior.class/instance/accessing-properties/removePropertiesIfEmpty.st A KernelTests.package/BehaviorTest.class/instance/test - properties/testPropertyValueAtPut.st A KernelTests.package/BehaviorTest.class/instance/test - properties/testRemoveProperty.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script307.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40307.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Traits.package/TBehavior.class/instance/accessing-properties/properties.st A Traits.package/TBehavior.class/instance/accessing-properties/propertyValueAt_.st A Traits.package/TBehavior.class/instance/accessing-properties/propertyValueAt_ifAbsent_.st A Traits.package/TBehavior.class/instance/accessing-properties/propertyValueAt_put_.st A Traits.package/TBehavior.class/instance/accessing-properties/removePropertiesIfEmpty.st A Traits.package/TBehavior.class/instance/accessing-properties/removeProperty_.st A Traits.package/TBehavior.class/instance/accessing-properties/removeProperty_ifAbsent_.st A Traits.package/TraitBehavior.class/class/initialization/initialize.st M Traits.package/TraitBehavior.class/definition.st A Traits.package/TraitBehavior.class/instance/accessing-properties/properties.st A Traits.package/TraitBehavior.class/instance/accessing-properties/removePropertiesIfEmpty.st Log Message: ----------- 40307 14177 Add properties to classes https://pharo.fogbugz.com/f/cases/14177 http://files.pharo.org/image/40/40307.zip

Oct. 15, 2014

CompiledMethod>>hash can produce clashes

by Max Leske

We found an issue where CompiledMethods can produce the same hash event within the same MethodDictionary. Reported here: https://pharo.fogbugz.com/f/cases/14246/CompiledMethod-hash-can-produce-cla… <https://pharo.fogbugz.com/f/cases/14246/CompiledMethod-hash-can-produce-cla…> Cheers, Max

Oct. 15, 2014

[Screencast] Using ZnLogEvents and GT Tools to look at HTTP traffic behind Monticello

by Sven Van Caekenberghe

Using ZnLogEvents and GT Tools to look at HTTP traffic behind Monticello. I love it when a plan comes together. Many small usability changes were added to GT Tools since they were included in Pharo 4. And a lot of small custom inspector presentations were added. http://youtu.be/rIBbeMdFCys (be sure to select the 720p version) This short screencast shows how to use ZnLogEvents and GT Tools in Pharo 4 to look at the HTTP traffic behing Monticello (more specifically, an MCSmalltalkhubRepository). This demonstrates how simple custom inspectors are combined to form a powerful tool - and how easy it is to learn about what is going on inside Pharo. Sven

Oct. 15, 2014

Re: [Pharo-dev] RFB - anyone having that working properly under linux?

by Max Leske

> On 15.10.2014, at 12:59, phil(a)highoctane.be wrote: > > Hi, > > Well, not really that. > I removed the method but the symptom remains. > > Logging gives me: > > > RFBSession running > RFBSession send protocol version > RFBSession RFB 003.007 > > RFBSession viewer using protocol 3.7 > RFBSession client shared: true > RFBSession a RFBSocket[connected] connected > RFBSession ignoring request for ZRLE encoding > RFBSession rfbEncodingCopyRect > RFBSession rfbEncodingTight > RFBSession using Hextile encoding > RFBSession rfbEncodingQualityLevel 6 > RFBSession ignoring unknown encoding: 4294967073 > RFBSession rfbEncodingLastRect > RFBSession enabling LastRect protocol extension > RFBSession rfbEncodingPointerPos > RFBSession enabling cursor position updates > RFBSession rfbEncodingRichCursor > RFBSession enabling full-colour cursor updates > RFBSession received rfbSetPixelFormat > RFBSession set pixel format: 32bpp, depth 24 LE, true colour 255,255,255 16+8+0 > RFBSession colour map a WordArray(16711680 65280 255 0) an IntegerArray(0 0 0 0) > RFBSession before color table > RFBSession rfbSetPixelFormat done <-- added by me. > > RFB: caught ConnectionClosed: Connection close while waiting for data. > RFB: caught ConnectionTimedOut: send data timeout; data not sent > > Still blocked on that then... > > What is your log giving? Strangeâ¦ To be fair, I run RFB in Pharo 1.3 and that (plus the click event) was the only thing I had to change. â¦ I hacked around and got it running in Pharo 4. Fileouts are attached. Note that this is probably an older version (copied from my 1.3 image). HTH, Max > > Phil > > â

Oct. 15, 2014

Re: [Pharo-dev] BlockClosure source code

by Christophe Demarey

Le 15 oct. 2014 Ã 14:18, Ben Coman a Ã©crit : > Marcus Denker wrote: >>> On 14 Oct 2014, at 16:42, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>> >>>> >>>> On 10 Oct 2014, at 12:29, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>>> >>>> >>>>> On 10 Oct 2014, at 10:57, Jan KurÅ¡ <kurs(a)iam.unibe.ch <mailto:kurs@iam.unibe.ch>> wrote: >>>>> >>>>> Hi All, >>>>> >>>>> Thank you for the replies. I see it is not an easy bug to fix. Do you have any idea, when this can be fixed? >>>> I will try to fix it next week... >>>> >>>>> Or can you suggest me some other way/workaround, how to get/generate the source code of a block? >>>>> >>>> >>>> The old compiler used a hack to decompile blocks for getting a textual representationâ¦ one could port >>>> the code from Pharo2 to the Package OpalDecompiler in Pharo4. (but I actually like the current scheme of >>>> using the byte code-offset-to-AST mapping more). >>>> >>> >>> step one: A nice toolâ¦ GTInspector view of the byte codes that highlights what is thinks is the corresponding code in the source. >>> (This living Bytecode view replaces what before just printed out the #longPrintString of the CompiledMethod): >>> >> This is now in 4.0 update 306. >> e.g. inspect OrderedCollection>>#do: >> then select the âSymbolicBCâ tab, click on a byte code, then select in the second view the âSourceâ tab. >> ==> when moving around the byte code, the text highlights the code that generated the byte code. >> Marcus > > This is be great to pull more people into understanding (and helping) the dark depths. What about a tab in the second pane named "Help" that describes what each bytecode does? (half serious) > > For example, line 32, what is the "2" in "pushTemp: 2", and "1" in "pushConstant: 1". the index

Oct. 15, 2014

Re: [Pharo-dev] BlockClosure source code

by Ben Coman

Marcus Denker wrote: > >> On 14 Oct 2014, at 16:42, Marcus Denker <marcus.denker(a)inria.fr >> <mailto:marcus.denker@inria.fr>> wrote: >> >>> >>> On 10 Oct 2014, at 12:29, Marcus Denker <marcus.denker(a)inria.fr >>> <mailto:marcus.denker@inria.fr>> wrote: >>> >>> >>>> On 10 Oct 2014, at 10:57, Jan KurÅ¡ <kurs(a)iam.unibe.ch >>>> <mailto:kurs@iam.unibe.ch>> wrote: >>>> >>>> Hi All, >>>> >>>> Thank you for the replies. I see it is not an easy bug to fix. Do >>>> you have any idea, when this can be fixed? >>>> >>> I will try to fix it next week... >>> >>>> Or can you suggest me some other way/workaround, how to get/generate >>>> the source code of a block? >>>> >>> >>> The old compiler used a hack to decompile blocks for getting a >>> textual representationâ¦ one could port >>> the code from Pharo2 to the Package OpalDecompiler in Pharo4. (but I >>> actually like the current scheme of >>> using the byte code-offset-to-AST mapping more). >>> >> >> step one: A nice toolâ¦ GTInspector view of the byte codes that >> highlights what is thinks is the corresponding code in the source. >> (This living Bytecode view replaces what before just printed out the >> #longPrintString of the CompiledMethod): >> > > This is now in 4.0 update 306. > > e.g. inspect > > OrderedCollection>>#do: > > then select the âSymbolicBCâ tab, click on a byte code, then select in > the second view the âSourceâ tab. > ==> when moving around the byte code, the text highlights the code that > generated the byte code. > > Marcus > This is be great to pull more people into understanding (and helping) the dark depths. What about a tab in the second pane named "Help" that describes what each bytecode does? (half serious) For example, line 32, what is the "2" in "pushTemp: 2", and "1" in "pushConstant: 1". cheers -ben

Oct. 15, 2014

[ANN] New Gold Member LabWare

by Marcus Denker

The Pharo Consortium is very happy to announce that LabWare has joined the Consortium as a Gold Industrial Member. About LabWare: "LabWare is recognized as the global leader in providing enterprise scale laboratory automation solutions. Our Enterprise Laboratory Platform combines the award-winning LabWare LIMSâ¢ and LabWare ELNâ¢, a comprehensive and fully integrated Electronic Laboratory Notebook application, which enables companies to optimize compliance, improve quality, increase productivity and reduce costs. LabWare is a full service provider offering software, professional implementation services and validation assistance, training, and world class technical support to ensure our customers get the maximum value from their LabWare products." - LabWare: http://www.labware.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

Oct. 15, 2014