- Pharo-dev - lists.pharo.org

[Pharo-project] Pharo name conflict
by David Hammond Jan. 15, 2009

Jan. 15, 2009

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.

6 9

[Pharo-project] That's a pharo!
by Hilaire Fernandes Jan. 14, 2009

Jan. 14, 2009

It is where I am working http://crdp.ac-bordeaux.fr/cddp40/ and it is a subliminal message ;-) -- http://blog.ofset.org/hilaire

2 1

Re: [Pharo-project] Watery2
by Bill Schwab Jan. 14, 2009

Jan. 14, 2009

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

3 3

[Pharo-project] Watery2
by Gary Chambers Jan. 14, 2009

Jan. 14, 2009

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.

2 1

Re: [Pharo-project] [ANN][Dev-Images] January 2000 versions
by Bill Schwab Jan. 14, 2009

Jan. 14, 2009

Gary, I saw mention of it, but I took "full screen" too literally. Thanks! 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 8:02 AM >>> ----- Original Message ----- From: "Bill Schwab" <BSchwab(a)anest.ufl.edu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, January 14, 2009 12:05 AM Subject: Re: [Pharo-project] [ANN][Dev-Images] January 2000 versions > Damien, all, > > Very impressive! I am looking forward to the new parser and a few > other things, but the results are speaking for themselves. One cosmetic > detail is that OB and Vistary (and even SoftSqueak) are not nearly as > happy as OB and Watery 2. I notice it most in the buttons, especially > those "in" the source pane. > > Gary, thinking ahead some (ok, a LOT), to deployed desktop apps, have > you given any thought to how one would create an alignment morph (or > whatever you recommend) maximized in the world to allow the non-client > parts of the host window to take over as the title bar and friends? Or, > are you expecting us to move to a way to allow individual host windows? > At some point, I would want to create what amounts to an SDI app. > Currently, the feel is essentially MDI. There is a FullscreenMorph in Polymorph-Widgets that we use. StandardWindow and subclasses support openFullscreen along with a few other bits to help out in deployed applications (see class comment). To change the host-windows title you will need to change your Squeak.ini (trickier in Linux...). Preferences class>>disableProgrammerFacilitiesWithoutWarning may also be of some help for deployed applications ;-) Regards, Gary. > > 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 > > > _______________________________________________ > 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

1 0

Re: [Pharo-project] [ANN][Dev-Images] January 2000 versions
by Bill Schwab Jan. 14, 2009

Jan. 14, 2009

Damien, all, Very impressive! I am looking forward to the new parser and a few other things, but the results are speaking for themselves. One cosmetic detail is that OB and Vistary (and even SoftSqueak) are not nearly as happy as OB and Watery 2. I notice it most in the buttons, especially those "in" the source pane. Gary, thinking ahead some (ok, a LOT), to deployed desktop apps, have you given any thought to how one would create an alignment morph (or whatever you recommend) maximized in the world to allow the non-client parts of the host window to take over as the title bar and friends? Or, are you expecting us to move to a way to allow individual host windows? At some point, I would want to create what amounts to an SDI app. Currently, the feel is essentially MDI. 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

2 1

[Pharo-project] [OT] Great job guys
by Torsten Bergmann Jan. 14, 2009

Jan. 14, 2009

see http://mue.tideland.biz/2009/01/great-job-guys.html -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

8 19

[Pharo-project] funy OB debugger
by Hilaire Fernandes Jan. 14, 2009

Jan. 14, 2009

In last pharo core, updated, and installation of the pharo dev package. the debugger always point to the next line in the stack, not the current one. Hilaire -- http://blog.ofset.org/hilaire

2 4

[Pharo-project] Ecompletion in SuperOB
by Rob Rothwell Jan. 14, 2009

Jan. 14, 2009

Hello, If I start from a core 10201, and apply updates to 10205, then do: ScriptLoader loadSuperOB, and then ScriptLoader loadEcompletion, Ecompletion works fine in a Workspace, but in an OB Code Pane reproducibly results in the stack trace below. Just wanted to let you know in case it has something to do with all the Morphic clean-up you are doing. Take care, Rob MessageNotUnderstood: TransformationMorph>>x:y: Proceed Abandon Debug Create TransformationMorph(Object)>>doesNotUnderstand: #x:y: ECMenuMorph>>createTitle ECMenuMorph>>setController:position: ECMenuMorph class>>controller:position: ECController>>openMenuFor: ECController>>handleKeystrokeBefore:editor: OBTextMorphWithShout(OBTextMorph)>>keyStroke: OBTextMorphWithShout(TextMorph)>>handleKeystroke: KeyboardEvent>>sentTo: OBTextMorphWithShout(Morph)>>handleEvent: OBTextMorphWithShout(Morph)>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. ActiveEvent := anEvent. result := focusHolder han...]} [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} BlockContext>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendKeyboardEvent: HandMorph>>handleEvent: HandMorph>>processEvents TransformationMorph(Object)>>doesNotUnderstand: #x:y: ECMenuMorph>>createTitle ECMenuMorph>>setController:position: ECMenuMorph class>>controller:position: ECController>>openMenuFor: ECController>>handleKeystrokeBefore:editor: OBTextMorphWithShout(OBTextMorph)>>keyStroke: OBTextMorphWithShout(TextMorph)>>handleKeystroke: KeyboardEvent>>sentTo: OBTextMorphWithShout(Morph)>>handleEvent: OBTextMorphWithShout(Morph)>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. ActiveEvent := anEvent. result := focusHolder han...]} [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} BlockContext>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendKeyboardEvent: HandMorph>>handleEvent: HandMorph>>processEvents

3 2

Jan. 13, 2009

- New Diff tools - More collection tests - Collections categories as packages (level one) Next - category as packages collections level two - mike network refactoring (I hope it loads). - bugs, watchit and others etoy removal

4 9