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

[Pharo-project] Issue 3015: When a test is restarted in the debugger, #tearDown and #setUp and not send
by Hernan Wilkinson Aug. 28, 2013

Aug. 28, 2013

Hi, I added a new issue (that I think it could be see as an improvement, not an issue) that is related to debugging a test case written with SUnit. The problem is that when you restart a test in the debugger (either by pressing the restart button or compiling the method again) the changes made by the test to the objects initialized in the #setUp are not rollbacked. This change sends the messages #tearDown and #setUp to the test when restarting it, therefore letting the test in the same state as when it was run in the first place. I uploaded the solution to this issue (or improvement) to pharo inbox under SLICE-Issue-3015-RestartingATestFromTheDebuggerSendsTearDownAndSetUp-HernanWilkinson.2 I hope you like it! Hernan. -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com <http://www.10pines.com/>*

3 3

Re: [Pharo-project] Adding a statement programmatically
by Marcus Denker June 7, 2013

June 7, 2013

On Mar 8, 2012, at 12:21 PM, Noury Bouraqadi wrote: > Hi Sean, > > Did you thought about: > -using method wrappers? > -object as methods. An object o put in a method dictionary instead of some method with selector #s. When #s is looked up, o receives the message > run: selector with: args in: originalReceiver > -proxies (look at Ghost) so you introduce an indirection to perform what ever action you want before performing the actual code > -> Compile the code to an RB AST, this then has all the interfaces needed to replace nodes or add nodes. You can then pretty print it back to source. Marcus -- Marcus Denker -- http://marcusdenker.de

3 6

[Pharo-project] Spec DropLists
by Sean P. DeNigris April 16, 2013

April 16, 2013

Issue 6551: [ENH Spec]: Spec-ify DropListModel http://code.google.com/p/pharo/issues/detail?id=6551 Currently: self instantiateModels: #(dropList #DropListModel). item1 := DropListItem named: 'Red morph' do: self redMorphBlock. item2 := DropListItem named: 'Blue morph' do: self blueMorphBlock. item3 := DropListItem named: 'Green morph' do: self greenMorphBlock. dropList items: {item1. item2. item3}. I'd prefer if DropLists were uniform with the rest of Spec, namely: I'd have my domain class MyColor>>description ^ nameOfColor dropList items: {myRedColor. myBlueColor. myGreenColor}; displayBlock: [ :e | e description, ' morph' ]; whenSelectionChanged: [ :e | self showMorphFor: e ]. I'd prefer not to even know that DropListItem exists, and have the model take care of it for me. Something like: DropListModel>>items: aList "Populate the drop list with a list of objects" | items | items := aList collect: [ :e | DropListItem named: e printString do: [ ] ]. listHolder contents: items. Incidentally, #whenSelectionChanged: exists for DropListModels, but is broken. When an item is chosen from the drop list, the announcement received by this block has both new and old contents set to nil: Issue 6550: [BUG Spec]: DropListModel>>whenSelectionChanged: http://code.google.com/p/pharo/issues/detail?id=6550 Cheers, Sean -- View this message in context: http://forum.world.st/Spec-DropLists-tp4643694.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 4

[Pharo-project] HMI (was: One more project proposal for GSoC)
by Dennis Schetinin March 30, 2013

March 30, 2013

So, here is the proposal: Name: Khubbatov Rustem Difficulty Level: Intermediate Description A framework for building Human-Machine Interfaces with Pharo back-end providing model, and presentation front-end in Amber. Technical Details A concrete task that should be implemented with this project is a prototype of UI for network management system or SCADA. Server-side (Pharo) will simulate network components and their data, and provide relevant events for client (Amber). The latter will present network items, their state and associated information, and provide UI to control them. An important part of this system is a communication layer between Amber and Pharo. Benefits for the Student The student will gain experience in building client-server applications with advanced UI and providing two-way communication between client and server. Benefits for the Community An ability to create highly interactive web-based applications is a must-have feature for any modern development system. Amber is a bleeding edge in this area in Smalltalk world. A good communication layer between Amber and (for example) Pharo is a very appealing decision for building complex client-server systems. Best regards, Dennis Schetinin Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Monday, 2 April 2012 Ð³. at 21:47, Janko MivÅ¡ek wrote: > Hi Dennis, > > I'd suggest to go ahead. This is first Amber-related project, so it seems even more interesting. But hurry up. Let Rustem prepare the proposal and you post here then we'll open the project page. > > Best regards > Janko > > On Mon, Apr 2, 2012 at 7:41 PM, Dennis Schetinin <chaetal(a)gmail.com (mailto:chaetal@gmail.com)> wrote: > > Rustem Kkubbatov (http://gsoc2012.esug.org/rustem-khubbatov) another student I mentor in Tver State University, decided to try his luck with a project for GSoC. The problem is he can't currently choose a better approach. > > > > The original idea is to build a two-tier Human-Machine Interface (HMI) system (which can be used in a wide range of projects) with Pharo image as back-end (where a model lives) and Amber-based client as a front-end. But this thing seems to be "a little bit" too large for GSoC, isn't it? > > > > An alternative task could be to build a framework for message exchanging between Pharo and Amber. I could be the first mentor for a project based on original idea, or the second/first (depending on if anyone interested) for communication framework. > > > > Any ideas and advices are welcome (ASAP). Thank you in advance. > > > > Best regards, > > Dennis Schetinin > > >

3 6

[Pharo-project] IMPORTANT: Issue 6351: FileReference>>deleteAll follows symlinks in 1.4
by Sean P. DeNigris March 12, 2013

March 12, 2013

This is a fun one to find out about by accident... Hey, what happened to my temporary variable names? Oh, they're decompiled because my image folder was deleted while deleting my home folder because the folder being deleted contained a symlink to it. Thank god for backups... and that it was deleting alphabetically, so mostly rarely-changed config files were deleted (i think/hope)... Pharo1.4 Latest update: #14448 '/path/to/dir' asFileReference deleteAll. * If the link is valid, it follows it and keeps deleting * If not, it claims the link file doesn't exist. http://code.google.com/p/pharo/issues/detail?id=6351 -- View this message in context: http://forum.world.st/IMPORTANT-Issue-6351-FileReference-deleteAll-follows-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 2

[Pharo-project] zero conf build
by Camillo Bruni Feb. 24, 2013

Feb. 24, 2013

I finally managed to create a zero conf pharo image build setup: # =========================================================================== curl http://pharo.gforge.inria.fr/ci/ciPharo20Cog.sh | sh ./vm.sh Pharo.image save $JOB_NAME REPO=http://smalltalkhub.com/mc/dh83/nabujito/main ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfNabujito --install=development ./vm.sh $JOB_NAME.image test --junit-xml-output Nabujito zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes # =========================================================================== ./ciPharo20Cog.sh --help This is an entry point script for any Pharo image CI This script will download the latest Pharo 2.0 image and the latest VM Result in the current directory: vm directory containing the VM vm.sh script forwarding to the VM inside vm/ Pharo.image The latest pharo image Pharo.changes The corresponding pharo changes" # =========================================================================== have fun!

9 24

[Pharo-project] The monkey is back in town
by Camillo Bruni Feb. 13, 2013

Feb. 13, 2013

I had a sudden urge to program something so I revived the monkey (partly) - full smalltalk implementation (no more ruby) - basic command line handler (could be better but works..) - using OSProcess with FileSystem-Legacy in 2.0 the only thing missing are the couple of changes I proposed for the main image: - http://code.google.com/p/pharo/issues/detail?id=7097 - http://code.google.com/p/pharo/issues/detail?id=7096 - http://code.google.com/p/pharo/issues/detail?id=7095 once they are in, we're ready to roll cami on fernet

13 54

[Pharo-project] [ann] glamorous debugger (alpha)
by Tudor Girba Feb. 13, 2013

Feb. 13, 2013

Hi, Over the last following days, Andrei Chis and me have worked on getting the Glamorous Debugger in a usable state (based on the original effort of Toon Verwaest): This debugger is part of the Glamorous Toolkit project, and it is based on Glamour (see the attached screenshots). You can find some details about it here: http://www.humane-assessment.com/blog/announcing-the-glamorous-debugger-alp… Some interesting characteristics: - It has an integrated inspector that shows all variables in one GTInspector with which you can browse in place all relevant variables - Code-wise, the debugger comes with an explicit model that relies neither on the old Debugger nor on the CodeHolder. The model is rather small and intelligible. In total, the entire code totals some 400 lines of code (at the moment). To put it into perspective, the Debugger class has 1096 lines of code (not counting the extra code used by it). Right now, we consider the code to be in a solid alpha, and we need more eyeballs and clicks to test it :). If you are interested in playing with it, you can either find it in the Moose image, or you can load it in Pharo 1.4 via: Gofer new squeaksource: 'glamoroust'; package: 'ConfigurationOfGlamoroust'; load. (Smalltalk at: #ConfigurationOfGlamoroust) loadDevelopment Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

7 19

[Pharo-project] ConfigurationOfPetitParser has broken #'common' section
by Frank Shearar Feb. 10, 2013

Feb. 10, 2013

By "broken" I mean "it might work fine in Pharo but it doesn't in Squeak". That's because PetitParser now uses Glamour, which pulls in a whole host of things that probably don't work in Squeak. (I don't know, I haven't tried, but these are all UI things, and the UI is where Pharo and Squeak are least compatible.) I'm being a bit rude in that I don't yet have a fix for the issue. Ideally, a ConfigurationOf would have Pharo specific stuff and Squeak specific stuff in separate sections, with only the shared things (right now, not Glamour, nor its dependents) in the #'common' section. However, if someone doesn't beat me to it, I'll submit a fix soon, once Squeak 4.4 is out the door. frank

5 10

[Pharo-project] Spec questions
by Torsten Bergmann Jan. 31, 2013

Jan. 31, 2013

Do we have Spec examples for - menues - lists with icons - trees already? What is the state and overall plan for the near future. Thx T.

6 19