November 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Strange with Author

by Hilaire Fernandes

I have a small script to build automatically DrGeo release. In this script, I need to set the Author fullName to the value 'DrGeoUserScript'. I have enclosed below the used script. Strangely, the author fullname is not persisted in the image, although I set the author name just before the snapshot of the prepared image. Any idea ? -- Dr. Geo, to discover geometry on Linux, Windows, MAC and XO http://community.ofset.org/index.php/DrGeo

Nov. 13, 2010

Re: [Pharo-project] Repackaging task force

by Adrian Lienhard

Hi Torsten, Nice to see that we also improve at this front again! The goals make sense. When I recategorized all the tests that were mixed with the code to the global "Tests" package, I followed your first goal ("separate tests and code"). The main objective was to be able to make tests unloadable for the #cleanUpForProduction stripping of an image. So I think that splitting up the monolithic Tests package is a good next step because we gain modularity as single packages can be moved out/in of core including their tests (which is currently not possible since the tests can only be loaded/unloaded at once). I've seen your Regex refactoring [3254], which splits the code into three separate Monticello packages: Regex-Core Regex-Tests Regex-Examples That is, there is no package "Regex" anymore. Looks good (also the removing of the 'VB-' prefix was long overdue). I don't think its a big drawback, but just because it was not mentioned before: the consequence is that we'll end up with more than twice as many Monticello packages in the system. Cheers, Adrian On Nov 12, 2010, at 15:17 , Torsten Bergmann wrote: > Hi, > > after an IRC discussion with Alexandre and Stef yesterday we agreed > that it would be good to start working on cleaning up/organizing > the packages and get better structure into the system. > > Goals: > - seperate tests, examples, help, ... from code in distinguishable packages > - but also have tests, examples, help packages closer to the code > - be able to have cleaned up and reproducable package dependencies > in the future > - provide quality checks to see if packages conform to cleanup rules > > The abusing of class categories for packaging will not be > replaced with a real packaging system in the near future but > that shouldnt be a problem so far. > > I dont know where we will end up, how much time we can devote and > what problems we may find but if we wont try we will never find > out ... > > Proposal: > ========= > 1. we should have an informal repackaging task force and I would > like to invite the following people since they already worked > on repackaging/loading/unloading before: > > Adrian, Pavel, Stef and any other who wants to help > > 2. since we have to use a naming convention we would like to start > with the one from Seaside: > http://code.google.com/p/seaside/wiki/PackageNaming > > since it is already used and may help us here. Lets see how > this turns out. > > 3. we should start with simple packages and clean them up > > 4. well formed packages also means we can run quality checks > per package. Maybe the hudson infrastructure can help us > here to tell if already cleaned up packages continue to be > clean. > > To wet your appetite a little bit I worked in the announcement > framework packages. > > See http://code.google.com/p/pharo/issues/detail?id=3252 > > As a goodie we have a new help book documenting the framework a little bit. > > Feel free to try the changesets in a recent 1.2 image and comment. > I hope this doesnt start a flamewar on the correct package naming > (which we can always change) but help to improve the quality of > each package one by one ... > > Thx > T. > > -- > GRATIS! Movie-FLAT mit Ã¼ber 300 Videos. > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome >

Nov. 13, 2010

Re: [Pharo-project] Issue 3253 in pharo: Announcer. Extraction ActionSequence creation in subscription logic

by pharo＠googlecode.com

Updates: Status: Fixed Cc: asta...(a)gmx.de Labels: Milestone-1.2 Comment #1 on issue 3253 by stephane.ducasse: Announcer. Extraction ActionSequence creation in subscription logic http://code.google.com/p/pharo/issues/detail?id=3253 (No comment was entered for this change.)

Nov. 13, 2010

Re: [Pharo-project] Issue 3247 in pharo: Remodel Text Constants

by pharo＠googlecode.com

Updates: Cc: marcus.denker adrian.lienhard siguctua Comment #4 on issue 3247 by stephane.ducasse: Remodel Text Constants http://code.google.com/p/pharo/issues/detail?id=3247 (No comment was entered for this change.)

Nov. 13, 2010

Re: [Pharo-project] Issue 3247 in pharo: Remodel Text Constants

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2 Comment #3 on issue 3247 by stephane.ducasse: Remodel Text Constants http://code.google.com/p/pharo/issues/detail?id=3247 I will have a look later in the afternoon but this is true that we should have a look at that because this is good to fix it.

Nov. 13, 2010

Re: [Pharo-project] Repackaging task force

by StÃ©phane Ducasse

***THANKS A LOT*** for this initiative!!!!!! thanks thanks thanks!!! Stef On Nov 12, 2010, at 3:17 PM, Torsten Bergmann wrote: > Hi, > > after an IRC discussion with Alexandre and Stef yesterday we agreed > that it would be good to start working on cleaning up/organizing > the packages and get better structure into the system. > > Goals: > - seperate tests, examples, help, ... from code in distinguishable packages > - but also have tests, examples, help packages closer to the code > - be able to have cleaned up and reproducable package dependencies > in the future > - provide quality checks to see if packages conform to cleanup rules > > The abusing of class categories for packaging will not be > replaced with a real packaging system in the near future but > that shouldnt be a problem so far. > > I dont know where we will end up, how much time we can devote and > what problems we may find but if we wont try we will never find > out ... > > Proposal: > ========= > 1. we should have an informal repackaging task force and I would > like to invite the following people since they already worked > on repackaging/loading/unloading before: > > Adrian, Pavel, Stef and any other who wants to help > > 2. since we have to use a naming convention we would like to start > with the one from Seaside: > http://code.google.com/p/seaside/wiki/PackageNaming > > since it is already used and may help us here. Lets see how > this turns out. > > 3. we should start with simple packages and clean them up > > 4. well formed packages also means we can run quality checks > per package. Maybe the hudson infrastructure can help us > here to tell if already cleaned up packages continue to be > clean. > > To wet your appetite a little bit I worked in the announcement > framework packages. > > See http://code.google.com/p/pharo/issues/detail?id=3252 > > As a goodie we have a new help book documenting the framework a little bit. > > Feel free to try the changesets in a recent 1.2 image and comment. > I hope this doesnt start a flamewar on the correct package naming > (which we can always change) but help to improve the quality of > each package one by one ... > > Thx > T. > > -- > GRATIS! Movie-FLAT mit Ã¼ber 300 Videos. > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome >

Nov. 13, 2010

Re: [Pharo-project] Smalltalks 2010

by Sean P. DeNigris

Mariano Martinez Peck wrote: > > Yes, the talks are being recorder, but no streamed. They will be uploaded > to > the website after. > Oh, cool thanks! I thought I was missing everything, now only missing my Smalltalk friends, but at least I'll get to see the talks ;-) Sean -- View this message in context: http://forum.world.st/Smalltalks-2010-tp3035795p3040532.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 13, 2010

Re: [Pharo-project] Issue 3254 in pharo: [Repackage] "Regular expressions" should be well structured

by pharo＠googlecode.com

Comment #2 on issue 3254 by Torsten....(a)astares.de: [Repackage] "Regular expressions" should be well structured http://code.google.com/p/pharo/issues/detail?id=3254 After loading the slice one should also evaluate: Smalltalk organization removeSystemCategory: 'VB-Regex'. Smalltalk organization removeSystemCategory: 'VB-Regex-Exceptions'. Smalltalk organization sortCategories. to remove the obsolete empty categories

Nov. 12, 2010

Re: [Pharo-project] Issue 3255 in pharo: It should be possible to print text from help browser to printer

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3255 by Torsten....(a)astares.de: It should be possible to print text from help browser to printer http://code.google.com/p/pharo/issues/detail?id=3255 (No comment was entered for this change.)

Nov. 12, 2010

[Pharo-project] Issue 3255 in pharo: It should be possible to print text from help browser to printer

by pharo＠googlecode.com

Status: Accepted Owner: Torsten....(a)astares.de CC: stephane.ducasse Labels: Milestone-1.2 New issue 3255 by Torsten....(a)astares.de: It should be possible to print text from help browser to printer http://code.google.com/p/pharo/issues/detail?id=3255 Small enhancement to be able to print a text from a help book directly in the help browser. To try: File in the attached changeset, open the help browser via "Help" -> "Help Browser" and click on the second button in the toolbar Attachments: HelpWithPrintButton.3.cs 1.6 KB

Nov. 12, 2010