February 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] Render images - Porting from Cincom VW to Pharo
by Emilia Oct. 15, 2013

Oct. 15, 2013

Hello! I'm porting code from Cincom Smalltalk to Pharo. It's a web application so I've got several WAComponent instances and one component which inherits from WAFileLibrary that renders images. In the original code ( the one that runned in VW) i had the following instance method in the component that inherits from WAFileLibrary: logoJpg ^ByteArray asPackagedString: '?=#?8@@PR$YIQ @A@ D@X@A @@C?8P))QW!)Y @@RT$*@@ @@@@G@AHA@0@......etc etc' But now when i run it in Pharo the debbugger doesn't recognize #asPackagedString: message. Does anyone know which method should I use in order to render that image? Thanks in advance! Mercy beaucoup! Emilia

4 5

[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] call for speakers - pharoconf (april 2, 3) / mooseday (april 4) - bern, switzerland
by Tudor Girba March 7, 2013

March 7, 2013

Hi, During April 2-4 we will organize a PharoConf and a MooseDay in Bern, Switzerland. Mark the day and join us. The participation will be free of charge. The conference will focus on interactivity and exchange, and will feature experience report talks, tutorials, show-us-your-project sessions and open discussions. We are looking for speakers: TUTORIAL These sessions will walk the audience through a piece of technology. Target duration: 30min - 60min. Example topics: - ZeroConf continuous integration builds - Building vectorial interfaces with Athens - Building UIs with Spec - New development tools (Fuel/Tanker, Glamorous Debugger, Nautilus ...) - Manipulating databases in Pharo (Riak, MongoDB ...) - Visualizing data (Roassal, EyeSee ...) TALK These sessions expose a topic that is not necessarily technical. Target duration: 30min - 60min. Example topics: - Experience of using Pharo to solve business problems - Experience of using Pharo and Moose to solve various technical problems (not necessarily related to Smalltalk) - Successes in marketing Pharo-based solutions - Future directions for Pharo or Moose SHOW-US-YOUR-PROJECT These sessions will feature short presentations of the projects (7-10 minutes) followed by open-space demos. Example topics: - The Glamorous Debugger - Nautilus - Analysis tools like Softwarenaut or Carrack - Fuel/Tanker - ... Please send us your submissions by email at tudor(a)tudorgirba.com. Cheers, Doru on behalf of the organizers -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

3 3

March 6, 2013

Hi Pharoers We got a discussion in the team to see how we will handle packages that are not in the Pharo image but that some of us maintain or participate to maintain. For example Soup and XMLWriter, XMLSupportâ¦. ProfStef,â¦. We decided to create a separate team on SmalltalkHub named PharoExtras to host such projects. http://smalltalkhub.com/#!/~PharoExtras/ Everybody is welcome to be member and to help us. We want that each of these projects get also associated with a jenkins job that runs automatically the tests of the projects. Like that we can immediately see if a change get an impact on the close ecosystem. I started with camillo to do it for XMLWriter and I will do it some the projects I'm using. https://ci.inria.fr/pharo-contribution/job/XMLWriter/ http://smalltalkhub.com/#!/~PharoExtras/XMLWriter Stef

7 9

[Pharo-project] Is this possible with XMLWriter?
by Mariano Martinez Peck March 5, 2013

March 5, 2013

Hi guys. I am using XMLWriter from http://www.squeaksource.com/XMLWriter to write a specific XML that a protocol expects. What I need is to build the XML file from parent to children and dynamically. For example, I want to be able to define a tag, but then, later on, add more tags to a parent element. I found this impossible to do with the current XMLWriter. Here, messages like #tag:with: , #with: do not help. I know I will need to build everything in memory and send a "write contents" at the end to get the final XML string... For example, say I wanna build this XML: <root> <parent1> <child1>grrr<child1> <child2>grrr<child2> </parent1> <parent2> <child3>buhhh<child3> </parent2> </root> i would like an API like this: | xmlWriter | xmlWriter := XMLWriter new. xmlWriter tag: 'root'. (xmlWriter named: 'root') tag: 'parent1'. (xmlWriter named: 'parent1') tag: 'child' with: 'grrr'. (xmlWriter named: 'root') tag: 'parent2'. .... xmlWriter write contents. Or even if I don't have #named: but I can store them in instVars it would be fine: | xmlWriter rootTag parent1Tag | xmlWriter := XMLWriter new. rootTag xmlWriter tag: 'root'. parent1Tag rootTag tag: 'parent1'. parent1Tag tag: 'child' with: 'grrr'. rootTag tag: 'parent2' xmlWriter write contents. Any ideas how to do this? Thanks, -- Mariano http://marianopeck.wordpress.com

5 13

[Pharo-project] Test Resources
by Noury Bouraqadi March 4, 2013

March 4, 2013

Hi, Jannik and I are having trouble dealing with resources in our robotic project. It's strange that resources are reset on every test run. This happens when resources are declared in test class method resources. My understanding of resources is that they should be reset only once for a whole test suite. For every test case, they should be setUp/tearDown, but not fully reset. We couldn't find a clean way of working this out. We ended up defining our own subclass of TestSuite, which I believe is dirty. Besides, the behavior is kind of random. It seems that there are some cleanups that aren't performed the right time. But, since the failure is random, we couldn't manage today to fix this. Any hint, idea is welcome, Noury Ecole des Mines de Douai http://car.mines-douai.fr/noury -- Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

7 20