- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Improving the GUI

by Norbert Hartl

+1 Very good point. I agree on all of them. Is it possible to choose any ttf font and make a NiceFont out of it? I don't know the real name but the package on universe is called this way. Or do you think we should make the trutetype plugin mandatory? Norbert On Sun, 2008-07-20 at 11:22 +0200, Adrian Lienhard wrote: > Hi, > > I'd like to get your opinion about how we could improve the GUI. I > believe that even a few small changes will make a significant > difference, especially for new people that come to Pharo. Just the > cleaned up world menu is such a relief... > > Here a three suggestions: > > Better fonts > ---------------- > I think the current code font is not a good one and it is too small > (for today's screen resolutions). I like for example the font used in > TextMate, which is Monaco 12, a monotype font. The page http://www.lowing.org/fonts/ > gives some samples for good code fonts. I've tried out the other > fonts in the Pharo image like the BitstreamVeraSansMono but they are > all very blurry. Just not good enough. I'm not a font expert, so I > don't know what the options for a better font are. > > Better menus > ------------------------------- > Current problems: > - bad organization menus only work when you have learned where > something is located > - duplicated entries e.g., Appearance is both in the top level world > menu and in the submenu Help > - useless entries e.g., set font, set style etc. in the context menu > are useless since code is never styled > - defective entries: e.g., "Make project link" in the context menu > does not work > > Larger windows > ------------------------------- > The default size of windows is usually too small. Often, after opening > a window I have to resize it. For example the hierarchy browser shows > only the 5 first classes. > > > Any other ideas what could be improved in the short term? I'm looking > for stuff that we can do now without having to rewrite the whole > system... > > Cheers, > Adrian > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2008

[Pharo-project] Improving the GUI

by Adrian Lienhard

Hi, I'd like to get your opinion about how we could improve the GUI. I believe that even a few small changes will make a significant difference, especially for new people that come to Pharo. Just the cleaned up world menu is such a relief... Here a three suggestions: Better fonts ---------------- I think the current code font is not a good one and it is too small (for today's screen resolutions). I like for example the font used in TextMate, which is Monaco 12, a monotype font. The page http://www.lowing.org/fonts/ gives some samples for good code fonts. I've tried out the other fonts in the Pharo image like the BitstreamVeraSansMono but they are all very blurry. Just not good enough. I'm not a font expert, so I don't know what the options for a better font are. Better menus ------------------------------- Current problems: - bad organization menus only work when you have learned where something is located - duplicated entries e.g., Appearance is both in the top level world menu and in the submenu Help - useless entries e.g., set font, set style etc. in the context menu are useless since code is never styled - defective entries: e.g., "Make project link" in the context menu does not work Larger windows ------------------------------- The default size of windows is usually too small. Often, after opening a window I have to resize it. For example the hierarchy browser shows only the 5 first classes. Any other ideas what could be improved in the short term? I'm looking for stuff that we can do now without having to rewrite the whole system... Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

July 20, 2008

Re: [Pharo-project] Pango support

by Michael Rueger

Serge Stinckwich wrote: > There is a Pango support in recent OLPC Squeak VM : > http://lists.laptop.org/pipermail/etoys/2008-June/002433.html > Pango is a rendering text with a strong emphasis on internationalization : > http://www.pango.org/ScriptGallery > > Maybe something to add in future Pharo releases ... Maybe, but it is really monkey patched into Morphic. Imagine the current ParagraphEditor and someone making it ten times worse. Not Yoshiki's fault, he just had to make it work with what's there. An amazing feat actually that he managed to get it to work. Michael

July 19, 2008

[Pharo-project] Pango support

by Serge Stinckwich

There is a Pango support in recent OLPC Squeak VM : http://lists.laptop.org/pipermail/etoys/2008-June/002433.html Pango is a rendering text with a strong emphasis on internationalization : http://www.pango.org/ScriptGallery Maybe something to add in future Pharo releases ... -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

July 19, 2008

Re: [Pharo-project] about ensuring file closing

by Bill Schwab

Stef, The streams are a mess, and the more I work with them, the more I understand the desire to replace them with Nile. For now, I am simply inserting some methods that behave well (work when they should, raise errors when they should) to allow me to begin doing some real work. My view is that I can always add helper classes and methods as needed. Whether that gets around fragile design (#nextOne) or is a one-place fix for the myriad times I open a file, it can always be rewritten to work with whatever we create. URIs make sense. I have never been happy with the ways I split and combine paths, so those things will have to be rewritten, especially since they are Windows-specific. 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) 846-1285 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 07/19/08 5:49 AM >>> On Jul 18, 2008, at 5:01 PM, Bill Schwab wrote: > Stef, > > I do not doubt that the image is littered with such problems. On > several occasions, I lost 10-15 minutes tracking down errors that > resulted from unopened files. It is all a continuation of my streams > "rant" (a well-intentioned one, of course). > > Meaning no disrespect to the milestones (in particular, streams being > slated for the future), I have undertaken an effort similar to what > you > propose: putting an end to silent failures and lack of protection. > As a > streams addict, I need stable semantics, and have thus embarked on my > #nextOne, #nextMany:, etc. solution to reaching that goal. It also > became clear that FileStream was quite unfriendly, so I started adding > Dolphin-compatible methods, at least to a point. My primary goal is > to > have errors arise when appropriate vs. waiting for > potentially/apparently disconnected collateral damage to occur. I have the impression that FileStream should be patched but also just rewritten from scratch. I was discussing with mike about the use of URI in sophie. He told me that they got a really nice solution which was offering cross platform real portability > > Dolphin's semantics will not be completely appropriate for Squeak, > because there are OS (in)dependencies to consider. I want that to > work > well so I can treat my Redmond allergy. > > I urge Smalltalkers to avoid #next and #next: like the plague, but one > could always use my changes and ignore the replacements. A very > incomplete but gradually evolving change set is available on request. ok good to know. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 19, 2008

[Pharo-project] [ANN] New release is out 10050

by StÃ©phane Ducasse

Hello Pharoers [ANN] New release is out 10050 update10047 Fixing the release. Adrian made a few cosmetic changes and tagged testUnimplementedNonPrimitiveCalls as expected failure Original description: - added allClassesWithUnimplementedCalls to SystemNavigation to return structured classes with unimplemented calls - added convenience method PackageOrganizer>>allPackagesContainingUnimplementedCalls - adjusted ReleaseTest>>testUnimplemented... to exclude TestCase classes ------------------------------------------------------ update10048 Fix the Scriptloader logStream + Collection tests http://bugs.squeak.org/view.php?id=6355 + Pharo Flaps ------------------------------------------------------ update10049 7073 CollectionAndCollectionTest * [http://bugs.squeak.org/view.php?id=6367 M6367] * seems good [http://bugs.squeak.org/view.php?id=5700 M5700] Add 2 tests for RunArray class + at:put: See : http://bugs.squeak.org/view.php?id=6070 ------------------------------------------------------ update10050 This update includes a set of Mantis fixes (that also went into Squeak 3.10): http://code.google.com/p/pharo/issues/detail?id=27 http://code.google.com/p/pharo/issues/detail?id=31 http://code.google.com/p/pharo/issues/detail?id=32 http://code.google.com/p/pharo/issues/detail?id=30 mark testUnwindDebuggerWithStep as expected failure

July 19, 2008

Re: [Pharo-project] Enough changes to release?

by StÃ©phane Ducasse

Ok I making a release now. Stef On Jul 18, 2008, at 9:54 AM, Damien Cassou wrote: > Hi, > > I don't know when you decide to release Pharo versions, but it might > be interesting to do that now. The previous version is 2 week old and > the changes take a long time to load. > > Bye > > -- > 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) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 19, 2008

Re: [Pharo-project] About HTMLFileStream

by StÃ©phane Ducasse

coool :) Stef On Jul 19, 2008, at 11:29 AM, Adrian Lienhard wrote: > Hi Stef, > > Its already done ;) > > I suggested to remove the whole HTML generation when looking at the > not working html menu implementation you pointed out. Damien then > did it; he removed around 50 methods, including the class > HtmlFileStream. His changes still need to be verified. > > See: http://code.google.com/p/pharo/issues/detail?id=115 > Code is: SLICE-remove-copyHtml-dc.5 > > Adrian > > > On Jul 18, 2008, at 14:24 , StÃ©phane Ducasse wrote: > >> Hello >> >> I was browsing and browsing code and I found HTMLFileStream >> Apparently positionableStream introduces command: just for this >> class. >> >> I have the impression that if we want a good htmlwriter we could >> extract it >> from seaside. But HTMLFileStream looks outdated. >> So I would propose to remove it. >> >> Any thoughts on that one? >> >> 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 >

July 19, 2008

Re: [Pharo-project] about ensuring file closing

by StÃ©phane Ducasse

On Jul 18, 2008, at 5:01 PM, Bill Schwab wrote: > Stef, > > I do not doubt that the image is littered with such problems. On > several occasions, I lost 10-15 minutes tracking down errors that > resulted from unopened files. It is all a continuation of my streams > "rant" (a well-intentioned one, of course). > > Meaning no disrespect to the milestones (in particular, streams being > slated for the future), I have undertaken an effort similar to what > you > propose: putting an end to silent failures and lack of protection. > As a > streams addict, I need stable semantics, and have thus embarked on my > #nextOne, #nextMany:, etc. solution to reaching that goal. It also > became clear that FileStream was quite unfriendly, so I started adding > Dolphin-compatible methods, at least to a point. My primary goal is > to > have errors arise when appropriate vs. waiting for > potentially/apparently disconnected collateral damage to occur. I have the impression that FileStream should be patched but also just rewritten from scratch. I was discussing with mike about the use of URI in sophie. He told me that they got a really nice solution which was offering cross platform real portability > > Dolphin's semantics will not be completely appropriate for Squeak, > because there are OS (in)dependencies to consider. I want that to > work > well so I can treat my Redmond allergy. > > I urge Smalltalkers to avoid #next and #next: like the plague, but one > could always use my changes and ignore the replacements. A very > incomplete but gradually evolving change set is available on request. ok good to know.

July 19, 2008

Re: [Pharo-project] A board for pharo

by StÃ©phane Ducasse

Thanks damien >> TODO: Pharo duplicated code in importAllIconNamed: and friends > > Issue #120 > >> TODO: may be include as ressources the pngSuite - see >> testPngSuite Yes it was critic. In the PNG writer tests you have to download the file and put them in your directory else the tests just run but test nothing. >> >> TODO: remove from UndefinedObject from3DS: aDictionary >> ^aDictionary > > > Patch sent to PharoInbox. Issue #121. Needs a review. > > >> TODO: BMPReadWriter>>nextPutImage: aForm as a stream close as >> the >> last messages >> while all the other methods do not and should be protected by an >> ensure: > > Issue #122 Thanks. Still no connection no phone...... stef

July 19, 2008