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

Google Chrome Native Client Technology and PharoVM
by phil＠highoctane.be Nov. 21, 2014

Nov. 21, 2014

https://developer.chrome.com/native-client provides support for running native stuff inside the browser (a kind of VMWare inside the browser). It would make sense to have Pharo running that way. Is there anyone looking into this? Phil

2 1

ConfigurationOfGlamour not connected to repository
by Stephan Eggermont Nov. 21, 2014

Nov. 21, 2014

In Pharo-40378, when I select the ConfigurationOfGlamour, it is not connected to a repository. (it also is an old version). Stephan

1 0

[ANN] Hubcap - a SmalltalkHub API and browser for Pharo
by Torsten Bergmann Nov. 21, 2014

Nov. 21, 2014

Hi, as I wanted to browse the SmalltalkHub contents directly from within Pharo image I wrote a simple browser: Gofer it url: 'http://www.smalltalkhub.com/mc/TorstenBergmann/Hubcap/main'; configurationOf: 'Hubcap'; loadDevelopment. Attached is a screenshot. Works on Pharo 4.0. Still not finished but maybe it is already useful to others as well. One can access the tool from the world menu, implementation lives in "Hubcap-Tools" package. The UI shows and allows to filter users, shows their projects and packages. Special icons display the state (loaded, modified, public writable, ...). One can load from the UI or open Monticello tools. The "Hubcap-Core" package includes an API to query STHub and write expressions like: HubClient new allProjectsForUserNamed: 'TorstenBergmann' HubClient new hasUserNamed: 'TorstenBergmann' So "Hubcap-Core" may be usefull to people who want to build other tools that depend on STHub infos. Basic documentation lives on http://www.smalltalkhub.com/#!/~TorstenBergmann/Hubcap and as class comment on ConfigurationOfHubcap. Beware: the tool is sill not optimized, any clicking involves a query to STHub (hope STHub will not crash when many people use it). API may still undergo changes in the future. Also teams are not yet supported as STHub still returns an MNU error in the REST interface: http://www.smalltalkhub.com/hub/teams?term=Pharo Anyone able to fix that? Thanks to Stephan Eggermonts who gave me the initial idea with some code I've found in "Deprecation finder" and to Sven for the easy to use NeoJSON package. Contributors can just commit, the project is public. Bye T.

2 1

[ANN] Hubcap - a SmalltalkHub API and browser for Pharo
by Stephan Eggermont Nov. 21, 2014

Nov. 21, 2014

Nice! I like being able to quickly search for someone and see their projects. Useful extensions would be: - Teams and their projects - My teams - Sorting mczs I think I'd prefer the menu location to be with Configuration Browser When I type moose<enter> there is an exception. There is an empty Array somewhere where you expect an OrderdCollection. I don't understand why the delay in the response from smalltalkhub is always so large. Stephan

1 0

Re: [Pharo-dev] [Pharo-users] [ANN] Hubcap - a SmalltalkHub API and browser for Pharo
by Sven Van Caekenberghe Nov. 21, 2014

Nov. 21, 2014

Yes, very nice. > On 21 Nov 2014, at 08:35, Hilaire <hilaire(a)drgeo.eu> wrote: > > Le 21/11/2014 08:32, Torsten Bergmann a Ã©crit : >> as I wanted to browse the SmalltalkHub contents directly from within Pharo image >> I wrote a simple browser: > > > Cool! > > Thanks > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > >

1 0

[Fwd: Re: Float hierarchy for 64-bit Spur]
by Ben Coman Nov. 21, 2014

Nov. 21, 2014

(sorry, I didn't notice the cross-post) Eliot Miranda wrote: > Hi All, > > 64-bit Spur can usefully provide an immediate float, a 61-bit subset > of the ieee double precision float. I wonder if class SmallDouble would be more intention revealing? In practice 61 bits will be "more than enough"(tm) for anyone. But I can envisage in a business environment environment software needing to comply with (sometimes irrelevant) feature checklists, with one of those likely being full 64 bit compliant IEEE Doubles. Can we have such a class, to which 61 bit floats are auto-promoted as required? > The scheme steals bits from the > mantissa to use for the immediate's 3-bit tag pattern. So values have > the same precision as ieee doubles, but can only represent the subset > with exponents between 10^-38 and 10^38, the single-precision range. > The issue here is how to organize the class hierarchy. > > The approach that looks best to me is to modify class Float to be an > abstract class, and add two subclasses, BoxedFloat and SmallFloat, such > that existing boxed instances of Float outside the SmallFloat range will > become instances of BoxedFloat and instances within that range will be > replaced by references to the relevant SmallFloat. > My first few pages of search results lead to a few references in conversation, but nothing that described what a boxed float is. Can someone explain? btw, http://www.ctan.org/pkg/float also mentioned boxed float, ruled float and plainÂtop float Anyone familiar with those? > With this approach ... > > - Float pi etc can still be used, even though they will answer instances > of SmallFloat. But tests such as "self assert: result class == Float." > will need to be rewritten to e.g. "self assert: result isFloat". This is probably a good change anyway. > > - BoxedFloat and SmallFloat will not be mentioned much at all since > floats print themselves literally, and so the fact that the classes have > changed won't be obvious. > > - the boxed Float primitives (receiver is a boxed float) live in > BoxedFloat and the immediate ones live in SmallFloat. Making SmallFloat > a subclass of Float** poses problems for all the primitives that do a > super send to retry, since the boxed Float prims will be above the > unboxed ones and so the boxed ones would have to test for an immediate > receiver. ** do you mean the current Float, or after Float become abstract? > > > An alternative, that VW took (because it has both Float and Double) is > to add a superclass, e.g. LimitedPrecisionReal, move most of the methods > into it, and keep Float as Float, and add SmallFloat as a subclass of > LimitedPrecisionReal. Then while class-side methods such as pi would > likely be implemented in LimitedPrecisionReal class, sends to Float to > access them find them via inheritance. An automatic reorganization > which moves only primitives out of LimitedPrecisionReal is easy to write. > A Float is defined as a limited precision real [1] having several types of precision, so I like the first option. [1] http://en.wikipedia.org/wiki/Floating_point cheers -ben

2 5

New Cog VMs available
by Eliot Miranda Nov. 21, 2014

Nov. 21, 2014

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3143. CogVM binaries as per VMMaker.oscog-tpr.949/r3143 Spur: Fix regression in primitiveNewWithArg from VMMaker.oscog-eem.859 which caused basicNew: on fixed classes to raise OutOfMemory instead of the relevant error. Have checkForAndFollowForwardedPrimitiveState follow other references in the frame if a forwarder is found on the stack. All: Add a first cut at the primitiveSlotAt[Put] primitives. Reimplement primitiveBitShift for 64-bits. Define areIntegers:and: for 64-bit Spur, and move it into the ObjectMemory hierarchies. Add maxSmallInteger and minSmallInteger and matching manifest constants. Use these in LargeIntegersPlugin and Matrix2x3Plugin. Use numBytesOf: instead of lengthOf: in the 64-bit integer conversion routines. Reorder cases in Spur's numBytesOf: to put common case first. -- best, Eliot

1 0

About the Playground cache
by Nicolai Hess Nov. 21, 2014

Nov. 21, 2014

I thought the Playground cache holds all evaluated/used expressions. But it just caches the current text and if you remove the current text, the cache file is deleted. And it does not use just one file, but one for every opened playground with text. And if you close the playground, without deleting the current text, you ' ll end up with many (many many) cache files. (and it takes some time opening the first playground after image start up). Pressing the little "..." icon shows an unscrollable large list with all the cache entries. (even duplicate entries). How about creating just one cache file, and only add used/evaluated expressions to the cache? nicolai

3 4

[Pharo4] down to 3 failing tests!
by Marcus Denker Nov. 21, 2014

Nov. 21, 2014

We are down to 3 failing tests! AJx64AssemblerTests>>#testStringOps64Mnemonics ObsoleteTest>>#testFixObsoleteSharedPools ReleaseTest>>#testObsoleteClasses https://pharo.fogbugz.com/f/search/?sSearchFor=outline%3A14445

2 1

Link between PetitParser and Roassal and Glamour
by Noury Bouraqadi Nov. 20, 2014

Nov. 20, 2014

Load PetitParser (dev version) => Roassal and Glamour loaded. Isnât it strange? I believe there should be less dependency. Noury

2 3