Re: [Pharo-project] Pragmas/Annotations for classes
I just said that we do not need a big infrastructure. We have methods / class methods and pragma so it should be enough. Stef On Jul 10, 2010, at 2:25 AM, csra...@bol.com.br wrote: Stef, Just to have a better grasp of your reasoning: Are you suggesting we put annotations in a method and just have it/them lumped in an 'Annotations' protocol or are you suggesting a more radical change which will require the toolset to have changes in sync to them? Em 08/07/2010 11:48, Stéphane Ducasse stephane.duca...@inria.fr escreveu: May be using a class method? But yes this would be important. Alex if we use comment we would have to parse them and this is not good. Stef On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: Hi, while it is possible to annotate methods using Pragmas, what about classes? Thx T. -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Pragmas/Annotations for classes
Hi guille I didn't understand if you want to replace the class pragmas with a simple class method for adding metadata, or to add the pragmas in a class method. In the first case I think I would like to have class pragmas because: - we can have a single, well known way, or concept, to generate metadata, which can allow us to: - build tools that can work with class and method pragmas in the same way (not only frameworks, a pragma browser can be benefited by this). If the metadata is disperse we have to know a lot of ways to do the same, or each one will define it's own. And we can't (or it should be difficult to) have tools to work with that metadata uniformly. Did you check setting? Did you check how pragma collection is done? Because it can help me to understand your answer. I don't know why this should be less cheaper than a class method. I don't think this is reaaally hard to do also... :S. It's even simpler than the method pragmas, because we don't have to change the compiler :P. Cheers, Guille On Fri, Jul 9, 2010 at 9:25 PM, csra...@bol.com.br wrote: Stef, Just to have a better grasp of your reasoning: Are you suggesting we put annotations in a method and just have it/them lumped in an 'Annotations' protocol or are you suggesting a more radical change which will require the toolset to have changes in sync to them? Em 08/07/2010 11:48, Stéphane Ducasse stephane.duca...@inria.fr escreveu: May be using a class method? But yes this would be important. Alex if we use comment we would have to parse them and this is not good. Stef On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: Hi, while it is possible to annotate methods using Pragmas, what about classes? Thx T. -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] New Engineer position for Moose
We got a one year engineer position to support the development of a demonstratior for Moose. The ***constraints*** linked with the position are that the person should have got his master in 2009 or 2010. The starting date is 1 of December 2010. The salary should be around 3500 Euros bruto ~ 2300 Euros before taxes (but after health insurance). The job will probably consist in - getting Moose running into a web browser - having a better reporting system. - building a dashboard - porting part of codecity What this of course means is that it's kind of a cool job: work in a research lab, but no paper writing, no teaching, no administration. In addition: - live in France (one hour from Paris, 1h20 from London, 35 min from Brussels) - try a lot of good beers (our office is just 10km from the border to Belgium) - enjoy french food - code all the day in Smalltalk and a bit of C By september we should decide if we take this year in 2010 or 2011 (for decembre 2011 the person should have got a master in 2010 or 2011). Please send your cv. More about: - RMoD: http://rmod.lille.inria.fr - INRIA Lille: http://www.inria.fr/lille/ - INRIA in General: http://www.inria.fr - Engineers at INRIA: http://bit.ly/cLe6q4 - Pharo: http://pharo-project.org - Lille: - http://en.wikipedia.org/wiki/Lille - http://www.mairie-lille.fr/en - http://wikitravel.org/en/Lille Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1
I saw that exist a preference, but seems not work. Also a closed issue talking about this topic (1544) but really don't understand how to use this in Pharo 1.0. Any clarification will be appreciated. Cheers. El 9 de julio de 2010 20:12, Germán Arduino gardu...@gmail.com escribió: I checked a bit and saw that such method is on Scanner class on PharoCore 1.2, but not on Pharo 1.0. What I missed? El 9 de julio de 2010 19:46, Germán Arduino gardu...@gmail.com escribió: Hi; Thanks by the useful configuration. I tried today by first time on a Pharo 1.0 image and get a DNU Scanner class(Object) doesNotUnderstand: #allowUnderscoreAsAssignment: I need to install some patch before run the installation? Cheers. Germán. El 3 de junio de 2010 21:46, Miguel Enrique Cobá Martínez miguel.c...@gmail.com escribió: I'm pleased to announce that the ConfigurationOfMagma now includes support for loading version 1.1r1 of Magma. In a Pharo or PharoCore 1.0 image evaluate: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. To install the Magma Client evaluate: ConfigurationOfMagma project latestVersion load: 'Client' To install the Magma Server evaluate: ConfigurationOfMagma project latestVersion load: 'Server' To install the Magma Tester evaluate: ConfigurationOfMagma project latestVersion load: 'Tester' Then if you want, run the test suite. Evaluate in a workspace: MagmaTestCase allowWriteBarrier: false. MagmaTestCase fullSuite maDebug. Enjoy -- Miguel Cobá http://miguel.leugim.com.mx ___ Magma mailing list ma...@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma -- = Germán S. Arduino gsa @ arsol.net Twitter: garduino Arduino Software Web Hosting http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com = ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] [update 1.2] #12044
12044 - - Issue 2652: better flush of class name cache when removing key - Issue 2568: Remove ancient j3 support - Issue 2650: Easier doit of commented expression Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] [update 1.2] #12045
Some fixes from squeak that accumulated in our bug tracker. 12045 - - Issue 2300: ServerDirectory cleanup - Issue 2226: shuffled and shuffle - Issue 2238: tests for FileStream behavior. - Issue 2129: Cursor with Alpha from OLPC CursorWithAlpha biggerNormal showWhile:[Sensor waitButton]. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] OB contextual menu item 'method containing' broken: is it useful?
Hi Simon. Can you open a bug ticket please? Lukas, it seems very easy to fix. If you want you can commit this change: OBSelectorNode methods methods ifNil: [methods := SystemNavigation default allMethodsSelect: [:m | m hasLiteralSuchThat: [:lit | lit isString and: [lit isSymbol not and: [lit includesSubstring: selector string caseSensitive: false]. ^ methods collect: [:m | OBMethodNode on: m] I only changed allMethodsNoDoitsSelect: by allMethodsSelect: Cheers mariano On Tue, Jul 6, 2010 at 11:50 AM, Simon Denier simon.den...@inria.fr wrote: In 1.1 RC4 (and before), when opening the contextual menu in the source pane, there is an option for 'method containing' among the search actions. It's not clear what is is supposed to do. Is it the OB implementation of the 'method strings with it' action, which is also available? Anyway, it is broken as it raises a DNU #allMethodsNoDoitsSelect: -- Simon ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] OB contextual menu item 'method containing' broken: is it useful?
If i remember correctly this is fixed and the bug is closed already a while ago. Or is this something new? Lukas On Saturday, July 10, 2010, Mariano Martinez Peck marianop...@gmail.com wrote: Hi Simon. Can you open a bug ticket please? Lukas, it seems very easy to fix. If you want you can commit this change: OBSelectorNode methods methods ifNil: [methods := SystemNavigation default allMethodsSelect: [:m | m hasLiteralSuchThat: [:lit | lit isString and: [lit isSymbol not and: [lit includesSubstring: selector string caseSensitive: false]. ^ methods collect: [:m | OBMethodNode on: m] I only changed allMethodsNoDoitsSelect: by allMethodsSelect: Cheers mariano On Tue, Jul 6, 2010 at 11:50 AM, Simon Denier simon.den...@inria.fr wrote: In 1.1 RC4 (and before), when opening the contextual menu in the source pane, there is an option for 'method containing' among the search actions. It's not clear what is is supposed to do. Is it the OB implementation of the 'method strings with it' action, which is also available? Anyway, it is broken as it raises a DNU #allMethodsNoDoitsSelect: -- Simon ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Lukas Renggli www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] OB contextual menu item 'method containing' broken: is it useful?
On Sat, Jul 10, 2010 at 7:38 PM, Lukas Renggli reng...@gmail.com wrote: If i remember correctly this is fixed and the bug is closed already a while ago. Or is this something new? Ups...yes. Sorry, I didn't see you have already commited a fix in the repo. Sorry for the mess. Yes, it is fixed. Thanks Mariano Lukas On Saturday, July 10, 2010, Mariano Martinez Peck marianop...@gmail.com wrote: Hi Simon. Can you open a bug ticket please? Lukas, it seems very easy to fix. If you want you can commit this change: OBSelectorNode methods methods ifNil: [methods := SystemNavigation default allMethodsSelect: [:m | m hasLiteralSuchThat: [:lit | lit isString and: [lit isSymbol not and: [lit includesSubstring: selector string caseSensitive: false]. ^ methods collect: [:m | OBMethodNode on: m] I only changed allMethodsNoDoitsSelect: by allMethodsSelect: Cheers mariano On Tue, Jul 6, 2010 at 11:50 AM, Simon Denier simon.den...@inria.fr wrote: In 1.1 RC4 (and before), when opening the contextual menu in the source pane, there is an option for 'method containing' among the search actions. It's not clear what is is supposed to do. Is it the OB implementation of the 'method strings with it' action, which is also available? Anyway, it is broken as it raises a DNU #allMethodsNoDoitsSelect: -- Simon ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Lukas Renggli www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Lost some classes
Apparently we lost some classes probably trying to changes packages with MC bad bad bad idea. We lost MczInstaller for example. ;) Bad bad bad. We will not change package structure before fixing MC else we are doomed to lose classes. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Lost some classes
(((Smalltalk globals allClasses reject: [:each | each inheritsFrom: Error]) reject: [:each | each inheritsFrom: Exception]) reject: [:each | each inheritsFrom: Announcement]) select: [:each | each methods size = 0 and: [each class methods size = 0] ] an OrderedCollection(DirectoryURI FT2BitmapSize MCMockAPoolDictionary MCMockClassF MCMockClassG MCMockClassH MCMockClassI MethodTempsNode MockForCompilation MorphicTextEditor NameOfSubclass PSMCOrganizationChangeWrapper PanelStub PasteUpMorphTest SARInstaller SketchMorph SoundService TarArchiveMember TestDynamicVariable TestRunnerBrowser WebBrowser WeightedAverageCost) Will check and fix that as soon as I can Stef On Jul 11, 2010, at 12:05 AM, stephane ducasse wrote: Apparently we lost some classes probably trying to changes packages with MC bad bad bad idea. We lost MczInstaller for example. ;) Bad bad bad. We will not change package structure before fixing MC else we are doomed to lose classes. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Pragmas/Annotations for classes
Haha yeah :). I only was telling that if we chose a non-pragma way to add metadata to a class, we cannot be benefited (simply) with a pragma collector, hehe. But that's because I didn't understand what you meant about using class methods to add metadata. On Sat, Jul 10, 2010 at 4:46 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi guille I didn't understand if you want to replace the class pragmas with a simple class method for adding metadata, or to add the pragmas in a class method. In the first case I think I would like to have class pragmas because: - we can have a single, well known way, or concept, to generate metadata, which can allow us to: - build tools that can work with class and method pragmas in the same way (not only frameworks, a pragma browser can be benefited by this). If the metadata is disperse we have to know a lot of ways to do the same, or each one will define it's own. And we can't (or it should be difficult to) have tools to work with that metadata uniformly. Did you check setting? Did you check how pragma collection is done? Because it can help me to understand your answer. I don't know why this should be less cheaper than a class method. I don't think this is reaaally hard to do also... :S. It's even simpler than the method pragmas, because we don't have to change the compiler :P. Cheers, Guille On Fri, Jul 9, 2010 at 9:25 PM, csra...@bol.com.br wrote: Stef, Just to have a better grasp of your reasoning: Are you suggesting we put annotations in a method and just have it/them lumped in an 'Annotations' protocol or are you suggesting a more radical change which will require the toolset to have changes in sync to them? Em 08/07/2010 11:48, Stéphane Ducasse stephane.duca...@inria.fr escreveu: May be using a class method? But yes this would be important. Alex if we use comment we would have to parse them and this is not good. Stef On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: Hi, while it is possible to annotate methods using Pragmas, what about classes? Thx T. -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
