June 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] flatten method is kind of broken

by Fabrizio Perin

Hi, I need to flatten a collection which does not contain other collections necessarily. The method flatten doesn't really work: #(#(1 2) #(3 4)) flatten -> #(1 2 3 4) OK #(#(1) #(2 3) #(#(4) 5) ) flatten -> #(1 2 3 #(4) 5) I would have expected something like #(1 2 3 4 5) #(1 2 3) flatten -> error #(#(1) 2 3) flatten -> error Is this the meant behavior for flatten? Any other method I could use instead? Thanks, Fabrizio

June 15, 2012

[Pharo-project] Wrong message displayed during refactoring?

by Conrad Taylor

Hi, when I'm on the class side, the wrong message is being displayed when trying to move a method. For example, I'm seeing the following: Refactoring -> Move to class side instead of Refactoring -> Move to instance side Also, I'm seeing the same thing when I'm on the instance side of a given class. However, the functionality is correct. -- * * *Think different and code well*, -Conrad

June 15, 2012

Re: [Pharo-project] donating money

by Luc Fabresse

Hi Alex, 2012/6/15 Alexandre Bergel <alexandre.bergel(a)me.com> > By the way, could this donation be included in the ESUG registration? > no. ESUG and Pharo are completly distinct. > Can I fix myself the amount of money I am willing to give? > For individuals, Stef spoke about two donation levels but if donation is achieved through a paypal account or so, you will be able to choose the amount. Cheers, Luc > > Cheers, > Alexandre > > > On Jun 15, 2012, at 4:50 AM, StÃ©phane Ducasse wrote: > > > Hi cameron > > > > right now there is no simple way to give money to pharo but we are > working on it. What is the amount that you have in mind. > > here is a sketch about what we are thinking after I gathered the ideas > people mentioned during the pharo conference. > > > > > > > > > > > > Individus managed via the association > > ================= > > - Supporter 40 Euros + cup/goody > > reduction at conference > > > > - Ambassador Supporter 99 Euros > > reduction at conferences + cup > > > > - Donation > > > > - Training sessions cheaper > > > > - Conference reduction > > > > managed by INRIA > > ========= > > > > A company or an institution can be a consortium member: > > > > The annual fees are > > - Bronze 1000 Euros > > - Silver 2000 Euros > > - Gold 4000 Euros > > > > Institutions 1000 Euros > > > > Main advantages for members. > > ========================== > > Non individual members of the consortium get the following advantages: > > - privileged access to the core development team via a specific > mailing-list > > pharo-core-team-for-members(a)lists.gforge.inria.fr > > > > - influence priorities of the next development. The member will be > able to propose > > agenda point and items for the core team. They will be requested > one month in > > advance before the annual committee meeting. > > > > - get access to privileged support > > > > - Bronze gets one day of support and platinum sponsor > status. > > > > - Silver two days of support + one job description for job > dashboard and platinum sponsor status. > > > > - Gold four days of support + 3 job description for job > dashboard and platinum sponsor status. > > > > - Training special prices and possibility to become pharo trainer > > - Member can advertise themselves on the consortium web site > > - Member can also ask and pay for extra support days at 1000 Euros > per day. > > - The consortium can provide access experts for certain tasks. > > > > Sponsoring > > ============= > > normal 500 Euros > > platinium 1000 Euros > > - Sponsor will get their logos name exposed to the consortium web > site. > > (the idea is that small companies can pay something) > > > > > > License 500 Euros > > ============= > > - via a member a non member company can also ask > and **pay** for extra support days at 800 Euros per day. > > - via a member a non member company can also get > privileged access to core dev via a mailing-list. > > (the idea there is to make it like an insurance or a way > to people to donate) > > > > Job offers dashboard > > ============= > > External entities can post job offers to the consortium job offers for > > 1000 Euros for one job > > 2000 Euros for an undefined number > > > > > > Gouvernance: steering committee > > > > â¢ A steering committee is composed of one representative of each > member (except individuals) > > > > â¢ The chairman of this committee will be Inria > > > > â¢ Agenda : will be established by Inria on proposals of the > members (the members will be queried a month in advance) > > > > â¢ Meeting : at least once every year > > > > â¢ Role : > > -Follow the execution of the PHARO R&D Team > > -Validate and give input about the task list > > -Identify members of the executing commitee > > -Prepare, organize conferences, seminars or other > animations to promote PHARO and have new members > > -Revise the annual fee > > â¢ Decisions making : after consultation and collect of > representative member points of views, Inria takes the final decision. > > > > > > Technical Executing Committee (akaR&D task) > > â¢Members proposed by the steering board and RMOD Team > > â¢Study, analyse and validate external contributions for PHARO > > â¢Report to the steering commitee > > â¢Propose, schedule and implement tasks in conformance with the > tasks list presented and approved the steering > > â¢Coordinate the release Pharo and its VMs > > > > > > Stef > > > > > > > > > > > > > > > > On Jun 14, 2012, at 9:34 PM, Cameron Sanders wrote: > > > >> I am under the impression that I can donate money to the Pharo group > through gforge.inria.fr. Is it possible to donate with a credit card > right through their website? If so, can you please share the link to that > page? [My tired eyes are not seeing it today and my searches are failing > too.] Thanks in advance. > >> > >> -Cam > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

June 15, 2012

[Pharo-project] Tests Guard report for 20132

by Pavel Krivanek

Tests Guard report for 20132 http://code.google.com/p/pharo/w/edit/TestsGuard Firstly good news: - we have working 2.0 builds and tests again - this tests are green again: * RPackage.Tests.RPackageWithDoTest.testWithDoIsCorrectlyReinstallingDefault * RPackage.Tests.RPackageWithDoTest.testWithDoIsCorrectlyReinstallingDefaultEvenIfHalt * Tests.SystemChangeNotification.ChangeHooksTest.testClassRecategorizedEvent1 and now bad news, as expected we have a lot of new failing tests: * CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNames * CompressionTests.Archive.ZipArchiveTest.testFilePermissions * CompressionTests.Archive.ZipArchiveTest.testZip * FileSystem.Tests.Disk.DiskFileSystemTest.testRootIsNotAFile * Gofer.Tests.GoferApiTest.testDirectoryRepository * Gofer.Tests.GoferApiTest.testSubDirectoryRepository * RPackage.Tests.RPackageImportFromPackageInfoTest.testImportExtensionFromParentPackageRegisterExtensionInParentPackage * SUnit.Tests.Core.SUnitTest.testDialectLocalizedException * SUnit.Tests.Core.TestCaseTest.testAssertEqualsActualAndExpectedOrder * Tests.Monticello.MCFileInTest.testStWriter * Tests.Monticello.MCMczInstallerTest.testInstallFromFile * Tests.Monticello.MCMczInstallerTest.testInstallFromStream * Tests.Monticello.MCMethodDefinitionTest.testCannotLoad * Tests.Monticello.MCMethodDefinitionTest.testComparison * Tests.Monticello.MCMethodDefinitionTest.testLoadAndUnload * Tests.Monticello.MCMethodDefinitionTest.testPartiallyRevertOverrideMethod * Tests.Monticello.MCMethodDefinitionTest.testRevertOldMethod * Tests.Monticello.MCMethodDefinitionTest.testRevertOverrideMethod * Tests.System.SmalltalkImageTest.testImageName * Tests.Traits.TraitTest.testTraitsMethodClassSanity ...and a lot of new Linux specific failing tests: * CompressionTests.Archive.ZipArchiveTest.testAddNonExistentFile * CompressionTests.Archive.ZipArchiveTest.testDate29Feb2000 * CompressionTests.Archive.ZipArchiveTest.testPackDate * CompressionTests.Archive.ZipArchiveTest.testPackTime * CompressionTests.Archive.ZipArchiveTest.testSetLastModification * CompressionTests.Archive.ZipArchiveTest.testUnpackDate * CompressionTests.Archive.ZipArchiveTest.testUnpackTime * FileSystem.Tests.Core.FileReferenceTest.testRename * FileSystem.Tests.Disk.DiskFileSystemTest.testCreateDirectoryNoParent * FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectory * FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectoryCreatesParent * FileSystem.Tests.Disk.DiskFileSystemTest.testFileNames * FileSystem.Tests.Disk.DiskFileSystemTest.testReadStreamDoIfAbsent * FileSystem.Tests.Disk.DiskFileSystemTest.testReadStreamIfAbsent * FileSystem.Tests.Disk.DiskFileSystemTest.testWriteStreamDoIfPresent * FileSystem.Tests.Disk.DiskFileSystemTest.testWriteStreamIfPresent * FileSystem.Tests.Disk.FileHandleTest.testEnsureClosed * Graphics.Tests.Files.PNGReadWriterTest.test1BitColors * Graphics.Tests.Files.PNGReadWriterTest.test2BitColors * Graphics.Tests.Files.PNGReadWriterTest.test4BitColors * Graphics.Tests.Files.PNGReadWriterTest.test8BitColors * Multilingual.Tests.TextConversion.MultiByteFileStreamTest.testBasicChunk * Multilingual.Tests.TextConversion.MultiByteFileStreamTest.testBinaryUpTo * Tests.System.CommandLine.BasicCodeLoaderTest.testInstallSourceFilesFail Cheers, -- Pavel

June 15, 2012

Re: [Pharo-project] donating money

by Marcus Denker

On Jun 15, 2012, at 4:06 AM, Alexandre Bergel wrote: > By the way, could this donation be included in the ESUG registration? > Can I fix myself the amount of money I am willing to give? > ESUG has nothing to do with Pharo. ESUG is a general Smalltalk User Group. The Consortium and ESUG are different legal entitities, and as ESUG support all Smalltalks, it would be very strange if it would take money for Pharo. So: No way. Marcus -- Marcus Denker -- http://marcusdenker.de

June 15, 2012

Re: [Pharo-project] start thinking on summer release of Pharo 1.4

by phil＠highoctane.be

Have been using Nautilus and OB and albeit Nautilus is nicer looking, I find my way better with OB. Especially with the top search bar and categorizing into protocols. More buttons under the lists in OB but I do prefer them actually. Phil 2012/6/14 Sean P. DeNigris <sean(a)clipperadams.com>: > > EstebanLM wrote >> >> I started thinking on next release of Pharo 1.4 (which will be code named >> "summer", not an ugly number). >> > Keep us posted on the target date. I want to review bug fixes integrated in > 2.0 [1] and see if any should be included for 1.4 per > http://forum.world.st/Backporting-fixes-tp4633625p4633635.html > > > EstebanLM wrote >> >> - pre-load Spotlight >> > +1. No brainer. It's small and really helpful. > > Re browsers... I would definitely include either OB or Nautilus. The default > is just too limiting. Nautilus does seem to be in a pretty usable state now, > and it'd be helpful for new users not to have to learn two browsers in two > releases... > > [1] > http://code.google.com/p/pharo/issues/list?can=1&q=status%3AIntegrated+Mile… > > > -- > View this message in context: http://forum.world.st/start-thinking-on-summer-release-of-Pharo-1-4-tp46345… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges Belgium

June 15, 2012

Re: [Pharo-project] start thinking on summer release of Pharo 1.4

by phil＠highoctane.be

FFI yes, useful as well. 2012/6/15 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > My gripe is not so much that configs don't work together, it's that they work (very) differently over time; the work I did "last week" to build an image could be (often is) worthless "today." Â Configs really need to reflect on versions and do the right thing vs. current complexity. Â If pre-loading, how about FFI? > > Bill > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of phil(a)highoctane.be [phil(a)highoctane.be] > Sent: Wednesday, June 13, 2012 6:23 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] start thinking on summer release of Pharo 1.4 > > Esteban, > > Definitely worth doing!!! > > Install all the stuff I need on new images etc just to the have to > discard them for some reason doesn't makes me reinstall anything > afterwards. > > Tried to work the way of Mariano with the "ConfigurationOfXXXX" but > frankly, let it fall by the wayside. > > Just too many problems with loading packages that do work well together etc. > > And no refactoring out of the box in 1.4 is really lame indeed. As for > Nautilus in 2.0, the regular yellow crosses on red background are > getting on my nerves, especially since I don't know why they do > appear.$ > > So, yeah: +100000000 > > Philippe > > 2012/6/13 Esteban Lorenzano <estebanlm(a)gmail.com>: >> Hi, >> >> I started thinking on next release of Pharo 1.4 (which will be code named "summer", not an ugly number). >> I've been monitoring the list and I think there are some things to improve, so I'm planning to add this things to new one click: >> >> - pre-load OmniBrowser. >> Why I'm suggesting this? Because nobody seems to notice that OB is actually working on 1.4 and everybody complains that "you cannot have refactors, blabla", which is just not true, but is causing a lot of bad feeling around what is a great release (yes, I'm making some constructive criticism about the list attitude, but also about our/mine communicational capabilities). >> Original idea was to allow people to choose OB or Nautilus, since the last one will be the browser for Pharo in the future, but truth is that Nautilus is still a "technology preview"... and it will be there for all those like me, who want to use it. >> Finally, most important issue is that newcomers expect to have a full environment working out of the box, and they don'y know how to use the Configuration Browser. >> >> - pre-load Spotlight >> Yeah, another small tool who can make your life easy. >> Why? just because I'm tired of seeing all of you typing class names at workspace and press cmd+b later... or using some more uncomfortable ways to reach your code. >> If you still prefer those ways, is up to you ;) >> >> So far, this and the bugfixes we already made (and some more)... >> >> What do you think? >> >> Esteban > > > > -- > Philippe Back > Dramatic Performance Improvments > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges > Belgium > > -- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges Belgium

June 15, 2012

Re: [Pharo-project] donating money

by Alexandre Bergel

By the way, could this donation be included in the ESUG registration? Can I fix myself the amount of money I am willing to give? Cheers, Alexandre On Jun 15, 2012, at 4:50 AM, StÃ©phane Ducasse wrote: > Hi cameron > > right now there is no simple way to give money to pharo but we are working on it. What is the amount that you have in mind. > here is a sketch about what we are thinking after I gathered the ideas people mentioned during the pharo conference. > > > > > > Individus managed via the association > ================= > - Supporter 40 Euros + cup/goody > reduction at conference > > - Ambassador Supporter 99 Euros > reduction at conferences + cup > > - Donation > > - Training sessions cheaper > > - Conference reduction > > managed by INRIA > ========= > > A company or an institution can be a consortium member: > > The annual fees are > - Bronze 1000 Euros > - Silver 2000 Euros > - Gold 4000 Euros > > Institutions 1000 Euros > > Main advantages for members. > ========================== > Non individual members of the consortium get the following advantages: > - privileged access to the core development team via a specific mailing-list > pharo-core-team-for-members(a)lists.gforge.inria.fr > > - influence priorities of the next development. The member will be able to propose > agenda point and items for the core team. They will be requested one month in > advance before the annual committee meeting. > > - get access to privileged support > > - Bronze gets one day of support and platinum sponsor status. > > - Silver two days of support + one job description for job dashboard and platinum sponsor status. > > - Gold four days of support + 3 job description for job dashboard and platinum sponsor status. > > - Training special prices and possibility to become pharo trainer > - Member can advertise themselves on the consortium web site > - Member can also ask and pay for extra support days at 1000 Euros per day. > - The consortium can provide access experts for certain tasks. > > Sponsoring > ============= > normal 500 Euros > platinium 1000 Euros > - Sponsor will get their logos name exposed to the consortium web site. > (the idea is that small companies can pay something) > > > License 500 Euros > ============= > - via a member a non member company can also ask and **pay** for extra support days at 800 Euros per day. > - via a member a non member company can also get privileged access to core dev via a mailing-list. > (the idea there is to make it like an insurance or a way to people to donate) > > Job offers dashboard > ============= > External entities can post job offers to the consortium job offers for > 1000 Euros for one job > 2000 Euros for an undefined number > > > Gouvernance: steering committee > > â¢ A steering committee is composed of one representative of each member (except individuals) > > â¢ The chairman of this committee will be Inria > > â¢ Agenda : will be established by Inria on proposals of the members (the members will be queried a month in advance) > > â¢ Meeting : at least once every year > > â¢ Role : > -Follow the execution of the PHARO R&D Team > -Validate and give input about the task list > -Identify members of the executing commitee > -Prepare, organize conferences, seminars or other animations to promote PHARO and have new members > -Revise the annual fee > â¢ Decisions making : after consultation and collect of representative member points of views, Inria takes the final decision. > > > Technical Executing Committee (akaR&D task) > â¢Members proposed by the steering board and RMOD Team > â¢Study, analyse and validate external contributions for PHARO > â¢Report to the steering commitee > â¢Propose, schedule and implement tasks in conformance with the tasks list presented and approved the steering > â¢Coordinate the release Pharo and its VMs > > > Stef > > > > > > > > On Jun 14, 2012, at 9:34 PM, Cameron Sanders wrote: > >> I am under the impression that I can donate money to the Pharo group through gforge.inria.fr. Is it possible to donate with a credit card right through their website? If so, can you please share the link to that page? [My tired eyes are not seeing it today and my searches are failing too.] Thanks in advance. >> >> -Cam > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 15, 2012

Re: [Pharo-project] donating money

by petton.nicolas＠gmail.com

StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> writes: Very cool draft stef! I really like the fact that even small companies like mine can fit here. nico > Hi cameron > > right now there is no simple way to give money to pharo but we are working on it. What is the amount that you have in mind. > here is a sketch about what we are thinking after I gathered the ideas people mentioned during the pharo conference. > > > > > > Individus managed via the association > ================= > - Supporter 40 Euros + cup/goody > reduction at conference > > - Ambassador Supporter 99 Euros > reduction at conferences + cup > > - Donation > > - Training sessions cheaper > > - Conference reduction > > managed by INRIA > ========= > > A company or an institution can be a consortium member: > > The annual fees are > - Bronze 1000 Euros > - Silver 2000 Euros > - Gold 4000 Euros > > Institutions 1000 Euros > > Main advantages for members. > ========================== > Non individual members of the consortium get the following advantages: > - privileged access to the core development team via a specific mailing-list > pharo-core-team-for-members(a)lists.gforge.inria.fr > > - influence priorities of the next development. The member will be able to propose > agenda point and items for the core team. They will be requested one month in > advance before the annual committee meeting. > > - get access to privileged support > > - Bronze gets one day of support and platinum sponsor status. > > - Silver two days of support + one job description for job dashboard and platinum sponsor status. > > - Gold four days of support + 3 job description for job dashboard and platinum sponsor status. > > - Training special prices and possibility to become pharo trainer > - Member can advertise themselves on the consortium web site > - Member can also ask and pay for extra support days at 1000 Euros per day. > - The consortium can provide access experts for certain tasks. > > Sponsoring > ============= > normal 500 Euros > platinium 1000 Euros > - Sponsor will get their logos name exposed to the consortium web site. > (the idea is that small companies can pay something) > > > License 500 Euros > ============= > - via a member a non member company can also ask and **pay** for extra support days at 800 Euros per day. > - via a member a non member company can also get privileged access to core dev via a mailing-list. > (the idea there is to make it like an insurance or a way to people to donate) > > Job offers dashboard > ============= > External entities can post job offers to the consortium job offers for > 1000 Euros for one job > 2000 Euros for an undefined number > > > Gouvernance: steering committee > > â¢ A steering committee is composed of one representative of each member (except individuals) > > â¢ The chairman of this committee will be Inria > > â¢ Agenda : will be established by Inria on proposals of the members (the members will be queried a month in advance) > > â¢ Meeting : at least once every year > > â¢ Role : > -Follow the execution of the PHARO R&D Team > -Validate and give input about the task list > -Identify members of the executing commitee > -Prepare, organize conferences, seminars or other animations to promote PHARO and have new members > -Revise the annual fee > â¢ Decisions making : after consultation and collect of representative member points of views, Inria takes the final decision. > > > Technical Executing Committee (akaR&D task) > â¢Members proposed by the steering board and RMOD Team > â¢Study, analyse and validate external contributions for PHARO > â¢Report to the steering commitee > â¢Propose, schedule and implement tasks in conformance with the tasks list presented and approved the steering > â¢Coordinate the release Pharo and its VMs > > > Stef > > > > > > > > On Jun 14, 2012, at 9:34 PM, Cameron Sanders wrote: > >> I am under the impression that I can donate money to the Pharo group >> through gforge.inria.fr. Is it possible to donate with a credit card >> right through their website? If so, can you please share the link to >> that page? [My tired eyes are not seeing it today and my searches >> are failing too.] Thanks in advance. >> >> -Cam > > -- Nicolas Petton http://nicolas-petton.fr

June 14, 2012

Re: [Pharo-project] start thinking on summer release of Pharo 1.4

by Schwab,Wilhelm K

My gripe is not so much that configs don't work together, it's that they work (very) differently over time; the work I did "last week" to build an image could be (often is) worthless "today." Configs really need to reflect on versions and do the right thing vs. current complexity. If pre-loading, how about FFI? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of phil(a)highoctane.be [phil(a)highoctane.be] Sent: Wednesday, June 13, 2012 6:23 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] start thinking on summer release of Pharo 1.4 Esteban, Definitely worth doing!!! Install all the stuff I need on new images etc just to the have to discard them for some reason doesn't makes me reinstall anything afterwards. Tried to work the way of Mariano with the "ConfigurationOfXXXX" but frankly, let it fall by the wayside. Just too many problems with loading packages that do work well together etc. And no refactoring out of the box in 1.4 is really lame indeed. As for Nautilus in 2.0, the regular yellow crosses on red background are getting on my nerves, especially since I don't know why they do appear.$ So, yeah: +100000000 Philippe 2012/6/13 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > I started thinking on next release of Pharo 1.4 (which will be code named "summer", not an ugly number). > I've been monitoring the list and I think there are some things to improve, so I'm planning to add this things to new one click: > > - pre-load OmniBrowser. > Why I'm suggesting this? Because nobody seems to notice that OB is actually working on 1.4 and everybody complains that "you cannot have refactors, blabla", which is just not true, but is causing a lot of bad feeling around what is a great release (yes, I'm making some constructive criticism about the list attitude, but also about our/mine communicational capabilities). > Original idea was to allow people to choose OB or Nautilus, since the last one will be the browser for Pharo in the future, but truth is that Nautilus is still a "technology preview"... and it will be there for all those like me, who want to use it. > Finally, most important issue is that newcomers expect to have a full environment working out of the box, and they don'y know how to use the Configuration Browser. > > - pre-load Spotlight > Yeah, another small tool who can make your life easy. > Why? just because I'm tired of seeing all of you typing class names at workspace and press cmd+b later... or using some more uncomfortable ways to reach your code. > If you still prefer those ways, is up to you ;) > > So far, this and the bugfixes we already made (and some more)... > > What do you think? > > Esteban -- Philippe Back Dramatic Performance Improvments Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges Belgium

June 14, 2012