March 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] cant squeak map

by GÃ¶ran Krampe

Hi! StÃ©phane Ducasse wrote: >> Hi! >> >> (being the creator of SM I can't resist this thread on Pharo-list...) >> >> Yes, I am cross-posting, so sue me. > > No we are not like that :) Goodie. :) >> The above is not really a problem with SM "as a tool" but with the >> contents of SM. > > Indeed. > >> And as I predicted a few years back, SS (Squeaksource) >> and PU (package universes) are indeed competing with SM and would >> (as it >> did) cause us to get a fragmentation. I am not blaiming anyone, but >> I do >> see that as the primary cause of "data rot". >> >> Since a lot of projects use SCM hosting as available on SS they don't >> bother taking the extra step in keeping entries at SM fresh. > > Come on. The publish was broken for years. Yes, broken in SS, not in SM AFAIK. Which indeed made it hard to keep entries in SM fresh, I have never looked into it because I haven't had that itch myself. [SNIP] >> And why do you think "cleaning it" would solve something? I am not >> saying that cleaning >> is not needed - just saying that cleaning is not solving the real >> problem. We can't seriously tell people to maintain their packages >> in 3 >> different places (SS, PU, SM) IMHO. >> >> I am interested in creating a new SM3 that can replace both PU and SM >> and that plays very well with SS installations (there are more than >> one >> even though squeaksource.com is the most important one) and can use >> Deltastreams. By "replace" I mean that SM3 of course should simply >> replace current SM but also that it could possibly "auto mirror" >> packages from SS installations making them available on SM3 *without >> any >> extra effort at all*. > > I think that the key point is that somebody is responsible for > publishing package in > a public ready to use Universe/Version I think it boils down to three different aspects/use cases: - Making versions/projects available in a single nice catalog (SM, SS) - Making controlled releases for a set of loosely defined environments (SM) - Making controlled releases for a specific environment (PU) The first is in its simplest form just access to an MC repo. Or just access to code in some other form on SM - load it at your own peril. The second is slightly more defined, since SM doesn't automatically expose "all versions" but only those that you specifically put there, in combination with categorization for Squeak version etc - it is not as "wild" as SS is. The third is hard core controlled - a specific version ONLY for a specific image. Including dependencies etc. regards, GÃ¶ran

March 12, 2009

Re: [Pharo-project] Fonts working great

by Damien Cassou

On Thu, Mar 12, 2009 at 1:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > may be we should start to add such nice snippets on the wiki :) Unnecessary because Pharo will come with a great font included. -- Damien Cassou http://damiencassou.seasidehosting.st

March 12, 2009

Re: [Pharo-project] Blocked while merging

by StÃ©phane Ducasse

Apparently with your fix I could merge. I will retry to be sure. On Mar 12, 2009, at 11:10 AM, Gary Chambers wrote: > Hi Stef. > For the old MC browser the revertSelection option doesn't have the > code to > do the option, seems to be present in 3.10 images though... I don't > get a > DNU for the diff option. > > As for the Polymorph tool, it looks like there can be cases where > there is a > conflict with a deletion present in the incoming version of the merge. > > Try replacing PSMCMergePatchMorph>>selectNextConflict with: > > selectNextConflict > "Select the next conflict after the current selection, if any." > > |next def| > next := self nextConflict ifNil: [^self]. > def := next remoteDefinition ifNil: [next localDefinition]. > self changed: {#changes. #openPath. next targetClassName asString. def > selector asString} > > And, if that works in your case I'll version up the change and put on > SqueakSource. > > None of these issues should actually prevent you from merging, as such > though. > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, March 10, 2009 10:22 AM > Subject: Re: [Pharo-project] Blocked while merging > > > Hi all > > did you see this mail > because I'm really blocked and cannot merge anymore in pharo. > > Stef > On Mar 9, 2009, at 1:56 PM, StÃ©phane Ducasse wrote: > >> Hi all >> >> I wanted to merge and I tried with the new Diff tools and I got a >> selector DNU, >> so I switched back to the old merge tool but I got the following bugs >> >> - click on an item >> bring the menu revertSelection -> DNU >> diff -> DNU >> install crahsed. >> >> Does anybody get the same, I'm using pharo 10248 >> >> Stef >> >> >> _______________________________________________ >> 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 >

March 12, 2009

Re: [Pharo-project] Fonts working great

by StÃ©phane Ducasse

may be we should start to add such nice snippets on the wiki :) Stef On Mar 12, 2009, at 11:02 AM, Damien Cassou wrote: > Hi, > > I've set-up the following script (based on a previous message in this > list) for people using a recent VM and having DejaVu: > > |font codeFont| > font := LogicalFont familyName: 'DejaVu Serif' pointSize: 10. > codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. > Preferences setListFontTo: font. > Preferences setMenuFontTo: font. > Preferences setCodeFontTo: codeFont. > Preferences setButtonFontTo: font. > Preferences setSystemFontTo: font. > font := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. > Preferences setWindowTitleFontTo: font. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 12, 2009

Re: [Pharo-project] cant squeak map

by StÃ©phane Ducasse

> Hi! > > (being the creator of SM I can't resist this thread on Pharo-list...) > > Yes, I am cross-posting, so sue me. No we are not like that :) >> > > The above is not really a problem with SM "as a tool" but with the > contents of SM. Indeed. > And as I predicted a few years back, SS (Squeaksource) > and PU (package universes) are indeed competing with SM and would > (as it > did) cause us to get a fragmentation. I am not blaiming anyone, but > I do > see that as the primary cause of "data rot". > > Since a lot of projects use SCM hosting as available on SS they don't > bother taking the extra step in keeping entries at SM fresh. Come on. The publish was broken for years. > Understandable but still a pity we couldn't create some harmony there. > > PU was a clear "fork" of SM (not the codebase but the use case) adding > dependencies. I still think it was sad that people couldn't instead > help > out in SM making it better. Indeed >> Sorry guys. clean SM first if you want it to be a credible >> alternative. > > This last line is... odd. What do you mean with "guys"? anybody. If somebody wants to have sm on pharo then they should clean the database. > And why do you think "cleaning it" would solve something? I am not > saying that cleaning > is not needed - just saying that cleaning is not solving the real > problem. We can't seriously tell people to maintain their packages > in 3 > different places (SS, PU, SM) IMHO. > > I am interested in creating a new SM3 that can replace both PU and SM > and that plays very well with SS installations (there are more than > one > even though squeaksource.com is the most important one) and can use > Deltastreams. By "replace" I mean that SM3 of course should simply > replace current SM but also that it could possibly "auto mirror" > packages from SS installations making them available on SM3 *without > any > extra effort at all*. I think that the key point is that somebody is responsible for publishing package in a public ready to use Universe/Version > If SM3 also covers the functionality that PU has > (dependencies etc) then perhaps we could migrate over to it from PU. > Or > again, we could make SM3 be able to "auto mirror" PUs, but that > would be > less optimal I think. Ok for me > Yes, I am picking up Deltastreams, have fixed lots of broken tests > over > the last few days and have read up on Matthew's code. I think DS is a > really promising technology that can open up new nice tools, and still > not compete head on with MC/MC2. Instead it should hopefully replace > changesets and form a nice complement to MC/MC2. I'm interested into that too. > Finally, I have always felt that SM should work in as many Squeak > images > as possible - and Pharo is one of them of course. I don't care if > Pharo > decides to not have SM as a "first class" citizen - as long as it > can be > loaded into Pharo, and I will try to help out with ensuring that it > can > - hopefully that is an effort that Pharo developers appreciate. (?) Sure! Stef > > > regards, GÃ¶ran > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 12, 2009

Re: [Pharo-project] Fonts working great

by Rob Rothwell

And...you can always replace the font name with another if you like...just look at exactly what it is called in the font dialog box when you choose a new font manually! Rob On Thu, Mar 12, 2009 at 6:02 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > Hi, > > I've set-up the following script (based on a previous message in this > list) for people using a recent VM and having DejaVu: > > |font codeFont| > font := LogicalFont familyName: 'DejaVu Serif' pointSize: 10. > codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. > Preferences setListFontTo: font. > Preferences setMenuFontTo: font. > Preferences setCodeFontTo: codeFont. > Preferences setButtonFontTo: font. > Preferences setSystemFontTo: font. > font := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. > Preferences setWindowTitleFontTo: font. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 12, 2009

Re: [Pharo-project] Blocked while merging

by Gary Chambers

Hi Stef. For the old MC browser the revertSelection option doesn't have the code to do the option, seems to be present in 3.10 images though... I don't get a DNU for the diff option. As for the Polymorph tool, it looks like there can be cases where there is a conflict with a deletion present in the incoming version of the merge. Try replacing PSMCMergePatchMorph>>selectNextConflict with: selectNextConflict "Select the next conflict after the current selection, if any." |next def| next := self nextConflict ifNil: [^self]. def := next remoteDefinition ifNil: [next localDefinition]. self changed: {#changes. #openPath. next targetClassName asString. def selector asString} And, if that works in your case I'll version up the change and put on SqueakSource. None of these issues should actually prevent you from merging, as such though. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, March 10, 2009 10:22 AM Subject: Re: [Pharo-project] Blocked while merging Hi all did you see this mail because I'm really blocked and cannot merge anymore in pharo. Stef On Mar 9, 2009, at 1:56 PM, StÃ©phane Ducasse wrote: > Hi all > > I wanted to merge and I tried with the new Diff tools and I got a > selector DNU, > so I switched back to the old merge tool but I got the following bugs > > - click on an item > bring the menu revertSelection -> DNU > diff -> DNU > install crahsed. > > Does anybody get the same, I'm using pharo 10248 > > Stef > > > _______________________________________________ > 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

March 12, 2009

[Pharo-project] Fonts working great

by Damien Cassou

Hi, I've set-up the following script (based on a previous message in this list) for people using a recent VM and having DejaVu: |font codeFont| font := LogicalFont familyName: 'DejaVu Serif' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. Preferences setWindowTitleFontTo: font. -- Damien Cassou http://damiencassou.seasidehosting.st

March 12, 2009

Re: [Pharo-project] cant squeak map

by GÃ¶ran Krampe

Hi! (being the creator of SM I can't resist this thread on Pharo-list...) Yes, I am cross-posting, so sue me. StÃ©phane Ducasse wrote: > Yes yes yes but we do not use SM since years. > I cannot load one single package without breaking my image. > If you read the comments of a package you should not load it because > most > of the time people entered that the code may work. > Then the version identification is often obsolete. The above is not really a problem with SM "as a tool" but with the contents of SM. And as I predicted a few years back, SS (Squeaksource) and PU (package universes) are indeed competing with SM and would (as it did) cause us to get a fragmentation. I am not blaiming anyone, but I do see that as the primary cause of "data rot". Since a lot of projects use SCM hosting as available on SS they don't bother taking the extra step in keeping entries at SM fresh. Understandable but still a pity we couldn't create some harmony there. PU was a clear "fork" of SM (not the codebase but the use case) adding dependencies. I still think it was sad that people couldn't instead help out in SM making it better. > So you may be able to load SM in pharo but we will not use it as a way > to manage code. Ehm... SM was never meant to "manage code". It is not an SCM. > Sorry guys. clean SM first if you want it to be a credible alternative. This last line is... odd. What do you mean with "guys"? And why do you think "cleaning it" would solve something? I am not saying that cleaning is not needed - just saying that cleaning is not solving the real problem. We can't seriously tell people to maintain their packages in 3 different places (SS, PU, SM) IMHO. I am interested in creating a new SM3 that can replace both PU and SM and that plays very well with SS installations (there are more than one even though squeaksource.com is the most important one) and can use Deltastreams. By "replace" I mean that SM3 of course should simply replace current SM but also that it could possibly "auto mirror" packages from SS installations making them available on SM3 *without any extra effort at all*. If SM3 also covers the functionality that PU has (dependencies etc) then perhaps we could migrate over to it from PU. Or again, we could make SM3 be able to "auto mirror" PUs, but that would be less optimal I think. Yes, I am picking up Deltastreams, have fixed lots of broken tests over the last few days and have read up on Matthew's code. I think DS is a really promising technology that can open up new nice tools, and still not compete head on with MC/MC2. Instead it should hopefully replace changesets and form a nice complement to MC/MC2. Finally, I have always felt that SM should work in as many Squeak images as possible - and Pharo is one of them of course. I don't care if Pharo decides to not have SM as a "first class" citizen - as long as it can be loaded into Pharo, and I will try to help out with ensuring that it can - hopefully that is an effort that Pharo developers appreciate. (?) regards, GÃ¶ran

March 12, 2009

Re: [Pharo-project] cant squeak map

by Damien Cassou

On Wed, Mar 11, 2009 at 8:45 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> But it is important that Universes UI is then "uplifted" to be as usable >> as SqueakMap is. This tool is namely aimed for end users, not developers >> and specially newbies need to have as simple as possible way to load >> software. >> >> SM is close to that, Universes not. Universes has the Â biggest advantage >> to load all prerequisite packages, but lacks other things like easy >> search for packages, etc. Have you tried the OB-based universe browser? It's included in all squeak-dev images. You can search for packages by name or by category or by status (installed, upgradable...). It's certainly not perfect but it works ok for me. If you have fixes, please commit them directly to the repository. > Totally agree. I would love having search option in universe or dependencies > management in SM haha. There is a search option in OB-universe -- Damien Cassou http://damiencassou.seasidehosting.st

March 12, 2009