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

Re: [Pharo-dev] [update 3.0] #30267

by Damien Cassou

On Thu, Jul 11, 2013 at 6:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > 11151 More changes needed to trait/classes polymorphism > https://pharo.fogbugz.com/f/cases/11151/ That's huge. Soon, we will be able to remove thr ClassDescription and Behavior classes. It makes sense because they are useless in the presence of traits. But do people want it? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 12, 2013

Re: [Pharo-dev] OpenDBX problem with simultaneus connections

by Facundo Vozzi

Mariano, is OpenDBXDriver-MarianoMartinezPeck.38 your last commit? Thanks On Thu, Jul 11, 2013 at 5:21 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > I recommend to update to the last commit I did... > Otherwise, if you were using different instances of Login for each session > you should have several SelmaConnectionPool alive :) (rather than 1) > > > On Sat, Jul 6, 2013 at 5:54 PM, Facundo Vozzi <facundov79(a)gmail.com>wrote: > >> Thanks Esteban. >> >> Now, I changed GlorpOpenDBXPoolingDriver for GlorpOpenDBXDriver and all >> is working properly. I'll try to fix the problem because I think that will >> be a problem the number of postgres.exe process running on the server this >> way. >> >> >> On Sat, Jul 6, 2013 at 5:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: >> >>> >>> On Jul 6, 2013, at 7:15 PM, Facundo Vozzi <facundov79(a)gmail.com> wrote: >>> >>> Hi, >>> I migrated my small app from Pharo 1.3 to Pharo 2.0. I'm using DBXTalk >>> and GlorpDBX. >>> >>> It's working perfectly on my notebook (Windows 7 64 bits and postgreSql >>> 9.1) but on my server (Windows 2003 32 bits server and postgreSql 9.0) I'm >>> getting this error at OpenDBXWin32 level with 3 simultaneus connections: >>> * 'FATAL: lo siento, ya tenemos demasiados clientes'*. >>> >>> It's strange (for me) because the version on Pharo 1.3 works properly in >>> both machines but the version on Pharo 2.0 works perfect on my notebook and >>> works properly for the first two connections on the server. >>> >>> I think that could be a problem with the OpenDBX library with the server >>> and the implementation of FFI on Pharo 2.0 but I can't figure out it. >>> >>> Any suggestions? >>> >>> Thanks in advance, >>> Facundo >>> >>> p.s.: where is hosted the DBXTalk project now? I can't find it on >>> http://dbxtalk.smallworks.com.ar/ anymore >>> >>> >>> sorry, I'm changing servers and the DNS is not well refreshed yet... >>> however, you can find it here: >>> >>> http://dbxtalk.smallworks.eu >>> >>> >>> <Error on the third connection attempt.txt> >>> >>> >>> >> > > > -- > Mariano > http://marianopeck.wordpress.com >

July 12, 2013

Fwd: What's new in Graph-ET?

by Alexandre Bergel

FYI Begin forwarded message: > From: Daniel Aviv Notario <daniel_avivnotario(a)hotmail.com> > Subject: What's new in Graph-ET? > Date: July 11, 2013 8:49:53 PM GMT-04:00 > To: "moose-dev(a)iam.unibe.ch" <moose-dev(a)iam.unibe.ch>, "alexandre.bergel(a)objectprofile.com" <alexandre.bergel(a)objectprofile.com>, "tudor(a)tudorgirba.com" <tudor(a)tudorgirba.com> > > Hi! > > Here is a report of the advances in Graph-ET, what I have been working on and what I have left. > > For those of you who (probably) don't know, Graph-ET is my project for the GSoC 2013, my mentors are Tudor Girba and Alexandre Bergel. Graph-ET is a charting tool, similar to EyeSee but with the difference that GET uses Roassal to make the visualizations. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > What's new? > - Worked a lot in the axis placement, both for horizontal and vertical bar diagrams. > - Added the line diagram in the form of two diagrams: GETLineDiagram (for ploting mathematical functions) and GETOrdinaryLineDiagram. > - Fixed A WHOLE LOT of bugs. > - Made a little refactoring. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > What's to come? > - Add the rest of the charts/diagrams in EyeSee. > - Fix some bugs. > - Probably do a little refactoring related to the axis, as I repeatedly do stuff like ifVertical:[...] ifHorizontal:[...]. > - Make some sexy examples ;-). > - Adding cool features present in EyeSee like labeling. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > How to get it? > Here's the Gofer: > > Gofer new > > smalltalkhubUser: ââ > > project: âGraph-ETâ > > package: âGraph-ETâ. > > > > Remember to load the last version of Roassal first thought! > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Some examples > > Try doing these in a workspace: > > "GETExamples verticalBarExample6" > > > "GETExamples lineBasicExample2" > > > > As always, any doubts, comments or questions just email me, I'll be glad to answer them ASAP :-) > > - Daniel Aviv Notario > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 12, 2013

Re: [Pharo-dev] the return of the strange methods

by Camillo Bruni

On 2013-07-11, at 09:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > On Jul 11, 2013, at 8:32 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> On Jul 11, 2013, at 8:26 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> I would really like to have Sunit 5 in Pharo. >>> >> >> Of course we added lots of things to Sunit, so this means rewriting tests. (e.g. skip). >> >> And we will get the sunit* methods backâ¦ I hate them :-) > this is why we should > - have the possibility to have two different Unit frameworks > - take the time to get the new version. It only makes sense to adapt the public methods on TestCase, the rest we should keep or rewrite. We really need a separate test runner (not UI, but model) as it is done in SMark for instance.

July 11, 2013

Ph.D. Student Position on Dynamic Reflective Language Integration with FPGAs for Robotic Applications

by jannik.laval

Dear Smalltalkers, We are searching for a PhD Student. Following you will find the proposal. Best regards, ====== Location: Mines de Douai and ENSTA Brest (France) Advisor and contacts: Noury Bouraqadi, Luc Fabresse, Jannik Laval (car(a)mines-douai.fr, website: http://car.mines-douai.fr/) LoÃ¯c Lagadec (loic.lagadec(a)ensta-bretagne.fr) Profile: the candidate must hold a recent Master of Science degree in Computer Science or Software Engineering and must have solid skills in dynamic reflective language and OOP. Description of the work: The goal of this PhD is to study Smalltalk integration with FPGAs for robotic applications. This integration will enable us get the best from both worlds. Developers are provided with a high-level dynamic reflective language (Smalltalk) for building and debugging their applications. Still, we can have high performances by projecting part of the programs into FPGAs. These reconfigurable hardware chips can achieve performance faster than C programs, while consuming much less energy. The work to do can decompose into the following tasks: -Build reference robotic applications fully in Pharo Smalltalk using actual robots (see http://car.mines-douai.fr/robots/) -Analyze these applications to identify critical parts to project on FPGAs to significantly increase performances (speed, energy) -Do the actual projection to FPGA and evaluate performances of the transformed applications -Generalize the approach and define a methodology for turning Smalltalk code into FPGA -Propose a solution to automate the methodology The Ph.D student will receive a grant which net amount is approximately 1420 euros per month for 3 years (36 months). He will be co-supervised by LoÃ¯c Lagadec from the ENSTA-Bretagne (Lab-STICC, Brest) and Jannik Laval, Luc Fabresse and Noury Bouraqadi from Ecole des Mines de Douai (CAR, http://car.mines-douai.fr/) The first 18th month will be spent in Douai (Lille area), while the last half of the PhD will be spent in Brest. However, during the full 3 years, there will be a strong interaction with co-supervisers from both labs. Bibliography: -A Robust Layered Control System For A Mobile Robot. R. Brooks. IEEE Journal of Robotics and Automation. Vol. 2. Num 1. March, 1985. -RCS: A Cognitive Architecture for Intelligent MultiAgent Systems. J.S. Albus and A. J. Barbera. Proceedings of the 5th IFAC/EURON Symposium on Intelligent Autonomous Vehicles (IAV 2004). Lisbon, Portugal, 2004. -Handbook of Robotics. Bruno Siciliano and Oussama Khatib editors. Springer. 2008. -Multi-Level Simulation of Heterogeneous Reconfigurable Platforms. D. Picard and L. Lagadec. International Journal of Reconfigurable Computing. 2012. -High-level synthesis for FPGAs: From Prototyping to Deployment. Jason cong and stephen neuendorffer and juanjo noguera and kees vissers and zhiru zhang. IEEE Transactions on Computer-aided design of integrated circuits and systems. Vol. 30. Num 4. April, 2011. -The MOLEN Polymorphic Processor. S. Vassiliadis and S. Wong and G. Gaydadjiev and K. Bertels and G. Kuzmanov and E. Moscu Panainte. IEEE Transactions on Computers. 2004. _______________________________________________________ Jannik LAVAL Enseignant-Chercheur TÃ©l. : 03 27 71 26 32 Mines Douai 941 rue Charles Bourseul BP 10838 59508 Douai Cedex _______________________________________________________

July 11, 2013

Re: [Pharo-dev] OpenDBX problem with simultaneus connections

by Mariano Martinez Peck

I recommend to update to the last commit I did... Otherwise, if you were using different instances of Login for each session you should have several SelmaConnectionPool alive :) (rather than 1) On Sat, Jul 6, 2013 at 5:54 PM, Facundo Vozzi <facundov79(a)gmail.com> wrote: > Thanks Esteban. > > Now, I changed GlorpOpenDBXPoolingDriver for GlorpOpenDBXDriver and all is > working properly. I'll try to fix the problem because I think that will be > a problem the number of postgres.exe process running on the server this way. > > > On Sat, Jul 6, 2013 at 5:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> >> On Jul 6, 2013, at 7:15 PM, Facundo Vozzi <facundov79(a)gmail.com> wrote: >> >> Hi, >> I migrated my small app from Pharo 1.3 to Pharo 2.0. I'm using DBXTalk >> and GlorpDBX. >> >> It's working perfectly on my notebook (Windows 7 64 bits and postgreSql >> 9.1) but on my server (Windows 2003 32 bits server and postgreSql 9.0) I'm >> getting this error at OpenDBXWin32 level with 3 simultaneus connections:* 'FATAL: >> lo siento, ya tenemos demasiados clientes'*. >> >> It's strange (for me) because the version on Pharo 1.3 works properly in >> both machines but the version on Pharo 2.0 works perfect on my notebook and >> works properly for the first two connections on the server. >> >> I think that could be a problem with the OpenDBX library with the server >> and the implementation of FFI on Pharo 2.0 but I can't figure out it. >> >> Any suggestions? >> >> Thanks in advance, >> Facundo >> >> p.s.: where is hosted the DBXTalk project now? I can't find it on >> http://dbxtalk.smallworks.com.ar/ anymore >> >> >> sorry, I'm changing servers and the DNS is not well refreshed yet... >> however, you can find it here: >> >> http://dbxtalk.smallworks.eu >> >> >> <Error on the third connection attempt.txt> >> >> >> > -- Mariano http://marianopeck.wordpress.com

July 11, 2013

Re: [Pharo-dev] Notification extends Exception...

by Frank Shearar

On 11 July 2013 19:20, Guillaume Larcheveque <guillaume.larcheveque(a)gmail.com> wrote: > In my opinion, Java have the right name: an exception is something that not > occurs every time by definition. In our case, a JobStartNotification is > always thrown; which is the opposite of an exception That's all fine and good, except Smalltalk defined what "exception" meant in 1980. Common Lisp uses the word "condition". Also, almost by definition, Java is wrong. frank > 2013/7/11 Frank Shearar <frank.shearar(a)gmail.com> >> >> On 11 July 2013 17:26, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> > On 2013-07-11, at 18:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> On 11 Jul 2013, at 18:05, Nicolas Cellier >> >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> >> >>> Catching all/any Exception is generally considered a code smell >> >> >> >> In Pharo 3.0 AssertionFailure inherits from Error, which takes away my >> >> reason to catch Exception instead of Error. >> > >> > I always think we should add something like AbstractException which only >> > contains the minimal interface. >> > For me Exception has the wrong name (of course my bad Java experience >> > doesn't help here...). >> >> Just think of it this way: Java got the name wrong! >> >> frank >> > > > > -- > Guillaume Larcheveque >

July 11, 2013

Re: [Pharo-dev] Notification extends Exception...

by Guillaume Larcheveque

In my opinion, Java have the right name: an exception is something that not occurs every time by definition. In our case, a JobStartNotification is always thrown; which is the opposite of an exception 2013/7/11 Frank Shearar <frank.shearar(a)gmail.com> > On 11 July 2013 17:26, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-07-11, at 18:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 11 Jul 2013, at 18:05, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> > >>> Catching all/any Exception is generally considered a code smell > >> > >> In Pharo 3.0 AssertionFailure inherits from Error, which takes away my > reason to catch Exception instead of Error. > > > > I always think we should add something like AbstractException which only > contains the minimal interface. > > For me Exception has the wrong name (of course my bad Java experience > doesn't help here...). > > Just think of it this way: Java got the name wrong! > > frank > > -- *Guillaume Larcheveque*

July 11, 2013

Re: [Pharo-dev] Notification extends Exception...

by Frank Shearar

On 11 July 2013 17:26, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-07-11, at 18:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> On 11 Jul 2013, at 18:05, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> Catching all/any Exception is generally considered a code smell >> >> In Pharo 3.0 AssertionFailure inherits from Error, which takes away my reason to catch Exception instead of Error. > > I always think we should add something like AbstractException which only contains the minimal interface. > For me Exception has the wrong name (of course my bad Java experience doesn't help here...). Just think of it this way: Java got the name wrong! frank

July 11, 2013

[update 3.0] #30267

by Esteban Lorenzano

July 11, 2013