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

Re: [Pharo-project] Big problem with the implementation of traits

by StÃ©phane Ducasse

No we check and this is strange. What is the hash of a trait? Stef On Jan 15, 2009, at 12:08 PM, Adrian Lienhard wrote: > Confirmed. I created http://code.google.com/p/pharo/issues/detail?id=443 > Not sure how it is possible that this IdentitySet can get into that > state. Any ideas? > > Adrian > > On Jan 15, 2009, at 11:01 , Damien Cassou wrote: > >> Hi, >> >> if you load the latest version of Collection package in PharoInbox >> and >> evaluate the following, you will see a problem: >> >> TCreationWithTest users ===> an IdentitySet(SetTest >> OrderedCollectionTest ArrayTest) >> >> TCreationWithTest users size =====> 5 >> >> >> Depending on your image, the results may vary but will probably still >> be incorrect. >> >> Bye >> >> -- >> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by Damien Cassou

On Thu, Jan 15, 2009 at 11:31 AM, Michael Rueger <m.rueger(a)acm.org> wrote: > yes, that is unfortunate that we chose the same name around the same > time and both projects are already well known enough to not easily > switch names. > But, as others already said, the projects are sufficiently different > to not be confused easily. > > Maybe we could cross-link on the sites? > "if you are looking for the PHP Pharo project go here" and vice versa? What about http://code.google.com/p/pharo/? -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 15, 2009

Re: [Pharo-project] Big problem with the implementation of traits

by Adrian Lienhard

Confirmed. I created http://code.google.com/p/pharo/issues/detail?id=443 Not sure how it is possible that this IdentitySet can get into that state. Any ideas? Adrian On Jan 15, 2009, at 11:01 , Damien Cassou wrote: > Hi, > > if you load the latest version of Collection package in PharoInbox and > evaluate the following, you will see a problem: > > TCreationWithTest users ===> an IdentitySet(SetTest > OrderedCollectionTest ArrayTest) > > TCreationWithTest users size =====> 5 > > > Depending on your image, the results may vary but will probably still > be incorrect. > > Bye > > -- > 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

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by Michael Rueger

Hi David, yes, that is unfortunate that we chose the same name around the same time and both projects are already well known enough to not easily switch names. But, as others already said, the projects are sufficiently different to not be confused easily. Maybe we could cross-link on the sites? "if you are looking for the PHP Pharo project go here" and vice versa? Michael On Thu, Jan 15, 2009 at 10:15 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi david > > We already communicated a lot on this project such as major > conferences in our field (www.esug.org) > Seaside (http://www.seaside.st) is developed using it and will start > to communicate on that too. > When we check in may it was clear that there was no other projects > around and pharo is close to > french so we expected that nobody else would take that name :) > Now we got a professional designer for our logo and invested a lot in > it. > We will have two or three books coming out around Pharo and > our community is active and growing. It also is a strong symbol for > us. So we will stick with our name. > > Stef > > > On Jan 15, 2009, at 1:56 AM, David Hammond wrote: > >> Hi, I don't intend to cause a big fuss, but I have a concern about the >> name of your project. >> >> I first became aware of your project yesterday when I ran a Google >> search for the word "pharo". This is the name I had chosen for my open >> source PHP framework project back in January of 2008. At the time, the >> Smalltalk-related Pharo project did not yet exist, and the Google >> search results yielded nothing at all similar or relevant to the >> project I wanted to start. I purchased pharo.org that month (with >> trac.pharo.org, svn.pharo.org, and apt-trunk.pharo.org currently in >> active use) and made a teaser post about the project on my blog: >> http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… >> >> My intention is to release the Pharo PHP framework under a BSD license >> and not profit directly from the project. I have no stakes in >> preserving the exclusiveness of the "Pharo" name aside from avoiding >> possible confusion. But I do believe that the name conflict is an >> issue of concern, since both of our projects are directly related to >> programming languages. >> >> _______________________________________________ >> 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 >

Jan. 15, 2009

[Pharo-project] Big problem with the implementation of traits

by Damien Cassou

Hi, if you load the latest version of Collection package in PharoInbox and evaluate the following, you will see a problem: TCreationWithTest users ===> an IdentitySet(SetTest OrderedCollectionTest ArrayTest) TCreationWithTest users size =====> 5 Depending on your image, the results may vary but will probably still be incorrect. Bye -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by StÃ©phane Ducasse

Hi david We already communicated a lot on this project such as major conferences in our field (www.esug.org) Seaside (http://www.seaside.st) is developed using it and will start to communicate on that too. When we check in may it was clear that there was no other projects around and pharo is close to french so we expected that nobody else would take that name :) Now we got a professional designer for our logo and invested a lot in it. We will have two or three books coming out around Pharo and our community is active and growing. It also is a strong symbol for us. So we will stick with our name. Stef On Jan 15, 2009, at 1:56 AM, David Hammond wrote: > Hi, I don't intend to cause a big fuss, but I have a concern about the > name of your project. > > I first became aware of your project yesterday when I ran a Google > search for the word "pharo". This is the name I had chosen for my open > source PHP framework project back in January of 2008. At the time, the > Smalltalk-related Pharo project did not yet exist, and the Google > search results yielded nothing at all similar or relevant to the > project I wanted to start. I purchased pharo.org that month (with > trac.pharo.org, svn.pharo.org, and apt-trunk.pharo.org currently in > active use) and made a teaser post about the project on my blog: > http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… > > My intention is to release the Pharo PHP framework under a BSD license > and not profit directly from the project. I have no stakes in > preserving the exclusiveness of the "Pharo" name aside from avoiding > possible confusion. But I do believe that the name conflict is an > issue of concern, since both of our projects are directly related to > programming languages. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by Serge Stinckwich

2009/1/15 David Hammond <dhammond(a)webdevout.net>: > Hi, I don't intend to cause a big fuss, but I have a concern about the > name of your project. > > I first became aware of your project yesterday when I ran a Google > search for the word "pharo". This is the name I had chosen for my open > source PHP framework project back in January of 2008. At the time, the > Smalltalk-related Pharo project did not yet exist, and the Google > search results yielded nothing at all similar or relevant to the > project I wanted to start. I purchased pharo.org that month (with > trac.pharo.org, svn.pharo.org, and apt-trunk.pharo.org currently in > active use) and made a teaser post about the project on my blog: > http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… > > My intention is to release the Pharo PHP framework under a BSD license > and not profit directly from the project. I have no stakes in > preserving the exclusiveness of the "Pharo" name aside from avoiding > possible confusion. But I do believe that the name conflict is an > issue of concern, since both of our projects are directly related to > programming languages. Hum, yes a bit annoying. Thank you David for your report. The name Pharo was selected at the end of april 2008/beginning of May 2008. Look here in this old archive : http://lists.gforge.inria.fr/pipermail/sapphire-devl/2008-May/thread.html I think that the two Pharos are sufficiently distinct not to confuse them. Maybe we could rename our Pharo to "Pharo Smalltalk" and yours "Pharo PHP Web framework" ? BTW, you could use Seaside (http://seaside.st) to switch to Pharo Smalltalk in order to implement Pharo framework ;-) -- Serge Stinckwich IRD - UR 079 Geodes, MSI Team, Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Jan. 15, 2009

[Pharo-project] Pharo name conflict

by David Hammond

Hi, I don't intend to cause a big fuss, but I have a concern about the name of your project. I first became aware of your project yesterday when I ran a Google search for the word "pharo". This is the name I had chosen for my open source PHP framework project back in January of 2008. At the time, the Smalltalk-related Pharo project did not yet exist, and the Google search results yielded nothing at all similar or relevant to the project I wanted to start. I purchased pharo.org that month (with trac.pharo.org, svn.pharo.org, and apt-trunk.pharo.org currently in active use) and made a teaser post about the project on my blog: http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… My intention is to release the Pharo PHP framework under a BSD license and not profit directly from the project. I have no stakes in preserving the exclusiveness of the "Pharo" name aside from avoiding possible confusion. But I do believe that the name conflict is an issue of concern, since both of our projects are directly related to programming languages.

Jan. 15, 2009

Re: [Pharo-project] That's a pharo!

by Alexandre Bergel

:-) Nice picture Alexandre On 14 Jan 2009, at 16:44, Hilaire Fernandes wrote: > It is where I am working http://crdp.ac-bordeaux.fr/cddp40/ > and it is a subliminal message ;-) > > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 14, 2009

Re: [Pharo-project] Watery2

by Gary Chambers

Indeed, SoftSqueak seems to outperform StandardSqueak while looking nicer. Surprising really. A taxonomy of themes: StandardSqueak Variable colour Variable extents of morphs Mostly solid fills Standard borders SoftSqueak Variable colour Variable extent of morphs Mostly gradient fills Standard borders Vistary Variable colour (translucency) Variable extent of morphs Gradient fills with translucency Rounded borders (some performance impact) Watery Fixed colour Variable extent of morphs Gradient fills (mostly solid) Standard borders Watery2 Fixed colour Checkboxes/radios fixed size, fixed width scrollbars, general buttons now variable Gradient/form-based fills (mostly solid) Standard or no borders (fillstyle by forms) excepting focus morph. Regards, Gary. ----- Original Message ----- From: "Hilaire Fernandes" <hilaire(a)ofset.org> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, January 14, 2009 7:39 PM Subject: Re: [Pharo-project] Watery2 > Recently (well just yesterday), I found SoftSqueak theme to be very > effective: CPU effective, nice looking and suitable for narrow > scrollbar to gain a few pixel in the line width. > > Hilaire > > > 2009/1/14 Gary Chambers <gazzaguru2(a)btinternet.com>: >> The fonts are of your own choosing... the fonts used in eah theme are >> those >> specified in preferences. Watery uses plain labels, Vistary "fuzzy" ones >> (have an alpha redraw around then to help contrast). Vistary benefits >> from >> having a nice FreeType fonts (all themes do). The standard bitmapped ones >> can lead to illegibility dependent on font size. The fuzzy labels come at >> a >> performance cost, of course. 5 times the redraw for the label itself. I >> guess the colour/alpha of the edges could also be themed and (see later) >> user selectable at some point. >> >> As for colour scheme, Watery (and Watery2) take a consistent colour >> approach. Vistary, SoftSqueak and StandardSqueak use the window/model >> colours. Vistary, by virtue of increased use of translucency, will >> inevitable "tone-down" the rather brash standard Squeak colours for >> various >> windows. >> >> I feel we have a good spread of the potential available with the use of >> Polymorph. Of course nobody can be totally pleased any of the time... >> but, >> the potential is there. All feedback welcomed. Getting the more flexible >> fillstyles and borderstyles in has really helped with the possibilities >> for >> the look of morphs. >> >> For the moment some (theme based) settings are essentially hardcoded (you >> can change via inspectors, for instance, Watery's window colour). Once >> Settled I envisiage a Theme settings tool (won't take long, all that kind >> of >> thing has already been done for our ReportBuilder). >> >> I am slightly disappointed in the responses wrt sound themes... perhaps >> most >> people don't produced end-user applications! >> >> Thanks for the feedback. >> >> ----- Original Message ----- >> From: "Bill Schwab" <BSchwab(a)anest.ufl.edu> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Wednesday, January 14, 2009 7:07 PM >> Subject: Re: [Pharo-project] Watery2 >> >> >>> Gary, >>> >>> No argument here. I find Watery a little bright for my taste, but >>> suspect that will ease off when I set the background colors to my >>> preference. There are aspects of Vistary that I like, though at least >>> in the older versions that I have used more extensively, there is a >>> little bit of a performance hit, and the button text can be hard to >>> read. Given the choice between two non-ugly options, I will invariably >>> go for the snappy one over the eye candy. >>> >>> FWIW, I think one of the things I like most about Vistary is that the >>> notifiers and debuggers are easier to identify than they are in recent >>> Watery with OB. STV had really strong red notifiers, and I hated them. >>> The clay rose that eventually evolved in Squeak was nice because it drew >>> attention w/o being overpowering. I am _not_ saying we should regress - >>> I greatly appreciate what you have been doing. I will do something to >>> get my ledger green editors back, and might try a subtle toning of the >>> stack list in the debugger; I'd have to see it to know whether it is a >>> useful clue or something Steve Jobs would have erased from my disk :) >>> >>> Another plus on Vistary is that the title bar text ends up being easy to >>> read; Watery's title bar font seems a little thin to me. But, simply >>> thickening it might be too much?? >>> >>> Most of this is editorial background noise. You offer great options and >>> they will no doubt get better over time. Watery does appear to be >>> standing out as the leader right now. Whether that is because it is >>> truly more effective or simply because we have a lot of mac users giving >>> attention to it is largely irrelevant. >>> >>> Thanks for the making choice so difficult!!!! >>> >>> Bill >>> >>> >>> >>> >>> Wilhelm K. Schwab, Ph.D. >>> University of Florida >>> Department of Anesthesiology >>> PO Box 100254 >>> Gainesville, FL 32610-0254 >>> >>> Email: bschwab(a)anest.ufl.edu >>> Tel: (352) 273-6785 >>> FAX: (352) 392-7029 >>> >>>>>> gazzaguru2(a)btinternet.com 01/14/09 1:18 PM >>> >>> Guess Watery2 will be the Pharo look-and-feel... not had any >>> correspondence >>> from Samuel for some time now... >>> >>> So, I'm focussing on Watery2 for the moment. The SVGs and exports do >>> take >>> some time. Square button corners next then the window controls >>> (experimented >>> with Vistary as proof-of-concept). >>> >>> Regards, Gary. >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 14, 2009