February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Path>>parentUpTo: aParentDirName

by Sven Van Caekenberghe

On 25 Feb 2014, at 15:01, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Okay, Iâll take a look later (donât know when) > > and > > I keep the impression of unnecessary friction to receive contributions > > Something to think about I am sorry it feels that way, but it is not. It is the difference between sending an actual git pull request on the source code and an email with some partial, copied code. The first is more work for you, but can be used in automated systems like our CI, can be merged with one operation and will serve as a historic record. The latter pushes all the work to the integrators, who are already overloaded. Making a slice is not more work that using Monticello, which you are probably doing every day. > On Feb 25, 2014, at 10:40 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 25 Feb 2014, at 14:36, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >> >>> Would this be okay? >>> >>> https://pharo.fogbugz.com/f/cases/12991/navigation-enhancement-Path-parentU… >> >> Well, not yet, you should learn how to make a actual slice... >> >> http://www.pharo-project.org/community/issue-tracking >> >> there are 2 movies and there is an explanation. >> >> Sven >> >> >> >

Feb. 25, 2014

image traffic

by Camillo Bruni

We finally have our stats for files.pharo.org online again: http://files.pharo.org/teststats/2014/02/awstats.awstats.en.html We're approaching around 300GB downloads per month, not bad I'd say :)

Feb. 25, 2014

Re: [Pharo-dev] Path>>parentUpTo: aParentDirName

by Sebastian Sastre

Okay, Iâll take a look later (donât know when) and I keep the impression of unnecessary friction to receive contributions Something to think about On Feb 25, 2014, at 10:40 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 25 Feb 2014, at 14:36, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> Would this be okay? >> >> https://pharo.fogbugz.com/f/cases/12991/navigation-enhancement-Path-parentU… > > Well, not yet, you should learn how to make a actual slice... > > http://www.pharo-project.org/community/issue-tracking > > there are 2 movies and there is an explanation. > > Sven > > >

Feb. 25, 2014

Re: [Pharo-dev] Fwd: [Moose-dev] Text Displaying issue with Roassal

by J.F. Rick

Here's an updated bug for this: https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug Cheers, Jeff On Tue, Feb 25, 2014 at 2:33 PM, Vincent Blondeau < vincent.blondeau(a)polytech-lille.net> wrote: > Hi Pharoers, > > We are encounter a problem with text displaying under Roassal. > Roassal is a Moose tool to make some graphics visualisations, principally > graphs. > Some visualisations are displaying some text, like : > > - ROMondrianExample new centeredText > - ROMondrianExample new temporaryEdges > - ROMondrianExample new labeledRectangle > > They use AthensCanvas to render. > > Since the beginning of February, we experiment very strange problems with > font displaying. See by yourself : > > What we expect : > > What we have : > > You can see that the letters in each word are not of the same size. > (To reproduce do : "ROMondrianExample new labeledRectangle" in a fresh > Moose image : > https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… > ) > > We thought it was a font problem. So we updated the fonts to use this one > : > LogicalFont familyName: StandardFonts defaultFont familyName pointSize: > aSize > which is the default system font. (The fonts are located in > ROFontOrganizerAthens). > > But the problem was not solved. > > After some searches, we saw that Roassal (via the ROAthensCanvas) uses > AthensCairoCanvas and this class has been changed begin February to use > native boost. > The closed issue related is : > > 12765 Athens font rendering missing letters and missizing others > https://pharo.fogbugz.com/f/cases/12765 > > That should resolve the problem instead of created one ;) > > > So if we load the older packages of Athens-Core and Athens-Cairo (before > the issue resolution): > > Name: Athens-Core-MarcusDenker.34 > Author: MarcusDenker > Time: 5 July 2013, 10:59:47.206954 am > UUID: e844b2d4-b091-42a4-9be0-17101dcdbd30 > Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33 > > Name: Athens-Cairo-MarcusDenker.51 > Author: MarcusDenker > Time: 26 August 2013, 4:03:06.190096 pm > UUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881 > Ancestors: Athens-Cairo-SebastianTleye.50 > > we have no problem of font displaying ! > > The question is : > What we should adapt in Roassal to support this new implementation of > Athens ? Or is Athens (by the native boost primitives) broken ? > > Thanks in advance ! > > > Vincent BLONDEAU > > > > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Feb. 25, 2014

Re: [Pharo-dev] Path>>parentUpTo: aParentDirName

by Sven Van Caekenberghe

On 25 Feb 2014, at 14:36, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Would this be okay? > > https://pharo.fogbugz.com/f/cases/12991/navigation-enhancement-Path-parentU… Well, not yet, you should learn how to make a actual slice... http://www.pharo-project.org/community/issue-tracking there are 2 movies and there is an explanation. Sven

Feb. 25, 2014

Re: [Pharo-dev] Path>>parentUpTo: aParentDirName

by Sebastian Sastre

Would this be okay? https://pharo.fogbugz.com/f/cases/12991/navigation-enhancement-Path-parentU… On Feb 25, 2014, at 4:05 AM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > hi seb > > could you add a test or two and a bug entry so that we include it in FS? > > Stef > > On 25 Feb 2014, at 03:18, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> Just made this convenience, sharing: >> >> Path>>parentUpTo: aParentDirName >> "Answers the path of the parent dir with name aParentDirName or root if not found." >> >> self withParents reversed do:[:dir| >> dir basename = aParentDirName ifTrue:[^dir]]. >> >> ^ Path root > > > > >

Feb. 25, 2014

Fwd: [Moose-dev] Text Displaying issue with Roassal

by Vincent Blondeau

Hi Pharoers, We are encounter a problem with text displaying under Roassal. Roassal is a Moose tool to make some graphics visualisations, principally graphs. Some visualisations are displaying some text, like : - ROMondrianExample new centeredText - ROMondrianExample new temporaryEdges - ROMondrianExample new labeledRectangle They use AthensCanvas to render. Since the beginning of February, we experiment very strange problems with font displaying. See by yourself : What we expect : What we have : You can see that the letters in each word are not of the same size. (To reproduce do : "ROMondrianExample new labeledRectangle" in a fresh Moose image : https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-…) Wethought it was a font problem. So we updated the fonts to use this one : LogicalFont familyName: StandardFonts defaultFont familyName pointSize: aSize which is the default system font. (The fonts are located in ROFontOrganizerAthens). But the problem was not solved. After some searches, we saw that Roassal (via the ROAthensCanvas) uses AthensCairoCanvas and this class has been changed begin February to use native boost. The closed issue related is : 12765 Athens font rendering missing letters and missizing others https://pharo.fogbugz.com/f/cases/12765 That should resolve the problem instead of created one ;) So if we load the older packages of Athens-Core and Athens-Cairo (before the issue resolution): Name: Athens-Core-MarcusDenker.34 Author: MarcusDenker Time: 5 July 2013, 10:59:47.206954 am UUID: e844b2d4-b091-42a4-9be0-17101dcdbd30 Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33 Name: Athens-Cairo-MarcusDenker.51 Author: MarcusDenker Time: 26 August 2013, 4:03:06.190096 pm UUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881 Ancestors: Athens-Cairo-SebastianTleye.50 we have no problem of font displaying ! The question is : What we should adapt in Roassal to support this new implementation of Athens ? Or is Athens (by the native boost primitives) broken ? Thanks in advance ! Vincent BLONDEAU

Feb. 25, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30781 Home: https://github.com/pharo-project/pharo-core

Feb. 25, 2014

[pharo-project/pharo-core] 45d352: 30781

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 45d35291e5155193e6ddb0c4d6675705b26f3171 https://github.com/pharo-project/pharo-core/commit/45d35291e5155193e6ddb0c4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-25 (Tue, 25 Feb 2014) Changed paths: M Monticello.package/MCPackageManager.class/instance/operations/unregister.st M Nautilus.package/AbstractNautilusUI.class/class/menu/packagesMenu_.st A Nautilus.package/AbstractNautilusUI.class/instance/menu-packages/demoteSelectedPackageAsPackageWithTag.st A Nautilus.package/AbstractNautilusUI.class/instance/menu-packages/promoteSelectedPackageTagAsPackage.st A Nautilus.package/NautilusUI.class/instance/menu-packages/demoteSelectedPackageAsPackageWithTag.st A Nautilus.package/NautilusUI.class/instance/menu-packages/promoteSelectedPackageTagAsPackage.st M Nautilus.package/PackageTreeNautilusUI.class/class/menu/packagesFixMenu_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/package/addPackageBasedOn_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private dispatch/removePackageCategory_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private/addClassCategoryBasedOn_.st A Nautilus.package/PackageTreeSelection.class/instance/testing/isPackageTag.st A Nautilus.package/PackageTreeTagSelection.class/instance/testing/isPackageTag.st A RPackage-Core.package/RPackage.class/instance/class tags/classTagNamed_.st A RPackage-Core.package/RPackage.class/instance/class tags/extensionsForTag_.st A RPackage-Core.package/RPackage.class/instance/class tags/removeClassesMatchingTag_.st M RPackage-Core.package/RPackage.class/instance/compiled method handling/addMethod_.st M RPackage-Core.package/RPackage.class/instance/compiled method handling/removeMethod_.st A RPackage-Core.package/RPackage.class/instance/compiled method handling/removeMethods_.st A RPackage-Core.package/RPackage.class/instance/converting/demoteToRPackageNamed_.st A RPackage-Core.package/RPackage.class/instance/private/classExtensionSelectors.st A RPackage-Core.package/RPackage.class/instance/private/importPackage_.st A RPackage-Core.package/RPackage.class/instance/private/metaclassExtensionSelectors.st M RPackage-Core.package/RPackageOrganizer.class/instance/private registration/basicRegisterPackage_.st M RPackage-Core.package/RPackageOrganizer.class/instance/private registration/basicUnregisterPackage_.st M RPackage-Core.package/RPackageOrganizer.class/instance/private registration/unregisterExtendingPackage_forClass_.st M RPackage-Core.package/RPackageOrganizer.class/instance/private registration/unregisterPackage_forClass_.st M RPackage-Core.package/RPackageOrganizer.class/instance/public registration/registerPackage_.st M RPackage-Core.package/RPackageOrganizer.class/instance/public registration/unregisterPackage_.st A RPackage-Core.package/RPackageTag.class/instance/converting/promoteAsRPackage.st A RPackage-Core.package/RPackageTag.class/instance/private /asRPackage.st M RPackage-SystemIntegration.package/extension/RPackage/instance/correspondingMcPackage.st M RPackage-Tests.package/RPackageTagTest.class/instance/running/tearDown.st A RPackage-Tests.package/RPackageTagTest.class/instance/tests/testAsRPackage.st A RPackage-Tests.package/RPackageTagTest.class/instance/tests/testAsRPackageWithExtensionMethods.st A RPackage-Tests.package/RPackageTagTest.class/instance/tests/testPromoteAsRPackage.st A RPackage-Tests.package/RPackageTagTest.class/instance/tests/testPromoteAsRPackageWithExtension.st M RPackage-Tests.package/RPackageTest.class/instance/running/tearDown.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testDemoteToRPackageNamed.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testDemoteToRPackageNamedExistingPackage.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testDemoteToRPackageNamedMultilevelPackage1.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testDemoteToRPackageNamedMultilevelPackage2.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testDemoteToRPackageNamedWithExtension.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script434.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30781.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Versionner-Tests-Core-Model.package/MBPackageInfoTest.class/instance/tests/testIsDirty.st Log Message: ----------- 30781 12601 Can not split Packages https://pharo.fogbugz.com/f/cases/12601 http://files.pharo.org/image/30/30781.zip

Feb. 25, 2014

Re: [Pharo-dev] iPad version does not work ?

by Esteban Lorenzano

btw what can be happening is that xcode fails to build freetype2. the way to workaround this problem is: first, build a makefile version of the app: sh build.sh then, re-prepare for xcode: rm CMakeCache.txt cmake -G Xcode . (that will build freetype2 first, and when xcode tries to get it, it will be already there, so it will ski the build part, who often and mysteriously fails) Esteban On 25 Feb 2014, at 13:22, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > that works for me. > what is the problem you are having? > > > On 25 Feb 2014, at 12:10, jannik laval <jannik.laval(a)gmail.com> wrote: > >> It seems to not work :( >> Here is the process I follow: >> >> === >> git clone https://github.com/pharo-project/pharo-vm.git >> cd pharo-vm/image/ >> ./newImage.sh ==> it load a pharo20 >> >> ./pharo generator.image eval --save PharoIPhoneBuilder buildIPhoneSimulator >> >> cd ../iosbuild/resources/ >> >> ./generate.sh ==> it is a pharo1.4 image. >> >> sudo ../scripts/extract-commit-info.sh >> sudo cmake -G Xcode . >> >> open iPharoSimulator.xcodeproj/ >> >> In the list "ALL_BUILD", go to edit scheme, and change the Executable field to the iPharo. >> Select your iOS version and compile it. >> === >> >> Jannik >> >> >> 2014-02-25 9:23 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> On 25 Feb 2014, at 08:04, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >> >>> >>> On 25 Feb 2014, at 01:31, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> it *should* be working now. >>>> >>>> cheers >>>> Esteban (who needs to write more documentation, but he does what he can :) ) >>> >>> No need lentghly sentences just some nice bulleted lists of actions >>> and we can do something with that. >> >> yes, I willâ¦ but as I always say: time is a tyrant. And writing documentation is boring :) >> Anyway most of the process is already covered with current documentation, I just need to add a few points. >> >> (no one reads documentation either, is a bit annoyingâ¦ every time is like starting from scratchâ¦ But donât take me into appoint, Iâm having a cynical morning :P) >> >> Esteban >> >>> >>> >>> >>>> >>>> On 24 Feb 2014, at 08:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>>> not yetâ¦ so far I restored the build capability, not the image event handling :( >>>>> (nevertheless, Iâm on it :) ) >>>>> >>>>> Esteban >>>>> >>>>> On 24 Feb 2014, at 08:00, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>> >>>>>> Hi Esteban, >>>>>> >>>>>> Did you already try ? >>>>>> I saw a message on the VM repo related to iOS, not sure it is for my problem. >>>>>> >>>>>> Cheers, >>>>>> Jannik >>>>>> >>>>>> >>>>>> 2014-01-29 17:32 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>>> oksâ¦ I will take a lookâ¦ as soon as I can :S >>>>>> >>>>>> (damnâ¦ I need to learn how to do a mitosisâ¦) >>>>>> >>>>>> On 29 Jan 2014, at 17:28, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>>> >>>>>>> I confirm that it does not work: the simulator compile (but not the non-simulator). >>>>>>> Then the image cannot be open: I have a white screen. >>>>>>> Here is my process: >>>>>>> >>>>>>> === >>>>>>> 1) git clone https://github.com/pharo-project/pharo-vm.git >>>>>>> 2) in ./image dir prepare a VMMaker image (including download of a pharo 2.0): >>>>>>> ./newImage.sh >>>>>>> >>>>>>> 3)open the generated.image and execute: >>>>>>> === >>>>>>> PharoIPhoneBuilder buildIPhone. >>>>>>> â or â >>>>>>> PharoIPhoneBuilder buildIPhoneSimulator. >>>>>>> >>>>>>> 4) Generate your iPhone image in iosbuild/resources/ >>>>>>> ./generate.sh >>>>>>> >>>>>>> 5) In dir ./build: >>>>>>> sh build.sh >>>>>>> === >>>>>>> >>>>>>> Cheers, >>>>>>> Jannik >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>> and btwâ¦ >>>>>>> >>>>>>> iosbuild/resource$ ./generate.sh >>>>>>> >>>>>>> should generate a 1.4 image that *should* work in ipad (no idea if that will be the case, its been more than 6months since I do not test it and vm changed since then). >>>>>>> >>>>>>> Esteban >>>>>>> >>>>>>> >>>>>>> On 29 Jan 2014, at 10:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>>>> >>>>>>>> PharoIPhoneBuilder buildIPhone. >>>>>>>> >>>>>>>> it should generate all sources and a âbuild.shâ >>>>>>>> >>>>>>>> then >>>>>>>> >>>>>>>> build$ sh build.sh >>>>>>>> >>>>>>>> will generate an xcode project. >>>>>>>> >>>>>>>> and let me rememberâ¦ mmmâ¦ yeah, that was all :) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 29 Jan 2014, at 08:10, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi Esteban, >>>>>>>>> >>>>>>>>> Hum, this means that my instructions are outdated. >>>>>>>>> Where are the right instructions ? The ones on Github do not mention IOS. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Jannik >>>>>>>>> >>>>>>>>> >>>>>>>>> 2014-01-29 Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>>>> >>>>>>>>> On 29 Jan 2014, at 00:18, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Tue, Jan 28, 2014 at 2:46 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>>>>>>> because you are not following the instructions ;) >>>>>>>>>> >>>>>>>>>> basicallyâ¦ you can generate them by: >>>>>>>>>> >>>>>>>>>> build$ ../scripts/extract-commit-info.sh >>>>>>>>>> >>>>>>>>>> I asked for this info last week ;-). Thanks! >>>>>>>>> >>>>>>>>> hey! I answered you! :P >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> But this is alarming: >>>>>>>>>> >>>>>>>>>> McStalker.pharovm$ ./scripts/extract-commit-info.sh >>>>>>>>>> readlink: ./scripts/extract-commit-info.sh Invalid argument >>>>>>>>>> >>>>>>>>>> I suggest changing >>>>>>>>>> SCRIPT_DIR=`readlink "$0"` || SCRIPT_DIR="$0"; >>>>>>>>>> to read >>>>>>>>>> SCRIPT_DIR=`readlink "$0" >/dev/null` || SCRIPT_DIR="$0"; >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Esteban >>>>>>>>>> >>>>>>>>>> On 28 Jan 2014, at 23:15, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Thank you, I am trying the latest one. >>>>>>>>>>> >>>>>>>>>>> When compiling for IOS, I have an error in sqSCCSVersion.h >>>>>>>>>>> >>>>>>>>>>> #include "vmVersionInfo.h" // defines REVISION_STRING >>>>>>>>>>> the file is not found. >>>>>>>>>>> >>>>>>>>>>> Anyone knows where is this file ? >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Jannik >>>>>>>>>>> >>>>>>>>>>> On Jan 28, 2014, at 8:58 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >>>>>>>>>>> >>>>>>>>>>>> jannik the latest vm is not on gitoruous anymore but git >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 27 Jan 2014, at 22:03, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hum, have I the correct repository ? >>>>>>>>>>>>> I used this one: https://git.gitorious.org/cogvm/cog-osx.git >>>>>>>>>>>>> >>>>>>>>>>>>> But, I just saw that this one exists: https://github.com/pharo-project/pharo-vm >>>>>>>>>>>>> I should use it no? >>>>>>>>>>>>> >>>>>>>>>>>>> Jannik >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 2014-01-27 Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>>>>>>>> 1.4 and 2.0 worked out of the boxâ¦ and after my latest integration, 3.0 should work too. >>>>>>>>>>>>> I will take a look as soon as I have half and hour to spare. >>>>>>>>>>>>> >>>>>>>>>>>>> Esteban >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On 27 Jan 2014, at 14:27, jannik laval <jannik.laval(a)gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi list, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Does anyone try to load Pharoon iPad ? >>>>>>>>>>>>>> In the past, the version 1.4 worked with XCode 4.4. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I just tried to recompile it with the new XCode (5.0.2). >>>>>>>>>>>>>> The VM seems to work, but the pharo 1.4 image freezes. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Any idea ? >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> ~~Jannik Laval~~ >>>>>>>>>>>>>> Ãcole des Mines de Douai >>>>>>>>>>>>>> Enseignant-chercheur >>>>>>>>>>>>>> http://www.jannik-laval.eu >>>>>>>>>>>>>> http://car.mines-douai.fr/ >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> ~~Jannik Laval~~ >>>>>>>>>>>>> Ãcole des Mines de Douai >>>>>>>>>>>>> Enseignant-chercheur >>>>>>>>>>>>> http://www.jannik-laval.eu >>>>>>>>>>>>> http://car.mines-douai.fr/ >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> best, >>>>>>>>>> Eliot >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> ~~Jannik Laval~~ >>>>>>>>> Ãcole des Mines de Douai >>>>>>>>> Enseignant-chercheur >>>>>>>>> http://www.jannik-laval.eu >>>>>>>>> http://car.mines-douai.fr/ >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ~~Jannik Laval~~ >>>>>>> Ãcole des Mines de Douai >>>>>>> Enseignant-chercheur >>>>>>> http://www.jannik-laval.eu >>>>>>> http://car.mines-douai.fr/ >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ~~Jannik Laval~~ >>>>>> Ãcole des Mines de Douai >>>>>> Enseignant-chercheur >>>>>> http://www.jannik-laval.eu >>>>>> http://car.mines-douai.fr/ >>>>>> >>>>> >>>> >>> >> >> >> >> >> -- >> ~~Jannik Laval~~ >> Ãcole des Mines de Douai >> Enseignant-chercheur >> http://www.jannik-laval.eu >> http://car.mines-douai.fr/ >> >

Feb. 25, 2014