- Pharo-dev - lists.pharo.org

[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

[Pharo-project] Keymapping KMShortcut combining
by Goubier Thierry Sept. 12, 2012

Sept. 12, 2012

Hi, Is it possible in Keymapping to have an alternative as shortcut ? I would like to map Tab/Shift Tab and Ctrl Tab/Shift Ctrl Tab to get next/previous focus to work with Spec, and I would like to be able to return a keystroke as Character tab | Character tab ctrl. For those interested, I'm trying to look at http://code.google.com/p/pharo/issues/detail?id=6657 and: http://code.google.com/p/pharo/issues/detail?id=6656 I have solutions for both : code that does 6657, and a way to disable all legacy shortcuts for 6656 for Spec applications on a per instance basis, without overriding or removing any existing code. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

6 9

[Pharo-project] pharo-2.0-tests Â» mac - Build # 341 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Sept. 12, 2012

Sept. 12, 2012

1 0

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

Sept. 12, 2012

20280 ----- Issue 6654: Make one RPackage maps one PackageInfo http://code.google.com/p/pharo/issues/detail?id=6654 (pass 2) - introduce RPackageSet - test RPackageSet is polymorphic with PackageInfo in MC context WARNING: This is still NOT the solution... but we are a lot closer :)

1 0

Sept. 12, 2012

Hi igor I started to reread again the code of EventModel that we started and I browse the rest of the systemâ¦. gloopsâ¦ DropEvent>>sentTo: anObject "Dispatch the receiver into anObject" self type == #dropEvent ifTrue:[^anObject handleDropMorph: self]. DropFilesEvent>>sentTo: anObject "Dispatch the receiver into anObject" self type == #dropFilesEvent ifTrue:[^anObject handleDropFiles: self]. it seems to me that sentTo: is a kind of double dispatch but not yet there. I do not see here the added value of the check except if this is to cancel event. Stef

5 10

[Pharo-project] SmallLint and Manifest
by Simon Allier Sept. 11, 2012

Sept. 11, 2012

Hi, I have published a new version of the Critics Browser (menuWorld > Tool > CriticBrowser). The new version is - refactoring friendly. Yes we listened to you :). - the browser has been improved. It works with the latest Spec. With the Critics browser you can inspect violations of the SmallLint rules and mark them as false positive or true positive (ToDo) and see previous warnings flagged as false positives or toDo. In addition all the logic of the browser has been developed so that the manifest can be saved within the package without adding dependencies. In this new version the format of the manifest has changed to be compatible with tools refactoting, the rules are organized in a tree and itâs possible to adds comment when we mark a false positive or todo. We are writing a nice chapter on SmallLint, critics and other for the new book. Soon we will release it for reviews. Gofer new url: 'http://www.squeaksource.com/PharoTaskForces'; package: 'ConfigurationOfManifest'; load. ((Smalltalk at: #ConfigurationOfManifest) project version: #stable) load Simon

5 12