August 2016 - Pharo-dev - lists.pharo.org

Epicea import+revert instead of redo+undo changes? (Was: Re: [pharo-project/pharo-core] f57843: 60163)
by Martin Dias Aug. 19, 2016

Aug. 19, 2016

Hi Stef, I come back to your observation about the words Redo and Undo used in Epicea menu. You proposed to use Import and Revert instead. Originally I chose redo/undo because they are very well known terms in text editing UIs, but it is true that they are different: in regular UIs you can't select an arbitrary operation in the history and redo or undo it, like in Epicea. So other names can be more adequate... any other opinion? Martin ps: other alternative is apply+"apply inverse" ps2: I'm preparing a major update in Epicea's UIs, which already has some renames. â El 7/8/2016 3:16, "stepharo" <stepharo(a)free.fr> escribiÃ³: Le 5/8/16 Ã 05:28, Martin Dias a Ã©crit : Hi Stef, good, I take note. I improved filters in the recent releases and will continue improving. Thanks Martin I have problems with the menu item names :) To me redo looks strange when I get a crash I want to import the changes not redo them. Then I do not get what undo means (yes I know this is probably revert) May be some pharoers have better names than mine. Stef Martin On Wed, Aug 3, 2016 at 5:30 PM, stepharo <stepharo(a)free.fr> wrote: > Thanks Martin. > > We missed yesterday: show only the latest version of every entities. :) > > > Setf > > > Le 3/8/16 Ã 11:23, Marcus Denker a Ã©crit : > > On 03 Aug 2016, at 11:07, GitHub <noreply(a)github.com> wrote: >>> >>> >>> Log Message: >>> ----------- >>> 60163 >>> 18831 Integrate new Epicea version >>> https://pharo.fogbugz.com/f/cases/18831 >>> >>> ChangeLog for this: >> >> - Case 18813: Implement redo and undo of protocol addition and removal. >> >> - Case 18612: disable drag&drop until TreeModel supports it correctly. >> >> - Case 18384: Redo and undo: show on any selection (not only when all >> selected entries are code changes). >> >> - Enhancement: Improve lost changes detection; show only the events >> actually lost. >> >> - Enhancement: Pass on filters. >> >> - Clean up: Do not show the "absent entry" item anymore since it was not >> useful at all. >> >> - Clean up: Remove unused "commit tags" in log browser. >> >> - Clean up: Remove unused tests. They were good idea, we can re-introduce >> them but working and covering more cases. >> >> - Clean up: Rename #displayWidget to #asMorph in EpLogBrowserItem''s >> hierarchy. It is more meaningful. >> >> - Workaround: Hide "Open in Sorter" menu action since it is useless until >> Treemodel drag&drop is fixed. >> >> >> >> 18768 Inlined method const could be implemented by metalinks >>> https://pharo.fogbugz.com/f/cases/18768 >>> >>> 18835 Update RBParser-Nodes class comments >>> https://pharo.fogbugz.com/f/cases/18835 >>> >>> http://files.pharo.org/image/60/60163.zip >>> >>> >>> >> >> > >

7 11

[pharo-project/pharo-core]
by GitHub Aug. 19, 2016

Aug. 19, 2016

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

1 0

[pharo-project/pharo-core] 5dfcea: 60188
by GitHub Aug. 19, 2016

Aug. 19, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 5dfcea3320fb3b8942a80337b07de7565f30e73c https://github.com/pharo-project/pharo-core/commit/5dfcea3320fb3b8942a80337… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-08-19 (Fri, 19 Aug 2016) Changed paths: M Kernel.package/MessageSend.class/instance/evaluating/value.st M Kernel.package/MessageSend.class/instance/evaluating/value_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60187.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60188.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60187.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60188.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60188 18158 MessageSend should not care about obsolete classes https://pharo.fogbugz.com/f/cases/18158 http://files.pharo.org/image/60/60188.zip

1 0

FileTree export format on Windows
by Peter UhnÃ¡k Aug. 19, 2016

Aug. 19, 2016

Hi, I just ran into a quite nasty issue when using GitFileTree on Windows with the FileTree export format. Apparently there are reserved names on Windows: > CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9 And I had an âauxâ and âaux:â methods in Pharo, which were attempted to be exported as âaux.stâ and âaux..stâ, but silently failed. There are also other rules https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#naming_conven… which might break binary selectors (I havenât tried those). I am not sure how I am supposed to deal with this, but assuming Pharo wants to support all platforms, this should be resolved in some manner; in the meantime I will use some alternative name. Thanks, Peter

2 1

Experience with FileSystem => proposal for improving user experience
by stepharo Aug. 18, 2016

Aug. 18, 2016

Hi I have a file /Users/ducasse/PharoMooc/Subtitles/W1/C019SD-W1-sous-titres-EN/EN_C019SD-W1-S1.srt and I would like to generate a new one with a different extension /Users/ducasse/PharoMooc/Subtitles/W1/C019SD-W1-sous-titres-EN/EN_C019SD-W1-S1.vtt Now I'm browsing FileReference and I do not find an easy way to do it. I had to peek and poke to get (self parent / self basenameWithoutExtension) withExtension: 'vtt' I analyse a bit why I was slow discovering it: I did not really find a nice way to obtain /Users/ducasse/PharoMooc/Subtitles/W1/C019SD-W1-sous-titres-EN/ or /Users/ducasse/PharoMooc/Subtitles/W1/C019SD-W1-sous-titres-EN/EN_C019SD-W1-S1 Proposal one: We could add withoutExtension withoutExtension ^ (self parent / self basenameWithoutExtension) Proposal two: We could add withoutBasename withoutBasename ^ self parent Proposal three: Not sure that it is worth (note that this is not a rename) withNewExtension: anExtension ^ self parent / self basenameWithoutExtension withExtension: anExtension So what do you think? Stef

3 4

Email bankruptcy: Can not keep up with mails
by Marcus Denker Aug. 18, 2016

Aug. 18, 2016

Hi, Over the summer with holidays email accumulatedâ¦ I started to get them down but there a re now still >300 unread Pharo mails left. I decided I will just delete themâ¦ if you expected an answer/input from me â> send me a private mail. Marcus

1 0

[Issue tracker] push on old issues needed
by Marcus Denker Aug. 18, 2016

Aug. 18, 2016

Hi, The issue tracker is accumulating issues fastâ¦ lots of them a half-finished, yet saw no action for quite some timeâ¦ Keep in mind that if *you* will not look at an issue you where involved in (or even created), chances are that *nobody* will look at itâ¦ it is your job to push it forward. (e.g. ask for help on the mailinglist or Slackâ¦) So please, everyone, have a look at old issues and push those forward that are ready or close those that are not relevant anymoreâ¦ **every single issue resolved helps!!** https://pharo.fogbugz.com/f/filters/57/All-newest-first <https://pharo.fogbugz.com/f/filters/57/All-newest-first> Marcus

1 0

[pharo-project/pharo-core]
by GitHub Aug. 18, 2016

Aug. 18, 2016

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

1 0

[pharo-project/pharo-core] 5b4669: 60187
by GitHub Aug. 18, 2016

Aug. 18, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 5b46698f658ee35055ac458d437d32035630c99a https://github.com/pharo-project/pharo-core/commit/5b46698f658ee35055ac458d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-08-18 (Thu, 18 Aug 2016) Changed paths: M Collections-Tests.package/SplitJoinTest.class/instance/running/testSplitJoinBoundaryCases.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/README.md R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/class/accessing/uniqueIdentifierName.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/class/testing/checksClass.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/definition.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/instance/accessing/group.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/instance/accessing/name.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/instance/accessing/rationale.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/instance/accessing/resultClass.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/instance/running/basicCheck_.st R Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/instance/running/checkClass_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60186.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60187.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60186.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60187.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/extension/String/instance/asSlotCollection.st Log Message: ----------- 60187 18953 remove Regex dependency from SplitJoinTest>>#testSplitJoinBoundaryCases https://pharo.fogbugz.com/f/cases/18953 18916 simplify asSlotCollection for bootstrap https://pharo.fogbugz.com/f/cases/18916 18938 Remove RBClassInstVarNotInitializedRule, it is a bad rule https://pharo.fogbugz.com/f/cases/18938 http://files.pharo.org/image/60/60187.zip

1 0

GTPlayground/Inspector print it
by Peter UhnÃ¡k Aug. 17, 2016

Aug. 17, 2016

Hi, does the print-it option always use only asString (or whatever it actually uses), or can it be modified in some way? I would like to modify it a bit, because for big numbers the default one is not easy to read, e.g. âinstead, I would like to see this âIt gives much better idea of the scale of the number. Can such thing be modified? Thanks, Peter

3 2