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

[Pharo-project] 2.0 compiler bug
by Camillo Bruni Sept. 14, 2012

Sept. 14, 2012

We still have a very nasty compiler bug open for 2.0 https://code.google.com/p/pharo/issues/detail?id=6601 The bug currently blocks all loading of configurations, since all references to previously undefined classes are not properly resolved => Compiler recompileAll is currently the only solution. Does anybody know where the undefined globals are handled? Otherwise I'll dig into it tomorrow morning...

2 1

[Pharo-project] A small quiz: longest selector
by Pavel Krivanek Sept. 13, 2012

Sept. 13, 2012

Hi, I've got a small quiz question for fun: What is the length of the longest method selector in Pharo? Before you will write an oneliner to get the exact result, try to make a tip ;-) Cheers, -- Pavel

6 12

[Pharo-project] [ANN] Zinc WebSockets
by Sven Van Caekenberghe Sept. 13, 2012

Sept. 13, 2012

Hi, I am pleased to announce the first public release of Zinc WebSockets, an implementation of client and server RFC 6455 regular (ws://) and secure (wss://) WebSockets on top of Zinc HTTP Components and Zodiac TLS/SSL Streams. High level documentation can be found here: https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md The code can be found in the regular Zinc repositories, or can be loaded using Metacello: ConfigurationOfZincHTTPComponents project latestVersion load: 'WebSocket'. Three examples are included and explained in the high level documentation: 1. a trivial echo service - each incoming message is simply echoed back to the client 2. a simple chatroom - each client opens a web socket to the chatroom service running on the server - the server keeps track of all connected client web sockets - when a message comes in from any client it is distributed to all clients - each client shows all incoming messages 3. a simple, continously updated status view - a client connects and listens for incoming messages containing a status report - the server streams status reports to each connected client every second - in the web browser you get to see the Smalltalk image's clock, memory and process stats Tested and approved on 2.0 #281. Portability to 1.3 and 1.4 should be OK. The implementation of Zinc WebSockets was made possible in part through financial backing by Andy Burnett of Knowinnovation Inc. and ESUG. Thanks! Questions, remarks, feedback ? Please use the Pharo Smalltalk mailing lists. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

5 7

[Pharo-project] Proxy Exception settings
by Santiago Bragagnolo Sept. 13, 2012

Sept. 13, 2012

Hi all. I just added a setting to specify exceptions for HTTP proxy. http://code.google.com/p/pharo/issues/detail?id=6663#makechanges regards Santiago.

2 1

[Pharo-project] [update 2.0] #20282
by Esteban Lorenzano Sept. 13, 2012

Sept. 13, 2012

20282 ----- Issue 6661: remove Rpackage package from monticello http://code.google.com/p/pharo/issues/detail?id=6661 Issue 6666: RPackageSet missing methods http://code.google.com/p/pharo/issues/detail?id=6666

1 0

[Pharo-project] [NativeBoost] 1.4 Bleeeding edge release
by Guy Hylton Sept. 13, 2012

Sept. 13, 2012

> just give me your squeaksource account, so i can add you as developer. grh > Oh, yeah.. > and this sort of problems (with re-initialization). > It would be nice to have them solved automatically. > I think it was bad idea to cache fields in NBExternalStructure. > It would be better to solve that differently. I expect that is more complicated than it first appears, but it will be good opportunity to look how the existing caching mechanism works. Thanks, Guy

2 1

[Pharo-project] FileSystem-Git GoogleGroup and mailing list
by Max Leske Sept. 13, 2012

Sept. 13, 2012

For those interested in FileSystem-Git there is now a dedicated GoogleGroup / mailing list: https://groups.google.com/forum/#!forum/smalltalk-git / smalltalk-git(a)googlegroups.com. Max

1 0

[Pharo-project] [NativeBoost] 1.4 Bleeeding edge release
by Guy Hylton Sept. 13, 2012

Sept. 13, 2012

Igor, > P.S. The configuration is freshly-baked, i didn't even checked if it > loads cleanly or not.. > so, i don't recommend updating it in image with your precious code :) I have tried loading your updated Configuration into Pharo1.4 #14438 and it loaded ok, but as a NativeBoost beginner it took me sometime to work out that I needed to run NBFFICallout>>initialize to get the new NB types registered. I found that this could be achieved using a postLoadDoIt message in the Configuration ... spec package: 'NativeBoost-Core' with: [ spec file: 'NativeBoost-Core-IgorStasenko.75'; postLoadDoIt: #postloadForCore ]. > Gofer it > squeaksource: 'NativeBoost'; > package: 'ConfigurationOfNativeBoost'; > load. > (ConfigurationOfNativeBoost project version: '1.4' ) load > P.P.S. i would really like some help with testing what i did, > including writing some more tests to cover type system more > broadly (now since type names follow certain naming rule, many > different types can be checked without much coding) Some of the tests failed after the update because it was necessary to rebuildAccessors for a couple of the structures used so that they referred to the new NB types. Although this is a trivial change I would like to try and help your efforts with some more tests and documentation, but how should I submit them? Should I follow the "HowToContribute" procedure on the Pharo website? Thanks, Guy

2 2

[Pharo-project] [update 2.0] #20281
by Esteban Lorenzano Sept. 12, 2012

Sept. 12, 2012

20281 ----- Issue 6654: Make one RPackage maps one PackageInfo http://code.google.com/p/pharo/issues/detail?id=6654 (pass 3) - Monticello to use RPackageSet finish :)

4 3

[Pharo-project] [Screencast] StoryBoard
by laurent laffont Sept. 12, 2012

Sept. 12, 2012

http://www.pharocasts.com/2012/09/getting-started-with-storyboard.html Storyboard is a multi-user agile planning board with drag and drop support. It shows how little code is needed to build a complete application with Deltawerken. It consists of 39 classes, of which 7 are announcements (very simple). It allows you to quickly enter stories, estimate and prioritize them. In addition to stories you can add issue, documentation and chore cards. The cards are colored based on their story state. More details can be entered/viewed by expanding the card. In the expanded view a change history is shown. Other users of Storyboard can be invited to participate. Deltawerken is a Seaside application level framework, allowing fast application development for medium-sized applications. We have used an earlier extended version of it to build a system with about 150 domain classes. Complexity was deliberately and systematically pushed from the application to the framework. It uses a declarative way to describe domain classes somewhat similar to Magritte or Mold. It uses Announcements, jQuery and jQueryUI. Storyboard was announced at ESUG2012 Thank you Stephan Eggermont! (Note: feel free to contact me if you want to publish on PharoCasts) Laurent

1 0