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

Re: [Pharo-project] Refactoring Browser depenences

by Lukas Renggli

> That's what I used, as it has a nice UI and it is easy to use. But there is > also something from Lukas that they use in Seaside and does that kind of > graphics. I don't know if it has a UI or a tutorial anywhere, thus. Load it using: Gofer new renggli: 'packaging'; package: 'GraphViz'; package: 'Package-Dependencies'; load Then have a look at the examples on the class side of PDPackageAnalyzer. It creates a .dot file that can be fed into GraphViz. Preferably you generate an SVG graphic as it has nice tooltips. Contrary to the other tool, Package-Dependencies does not show unnecessary transitive dependencies. It only displays the direct and shortest dependencies. Circular dependencies are highlighted in red. Very useful for complicated packages like Seaside (http://builder.seaside.st/distributions/004-Seaside3.0.0-a5/seaside.svg) I should add it to the build-server :-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by Mariano Martinez Peck

2010/1/12 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El vie, 08-01-2010 a las 13:48 +0100, Mariano Martinez Peck escribiÃ³: > > > > > > On Fri, Jan 8, 2010 at 1:12 PM, Esteban Lorenzano > > <estebanlm(a)gmail.com> wrote: > > btw, ConfigurationOfPharo shouldn't be > > ConfigurationOfPharoDev? > > > > > > No. For that we have the groups. The same ConfigurationOfPharo will be > > used for differents stuff: > > > > ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoDev' > > > > or > > > > ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoWeb ' > > (if they came back) > > > > or > > > > ConfigurationOfPharo project version: 'xxx' load: 'SOMETHING' (if > > they came back) > > > > I'm writing the metacello config for Magma. I suppose that the same > applies here. > > a group for Client, a group for Server and a group for Tester. > all of them defined in ConfigurationOfMagma. > > right? > > Yes. You can also create groups from others groups. For example you may want a client and the test, so, you can create another groups that brings both. However it is not NECESSARY as you can always do: (ConfigOfXX project version: 'YYY' ) load: 'aGroup' or: (ConfigOfXX project version: 'YYY' ) load: #('aGroup' 'anotherGroup'). > BTW. How did you compute dependencies in packages you aren't completely > aware of the details. I remember a tool for this. Where can I find them? > > you found it :) > Cheers > > > Cheers > > > > Mariano > > > > > > On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck > > > > <marianopeck(a)gmail.com> said: > > > > > > > > > > > (Sorry for the long email) > > > > > > Yes, after a couple of weeks, I have written most of the > > needed Metacello > > > configurations for the Dev images 1.0. Forget 1.1 for a > > while. Now we are > > > able to: > > > > > > 1) Load stable version of packages > > > 2) Manage the dependencies automatically > > > 3) Each developer can create its custom PharoDev image > > > 4) Flexibility to load the packages you want > > > 5) Choose the browser for example: OB or O2 > > > 6) Choose to load the tests or not > > > 7) Load each package in a PharoCore image without having to > > install anything > > > else (all the dependencies should be managed automatically) > > > 8) You can take a PharoCore image and "transform" it to a > > Dev image, or even > > > web. > > > 9) Others... > > > > > > This is not completed yet. There are some things that we are > > discussing with > > > Dale, but they are ok as a first step. I rather go step by > > step. > > > > > > What I did is to create all the infrastructure: > > > > > > a) The Configuration classes > > > b) The dependencies > > > c) the groups, > > > > > > In summary, most of the "structure" and static information. > > However, I am > > > not sure which version to load of each package. I will > > probable take care of > > > building the Dev images, but I won't: > > > > > > - Merge anything. It will not be my task to merge OB, or RB > > or whatever. > > > - Check every version of each package before doing a release > > to see if it is > > > stable or not. > > > > > > So...what I REALLY (actually, WE) need is that each > > developer, each > > > maintainer of the packages that we load of a PharoDev image, > > help us to > > > create the stable versions. To create a new version for the > > Metacello > > > configuration is VERY easy, The hard part is already done. > > You just have to > > > create a method and say which versions (except you create or > > eliminate > > > packages or dependencies). If you read the code, you will > > probably > > > understand it. However, you can read the Metacello tutorial > > (no more than > > > one hour), or ask me or even more in the Metacello mailing > > list. > > > So...PLEASE, I need the help of the maintainers to create > > the versions. So > > > far, I created the first version (1.0) with the latest > > version. But the idea > > > is that then you create 1.1.1 or 1.2 or whatever you > > consider. > > > > > > All the configurations can be found in > > > http://www.squeaksource.com/MetacelloRepository > > > > > > So far, I created: ConfigurationOfNewInspector, > > ConfigurationOfOCompletion, > > > ConfigurationOfOmniBrowser, > > ConfigurationOfPharoMorphicExtras, > > > ConfigurationOfPharoSound, > > ConfigurationOfRefactoringBrowser, > > > ConfigurationOfShout , and......ConfigurationOfPharo!!! > > > > > > To install them, just download that package and evaluate the > > load. Example: > > > > > > Gofer new > > > squeaksource: 'MetacelloRepository'; > > > package: 'ConfigurationOfShout'; > > > load. > > > > > > ((Smalltalk at: #ConfigurationOfShout) project version: > > '1.0') load. > > > > > > And then, you can also for exaple do: > > > > > > ((Smalltalk at: #ConfigurationOfShout) project version: > > '1.0') load: 'Core' > > > > > > this doesn't install the tests. > > > > > > Or for example: (ConfigurationOfOmniBrowser project > > version: '1.0') load: > > > 'Dev' > > > > > > etc... > > > > > > So, you can load any project and with the group you want. > > All of that can be > > > (or should be hahahaha) perfectly loaded in a 1.0 Core > > image. > > > > > > What I would really appreciate is if each maintainer can > > look at the code, > > > load the different groups and give me feedback on the > > dependencies or > > > whatever. > > > > > > I really wait your feedback. > > > > > > Mariano > > > > > > ps: I will release soon the first dev image using this :) > > > > > > > > > > > (Sorry for the long email) Yes, after a couple of > > weeks, I have writ= > > > ten most of the needed Metacello configurations for the Dev > > images 1.0. For= > > > get 1.1 for a while. Now we are able to: 1) Load > > stable version of p= > > > ackages > > > 2) Manage the dependencies automatically 3) Each > > developer can create it= > > > s custom PharoDev image > > > 4) Flexibility to load the packages you want 5) Choose > > the browser for e= > > > xample: OB or O2 6) Choose to load the tests or not 7) > > Load each pack= > > > age in a PharoCore image without having to install anything > > else (all the d= > > > ependencies should be managed automatically) > > > > > > 8) You can take a PharoCore image and "transform" > > it to a Dev ima= > > > ge, or even web. 9) Others... This is not > > completed yet. There a= > > > re some things that we are discussing with Dale, but they > > are ok as a first= > > > > > step. I rather go step by step. > > > What I did is to create all the > > infrastructure: a) The Configura= > > > tion classes b) The dependencies > > > c)=A0 the groups, In summary, most of the > > "structure" and = > > > static information. However, I am not sure which version to > > load of each pa= > > > ckage. I will probable take care of building the Dev images, > > but I won'= > > > t: > > > > > > - Merge anything. It will not be my task to merge OB, or > > RB or whatever= > > > . - Check every version of each package before doing a > > release to see if= > > > it is stable or not. So...what I REALLY (actually, > > WE) need is that= > > > each developer, each maintainer of the packages that we > > load of a PharoDev= > > > image, help us to create the stable versions. To create a > > new version for = > > > > > the Metacello configuration is VERY easy, The hard part is > > already done. Yo= > > > u just have to create a method and say which versions > > (except you create or= > > > > > eliminate packages or dependencies). If you read the code, > > you will probab= > > > ly understand it. However, you can read the Metacello > > tutorial (no more tha= > > > n one hour), or ask me or even more in the Metacello mailing > > list. So...PLE= > > > ASE, I need the help of the maintainers to create the > > versions. So far, I c= > > > reated the first version (1.0) with the latest version. But > > the idea is tha= > > > t then you create 1.1.1 or 1.2 or whatever you consider. > > > All the configurations can be found in <a > > href=3D"http://www.squeaksour= > > > > > ce.com/MetacelloRepository"> > http://www.squeaksource.com/MetacelloRepository= > > > </a> So far, I created:=A0 > > ConfigurationOfNewInspector, Configuratio= > > > nOfOCompletion, ConfigurationOfOmniBrowser, > > ConfigurationOfPharoMorphicExtr= > > > as, ConfigurationOfPharoSound, > > ConfigurationOfRefactoringBrowser, Configura= > > > tionOfShout , and......ConfigurationOfPharo!!! > > > To install them, just download that package and evaluate > > the load. Exam= > > > ple: Gofer new =A0=A0=A0 squeaksource: > > 'MetacelloRepository&#= > > > 39;; =A0=A0=A0 package: > > 'ConfigurationOfShout'; =A0=A0=A0 loa= > > > d. ((Smalltalk at: #ConfigurationOfShout) project > > version: '1.0&= > > > #39;) load. > > > And then, you can also for exaple do:=A0 > > > ((Smalltalk at: #ConfigurationOfShout) project version: > > '1.0') load= > > > : 'Core'=A0 this doesn't install the tests. > > Or for = > > > example:=A0 (ConfigurationOfOmniBrowser project version: > > '1.0') loa= > > > d: 'Dev' > > > etc... So, you can load any project and with the > > group you want.= > > > All of that can be (or should be hahahaha) perfectly loaded > > in a 1.0 Core = > > > > > image. What I would really appreciate is if each > > maintainer can look= > > > at the code, load the different groups and give me feedback > > on the depende= > > > ncies or whatever. > > > I really wait your feedback. > > Mariano ps:=A0 I will relea= > > > se soon the first dev image using this :) > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2010

Re: [Pharo-project] Refactoring Browser depenences

by Mariano Martinez Peck

2010/1/12 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > > > > > How can I get the dependencies of a given package by software? Mind to > > share the package? > > > > Thanks > > I think I found it. Dependency Browser from HernÃ¡n Morales: > > http://cs.hernanmorales.com.ar/projects/dependencyBrowser/DBrowser-en.php > > Or are you using something else? > > That's what I used, as it has a nice UI and it is easy to use. But there is also something from Lukas that they use in Seaside and does that kind of graphics. I don't know if it has a UI or a tutorial anywhere, thus. Cheers > Thanks anyway. > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2010

Re: [Pharo-project] System -> About in Dev images

by Mariano Martinez Peck

2010/1/12 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El lun, 11-01-2010 a las 23:41 +0100, Mariano Martinez Peck escribiÃ³: > > > > > > 2010/1/11 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > > El lun, 11-01-2010 a las 22:06 +0000, Michael Roberts > > escribiÃ³: > > > I'm afraid i've got rather lost in this thread. > > > > > > >> As an after thought after seeing other posts on the > > issue, I think > > > >> more than a generic warning that "may break the > > image" the > > > >> Monticello comments and/or a simple explanation on the > > reasons and > > > >> affected packages *before* the update starts with > > an option to > > > >> proceed or abort is much in need. > > > >> > > > >> > > > >> Yes, maybe. Then thing is that I am not sure in > > which cases it > > > >> would break. Only in overrides? How many overrides do > > we have from > > > >> external pacakges in Core stuff? I have no idea. > > > > > > > > > > I think given that we are at a very early stage of building > > the Pharo > > > image from PharoCore i.e Metacello just coming on etc, we > > should > > > simplify the concerns above. > > > > > > Basically we should only build Pharo on top of a known > > PharoCore. Just > > > because packages don't contain overrides does not imply that > > moving > > > the core image will break packages on top. Don't offer such > > a feature, > > > and then worry about what will happen. > > > > > > Part of the Pharo build script should set a flag that > > prevents system > > > update in the short term. Longer term we should switch the > > available > > > update mechanism to #loadLatest on the > > ConfigurationOfPharo. There is > > > then one System update feature, but different implementation > > in Pharo > > > vs PharoCore. > > > > > > > > > So the vote is for disabled for now? > > > > > > > > Yes. And this is cool because we have to put focus in to make Pharo > > images more stable. We cannot introduce such a feature when we are not > > even stable with Dev images. Let's go step by step. Once we get stable > > Dev images, good processes and package managment, then we can review > > this stuff about updating. > > > > > > Do you want to do it ? ;) > > > > Yes, I will do it, but tomorrow. Cool!! No hurry.. > My idea is to make this a preference > and the the build script just disable it. > > Be careful with the preferences....remember all the changes in 1.1 > More tomorrow. > > Cheers > > > > > cheers, > > > Mike > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > Miguel CobÃ¡ > > http://miguel.leugim.com.mx > > > > > > _______________________________________________ > > > > > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2010

Re: [Pharo-project] Pharo 64bits

by John M McIntosh

I don't have a current V5 64bit VM for Squeak that is setup for running 64bit images. The one out there doesn't work properly with cursor keys, and likely has the draw/crash bug, also I've not built a FreeType2 plugin for a 64bit VM yet, so I can't say if that even works. Maybe that will happen on the weekend. However people can try the Squeak.5.0.0.b9.64*64.app and see what flies... On 2010-01-11, at 11:33 PM, Laval Jannik wrote: > Hi folks, > > I would really like to put pharo64bit on the pharo forge. > We need people to work on it. > > Does anybody know how I can put it on gforge ? > > Cheers > > Jannik > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 12, 2010

Re: [Pharo-project] Pharo 64bits

by Damien Cassou

Hi Jannik On Tue, Jan 12, 2010 at 8:33 AM, Laval Jannik <jannik.laval(a)gmail.com> wrote: > I would really like to put pharo64bit on the pharo forge. > We need people to work on it. > > Does anybody know how I can put it on gforge ? please try again. If it still doesn't work, contact me privately by IM or email. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Jan. 12, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Lukas Renggli

> I found on the iPhone the currently Â RBInternalSpellChecker took up lots of memory, and did > a frightful unpack initialization process at startup time (many many seconds) on an iPhone. > It was ditched... That was fixed a long time ago. I flushed the cache on shutDown and it only reinitializes it again if it is used. Luka -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010

Re: [Pharo-project] [ANN] WorkingSet

by Lukas Renggli

>>> That's strange, since I use Toolset for these queries. Should I use something else? >> >> I am using OB, but I get the old system browser in some cases: for >> senders, implementors and sets of classes. > > What ToolSet do you use? In the Pharo images, the ToolSet I install > takes care of launching OB in all cases. OBSystemBrowserAdaptor Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010

[Pharo-project] Pharo 64bits

by Laval Jannik

Hi folks, I would really like to put pharo64bit on the pharo forge. We need people to work on it. Does anybody know how I can put it on gforge ? Cheers Jannik

Jan. 12, 2010

Re: [Pharo-project] Spell check test cases

by Lukas Renggli

> Glad you like the tests. > > In my version of RBSpellChecker>>normalize, I also commented out the line: > Â Â Â Â "or: [ input peek = $' ]" "this causes false positives eg 'OK' in class > comments" That change breaks word like don't Smalltalk's etc. I see that there are a few other cases where you don't want any $'. So I removed it for now. > OK returns an error on k, RB b etc. > > So that's what causes the two cases on a Linux box (fairly sure). I'm > guessing you have letters k i b and t in the Mac dictionary, or it > specifically doesn't check one letter words? RBSpellChecker>>#normalize: removes one letter words, so I don't think this can be the error. If you show the individual words that are checked against the dictionary on the transcript, you will see that they all look pretty ok. > BTW, it looks like RBPoolVariableNameSpellingRule should be > RBPoolDictionaryNameSpellingRule, as that's what it looks at? Ok, I renamed that. Probably this rule isn't really needed anyway ... Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010