- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50010 Home: https://github.com/pharo-project/pharo-core

April 24, 2015

[pharo-project/pharo-core] ea77a4: 50010

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ea77a439473114886c6b38b907dd2425fc89e8db https://github.com/pharo-project/pharo-core/commit/ea77a439473114886c6b38b9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-24 (Fri, 24 Apr 2015) Changed paths: M Collections-Sequenceable.package/OrderedDictionary.class/instance/accessing/associationAt_ifPresent_.st M Collections-Sequenceable.package/OrderedDictionary.class/instance/accessing/at_put_.st A Collections-Sequenceable.package/OrderedDictionary.class/instance/accessing/identityIndexOfKey_.st M Collections-Sequenceable.package/OrderedDictionary.class/instance/adding/add_.st R Collections-Sequenceable.package/OrderedDictionary.class/instance/private/deleteOrderedKey_.st M Collections-Sequenceable.package/OrderedDictionary.class/instance/private/errorInvalidIndex_.st A Collections-Sequenceable.package/OrderedDictionary.class/instance/private/orderedKeysIndexOf_.st A Collections-Sequenceable.package/OrderedDictionary.class/instance/private/orderedKeysRemove_.st M Collections-Sequenceable.package/OrderedDictionary.class/instance/removing/removeKey_.st M Collections-Sequenceable.package/OrderedDictionary.class/instance/removing/removeKey_ifAbsent_.st A Collections-Sequenceable.package/OrderedIdentityDictionary.class/instance/private/orderedKeysIndexOf_.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/accessing/absentKey.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/accessing/defaultCapacity.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/accessing/dictionaryAssociations.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/accessing/emptyInternalDictionary.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/accessing/internalDictionaryClass.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/accessing/internalDictionaryWithSingleAssociation.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/accessing/nonIdentityAbsentKey.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/accessing/nonIdentityDictionaryAssociations.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/assertions/assertRemovedKey_from_.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/assertions/assertSelector_collects_from_.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/testing/isTestingIdentityDictionary.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testDictionary.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testEqualsDictionary.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testHash.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testIdentityIndexOfKey.st A CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testIdentityIndexOfKeyIfAbsent.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testIndexOfKeyIfAbsent.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testKeyAtIdentityValue.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testKeyAtIdentityValueIfAbsent.st M CollectionsTests.package/OrderedDictionaryTest.class/instance/tests/testRemoveKey.st R CollectionsTests.package/OrderedIdentityDictionaryTest.class/instance/accessing/absentKey.st R CollectionsTests.package/OrderedIdentityDictionaryTest.class/instance/accessing/dictionaryAssociations.st R CollectionsTests.package/OrderedIdentityDictionaryTest.class/instance/accessing/internalDictionaryClass.st A CollectionsTests.package/OrderedIdentityDictionaryTest.class/instance/testing/isTestingIdentityDictionary.st A Morphic-Core.package/Morph.class/instance/converting/asText.st A MorphicTests.package/TextAnchorTest.class/instance/running/testMorphInline.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script618.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script619.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50009.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50010.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50010 12595 Add Morph>>#asText https://pharo.fogbugz.com/f/cases/12595 15338 OrderedDictionary changes to merge https://pharo.fogbugz.com/f/cases/15338 http://files.pharo.org/image/50/50010.zip

April 24, 2015

Re: [Pharo-dev] TDD and BDD

by Christophe Demarey

Le 22 avr. 2015 Ã 20:19, stepharo a Ã©crit : > Christophe > > I do not have the answer just the constraints. > This is hyper important that the solution does not change much SUnit. > This way we do not end up with a mess with Sunit version. > > It is better to have a separate package. I ckecked and we already diverged a lot from the SUnit standard (use of Traits, announcements, etc.). Do you want I integrate the refactoring to have the test selectors selection coherent? If yes, my proposal just adds 'or: [ selector name beginsWith: 'should' ]. I do not see the point of having a separate package. If no, does it mean that we should never touch the SUnit package?

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by kilon alios

The No1 thing that bothered me with Pharo was its white theme, found it both horrible (yes much worse than Squeak) and very tiresome for my eyes. Even worse was the white theme of Moose which made it impossible or really hard to see scrollbars , for me, so it was also a problem of contrast not just color. Moving to Dark theme , fundamentally changed my experience with Pharo and made coding much more relaxing. Then I decided to go one step further and implement my own theme, a dark blue theme and add to it a gui tool to allow for full customisation of colors (the theme with the tool are available from configuration Browsers with the name Nireas). Blue is my favorite color afterall, reminds me of sea, relaxing and full of positive energy. In the end it comes down to what you like and what you find more enjoyable to work with. For me it played a small role that the Dark theme is a new thing with its own set of problem since the change of colors had such a profound effect on my experience with Pharo. I cannot imagine myself going back to the default theme, ever. I would love to see more themes in the future, pink, yellow, brown, green and much more. On Fri, Apr 24, 2015 at 11:52 AM Stephan Eggermont <stephan(a)stack.nl> wrote: > On 24/04/15 01:48, Sean P. DeNigris wrote: > > Why didn't/don't we make it the default for 4.0? Everyone seems to love > it, > > and people are commenting that the UI looks dated. > > The advantages of a dark theme: > - works well for photo/video apps where you don't want extra (colored) > light; > - works well in a dark environment; > - provides little blue light, so doesn't influence sleep; > - works for certain eye problems; > don't apply to me much. > I find reducing eye stress for me is mostly a question > of adding more ambient light (also works well for my mood). > In a light environment a light theme works much better. > > Stephan > > > >

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by Marcus Denker

> > The short term real life goals are: > > - unify keyboard shortcuts. > - improve event handling so that the use of a magic mouse does not produce dozens of events that make the UI go crazy > Yes! Marcus

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by Norbert Hartl

> Am 24.04.2015 um 08:38 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > I disagreeâ¦ DarkTheme is just for certain tastes, while regular one, while probably dated, is more âstandardâ. > Also, DarkTheme is not ready. yeah, yeahâ¦ it works and works fine most of the timeâ¦ but not *all* the time (take for example find string dialogâ¦ I never found the time to fix it, and nobody complained soâ¦ :P). Finally. we need to adopt SVG icons (in my TODO list since a couple of months, I will deliver soon, I hope), otherwise they do not look good (this is a problem eclipse itself had itâ¦ we are just inheriting it :) ) > > But a good question would be: How can we push forward our UI, besides using a darker or clearer theme? > I would like to hear some opinions here :) > I like the way pharo4 took towards finding and navigating. With spotter it is easy to find an entry point to the image graph. With the gt inspector you can navigate the graph then. Bringing those tools closer together could make it even better. Now we have find and navigate we could also have some help in creating things which is prerequisite to finding and navigating. My dream would be that e.g. when you find a class spotter has an action with shortcut to create an instance of that class. The inspector has a tab with an editor that lets you enter values (or better ways to do it). Those could be created by an object meta description. This could be something like magritte. But I hope we manage to build a better magritte based on slots. The short term real life goals are: - unify keyboard shortcuts. - improve event handling so that the use of a magic mouse does not produce dozens of events that make the UI go crazy Norbert > > >> On 24 Apr 2015, at 08:33, stepharo <stepharo(a)free.fr> wrote: >> >> comments about color is to be taken with care. >> >> >> Le 24/4/15 02:48, Sean P. DeNigris a Ã©crit : >>> Why didn't/don't we make it the default for 4.0? Everyone seems to love it, >>> and people are commenting that the UI looks dated. >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/Release-with-Dark-Theme-tp4821496.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >>> >> >> > >

April 24, 2015

Re: [Pharo-dev] Small ScreenTheme [was: Release with Dark Theme]

by Stephan Eggermont

On 24/04/15 10:19, Nicolas Anquetil wrote: > In a related domain, I am launching a petition for a SmallScreenTheme and a large screen one too. 24 or 40" UHD has lots of empty space, and default browser sizes are too small The first thing to do is to make sure we don't create more legacy code with hardcoded sizes for fonts, borders, margins, padding. Stephan

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by Stephan Eggermont

On 24/04/15 01:48, Sean P. DeNigris wrote: > Why didn't/don't we make it the default for 4.0? Everyone seems to love it, > and people are commenting that the UI looks dated. The advantages of a dark theme: - works well for photo/video apps where you don't want extra (colored) light; - works well in a dark environment; - provides little blue light, so doesn't influence sleep; - works for certain eye problems; don't apply to me much. I find reducing eye stress for me is mostly a question of adding more ambient light (also works well for my mood). In a light environment a light theme works much better. Stephan

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by Thierry Goubier

Le 24/04/2015 10:11, phil(a)highoctane.be a Ã©crit : > > > On Fri, Apr 24, 2015 at 8:38 AM, Esteban Lorenzano <estebanlm(a)gmail.com > <mailto:estebanlm@gmail.com>> wrote: > > I disagreeâ¦ DarkTheme is just for certain tastes, while regular one, > while probably dated, is more âstandardâ. > Also, DarkTheme is not ready. yeah, yeahâ¦ it works and works fine > most of the timeâ¦ but not *all* the time (take for example find > string dialogâ¦ I never found the time to fix it, and nobody > complained soâ¦ :P). Finally. we need to adopt SVG icons (in my TODO > list since a couple of months, I will deliver soon, I hope), > otherwise they do not look good (this is a problem eclipse itself > had itâ¦ we are just inheriting it :) ) > > But a good question would be: How can we push forward our UI, > besides using a darker or clearer theme? > I would like to hear some opinions here :) > > > > I'd like to have some solution for that "windows popping up everywhere" > thing. AltBrowser has some good ideas. > > In fact I'd like to have AltBrowser and Nautilus together (as in > additional entries in the "Browse", "Browse Scoped", ..."Alt Browse", > "Alt Browse Scoped") > > Also, having a way to see a class with all the methods in a long pane. > Yeah, Smalltalk is all about short methods but it is hard to explain > things to people when looking at a ravioli at a time. Like the Newspeak browser? > Navigating hierarchies should be made easier (switching on the > "hier/flat" button gets tiring). This one is difficult to solve. > I need to see how spotter will make this easier anyway. Still not using > it, need to bring all my code to 4.0 before. I'm a bit: Spotter is an external tool to the browser. If my searches are well answered in the browser, I'll prefer to avoid switching back and forth between two GUIs. It would be nice to have a closer integration between Browser and Spotter. When looking at methods, Spotter and AltBrowser show a very similar GUI: context tree on the left (i.e. where is the element in the overall scheme), element/work pane on the right. Like all the tree-based browsers have done in the past, really (the Star browser, the Whisker browser). Which makes Spotter a kind of reimplementation of a tree browser with object-driven representations on the right... was that a project by Alain Plantec in the Squeak days? Thierry > Phil > >

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by Norbert Hartl

> Am 24.04.2015 um 09:45 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > That's a bit harsh, the fonts are the same ;-) No, they weren't. I had my font setup and after applying the dark theme the fonts were changed. > And it is of course possible that you don't like it, it is a matter of taste. > The contrast thing is also taste, but for some people it solve certain vision problems. > Sure, that's why I said "I don't like it". I used dark themes in the last decades. But the setup I had it was hard to orientate my eyes. Area borders were not contrasting to the rest. Having multiple windows overlap makes it really hard to distinguish. So, if this is the cure for anybody then it's good :) Norbert >> On 24 Apr 2015, at 09:27, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> That's funny because I tried it two days ago the first time and I didn't like it. I had troubles to get anything but bitmap fonts. After setting all things up I was a bit disappointed that contrast wise it doesn't work for me. Can someone send a screenshot with one setup that he/she considers good? >> >> thanks, >> >> Norbert >> >>> Am 24.04.2015 um 08:38 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>> I disagreeâ¦ DarkTheme is just for certain tastes, while regular one, while probably dated, is more âstandardâ. >>> Also, DarkTheme is not ready. yeah, yeahâ¦ it works and works fine most of the timeâ¦ but not *all* the time (take for example find string dialogâ¦ I never found the time to fix it, and nobody complained soâ¦ :P). Finally. we need to adopt SVG icons (in my TODO list since a couple of months, I will deliver soon, I hope), otherwise they do not look good (this is a problem eclipse itself had itâ¦ we are just inheriting it :) ) >>> >>> But a good question would be: How can we push forward our UI, besides using a darker or clearer theme? >>> I would like to hear some opinions here :) >>> >>> Esteban >>> >>> >>>> On 24 Apr 2015, at 08:33, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> comments about color is to be taken with care. >>>> >>>> >>>> Le 24/4/15 02:48, Sean P. DeNigris a Ã©crit : >>>>> Why didn't/don't we make it the default for 4.0? Everyone seems to love it, >>>>> and people are commenting that the UI looks dated. >>>>> >>>>> >>>>> >>>>> ----- >>>>> Cheers, >>>>> Sean >>>>> -- >>>>> View this message in context: http://forum.world.st/Release-with-Dark-Theme-tp4821496.html >>>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

April 24, 2015