- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing
by Fernando Olivero Feb. 20, 2012

Feb. 20, 2012

What about: Pharo a MALEABLE language to build evolvable and debuggable applications. Fernando On Mon, Feb 20, 2012 at 11:03 AM, Guido Stepken <gstepken(a)googlemail.com> wrote: > http://en.m.wikipedia.org/wiki/Plasticity > > Am 20.02.2012 09:24 schrieb "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>>: > > On Feb 20, 2012, at 2:26 AM, Ben Coman wrote: > >> StÃ©phane Ducasse wrote: >>> I would like to get from you why you use Pharo? >>> >>> >>> >>> After thinking a lot about that recently I think that I would like to have something like that: >>> >>> Pharo a plastic language to build evolvable and debuggable applications. With Pharo and its ecosystem you can build powerful tools (web application, data management, business processesâ¦). Â Pharo philosophy is driven by domain driven design. Modeling is agile. Pharo is an executable modeling language. Pharo is not only a language but an infrastructure with powerful tools like Moose. >>> Â Â Â Plastic = "(in science and technology) of or relating to the permanent deformation of a solid without fracture by the temporary application of force." >>> >> I agree with your usage of "plastic", but there are some unfortunate english slang associations that you might want to stay away from... >> "General term for a fake, or in reference to a shallow person." >> http://onlineslangdictionary.com/meaning-definition-of/plastic > > > Yes I looked at that and I was not happy with it. > > resilience may be better > > >> >> Perhaps "ductile" would suit the same purpose. >> "able to undergo change of form without breaking" >> http://dictionary.reference.com/browse/ductile >> >> There is also "malleable" (but I think the shorter syllables of ductile is nicer to read) >> http://www.thefreedictionary.com/malleable >> >> cheers, -ben >> >>> Pharo: ease of modeling, essence of agile, close to objects all the time. >>> Stef >>> >>> >> >> > >

3 2

[Pharo-project] [update 1.3] #13323
by Marcus Denker Feb. 20, 2012

Feb. 20, 2012

13323 ----- Issue 5299: Yet another Zn update http://code.google.com/p/pharo/issues/detail?id=5299 -- Marcus Denker -- http://marcusdenker.de

3 2

[Pharo-project] Updated Pharo HTTP Server Single Command Line Demo
by Sven Van Caekenberghe Feb. 20, 2012

Feb. 20, 2012

I updated my Pharo HTTP Server OneCommandLine Demo for 1.4 http://forum.world.st/Pharo-Core-HTTP-Server-OneCommandLine-Demo-td3702218.… How easy and how fast can you download, install and start an complete Pharo based HTTP Server on a bare Linux machine ? It just takes One Single Command Line: $ curl http://zn.stfx.eu/zn/pharo-server.sh | bash In well under a minute, you can browse http://localhost:1701 and all this with less than 20Mb being downloaded. Enjoy, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

2 2

[Pharo-project] Script for building 1-click images
by Martin Sandiford Feb. 20, 2012

Feb. 20, 2012

Hi Folks, In the hope that it might be useful, I've somewhat tidied up some scripts I've been using to build 1-click images from Jenkins and uploaded to github. Nothing much to the script, but hoping it might ease the burden for whomever is doing this by hand at the moment. Git repo is here: https://github.com/msandiford/mk1click Cheers, Martin

3 4

[Pharo-project] Craig Latta is available for work
by Craig Latta Feb. 20, 2012

Feb. 20, 2012

Hi-- I'm looking for new clients or an employer; my resume is at http://netjam.org/resume/. thanks! -C -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547

1 0

[Pharo-project] Putting source code in method trailer [WAS] Re: Speeding up Finder string search
by Mariano Martinez Peck Feb. 20, 2012

Feb. 20, 2012

On Tue, Jan 17, 2012 at 6:31 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > If you don't bother about being slow, you can also make it much easier: >> >> >> |trailer source m | >> m := (Gofer>>#load). >> trailer := m trailer. >> source := m getSource. >> trailer sourceCode: source. >> m becomeForward: (m copyWithTrailerBytes: trailer) >> >> and if you want to do it for the whole image you can use one bulk become >> and it will be fast. >> >> I will experiment and see if it is working. >> >> > Well, with the following script it seems I am able to embed all source code in trailers: | trailer source key dict classes | dict := IdentityDictionary new. CompiledMethod allInstances do: [:aMethod | trailer := aMethod trailer. source := aMethod getSource. trailer sourceCode: source. dict at: aMethod put: (aMethod copyWithTrailerBytes: trailer). ]. dict keys asArray elementsExchangeIdentityWith: dict values asArray. Problem is that after executing the script, when a method is recompiled from the system browser, it puts back a trailer with a .changes pointer :( I will see if I find where I can change that. Cheers -- Mariano http://marianopeck.wordpress.com

7 11

[Pharo-project] Marking methods
by Bernat Romagosa Feb. 20, 2012

Feb. 20, 2012

Hi list, I've been thinking for a while that it'd be great if we could somehow graphically mark methods in the browser. Like adding an icon next to their name or highlighting them in different colors. When reviewing code, I find myself going through methods and would love to be able to mark them once they've been reviewed, to prevent me from going through them again. Does anyone else have the same needs? How do you guys manage this? I thought about flagging methods, but that'd mean I'd have to read through all my methods again to remove the flags once I'm done with the revision. Cheers, -- Bernat Romagosa.

6 5

[Pharo-project] [update 1.4] #14341
by Marcus Denker Feb. 20, 2012

Feb. 20, 2012

14341 ----- Issue 5329: ToolsTest-PointerFinder failing tests http://code.google.com/p/pharo/issues/detail?id=5329 Issue 5334: new method in AstractTool http://code.google.com/p/pharo/issues/detail?id=5334 Issue 5333: Improve LazyMultiColumnMorph http://code.google.com/p/pharo/issues/detail?id=5333 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] [squeak-dev] first draft of the next Spoon presentation
by Enrico Spinielli Feb. 20, 2012

Feb. 20, 2012

Slides look ok, but its the voice I missed most ;-) It is since long time I am watching from distance Spoon, i.e. tried to read and understand what it is about and more importantly what its potentials are. I am still willing to understand more. Please go ahead with documenting/explaining your work and vision! All the best Enrico On Sun, Feb 19, 2012 at 23:53, Craig Latta <craig(a)netjam.org> wrote: > > Hi all-- > > Here's the first draft of my next Spoon presentation. I would love > to hear any feedback you have! > > http://wp.me/psJuY-3e > > > thanks! > > -C > > -- > Craig Latta > www.netjam.org/resume > +31 6 2757 7177 > + 1 415 287 3547 > > > -- Enrico Spinielli "Do Androids dream of electric sheep?"â Philip K. Dick "Hear and forget; see and remember;do and understand."âMitchel Resnick "He who refuses to do arithmetic is doomed to talk nonsense."âJohn McCarthy

1 0

[Pharo-project] Call for Submission on Special issue on "Advances in Dynamic Languages"
by Andres Valloud Feb. 20, 2012

Feb. 20, 2012

================================================ Special issue on "Advances in Dynamic Languages" ================================================ Special issue of Elsevier's Science of Computer Programming (SCICO) Context ------- Over recent years we have seen an increased interest in dynamic programming languages such as Smalltalk, Lisp, Scheme, PHP, JavaScript, Self, Python, Ruby, and so on. These languages have taken a prominent role in teaching, web development, scripting, rapid prototyping, tool building, language engineering, and many other domains. For this special issue we invite high-quality papers that focus on novel research related to dynamic programming languages and applications of these languages. We are interested in research that uses dynamic languages in the context of, but not restricted to: - Aspects, aspect Languages and applications. - Ambient intelligence, ubiquitous / pervasive computing and embedded systems. - Compilation technology, optimization, virtual machines. - Language engineering, extensions. - Model-driven engineering / development. - Meta-modeling, reflection and meta-programming. - Programming in the large; design, architectures and components. - Programming environments, browsers, user interfaces, UI frameworks. - Source-code analysis and manipulation (static analysis, refactoring, type inference, metrics). - Testing, eXtreme Programming / practices. - Web services, internet applications, event-driven programming. - Experience reports. The special issue is associated with the Smalltalks 2011 conference. The Smalltalks series of conferences (www.fast.org.ar) is a lively forum on Smalltalk-based software technologies that brings together more than 200 people from both academia and industry for a period of three days. Submission Guidelines --------------------- Papers should be written in English, in PDF-format and should not exceed 25 pages (including references and figures), using the Elsevier journal format. The LaTeX template for this format can be found at http://www.elsevier.com/wps/find/authorsview.authors/latex Papers must be submitted through the EES submission system located at http://ees.elsevier.com/scico/default.asp. When reaching the "Article type" step in the submission process, it is important to select "Special issue: Advances in Dynamic Languages". Each paper will be reviewed by at least 3 experts within the domain. The accepted papers will be published in a special edition of Elsevier's Science of Computer Programming. Papers submitted must not have been previously published (at least 30% new material) and must not be under review for publication elsewhere. Papers must strictly adhere to submission guidelines. If you have questions, please send an e-mail to Jannik Laval (jlaval(a)labri.fr) and Andy Kellens (akellens(a)vub.ac.be) Important dates (tentatively) ----------------------------- - Submission round 1: March 16, 2012 - Feedback round 1: May 17, 2012 - Submission round 2: June 29, 2012 - Feedback round 2 (final notification): August 17, 2012 - Camera ready version: September 14, 2012 Guest editors ------------- - Andy Kellens (Vrije Universiteit Brussel, Belgium) - Jannik Laval (LaBRI Bordeaux, France) .

1 0