- Pharo-dev - lists.pharo.org

[Pharo-project] MC dependency issue
by Camillo Bruni April 1, 2011

April 1, 2011

Hhere is my problem. v169 has (v165 and v168) as ancestors. BUT v165 does no longer exist, locally nor on the squeaksource server. Is there way to manually fix this? Due to this I am currently unable to load any future versions... ~(x_x)~ camillo

1 0

[Pharo-project] Issue 3896 in pharo: 1.3 core has wrong theme enabled
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3896 by marcus.d...(a)gmail.com: 1.3 core has wrong theme enabled http://code.google.com/p/pharo/issues/detail?id=3896 ... should turn on Glamour theme

1 2

[Pharo-project] Issue 3920 in pharo: String has extension for *graphics
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3920 by marcus.d...(a)gmail.com: String has extension for *graphics http://code.google.com/p/pharo/issues/detail?id=3920 String has extension for *graphics this package does not exist.

1 2

[Pharo-project] Issue 3922 in pharo: Add ClassHierarchy Checks
by pharo＠googlecode.com April 1, 2011

April 1, 2011

Status: New Owner: ---- New issue 3922 by camillob...(a)gmail.com: Add ClassHierarchy Checks http://code.google.com/p/pharo/issues/detail?id=3922 Verify all the classes in the system that superclass and subclass are set correctly: Attachments: ClassHierarchyTest.st 908 bytes

1 3

[Pharo-project] Dynamic Languages Symposium 2011: call for participation
by Theo D'Hondt April 1, 2011

April 1, 2011

Dynamic Languages Symposium 2011 Co-located with SPLASH 2011 In association with ACM SIGPLAN Portland, Oregon, USA, October 24, 2011 http://www.dynamic-languages-symposium.org/dls-11/ *** Call for papers *** The 7th Dynamic Languages Symposium (DLS) at SPLASH 2011 is a forum for discussion of dynamic languages, their implementation and application. While mature dynamic languages including Smalltalk, Lisp, Scheme, Self, Prolog, and APL continue to grow and inspire new converts, a new generation of dynamic scripting languages such as Python, Ruby, PHP, Tcl, Lua, and JavaScript are successful in a wide range of applications. DLS provides a place for researchers and practitioners to come together and share their knowledge, experience, and ideas for future research and development. DLS 2011 invites high quality papers reporting original research, innovative contributions or experience related to dynamic languages, their implementation and application. Accepted Papers will be published in the ACM Digital Library. Areas of interest include but are not limited to: - Innovative language features and implementation techniques - Development and platform support, tools - Interesting applications - Domain-oriented programming - Very late binding, dynamic composition, and runtime adaptation - Reflection and meta-programming - Software evolution - Language symbiosis and multi-paradigm languages - Dynamic optimization - Hardware support - Experience reports and case studies - Educational approaches and perspectives - Object-oriented, aspect-oriented, and context-oriented programming * Submissions and proceedings * We invite original contributions that neither have been published previously nor are under review by other refereed events or publications. Research papers should describe work that advances the current state of the art. Experience papers should be of broad interest and should describe insights gained from substantive practical applications. The program committee will evaluate each contributed paper based on its relevance, significance, clarity, and originality. Accepted papers will be published in the ACM Digital Library. Papers are to be submitted electronically at http://www.easychair.org/conferences?conf=dls2011 in PDF format. Submissions must not exceed 12 pages and need to use the ACM format, templates for which can be found at http://www.acm.org/sigs/pubs/proceed/template.html. * Important dates * Submission of papers: June 17, 2011 (hard deadline) Author notification: July 19, 2011 Final versions due: August 19, 2011 DLS 2011: October 24, 2011 SPLASH 2011: October 22-27, 2011 * Program chair * Theo D'Hondt, Software Languages Lab, Vrije Universiteit Brussel, Belgium * Program committee * Andrew Black, Portland State University, USA William R. Cook, University of Texas at Austin, USA Marc Feeley, University of Montreal, Canada Roberto Ierusalimschy, PUC-Rio, Brazil Michele Lanza, University of Lugano, Switzerland Hidehiko Masuhara, University of Tokyo, Japan Mira Mezini, University of Darmstadt, Germany Mark Miller, Google, USA Manuel Serrano, INRIA Nice, France Laurence Tratt, Middlesex University, UK David Ungar, IBM, USA Didier Verna, EPITA Research and Development Laboratory, France ________________ Theo D'Hondt tjdhondt(a)vub.ac.be

1 0

[Pharo-project] Regarding SimpleMorphic
by Torsten Bergmann April 1, 2011

April 1, 2011

Stef wrote: >Why this hierarchy is wrong? I did not say that the hierarchy is correct! And agree that composition is better suited than inheritance here. But Benjamin said "Workspace is not a model, it's a view basically." This is wrong since this is more centralized towards what you see (the workspace view) and not whats behind it. I'm just at the position that a Browser IS A model and NOT a view and that it can have one or more different views. Nothing more said in my post. Fernando Olivero >Correct, but this is not enough to advocate for the removal of the >Browser as a "model" for the view. +100 Just because the model assembles the view that doesnt mean we should remove a clean browser model!!! We should clearly support MVC in the future and also introduce a View class. Let's think about it: Model subclass Browser View subclass BrowserView If we have a browser view - how strongly connected should it be to Morphic - especially when we think of other kind of UI bindings like Morphic, SimpleMorphic, GtK, HTML, ... Or should we name it BrowserMorph? And is this hierarchy design/naming correct. Let's verify: It is not necessary that the model assembles the view - but often wished that you open the view by sending a simple message. Currently in Pharo you send it to the model: "Browser open" If you evaluate the result you SEE is a view, the result you GET if you inspect it is the model (who shouldnt know about the views). But often you also wish to acess the view (who always knows about its model). So we have a conflict here and have to use tricks to access the view afterwards. So what about a different design, lets use the name "Browser" for the view part: Model subclass BrowserModel View subclass Browser If you evaluate "Browser open" you should get a view back on the browser and if you ask for "model" you should get the instance of BrowserModel. Looks cleaner but different from what we currently have. Maybe we talk all about the same thing and it is more about naming. We could also be more explicit: Model subclass BrowserModel View subclass BrowserView Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

1 0

[Pharo-project] [OT] I've started blogging
by Mariano Martinez Peck April 1, 2011

April 1, 2011

Hi guys. Just in case someone is interested, I've have started blogging: "Sending messages through small talks" The blog is here: http://marianopeck.wordpress.com/ Any kind of feedback is more than welcome. Mariano

5 5

[Pharo-project] Issue 3088: MNU Text>>withBlanksTrimmed
by Bernardo Ezequiel Contreras March 31, 2011

March 31, 2011

Hi All, Could you check this issue http://code.google.com/p/pharo/issues/detail?id=3088 ? IMHO it is not closed. Thanks

1 0

[Pharo-project] [OT] Blog sequence "Journey through the VM"
by Mariano Martinez Peck March 31, 2011

March 31, 2011

Hi folks. I will start a sequence of VM related posts called âJourney through the VMâ, similar to what Igor did in Deep Smalltalk School<http://www.inria.fr/centre-de-recherche-inria/lille-nord-europe/agenda/smal…>. My main focus is that a regular Smalltalker, without any knowledge in VM stuff can understand the basis of it (ObjectMemory, Interpreter, etc). In addition, I expect the reader can download, change, compile, run, and debug (and why not fixing?) the VM. Later on in the journey, I would also like to talk about what the compiler does, what bytecodes are, how to read them, how they are mapped to the VM, etc. I will also show some hooks or tricks that the VM provides and that are not always known. Moreover, I will explain what a primitive is, how they are executed by the VM, how you can write your own primitives, etc. FFI and writing your own plugin are also in my plans. It is important to notice that all these posts are thought for VM newbies. I would appreciate if there can be some VM hackers paying attention that I don't say stupid things. http://marianopeck.wordpress.com/ Cheers

3 2

March 31, 2011

13124 ----- - Issue 3928: Add reciprocalModulo: support in Kernel. Thanks Nicolas Cellier - Issue 3926: MorphTreeMorph autoSelet. Thanks Benjamin van Ryseghem. - Lesser Polymorph overrides Thanks guys. the community pulses....

1 0