February 2014 - Pharo-users

Improving Strings Manipulation topic

by Daniela Meneses

Hi to all: I'm Daniela, I'm starting to work on "Improving Strings Manipulation" topic. The idea of this project is to help rethinking the string manipulation API of Pharo. So, from now and on, I will be posting some questions and doubts that I may have. I hope you can help me. Besides If you have suggestions or anything to comment about it, please let me know. -- Thanks in advance , Daniela Meneses

Feb. 13, 2014

Re: [Pharo-users] [Pharo-dev] [ANN] Spec documentation in PFTE book finished

by Sven Van Caekenberghe

Thanks a lot, Johan & Ben, this is great work ! On 12 Feb 2014, at 16:08, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Hi all, > > I am happy to announce that Ben and I finished the documentation of Spec for the Pharo For The Enterprise book. This documentation is up-to-date with the latest version of Spec, and is focused towards people wanting to use it and even extend it (in contrast to the academic papers which are â¦ academic ;-) ). I hope that this text will help all the people that are building UIs in Pharo, and it will clear up any doubts that they may have. > > The chapter is available in source form from the GitHub project of the PFTE book: https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english > > The easiest way to read the chapter is from the continuous integration server, which produces a html file of the chapter here: > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > (The same server also produces pdf and markdown files, but there are some strange artifacts there, currently. I guess this will be cleared up in the future) > > We tried our best to make it understandable and complete, but if you have any doubts or comments please do not hesitate to let us know !! Ben prefers Github apparently, but if you are oldskool like me you can also send a mail (privately or to the mailing list). > > Now it's time to build some cool user interfaces! :-) > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >

Feb. 12, 2014

Athens question - #openInSceneView

by Torsten Bergmann

If I understand correctly #openInSceneView wraps a morph in an Athens scene. I tried some examples: "Smalltalk ui icons configIcon asMorph openInSceneView" "BorderedMorph new openInSceneView" First two work, but the third: "EllipseMorph new openInSceneView" brought up a yellow morph - but as rectangle not as ellipse like in "EllipseMorph new openInWorld". Havent looked deeper. Incomplete or a bug? Thx T.

Feb. 12, 2014

Re: [Pharo-users] index of element matching block

by Norbert Hartl

We should do that more often. Especially here on the users list. IMHO it has three advantages: - asking here may show new ways of doing things. And we know in smalltalk it is most of the time the most obvious choice we do not find - I assume there are quite some readers in this list which have fun answering and trying things out if they do not know it. Sven is a good example for that. Iâm just an example :) - Everyone has the chance to learn something new my 2 cents, Norbert Am 12.02.2014 um 15:03 schrieb btc(a)openinworld.com: > Norbert Hartl wrote: >> >> Am 12.02.2014 um 11:44 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> >>> #( 11 7 4 21 ) detectIndex: #even >>> >>> >> I knew it makes sense to ask. Only slightly embarrasing :) >> > Thanks for asking. I learnt something new. > cheers -ben >> Norbert >> >> >>> ;-) >>> >>> On 12 Feb 2014, at 12:37, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>>> I just discovered that there is no method like >>>> >>>> indexOf: aBlock >>>> >>>> where the index of the element matching the block is returned. What would be the usual way to achieve this functionality? >>>> >>>> Norbert >>>> >>>> >>>> >>> >> >> >> > >

Feb. 12, 2014

[ANN] Spec documentation in PFTE book finished

by Johan Fabry

Hi all, I am happy to announce that Ben and I finished the documentation of Spec for the Pharo For The Enterprise book. This documentation is up-to-date with the latest version of Spec, and is focused towards people wanting to use it and even extend it (in contrast to the academic papers which are â¦ academic ;-) ). I hope that this text will help all the people that are building UIs in Pharo, and it will clear up any doubts that they may have. The chapter is available in source form from the GitHub project of the PFTE book: https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english The easiest way to read the chapter is from the continuous integration server, which produces a html file of the chapter here: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… (The same server also produces pdf and markdown files, but there are some strange artifacts there, currently. I guess this will be cleared up in the future) We tried our best to make it understandable and complete, but if you have any doubts or comments please do not hesitate to let us know !! Ben prefers Github apparently, but if you are oldskool like me you can also send a mail (privately or to the mailing list). Now it's time to build some cool user interfaces! :-) ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 12, 2014

Re: [Pharo-users] index of element matching block

by btc＠openinworld.com

Feb. 12, 2014

Re: [Pharo-users] [Pharo-dev] [gsoc-mentors] GSoC: call for ideas

by Camille Teruel

Hello, Here are my proposals, ================================================== Title: Slots, batteries included Context: Pharo has recently introduced a model for first-class class layouts and instance variables (slots). This model will permit to customize the memory layout of instances of a class and the read/write logic of instance variables. However, the current compiler doesn't take the custom read/write logic into account and the implementation need some love. Goal: The student will first have to understand the model of layout and slots (http://rmod.lille.inria.fr/archives/papers/Verw11a-OOSPLA11-FlexibleObjectL…) The next step is to modify the compiler (Opal) so that it take slots into account. Then, the student will improve the current implementation: - Expand the API: Each class should responds to #slots #ownSlots, each object to #slotNamed:set:, #slotNamed:, etc... - Fix the class installer to use the new instance migration model instead of the old one. - Study whether scopes can be removed from the core model or not. - Better definition of the interactions/responsibilities of the class builder and the class installer and fix the problem of modification of anonymous classes. Then the student can provides several examples of custom slots and identify potential clients of these new facilities. Dialect: Pharo Skill level: intermediate Mentors: Camille Teruel / Martin Dias ================================================== Title: Baobab Context: Pharo sources are currently stored in a separated file (.sources). We plan to remove that file and instead store all sources in the image in AST form. But keeping all the ASTs of the system methods would cost too much memory. Bonsai, is one possible solution for saving memory: it is just a flyweight pattern for ASTs. Additionally, we want to annotate the nodes of the ASTs various informations (bindings, additional comments, discussions, false positive critics, debugging code, typing information for various pluggable type systems, statistics like code coverage, etc...). All these annotations would also take too much space in the image. Moreover, not all of them are needed by all developers. Some must be kept in the image, others not. Goal: The goal of Baobab is to offer a flexible AST annotation and serialization system. An annotation should be able to define if it's transient (kept in the image but not serialized with the AST), local (kept in the image and serialized with the AST) or remote (stored on remote repositories so that teams of developers can share and edit them). Dialect: Pharo Skill level: easy/intermediate Mentor: Camille Teruel =================================================== Title: Generic rewriting engine Context: Rewriting is an useful technique that has a lot of applications in many functional programming language. A rewriting engine that can rewrite arbitrary graph of objects would have a lot of useful applications like code refactoring and migration of instances in an alive program. Goal: The goal of this proposal is to implement a rewriting engine for arbitrary tree/graph of object. A rewriting rule must be able to define: - Patterns to match a part of the graph possibly including metavariables (variables that match subparts of the matched part) - Transformation of the matched part using the metavariables The engine is parametrized with a set of rules an a traversal of the graph (look at http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects for ideas). Inspirations can be found in the pattern-matching library of Newspeak: (http://www.hpi.uni-potsdam.de/hirschfeld/publications/media/GellerHirschfel…) Skill level: intermediate Dialect: Free Mentor: Camille Teruel =================================================== Title: Object based IDE Context: An object oriented program is based on objects that send messages to other objects. However, source code and IDE shows only classes and methods. There is a huge gap between the source code that the IDEs show and the runtime entities of a program: object and messages. This gap make program comprehension difficult because it is up to the programmer to fill this gap in is head. That is certainly the reason why many Smalltalk programmers like to program in the debugger: they deal with an actual instance of their program. Goal: The goal of this proposal is to set up the first bricks toward a graphical IDE centered around objects that are alive during a program execution. The first step is to provide a view to easily navigate through a graph of objects. Then objects should be able to customize their view and several default views for common classes must be provided: Array, Dictionary, Set, etc... The final step is to be able to run a program step by step as in a debugger and display the messages sent between objects using Granovetter diagrams. Dialect: any Skill level: intermediate Mentor: Camille Teruel

Feb. 12, 2014

Re: [Pharo-users] index of element matching block

by Norbert Hartl

Am 12.02.2014 um 12:25 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 12 Feb 2014, at 13:02, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 12.02.2014 um 11:44 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >>> #( 11 7 4 21 ) detectIndex: #even >>> >> I knew it makes sense to ask. Only slightly embarrasing :) > > These little challenges are always quite fun. > Yep, because the closest I could create was using withIndexDo: and looking at #detectIndex:ifNone: confirms that. thanks, Norbert > Sven > >> Norbert >> >>> ;-) >>> >>> On 12 Feb 2014, at 12:37, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> I just discovered that there is no method like >>>> >>>> indexOf: aBlock >>>> >>>> where the index of the element matching the block is returned. What would be the usual way to achieve this functionality? >>>> >>>> Norbert >>>> >>>> >>> >>> >> >> > >

Feb. 12, 2014

Re: [Pharo-users] Applications, features and unit tests

by Marcus Denker

On 12 Feb 2014, at 13:18, Leonardo Silva <leonardo.humberto(a)gmail.com> wrote: > Hi everyone, > > I am a PhD student at UFMG-Brazil (together with INRIA-France in a project) working with dynamic analysis of software systems' architecture. > The idea, initially, is to check the link between dynamic behavior and static structure (architecture) of a system, regarding its features. > > I am looking for real applications in Smalltalk that have a mapping between its features and the specific unit tests for them. I once did something that might be related: Marcus Denker, Jorge Ressia, Orla Greevy, and Oscar Nierstrasz. Modeling Features at Runtime. In Proceedings of MODELS 2010, LNCS 6395 p. 138â152, Springer-Verlag, 2010. A feature represents a functional requirement fulfilled by a system. Since many maintenance tasks are expressed in terms of features, it is important to establish the correspondence between a feature and its implementation in source code. Traditional approaches to establish this correspondence exercise features to generate a trace of runtime events, which is then processed by post-mortem analysis. These approaches typically generate large amounts of data to analyze. Due to their static nature, these approaches do not support incremental and interactive analysis of features. We propose a radically different approach called live feature analysis, which provides a model at runtime of features. Our approach analyzes features on a running system and also makes it possible to grow feature representations by exercising different scenarios of the same feature, and identifies execution elements even to the sub-method level. We describe how live feature analysis is implemented effectively by annotating structural representations of code based on abstract syntax trees. We illustrate our live analysis with a case study where we achieve a more complete feature representation by exercising and merging variants of feature behavior and demonstrate the efficiency or our technique with benchmarks. Slides: http://marcusdenker.de/talks/coauthors/10MODELS/2010-Models-LiveFeatureAnal… Paper: http://rmod.lille.inria.fr/archives/papers/Denk10a-Models10-FeatureModels.p…

Feb. 12, 2014

Re: [Pharo-users] index of element matching block

by Sven Van Caekenberghe

On 12 Feb 2014, at 13:02, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 12.02.2014 um 11:44 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> #( 11 7 4 21 ) detectIndex: #even >> > I knew it makes sense to ask. Only slightly embarrasing :) These little challenges are always quite fun. Sven > Norbert > >> ;-) >> >> On 12 Feb 2014, at 12:37, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> I just discovered that there is no method like >>> >>> indexOf: aBlock >>> >>> where the index of the element matching the block is returned. What would be the usual way to achieve this functionality? >>> >>> Norbert >>> >>> >> >> > >

Feb. 12, 2014