- Pharo-dev - lists.pharo.org

[Pharo-project] How do we manage todos?
by StÃ©phane Ducasse Sept. 29, 2008

Sept. 29, 2008

I would prefer a bugtraker with a tag todo that are not bug fixes. Stef

4 4

Re: [Pharo-project] OB's icon support improved
by Bill Schwab Sept. 29, 2008

Sept. 29, 2008

I apologize for not paying more attention to this thread. Visual feedback in the browser is very much appreciated, and you seem to be doing a very nice job! Had I been paying attention, I'd have said things like the following: (1) Red is probably not the best choice to have lurking on the screen. Maroon/purple/clay rose or just about any "muted" or muddy red IMHO is a much better choice for most things. It might help to add a small amount of blue to the greens too for the same reason. I recommend trying for the psychological benefit with as little eye strain potential as possible. (2) For collections, consider something like a circle drawn a few times from right to left to give an overlapping effect, maybe ... thrown in there if there is room. (3) For exceptions, I like the icon, but two concerns: it might be a little faint/bland; it might work better if its implied movement were upward. Dolphin 5 uses an explosion icon in some situations. That might work well for exceptions and errors. (4) Do we have any color blind people among us? IIRC, something around 12-14% of the population is affected to some degree, so we will encounter it. The test icons will be lost on some of the more extreme red/green sufferers. An alternative would be a boxed check, X or ?. The box (or other border shape) being the suggestion of the test, and the symbol indicating the state. It is fine to add color too, but we should give the red/green crowd a way to see what is going on. Not meaning to jab anyone in the eye, the Installer script is just the kind of thing I'd hope to be able to exchange in situations like this. I do not care so much that it is Installer that we use, but _something_ that can cope with the various publication methods and cope with the details is much needed. 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

4 3

[Pharo-project] About Network-YM.44.mcz
by Yann Monclair Sept. 29, 2008

Sept. 29, 2008

Hi list, I figured I'd explain my commit here, since I don't know how you handle your issue tracker. While I was loading some code in my image (Universes iirc), I got a lot of warnings pop up, about Url>>#toText being deprecated. After taking a look at it, I saw that the deprecation comment recommended using instead Url>>#asText. Which I tried, but it broke most of the SUnits and also the expected behaviour. Looking at the code, I saw that Url>>#toText simply did ^self asString, when Url>>#asText does ^self asString asText. The semantic leap between Text and String is too big (imo) to force that change on users. I thought it would be better to replace the deprecation comment to recommend replacing the obsolote Url>>#toText by Url>>#asString (which is what this method actually does). I would rather have removed the method, since it has been marked for obsolete for more than 3 years now! But I don't know what the approach is to deleting methods, and how to communicate to people that this isn't a missing method but an intentional removal. I hope this helps understand this version. Cheers, Yann

3 4

[Pharo-project] Update 10082
by Norbert Hartl Sept. 28, 2008

Sept. 28, 2008

In 10082 the script is buggy. script174 contains a line with only .mcz and one line with an archive Pinesoft-Removals-EToys-stephane.ducasse.1.mcz that is not in the repository. Norbert

2 5

[Pharo-project] who is YM
by StÃ©phane Ducasse Sept. 28, 2008

Sept. 28, 2008

because there is a package Network YM 44 Please please avoid to use initials. Stef

3 3

[Pharo-project] [ANN] 10082 More etoy cleaning
by StÃ©phane Ducasse Sept. 28, 2008

Sept. 28, 2008

Hi all I'm slowing going over gary's fixes and cleaning etoy. Etoy cleaning from gary (continued) Removed UndefinedObjectTest>>testNewTileMorphRepresentative Removed BooleanTest>>testNewTileMorphRepresentative Removed BookMorph>>chooseAndRevertToVersion Removed BookMorph>>revertToCheckpoint: secsSince1901 BookMorph>>installRollBackButtons BookMorph>>methodHolderVersions BookMorph>>methodHolders BookMoprh>>goToPageMorph: transitionSpec: runTransitionScripts: BookMorph>>goToPageMorph: transitionSpec: TabbedPalette>>selectTab: cleaned Removed TabbedPalette>>becomeStandPalette Removed>>currentPlayerDo: and fixed sender EncodedCharSet fixed initialize stef

1 0

[Pharo-project] what about squeakPage
by StÃ©phane Ducasse Sept. 28, 2008

Sept. 28, 2008

Hi guys I was browsing some etoy cleans of gary and I found somewhere sqPage and SqueakPage. Apparently we can save on disc a bookmorph. Any ideas if this is working/useful/fun? Stef

2 2

Re: [Pharo-project] Fwd: [Seaside-dev] preliminary Seaside2.9alphauniverse
by Bill Schwab Sept. 28, 2008

Sept. 28, 2008

Damien, Sounds good. 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 >>> damien.cassou(a)gmail.com 09/28/08 9:16 AM >>> On Sun, Sep 28, 2008 at 3:07 PM, Bill Schwab <BSchwab(a)anest.ufl.edu> wrote: > Damien, > > Now I'm confused :) If installing Seaside is easy, then the web image > is not all that necessary, agreed. With PolyMorph in Pharo, every image > gets better. No worries so far. > > You said "we want one image for Pharo." That is probably a good goal. > Will the RB go into Pharo, or will you continue to produce the developer > images? Yes, RB will be part of the official Pharo release and I won't generate specific pharo-dev images anymore. The list of packages in Pharo is maintained at: http://code.google.com/p/pharo/wiki/Packages -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

1 0

Re: [Pharo-project] Fwd: [Seaside-dev] preliminary Seaside 2.9alphauniverse
by Bill Schwab Sept. 28, 2008

Sept. 28, 2008

Damien, Now I'm confused :) If installing Seaside is easy, then the web image is not all that necessary, agreed. With PolyMorph in Pharo, every image gets better. No worries so far. You said "we want one image for Pharo." That is probably a good goal. Will the RB go into Pharo, or will you continue to produce the developer images? 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 >>> damien.cassou(a)gmail.com 09/28/08 5:38 AM >>> Hi Bill, I'm not sure I understand your email completly. Please tell me if it is not the case. On Sat, Sep 27, 2008 at 5:44 PM, Bill Schwab <BSchwab(a)anest.ufl.edu> wrote: > Damien, I suspect you put a lot of work into preparing your images, so please do not view this as anything other than gratitude driving some suggestions. With proper selection of browser and (sorry<g>) deactivating eCompletion, I very much enjoy your web image as a starting point. Whether I continue using it will depend on how hard it is to install Polymorph and the RB vs. Seaside and friends. Polymorph is going to be included in all Pharo images so you don't have to worry. RB as been in all my images from the beginning and will continue to be. I think I will stop generating web images for Pharo because we want only one image for Pharo. I will try to find a way to make installing Seaside easy. > Call me demanding, I want it all :) Installer can probably (either now or with some refinement) reduce Polymorph (which appears to be on its way into the Pharo base anyway???) and Seaside to one-liners in a script. Ditto cryptography. Add some lines to load .cs or whatever files I create on my own, and I should be able to download an image, and then run one script that builds the new image. > > I will stop short of asking you to manually keep up with the small releases, as I probably would end up waiting for the October release before building a new image. It would however be great to either reduce what you do to a simple script, or have it aggressively track updates once Pharo is officially released. I'm sorry but I do not understand this paragraph. > >From a gradually decreasing distance at least, Installer looks like it is trying to fill a gap. As always, I would like to see Pharo sprout an ability to apply multiple categories per method; Dolphin has done that from (almost?) the beginning, and it is quite addictive. My point being that however clever, systems that take the one available category to package methods make the restriction all the more obvious. > > I hope that makes some sense. Thanks to all for what is shaping up to be a nice system! > > Bill > > >

2 1

Re: [Pharo-project] Fwd: [Seaside-dev] preliminary Seaside 2.9 alphauniverse
by Bill Schwab Sept. 28, 2008

Sept. 28, 2008

Damien, Stef, I _think_ what I would want for a starting point is something like Damien's web image, followed by a script that gets the latest of a few things, specific versions of others, and then loads a bunch of .cs or other files for my code. Damien, I suspect you put a lot of work into preparing your images, so please do not view this as anything other than gratitude driving some suggestions. With proper selection of browser and (sorry<g>) deactivating eCompletion, I very much enjoy your web image as a starting point. Whether I continue using it will depend on how hard it is to install Polymorph and the RB vs. Seaside and friends. Call me demanding, I want it all :) Installer can probably (either now or with some refinement) reduce Polymorph (which appears to be on its way into the Pharo base anyway???) and Seaside to one-liners in a script. Ditto cryptography. Add some lines to load .cs or whatever files I create on my own, and I should be able to download an image, and then run one script that builds the new image. I will stop short of asking you to manually keep up with the small releases, as I probably would end up waiting for the October release before building a new image. It would however be great to either reduce what you do to a simple script, or have it aggressively track updates once Pharo is officially released. >From a gradually decreasing distance at least, Installer looks like it is trying to fill a gap. As always, I would like to see Pharo sprout an ability to apply multiple categories per method; Dolphin has done that from (almost?) the beginning, and it is quite addictive. My point being that however clever, systems that take the one available category to package methods make the restriction all the more obvious. I hope that makes some sense. Thanks to all for what is shaping up to be a nice system! 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 >>> damien.cassou(a)gmail.com 09/26/08 11:03 AM >>> On Fri, Sep 26, 2008 at 8:26 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > - For example I would like to have a real look at MC1.6 but the > message around it is blurry MC1.6 is not the topic here. > I tried LFP and it broke on me. It worked fine for me. You may want to try again and send bug report to Keith who answered all my emails. > - I like installer but when I look at the code I would like to refactor it. The code may not be perfect but it works fine. I don't think Keith would ignore our enhancements to his code. > - There is no document in a nice format that explain why and how (i'm > fixing that for installer and I was waiting because I will refactor it else I do not publish the chapter but I did not want to insult keith since this is not the point since I like installer). This is not fair. There is "no document in a nice format that explains" most of the tools you use everyday. But you still use them. The more people use a tool, the best chance you have to get documentation. Moreover, Keith and Matthew wrote a lot of things in pbwiki, squeak wiki and mailing lists. > - unknown is strange :) Should not be for us Squeakers and Pharoers. > - So if you want to help me I would love to have a > - Installer code refactored > - Installer chapter > - Sake (have a look at the code) > - Sake Chapter for the book I would love that too -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

3 3