- Pharo-dev - lists.pharo.org

Re: [Pharo-project] BalloonCanvas>>drawPolygon

by Hilaire Fernandes

Le 26/02/2013 16:43, stephane ducasse a Ã©crit : > can you open a bug entry on the pharo bug tracker? so that we can have a look. Done. Btw, a redirection http://bug[s].pharo.org will be very handy. Hilaire

Feb. 26, 2013

[Pharo-project] Call for papers for Dyla'13: 7th Workshop on Dynamic Languages and Applications @ ECOOP

by Alexandre Bergel

Dyla'13, 7th Workshop on Dynamic Languages and Applications Colocated with ECOOP, ECMFA and ECSA 1â5 July, Montpellier, France http://rmod.lille.inria.fr/web/pier/Events/Dyla13 !! Important dates - Submission deadline: April 19th - Notification: mid-May - Workshop: July 1st - Ecoop early registration: mid-May !! Abstract The advent of Java and C# has been a major breakthrough in the adoption of some important object-oriented language characteristics. This breakthrough turned academic features like interfaces, garbage collection, and meta-programming into technologies generally accepted by industry. Nevertheless, the massive adoption of these languages now also gives rise to a growing awareness of their limitations. A number of reactions from industry testify this: invokedynamic bytecode instruction has been included in latest Java virtual machine release; the dynamic language runtime (DLR) is gaining popularity; C# adopted dynamic as a valid static type. Gartner prognoses further growth (http://blogs.gartner.com/mark_driver/2008/12/10) of dynamic languages. Researchers and practitioners struggle with static type systems, overly complex abstract grammars, simplistic concurrency mechanisms, limited reflection capabilities, and the absence of higher-order language constructs such as delegation, closures and continuations. Dynamic languages such as Ruby, Python, JavaScript and Lua are a step forward in addressing these problems while getting more and more popular. Making these languages mainstream requires practitioners to look back and pick mechanisms up in existing dynamic languages such as Lisp, Scheme, Smalltalk and Self. Practitioners also need to further explore discover new dynamic approaches in the context of new challenging fields such as pervasive computing. The goal of this workshop is to act as a forum where practitioners can discuss new advances in the design, implementation and application of dynamically typed languages that, sometimes radically, diverge from the statically typed class-based mainstream. Another objective is to discuss new as well as older "forgotten" languages and features in this context. Topics of interest include, but are not limited to: - programming language extensions - programming environment extensions - executing environments - static and dynamic analyses - optional type-checking - meta-object protocols - reserve engineering - domain-specific languages/tooling - testing environments - live programming !! Targeted audience The expected audience of this workshop is practitioners and researchers sharing the same interest in dynamically typed languages. Lua, Python, Ruby, Scheme and Smalltalk are gaining a significant popularity both in industry and academia. Nevertheless, each community has the tendency to only look at what it produces. Broadening the scope of each community is the goal of the workshop. To achieve this goal we will form a PC with leading persons from all languages mentioned above, fostering participation from all targeted communities. !! Workshop Format and Submission Information The workshop will have a demo-oriented style. The idea is to allow participants to demonstrate new and interesting features and discuss what they feel is relevant for the dynamic-language community. To participate to the workshop, you can either - submit (before __April 19th 2013__) an article (ACM Tighter Alternate style http://www.acm.org/sigs/publications/proceedings-templates) describing your presentation and/or tool. Articles whose length ranges from 2 to 15 pages will be carefully reviewed by a program committee including but not limited to the organizers. Each accepted paper will be presented for 20 to 30 minutes and be published to the ACM Digital Library (at the option of each author) and the workshop's web site. The submission website is http://www.easychair.org/conferences/?conf=dyla2013. - or give a 10-minute lightning demo of your work. A dedicated session will be allocated for this, provided there is ample time available. A session on pair programming is also planned. People will then get a chance to share their technologies by interacting with other participants. !! Program committee - Carl Friedrich Bolz, Heinrich-Heine-UniversitÃ¤t DÃ¼sseldorf, Germany (http://cfbolz.de) - Camillo Bruni, Inria Lille-Nord Europe, France (http://rmod.lille.inria.fr/web/pier/team/bruni) - Adrian Kuhn, University of British Columbia, Canada (https://www.cs.ubc.ca/people/adrian-kuhn) - Lukas Renggli, Google, Switzerland (http://www.lukas-renggli.ch/) - Juan Pablo Sandoval Alcocer, University of Chile (http://users.dcc.uchile.cl/~jsandova/) - Bastian Steinert, Hasso-Plattner-Institute, Germany (http://www.bastiansteinert.org) - Veronica Uquillas Gomez, Vrije Universiteit Brussel, Belgium (http://soft.vub.ac.be/~vuquilla/) - Simon Urli, University of Nice-Sophia Antipolis, France (http://www.simonurli.fr/) - Didier Verna, EPITA Research and Development Laboratory, France (http://www.lrde.epita.fr/~didier) - the 4 workshop organizers !! Workshop Organizers - Alexandre Bergel (http://bergel.eu) - Damien Cassou (http://damiencassou.seasidehosting.st) - Jorge Ressia (http://www.jorgeressia.com) - Serge Stinckwich (http://www.doesnotunderstand.org) !! News feed Follow us on twitter: http://twitter.com/dyla2013 For further information: http://rmod.lille.inria.fr/web/pier/Events/Dyla13 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by Frank Shearar

On 26 February 2013 19:06, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Hi Frank, > > 2013/2/26 Frank Shearar <frank.shearar(a)gmail.com>: >> On 26 February 2013 18:33, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> But it is true that GitHub is to SmalltakHub what npm/gem is to...? >> >> No. GitHub and SmalltalkHub are repositories. Rubygems for Ruby (or >> clojars for Clojure, or CPAN for Perl) - are like SqueakMap - catalogs >> that point to packages/applications. > > That's exactly what I said, that GitHub and SmalltalkHub are analogous. > But we also need something like rubygems or npm or CPAN. > > I never used SqueakMap, so I can't tell. But if it is there, why is it > not being used? That's an excellent question, and one that Chris Muller and I would love an answer to. Partly it's because it's old and crufty. It could do with a rewrite, to be honest. But the idea is sound - the one place to go to find packages - and it works _today_. frank

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by Esteban A. Maringolo

Hi Frank, 2013/2/26 Frank Shearar <frank.shearar(a)gmail.com>: > On 26 February 2013 18:33, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> But it is true that GitHub is to SmalltakHub what npm/gem is to...? > > No. GitHub and SmalltalkHub are repositories. Rubygems for Ruby (or > clojars for Clojure, or CPAN for Perl) - are like SqueakMap - catalogs > that point to packages/applications. That's exactly what I said, that GitHub and SmalltalkHub are analogous. But we also need something like rubygems or npm or CPAN. I never used SqueakMap, so I can't tell. But if it is there, why is it not being used? Regards,

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by Frank Shearar

On 26 February 2013 18:33, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2013/2/26 Marcus Denker <marcus.denker(a)inria.fr>: >> On Feb 26, 2013, at 5:33 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > >>> If you count the number of packages in SmalltalkHub and compare them >>> to the ones in Npmjs.org, it is impressive how much we have. >> But isn't "package" more like "repository" on smalltalkhub? > > It is a Project, but on the explore screen it says Packages, so... who knows? :) > > But it is true that GitHub is to SmalltakHub what npm/gem is to...? No. GitHub and SmalltalkHub are repositories. Rubygems for Ruby (or clojars for Clojure, or CPAN for Perl) - are like SqueakMap - catalogs that point to packages/applications. frank >>> Of course NPM's user base is two orders of magnitude greater, but we >>> need to start having more killer app "modules", and some sort of >>> guideline for those starting with Pharo and/or Smalltalk. >> And we need a system in the first place like thatâ¦ smalltalkhub is more for code >> repositories, not in itself a repository of installable entities. > > Yes, having packages as "artifacts" is more straightforward than the > configurations and all that jazz. > > The MetaRepo is going in that direction, but I still think that > evaluating the install statements with Gofer or anything similar in a > Workspace is somehow alien for a non smalltalker. > > There should be something that wraps Gofer and works like the apt, npm > or gem commands. > >> So there is a lot of work aheadâ¦ but we will get there. > > No doubts of that. > > > Regards! >

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by Sven Van Caekenberghe

On 26 Feb 2013, at 17:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > On Feb 26, 2013, at 4:57 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> I love the complete ecosystem you are step by step building. >> This is so great! > > Yes! Just imagine we continue like thatâ¦ we are now (slowly, slowly) reaching a point > where for the first time we can really build on top of the foundation we did. > > One central idea behind Pharo was to so we can do better on top of what we did. > The effect we will get from that will be very interesting. Until now we have seen almost > nothing, but now we are entering a phase where the difference will be not very pronounced > but visible if you look for it. > > Reflective improvement, leading to a feedback loopâ¦ and thus non-linear effects. > I know that some people are laughing about this, but I really believe in it :-) > > Marcus Yes, that is certainly true. But there is not only a technical feedback loop with non linear effects, there is also a human and community reinforcement and accelleration going on that is really, really impressive. There are so many sub projects in/on Pharo, actually way too many to enumerate. They each directly or indirectly help or facilitate the others, spreading knowledge, creating Smalltalkers all over the world doing amazing stuff on the same base system. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by Esteban A. Maringolo

2013/2/26 Marcus Denker <marcus.denker(a)inria.fr>: > On Feb 26, 2013, at 5:33 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: >> If you count the number of packages in SmalltalkHub and compare them >> to the ones in Npmjs.org, it is impressive how much we have. > But isn't "package" more like "repository" on smalltalkhub? It is a Project, but on the explore screen it says Packages, so... who knows? :) But it is true that GitHub is to SmalltakHub what npm/gem is to...? >> Of course NPM's user base is two orders of magnitude greater, but we >> need to start having more killer app "modules", and some sort of >> guideline for those starting with Pharo and/or Smalltalk. > And we need a system in the first place like thatâ¦ smalltalkhub is more for code > repositories, not in itself a repository of installable entities. Yes, having packages as "artifacts" is more straightforward than the configurations and all that jazz. The MetaRepo is going in that direction, but I still think that evaluating the install statements with Gofer or anything similar in a Workspace is somehow alien for a non smalltalker. There should be something that wraps Gofer and works like the apt, npm or gem commands. > So there is a lot of work aheadâ¦ but we will get there. No doubts of that. Regards!

Feb. 26, 2013

Re: [Pharo-project] fast #becomeForward: crashes without PharoV10.sources

by Eliot Miranda

On Tue, Feb 26, 2013 at 4:13 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > we should reafctor the code for changing the method's trailer (source > pointer) to > avoid using #become: at all. > this won't deal with VM bug per se, but at least prevent it from > triggering. > No, that makes little sense. Instead provide me with a reproducible case and I'll fix it quickly. I fixed the case form last week in one day. Become: should work, but I can't fix things if I can't reproduce the bugs. So please take the time to produce an image that crashes from start-up. > > On 25 February 2013 23:26, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > he is talking about some chrashes that happens fast, when you do become > :) > > > > nothing about "fast become" > > > > On Feb 25, 2013, at 10:26 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> > > wrote: > > > > mmm what do you mean by "fast becomeForward:" ? > > > > On Mon, Feb 25, 2013 at 1:01 PM, Camillo Bruni <camillobruni(a)gmail.com> > > wrote: > >> > >> While setting up the new multi platform VM tests I saw that the tests > fail > >> extremely quickly > >> when there are not PharoV10.sources available. > >> > >> It is still our know #becomeForward: but on CompiledMethods, but I just > >> want to share that. > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > > > -- > Best regards, > Igor Stasenko. > > -- best, Eliot

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by stephane ducasse

Serge what is important is to produce configuration for the projects. We are working on a tool to help us with that but this is not ready yet. >> > > This is a great strength of programming languages like Ruby or JavaScript/Node > to propose large repositories of packages that could be installed very > easily with all the correct dependencies. > > Nice to see that thanks to the guys from INRIA (and more generally > from the community), the Pharo ecosystem is following the same way. I > also agree with Marcus that the day will come where the progress will > be more visible. > > I'm currently on the way to move all my packages from SqueakSource to > SmalltalkHub. > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ >

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by stephane ducasse

I like a lot this prediction and we will see that it will start to happen in Pharo3.0 Stef On Feb 26, 2013, at 5:18 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 26, 2013, at 4:57 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> I love the complete ecosystem you are step by step building. >> This is so great! >> > > Yes! Just imagine we continue like thatâ¦ we are now (slowly, slowly) reaching a point > where for the first time we can really build on top of the foundation we did. > > One central idea behind Pharo was to so we can do better on top of what we did. > The effect we will get from that will be very interesting. Until now we have seen almost > nothing, but now we are entering a phase where the difference will be not very pronounced > but visible if you look for it. > > Reflective improvement, leading to a feedback loopâ¦ and thus non-linear effects. > I know that some people are laughing about this, but I really believe in it :-) > > Marcus > > > > > >

Feb. 26, 2013