April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Release with Dark Theme

by Thierry Goubier

Le 24/04/2015 12:21, phil(a)highoctane.be a Ã©crit : > > > On Fri, Apr 24, 2015 at 10:48 AM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Le 24/04/2015 10:11, phil(a)highoctane.be <mailto:phil@highoctane.be> > a Ã©crit : > > > > On Fri, Apr 24, 2015 at 8:38 AM, Esteban Lorenzano > <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com> > <mailto:estebanlm@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? > > > Don't know about that one. http://bracha.org/hopscotch-wasdett.pdf Look for the IDE description (i.e. Figure 1). A web browser metaphor, where you can open all elements and edit in place; not that different from what it could be in Self. I believe it's not as efficient in practice as it could be, for editing code. But for overall viewing, could be very effective. I toyed with multiple selection in the AltBrowser (i.e. opening multiple edit panes on the right) but never went that way. Maybe merging both could be an idea: Newspeak browser + tree navigation on the left :) > > > Navigating hierarchies should be made easier (switching on the > "hier/flat" button gets tiring). > > > This one is difficult to solve. > > > Maybe a popup with the hierarchy would do (with some keybinding, like C-h) In AltBrowser, I'm searching around how to do that, so what I have is: - menu navigation commands (super, first subclass, sibling) with a memory (back), but I'm not satisfied because often what I want is see both at the same time. Back really works well, but maybe with a button on the toolbar (or linked to the back and forward keys on my Chromebook? Not used to that keyboard layout yet) - What I use most often is: right click on superclass name in the description, choose browse to open a browser on the superclass... Not too bad for what I want. Works for any class name everywhere, which is very convenient. - I also have a hierarchy command which opens a browser scoped on the hierarchy. For certain types of searches, it can be very convenient (i.e. all callers of printString in the hierarchy...) But, still: three ways to do the same thing? Clearly could be better. Thierry > > 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

What's new on Pillar ?

by Cyril Ferlicot

Hi everyone ! I'm currently working on Pillar ! It's been a little while now so I wanted to share what's new. --> First of all, with Stephane we created a new project, Cocoon, based on the configuration system of Pillar. And now Pillar uses Cocoon for his configurations. http://smalltalkhub.com/#!/~PharoExtras/Cocoon --> Pillar unit tests weren't working on Windows before --> With Damien we also added two new abstractions: --> The transformers: They take the Pillar tree and modify it. For exemple we have a transformer which evaluates the scripts with a "eval=true" parameter. --> The annotations: They let the writer specify many different things in their document using just 1 syntax (see below for an example) --> We now have our first annotation tag: the inclusion tag ! If you add this: ${inputFile:test.pillar}$ or ${inputFile:folder/test.pillar}$ into your Pillar file, that will include the content of test.pillar. I recommend for now to use it at the root of the pillar file and not inside a paragraph. That still needs some improvement. --> We now have a transformer which adds an anchor after each title. The anchor will have the text of the title. This still needs some improvement, it's really simple for now. For exemple we need to consider the case where we have 2 titles with the same text (like 'introduction'). --> Now you can add 'lineNumber=true' as parameter for a Script. This will add a numerotation at your script, usefull if we want to explain a long code. --> I did some refactorisation on the parameters used by pillar to clean the code. --> I did some refactorisation of the template system, the old one was really ugly and changed the baseDirectory. Now template are managed by a stream and not a file. --> I improved a little the configuration --> Now if you want to change the baseDirectory you can pass a FileReference, a relative path or an absolute path. --> Now we look for the inputFiles from the baseDirectory and not the working directory like before. You can also pass a FileReference, a relative path or an absolute path. --> I added some tests to Pillar. --> I added some doc to EnterprisePharo https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… --> To help the users I improved the error reports. Before we had really few errors specific to Pillar. For this one you can help me ! If you found a weird error or something really not easy to deal with, send me your problem ! -- Cheers Cyril Ferlicot

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by phil＠highoctane.be

On Fri, Apr 24, 2015 at 10:48 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > 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? > Don't know about that one. > > Navigating hierarchies should be made easier (switching on the >> "hier/flat" button gets tiring). >> > > This one is difficult to solve. > Maybe a popup with the hierarchy would do (with some keybinding, like C-h) > > 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

[pharo-project/pharo-core]

by GitHub

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

April 24, 2015

[pharo-project/pharo-core] 6b767c: 40611

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 6b767c1d3004fcce812202cabf2cfa910c56756b https://github.com/pharo-project/pharo-core/commit/6b767c1d3004fcce812202ca… 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 M Monticello.package/MCLazyVersionInfo.class/instance/initialization/initializeWithName_id_message_date_time_author_ancestors_stepChildren_.st M Monticello.package/MCVersionInfo.class/instance/initialization/initializeWithName_id_message_date_time_author_ancestors_stepChildren_.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/accessing/selectedPackageAncestors.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script610.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script611.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40610.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40611.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40611 15338 OrderedDictionary changes to merge https://pharo.fogbugz.com/f/cases/15338 15339 Monticello with spotter extension methods throws MNU errors when browsing packages in repos that dont contain every package https://pharo.fogbugz.com/f/cases/15339 http://files.pharo.org/image/40/40611.zip

April 24, 2015

[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