January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] Updated ConfigurationsOf...scripts?

by Miguel CobÃ¡

Hi HernÃ¡n Isn't this a feature instead for Loader or MetacelloBrowser ? Cheers El jue, 13-01-2011 a las 13:53 -0300, HernÃ¡n Morales Durand escribiÃ³: > Hi Dale, > > 2011/1/12 Dale Henrichs <dhenrich(a)vmware.com>: > > HernÃ¡n, > > > > It _is_ possible to write some scripts that could automate the checking: > > > > ConfigurationOfXXX project updateProject > > > > loads the latest version of the mcz file for the configuration. Then you > > could write a little script like: > > > > Not so fast :) > What would be nice is to > > A - Checking for new Configurations > 1) Detect new uploaded ConfigurationOfXXX > > B - Checking for new package versions of existing Configurations > 1) Detect new versions of loaded ConfigurationOfXXX > > 2) Inform the user > 3) Ask the user if wants to load/update the ConfigurationOfXXX in background. > 4) Ask the user if want to apply the new ConfigurationOfXXX for > updating the XXX. > > Then people don't have to search ConfigurationOfXXX scripts over > mailing lists and web pages. > > > | project | > > project := ConfigurationOfXXX project. > > project updateProject > > project currentVersion < project latestVersion > > ifTrue: [ > > self inform: 'A new version of ConfigurationOXXX is available' ]. > > > > to simplify the check for new versions a bit more...you could even automate > > the load of the newer version if you were brave:) > > > > I think brave souls were gone from earth long time ago :) but anyway > this could be a dirty script to start > > [ > | packageName pkgNames oldPkgsNames | > packageName := 'ConfigurationOf'. > pkgNames := OrderedCollection new. > [ oldPkgsNames := pkgNames. > [ pkgNames := ( ScriptLoader new metacelloRepository allFileNames > select:[ : name | name beginsWith: packageName ] > thenCollect: [: v | v copyUpTo: $- ] ) asSet. > Transcript show: TimeStamp current. > pkgNames size > oldPkgsNames size > ifTrue: [Transcript > show: ' : New ConfigurationOf found : ' , ( pkgNames difference: > oldPkgsNames ) asString; cr ] > ifFalse: [ Transcript > show: ' : No new ConfigurationOf were found'; cr ]. > ] > on: Error > do: [ :ex | Transcript show: TimeStamp current; space; show: ex messageText ]. > ( Delay forSeconds: 10 ) wait. > true ] whileTrue ] forkAt: Processor userBackgroundPriority. " 20 " > > then you may modify it for detecting new package versions, checking > frequency, etc. I've seen there's a sort of Metacello UI... > > HernÃ¡n > > > > Dale > > > > > > On 01/12/2011 01:56 PM, HernÃ¡n Morales Durand wrote: > >> > >> Yes thanks. > >> notice there are 80+ ConfigurationOf... in the MetacelloRepository and > >> so many not listed there > >> > >> 2011/1/12 laurent laffont<laurent.laffont(a)gmail.com>: > >>> > >>> Isn't what you're looking for ? > >>> http://book.pharo-project.org/book/PharoTools/ > >>> Laurent > >>> > >>> On Wed, Jan 12, 2011 at 8:44 PM, HernÃ¡n Morales Durand > >>> <hernan.morales(a)gmail.com> wrote: > >>>> > >>>> Ok if there are not, I think is a must, I spend a lot of time > >>>> searching for the updated scripts or exporting/importing them in my > >>>> images. What about creating a wiki page in the google project? > >>>> > >>>> HernÃ¡n > >>>> > >>>> 2011/1/11 HernÃ¡n Morales Durand<hernan.morales(a)gmail.com>: > >>>>> > >>>>> Hi, > >>>>> > >>>>> Is there any page/tool where all the updated ConfigurationOf.... > >>>>> installing scripts are found? > >>>>> Best regards, > >>>>> > >>>>> -- > >>>>> HernÃ¡n Morales > >>>>> Information Technology Manager, > >>>>> Institute of Veterinary Genetics. > >>>>> National Scientific and Technical Research Council (CONICET). > >>>>> La Plata (1900), Buenos Aires, Argentina. > >>>>> Telephone: +54 (0221) 421-1799. > >>>>> Internal: 422 > >>>>> Fax: 425-7980 or 421-1799. > >>>>> > >>>> > >>> > >> > > > > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Jan. 13, 2011

Re: [Pharo-project] [update 1.2] #12297

by Igor Stasenko

here is updated version of it. more consistent colors (note the ">" button now not highlighted by default, also added thin border for lists and thin border for system windows, and removed 1pixel-wide shadow for system window. -- Best regards, Igor Stasenko AKA sig.

Jan. 13, 2011

Re: [Pharo-project] [Pharo-users] Updated ConfigurationsOf...scripts?

by Dale Henrichs

HernÃ¡n, Good points...I've opened a feature request against Metacello: http://code.google.com/p/metacello/issues/detail?id=105 with your suggestions ... I agree that this kind of functionality should be included in a Metacello tool ... I think that Alexandre Bergel is working on just such a tool:) Dale On 01/13/2011 08:53 AM, HernÃ¡n Morales Durand wrote: > Hi Dale, > > 2011/1/12 Dale Henrichs<dhenrich(a)vmware.com>: >> HernÃ¡n, >> >> It _is_ possible to write some scripts that could automate the checking: >> >> ConfigurationOfXXX project updateProject >> >> loads the latest version of the mcz file for the configuration. Then you >> could write a little script like: >> > > Not so fast :) > What would be nice is to > > A - Checking for new Configurations > 1) Detect new uploaded ConfigurationOfXXX > > B - Checking for new package versions of existing Configurations > 1) Detect new versions of loaded ConfigurationOfXXX > > 2) Inform the user > 3) Ask the user if wants to load/update the ConfigurationOfXXX in background. > 4) Ask the user if want to apply the new ConfigurationOfXXX for > updating the XXX. > > Then people don't have to search ConfigurationOfXXX scripts over > mailing lists and web pages. > >> | project | >> project := ConfigurationOfXXX project. >> project updateProject >> project currentVersion< project latestVersion >> ifTrue: [ >> self inform: 'A new version of ConfigurationOXXX is available' ]. >> >> to simplify the check for new versions a bit more...you could even automate >> the load of the newer version if you were brave:) >> > > I think brave souls were gone from earth long time ago :) but anyway > this could be a dirty script to start > > [ > | packageName pkgNames oldPkgsNames | > packageName := 'ConfigurationOf'. > pkgNames := OrderedCollection new. > [ oldPkgsNames := pkgNames. > [ pkgNames := ( ScriptLoader new metacelloRepository allFileNames > select:[ : name | name beginsWith: packageName ] > thenCollect: [: v | v copyUpTo: $- ] ) asSet. > Transcript show: TimeStamp current. > pkgNames size> oldPkgsNames size > ifTrue: [Transcript > show: ' : New ConfigurationOf found : ' , ( pkgNames difference: > oldPkgsNames ) asString; cr ] > ifFalse: [ Transcript > show: ' : No new ConfigurationOf were found'; cr ]. > ] > on: Error > do: [ :ex | Transcript show: TimeStamp current; space; show: ex messageText ]. > ( Delay forSeconds: 10 ) wait. > true ] whileTrue ] forkAt: Processor userBackgroundPriority. " 20 " > > then you may modify it for detecting new package versions, checking > frequency, etc. I've seen there's a sort of Metacello UI... > > HernÃ¡n > > >> Dale >> >> >> On 01/12/2011 01:56 PM, HernÃ¡n Morales Durand wrote: >>> >>> Yes thanks. >>> notice there are 80+ ConfigurationOf... in the MetacelloRepository and >>> so many not listed there >>> >>> 2011/1/12 laurent laffont<laurent.laffont(a)gmail.com>: >>>> >>>> Isn't what you're looking for ? >>>> http://book.pharo-project.org/book/PharoTools/ >>>> Laurent >>>> >>>> On Wed, Jan 12, 2011 at 8:44 PM, HernÃ¡n Morales Durand >>>> <hernan.morales(a)gmail.com> wrote: >>>>> >>>>> Ok if there are not, I think is a must, I spend a lot of time >>>>> searching for the updated scripts or exporting/importing them in my >>>>> images. What about creating a wiki page in the google project? >>>>> >>>>> HernÃ¡n >>>>> >>>>> 2011/1/11 HernÃ¡n Morales Durand<hernan.morales(a)gmail.com>: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Is there any page/tool where all the updated ConfigurationOf.... >>>>>> installing scripts are found? >>>>>> Best regards, >>>>>> >>>>>> -- >>>>>> HernÃ¡n Morales >>>>>> Information Technology Manager, >>>>>> Institute of Veterinary Genetics. >>>>>> National Scientific and Technical Research Council (CONICET). >>>>>> La Plata (1900), Buenos Aires, Argentina. >>>>>> Telephone: +54 (0221) 421-1799. >>>>>> Internal: 422 >>>>>> Fax: 425-7980 or 421-1799. >>>>>> >>>>> >>>> >>> >> >>

Jan. 13, 2011

Re: [Pharo-project] Changes for PharoDev

by Schwab,Wilhelm K

+1 ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck(a)gmail.com] Sent: Thursday, January 13, 2011 11:41 AM To: Pharo Development Subject: [Pharo-project] Changes for PharoDev Hi. Today, we have a good way to manage packages/projects (Metacello) and a good way to automatically build images (Hudson). Several months ago, I suggested to remove the PharoWeb image for several reasons (I won't mention them here, check in the mailing list). People have different ideas of what to put in dev images and we cannot all agree. So, I won't say anything new, but just suggest something: Pharo1.2 is beta and it is almost there. We shouldn't change it that much before the release. So, I would include in the Pharo1.2 image what we were including more or less in Pharo1.1. The dev image is being built using ConfigurationOfPharo. This conf, has defined different groups, included the 'Dev' group which us used for building the dev image. Now, what about adding to ConfugurationOfPharo, much more projects, and creating groups for them. Then, with Hudson we can REALLY EASY build another image, but not with the 'Dev' group, but with 'Web' for example. Web is just an example, but we can put as much as we want. I would create a PharoWeb which can contain ALL seaside related stuff (core, addons, pier, margitte, blah). We can use ConfigurationOfSeaside. The same for Aida. We can also add WebClient, Zn, seaside testing, or whatever web related you want. Then we can create a PharoExtras, where we can put (in addition to pharoDev) what it is now in PharoNonCore, plus MemoryMonitor, XMLSupport, Mocker, AutoTest, KeyBindings, etc etc etc. Things that are not "dev tools" but that they are working in pharo and that would be welcome for newcomers. Last comment is that it would be nice if all this can be done using the new symbolicVersions of the new Metacello version. what do you think ? cheers mariano ps: if you like it, we need help to update ConfigurationOfPharo and probably all its referenced confs (to use the stale symbolic version)

Jan. 13, 2011

Re: [Pharo-project] [Pharo-users] Updated ConfigurationsOf...scripts?

by HernÃ¡n Morales Durand

Hi Dale, 2011/1/12 Dale Henrichs <dhenrich(a)vmware.com>: > HernÃ¡n, > > It _is_ possible to write some scripts that could automate the checking: > > Â ConfigurationOfXXX project updateProject > > loads the latest version of the mcz file for the configuration. Then you > could write a little script like: > Not so fast :) What would be nice is to A - Checking for new Configurations 1) Detect new uploaded ConfigurationOfXXX B - Checking for new package versions of existing Configurations 1) Detect new versions of loaded ConfigurationOfXXX 2) Inform the user 3) Ask the user if wants to load/update the ConfigurationOfXXX in background. 4) Ask the user if want to apply the new ConfigurationOfXXX for updating the XXX. Then people don't have to search ConfigurationOfXXX scripts over mailing lists and web pages. > Â | project | > Â project := ConfigurationOfXXX project. > Â project updateProject > Â project currentVersion < project latestVersion > Â Â ifTrue: [ > Â Â Â self inform: 'A new version of ConfigurationOXXX is available' ]. > > to simplify the check for new versions a bit more...you could even automate > the load of the newer version if you were brave:) > I think brave souls were gone from earth long time ago :) but anyway this could be a dirty script to start [ | packageName pkgNames oldPkgsNames | packageName := 'ConfigurationOf'. pkgNames := OrderedCollection new. [ oldPkgsNames := pkgNames. [ pkgNames := ( ScriptLoader new metacelloRepository allFileNames select:[ : name | name beginsWith: packageName ] thenCollect: [: v | v copyUpTo: $- ] ) asSet. Transcript show: TimeStamp current. pkgNames size > oldPkgsNames size ifTrue: [Transcript show: ' : New ConfigurationOf found : ' , ( pkgNames difference: oldPkgsNames ) asString; cr ] ifFalse: [ Transcript show: ' : No new ConfigurationOf were found'; cr ]. ] on: Error do: [ :ex | Transcript show: TimeStamp current; space; show: ex messageText ]. ( Delay forSeconds: 10 ) wait. true ] whileTrue ] forkAt: Processor userBackgroundPriority. " 20 " then you may modify it for detecting new package versions, checking frequency, etc. I've seen there's a sort of Metacello UI... HernÃ¡n > Dale > > > On 01/12/2011 01:56 PM, HernÃ¡n Morales Durand wrote: >> >> Yes thanks. >> notice there are 80+ ConfigurationOf... in the MetacelloRepository and >> so many not listed there >> >> 2011/1/12 laurent laffont<laurent.laffont(a)gmail.com>: >>> >>> Isn't what you're looking for ? >>> http://book.pharo-project.org/book/PharoTools/ >>> Laurent >>> >>> On Wed, Jan 12, 2011 at 8:44 PM, HernÃ¡n Morales Durand >>> <hernan.morales(a)gmail.com> Â wrote: >>>> >>>> Ok if there are not, I think is a must, I spend a lot of time >>>> searching for the updated scripts or exporting/importing them in my >>>> images. What about creating a wiki page in the google project? >>>> >>>> HernÃ¡n >>>> >>>> 2011/1/11 HernÃ¡n Morales Durand<hernan.morales(a)gmail.com>: >>>>> >>>>> Hi, >>>>> >>>>> Is there any page/tool where all the updated ConfigurationOf.... >>>>> installing scripts are found? >>>>> Best regards, >>>>> >>>>> -- >>>>> HernÃ¡n Morales >>>>> Information Technology Manager, >>>>> Institute of Veterinary Genetics. >>>>> National Scientific and Technical Research Council (CONICET). >>>>> La Plata (1900), Buenos Aires, Argentina. >>>>> Telephone: +54 (0221) 421-1799. >>>>> Internal: 422 >>>>> Fax: 425-7980 or 421-1799. >>>>> >>>> >>> >> > >

Jan. 13, 2011

Re: [Pharo-project] Issue 3539 in pharo: SettingBrowser class comment is out of date

by pharo＠googlecode.com

Comment #1 on issue 3539 by aplantec: SettingBrowser class comment is out of date http://code.google.com/p/pharo/issues/detail?id=3539 yes, i'm currently rewritting them

Jan. 13, 2011

[Pharo-project] Changes for PharoDev

by Mariano Martinez Peck

Hi. Today, we have a good way to manage packages/projects (Metacello) and a good way to automatically build images (Hudson). Several months ago, I suggested to remove the PharoWeb image for several reasons (I won't mention them here, check in the mailing list). People have different ideas of what to put in dev images and we cannot all agree. So, I won't say anything new, but just suggest something: Pharo1.2 is beta and it is almost there. We shouldn't change it that much before the release. So, I would include in the Pharo1.2 image what we were including more or less in Pharo1.1. The dev image is being built using ConfigurationOfPharo. This conf, has defined different groups, included the 'Dev' group which us used for building the dev image. Now, what about adding to ConfugurationOfPharo, much more projects, and creating groups for them. Then, with Hudson we can REALLY EASY build another image, but not with the 'Dev' group, but with 'Web' for example. Web is just an example, but we can put as much as we want. I would create a PharoWeb which can contain ALL seaside related stuff (core, addons, pier, margitte, blah). We can use ConfigurationOfSeaside. The same for Aida. We can also add WebClient, Zn, seaside testing, or whatever web related you want. Then we can create a PharoExtras, where we can put (in addition to pharoDev) what it is now in PharoNonCore, plus MemoryMonitor, XMLSupport, Mocker, AutoTest, KeyBindings, etc etc etc. Things that are not "dev tools" but that they are working in pharo and that would be welcome for newcomers. Last comment is that it would be nice if all this can be done using the new symbolicVersions of the new Metacello version. what do you think ? cheers mariano ps: if you like it, we need help to update ConfigurationOfPharo and probably all its referenced confs (to use the stale symbolic version)

Jan. 13, 2011

[Pharo-project] Issue 3539 in pharo: SettingBrowser class comment is out of date

by pharo＠googlecode.com

Status: Accepted Owner: siguctua Labels: Milestone-1.3 New issue 3539 by siguctua: SettingBrowser class comment is out of date http://code.google.com/p/pharo/issues/detail?id=3539 the documentation is completely misleading, talks about using SettingManager while this class even not present in system

Jan. 13, 2011

Re: [Pharo-project] Issue 3533 in pharo: add Dictionary>>at:ifAbsentValue:

by Levente Uzonyi

On Wed, 12 Jan 2011, pharo(a)googlecode.com wrote: > > Comment #4 on issue 3533 by siguctua: add Dictionary>>at:ifAbsentValue: > http://code.google.com/p/pharo/issues/detail?id=3533 > > Of course, you can always use: > > dict at: x ifAbsent: y > > except that it is not always desirable to send #value message to 'y' > argument, especially if you can't tell anything about nature of objects you > are storing in dictionary, and when speed is essential, it would be good to > have something like this: > > at: key ifAbsentValue: defaultValue > "Answer the value associated with the key or, if key isn't found, > answer the default value" > ^((array at: (self findElementOrNil: key)) ifNil: [ ^ > defaultValue ]) value > > > Cog VM shows a significant difference in delivering an answer: > > | dict | > dict := Dictionary new. > dict at: #a put: 1. > > [ 1000000 timesRepeat: [ dict at: #foo ifAbsentValue: #bar ] ] timeToRun > 236 234 239 > > [ 1000000 timesRepeat: [ dict at: #a ifAbsentValue: #bar ] ] timeToRun > 241 234 236 237 > > [ 1000000 timesRepeat: [ dict at: #foo ifAbsent: [#bar] ] ] timeToRun > 322 318 > > [ 1000000 timesRepeat: [ dict at: #a ifAbsent: [ #bar ] ] ] timeToRun > 363 336 340 Note that the block creation causes the slowdown, so if you create a block and reuse that, then there should be no measureable difference in performance. Try this: | absentBlock | absentBlock := [ #bar ]. [ 1000000 timesRepeat: [ dict at: #a ifAbsent: absentBlock ] ] timeToRun Levente > > > >

Jan. 13, 2011

Re: [Pharo-project] Socket question (Was Re: Xtreams up to date)

by Levente Uzonyi

On Wed, 12 Jan 2011, mkobetic(a)gmail.com wrote: > I started looking at the Socket failures that I can reproduce and I can't wrap my head around the SocketReadingWritingTest>>setUp. Based on what I know about TCP sockets it doesn't make sense to me. AFAIK to get both ends of a connected TCP connection (lacking a socketpair call) I need 3 sockets. A listening socket, a client socket (doing connect) and finally the server socket that comes out as a result of accept on the listener. So I'd expect to see something like this in the setUp: There's a way to use only 2 sockets and this causes the problem. If you use #listenOn:, then there will be no backlog and the listening socket will accept the connection. If you use #listenOn:backlogSize: instead, then it should work. Levente > > | data input output listener socket1 socket2 process sync | > Socket initializeNetwork. > sync := Semaphore new. > listener := Socket newTCP. > listener listenOn: 9999. > process := [ [ socket1 := listener accept ] ensure: [ listener close ]. sync signal ] fork. > socket2 := Socket newTCP. > socket2 connectTo: (NetNameResolver localHostAddress) port: 9999. > sync wait. > output := socket1 reading. > input := socket2 writing. > > Surprisingly, the above doesn't work, while many of the Socket tests seem to pass for me despite my brain telling me that it can't possibly. Can anyone shed some light on this for me ? > > Thanks, > > Martin > > >

Jan. 13, 2011