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

[pharo-project/pharo-core]

by GitHub

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

Sept. 22, 2016

[pharo-project/pharo-core] d3c4dd: 60236

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d3c4dd1986da6a82d3a646cce151c8ff44913bfb https://github.com/pharo-project/pharo-core/commit/d3c4dd1986da6a82d3a646cc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-22 (Thu, 22 Sep 2016) Changed paths: M AST-Core.package/NumberParser.class/instance/parsing-private/readExponent.st R Compiler.package/Compiler.class/instance/public - opal compatibility/category_.st M Compiler.package/Compiler.class/instance/public - opal compatibility/compilationContext.st M ConfigurationOfTxText.package/ConfigurationOfTxText.class/instance/symbolic versions/stable_.st A ConfigurationOfTxText.package/ConfigurationOfTxText.class/instance/versions/version2126_.st M Kernel.package/Deprecation.class/definition.st M Kernel.package/Deprecation.class/instance/accessing/messageText.st A Kernel.package/Deprecation.class/instance/accessing/sendingMethodName.st A Kernel.package/Deprecation.class/instance/accessing/sendingMethodName_.st M Kernel.package/Object.class/instance/deprecation/deprecated_.st M Kernel.package/Object.class/instance/deprecation/deprecated_on_in_.st M Kernel.package/Object.class/instance/deprecation/deprecated_on_in_transformWith_.st M Kernel.package/Object.class/instance/deprecation/deprecated_transformWith_.st M Monticello.package/MethodAddition.class/instance/operations/createCompiledMethod.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui text/buildNewCodeSourceAreaRubric.st M Nautilus.package/Nautilus.class/class/settings/nautilusSettingsOn_.st A Nautilus.package/Nautilus.class/class/settings/showSourceCodeAnnotation.st A Nautilus.package/Nautilus.class/class/settings/showSourceCodeAnnotation_.st R OpalCompiler-Core.package/AbstractCompiler.class/instance/accessing/category_.st M OpalCompiler-Core.package/AbstractCompiler.class/instance/old - public/compile_in_classified_notifying_ifFail_.st M OpalCompiler-Core.package/CCompilationContext.class/definition.st R OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/category.st R OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/category_.st M OpalCompiler-Core.package/CompilationContext.class/definition.st R OpalCompiler-Core.package/CompilationContext.class/instance/accessing/protocol.st R OpalCompiler-Core.package/CompilationContext.class/instance/accessing/protocol_.st R OpalCompiler-Core.package/CompilationContext.class/instance/backward compatibility/category.st R OpalCompiler-Core.package/CompilationContext.class/instance/backward compatibility/category_.st M OpalCompiler-Core.package/OCSemanticError.class/instance/error handling/notify_at_.st R OpalCompiler-Core.package/OpalCompiler.class/instance/accessing/category_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60235.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60236.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60235.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60236.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TClassDescription.class/instance/compiling/compile_classified_withStamp_notifying_logSource_.st R TxText-Athens.package/TxAthensLayout.class/instance/as yet unclassified/hideEmbeddedObject_.st A TxText-Athens.package/TxAthensLayout.class/instance/view notifications/hideEmbeddedObject_.st A TxText-Athens.package/TxAthensLayoutView.class/class/examples/example.st M TxText-Athens.package/TxAthensLayoutView.class/instance/rendering/renderOn_.st M TxText-Athens.package/TxBasicViewMorph.class/README.md M TxText-Athens.package/TxBasicViewMorph.class/definition.st A TxText-Athens.package/TxBasicViewMorph.class/instance/accessing/backgroundColor.st A TxText-Athens.package/TxBasicViewMorph.class/instance/accessing/backgroundColor_.st A TxText-Athens.package/TxBasicViewMorph.class/instance/visual properties/fillStyle.st R TxText-Athens.package/TxDeleteOperation.class/instance/as yet unclassified/do.st A TxText-Athens.package/TxDeleteOperation.class/instance/undo-undo/do.st A TxText-Athens.package/TxInsertOperation.class/instance/accessing/text_.st R TxText-Athens.package/TxInsertOperation.class/instance/as yet unclassified/text_.st R TxText-Athens.package/TxInsertOperation.class/instance/as yet unclassified/undo.st A TxText-Athens.package/TxInsertOperation.class/instance/do%2Fundo/undo.st A TxText-Athens.package/TxNewTextAnnouncement.class/README.md A TxText-Athens.package/TxNewTextAnnouncement.class/definition.st M TxText-Athens.package/TxSelectionChangeOperation.class/instance/do%2Fundo/redo.st M TxText-Athens.package/TxSelectionChangeOperation.class/instance/do%2Fundo/undo.st M TxText-Athens.package/TxTextEditor.class/instance/editing/backspace.st M TxText-Athens.package/TxTextEditor.class/instance/editing/delete.st M TxText-Athens.package/TxTextEditor.class/instance/editing/insert_.st M TxText-Athens.package/TxTextEditor.class/instance/initialization/text_.st A TxText-Athens.package/TxTextEditor.class/instance/private notifying/notifyDeleted.st A TxText-Athens.package/TxTextEditor.class/instance/private notifying/notifyInserted_.st A TxText-Athens.package/TxTextEditor.class/instance/private notifying/notifyNewText.st A TxText-Athens.package/TxTextEditor.class/instance/private notifying/notifySelectionChange_.st M TxText-Athens.package/TxTextEditor.class/instance/private/recordSelectionChange_.st A TxText-Athens.package/TxTextEditor.class/instance/selection/shiftSelectionTo_.st M TxText-Athens.package/TxTextEditorMorph.class/instance/drawing/drawKeyboardFocusOn_.st M TxText-Athens.package/TxTextEditorMorph.class/instance/drawing/drawOnAthensCanvas_.st M TxText-Athens.package/TxTextEditorMorph.class/instance/drawing/drawSelectionOn_.st A TxText-Athens.package/TxTextRenderer.class/instance/accessing/advance_.st A TxText-Athens.package/TxTextRenderer.class/instance/accessing/canvas.st A TxText-Athens.package/TxTextRenderer.class/instance/accessing/setColor_.st A TxText-Athens.package/TxTextRenderer.class/instance/accessing/setFont_.st R TxText-Athens.package/TxTextRenderer.class/instance/as yet unclassified/advance_.st R TxText-Athens.package/TxTextRenderer.class/instance/as yet unclassified/canvas.st R TxText-Athens.package/TxTextRenderer.class/instance/as yet unclassified/initialize.st R TxText-Athens.package/TxTextRenderer.class/instance/as yet unclassified/renderLines_on_.st R TxText-Athens.package/TxTextRenderer.class/instance/as yet unclassified/render_lines_on_.st A TxText-Athens.package/TxTextRenderer.class/instance/initialization/initialize.st A TxText-Athens.package/TxTextRenderer.class/instance/rendering/renderLines_on_.st A TxText-Athens.package/TxTextRenderer.class/instance/rendering/render_lines_on_.st R TxText-Athens.package/TxTextRenderer.class/instance/rendering/setColor_.st R TxText-Athens.package/TxTextRenderer.class/instance/rendering/setFont_.st M TxText-Model.package/TxBackColorAttribute.class/class/defaults/defaultValue.st A TxText-Model.package/TxEmbeddedObjectSpan.class/instance/as yet unclassified/initWithText_.st M TxText-Model.package/TxForeColorAttribute.class/class/defaults/defaultValue.st A TxText-Styler.package/TxTextStyler.class/instance/attributes/addAttribute_forNode_.st A TxText-Styler.package/TxTextStyler.class/instance/attributes/addAttribute_startPosition_stopPosition_.st A TxText-Styler.package/TxTextStyler.class/instance/attributes/addAttributes_forNode_.st A TxText-Styler.package/TxTextStyler.class/instance/attributes/addAttributes_startPosition_stopPosition_.st M TxText-Styler.package/TxTextStyler.class/instance/initialization/initialize.st A TxText-Styler.package/TxTextStyler.class/instance/styling/addStyle_forNode_.st A TxText-Styler.package/TxTextStyler.class/instance/styling/addStyle_startPosition_stopPosition_.st R TxText-Styler.package/TxTextStyler.class/instance/visiting/addAttribute_forNode_.st R TxText-Styler.package/TxTextStyler.class/instance/visiting/addAttribute_startPosition_stopPosition_.st R TxText-Styler.package/TxTextStyler.class/instance/visiting/addAttributes_forNode_.st R TxText-Styler.package/TxTextStyler.class/instance/visiting/addAttributes_startPosition_stopPosition_.st R TxText-Styler.package/TxTextStyler.class/instance/visiting/addStyle_forNode_.st R TxText-Styler.package/TxTextStyler.class/instance/visiting/addStyle_startPosition_stopPosition_.st M TxText-Styler.package/TxTextStyler.class/instance/visiting/visitAssignmentNode_.st M TxText-Styler.package/TxTextStyler.class/instance/visiting/visitBlockNode_.st A TxText-Styler.package/TxTextStyler.class/instance/visiting/visitCascadeNode_.st M TxText-Styler.package/TxTextStyler.class/instance/visiting/visitMethodNode_.st A TxText-Styler.package/TxTextStyler.class/instance/visiting/visitPragmaNode_.st M TxText-Styler.package/TxTextStyler.class/instance/visiting/visitReturnNode_.st A TxText-Styler.package/TxTextStyler.class/instance/visiting/visitSuperNode_.st A TxText-Styler.package/TxTextStyler.class/instance/visiting/visitThisContextNode_.st Log Message: ----------- 60236 19039 Optional source code annotation pane Nautilus https://pharo.fogbugz.com/f/cases/19039 18482 Typing a large number into a playground freezes the image https://pharo.fogbugz.com/f/cases/18482 19124 enhance Deprecation to log sending method https://pharo.fogbugz.com/f/cases/19124 19122 Remove category from Opal https://pharo.fogbugz.com/f/cases/19122 18788 TxTextStyler do not work https://pharo.fogbugz.com/f/cases/18788 http://files.pharo.org/image/60/60236.zip

Sept. 22, 2016

Re: [Pharo-dev] How do recover change with epicea?

by stepharo

:) I'm trying to remember if we have fly by help on menu item because this descriptions would fit nicely there. Martin the names proposed by Norbert are cool. Stef Le 21/9/16 Ã 13:00, Sven Van Caekenberghe a Ã©crit : > Thank you for this clear explanation, Martin. People will always have trouble using any tool/UI if they do not understand the underlying model. It helped me. Needless to say, such high level documentation needs to go somewhere. > >> On 21 Sep 2016, at 06:50, Martin Dias <tinchodias(a)gmail.com> wrote: >> >> Hi Stef, âNo idea why Epicea didn't log your changes. >> >> About "monitor vs. log set"... the two new entries in World Menu > Tools > Epicea... I'd like user opinions to improve naming and UI. I can tell some things introduced in the latest integration. >> >> - The Log Set >> As you know, Epicea Monitor logs code changes (and some IDE events such as MC load/save and refactorings). Such data is placed in .ombu files in a local directory. Each time a Pharo image opens, Epicea Monitor logs code changes into a new ombu file. Those ombu files in the local directory is what is currently called "Log Set". >> >> - The Monitor UI shows the code changes since Epicea started to log. >> ===> This means it shows changes placed in potentially several ombu files. >> >> - The Log Set UI shows: >> -- all the logs in the local directory on the left panel, and >> -- the content of the selected log in the right panel. >> ===> This UI visually connects the logs to help user to understand how the ombu files are related. Note that the code changes displayed on the right panel belong to only one log (different than in the Monitor UI, that might show changes in several logs). >> >> Cheers, >> Martin >> >> On Tue, Sep 20, 2016 at 4:57 PM, stepharo <stepharo(a)free.fr> wrote: >> even better >> >> Smalltalk tools changeList browseRecentLog >> >> does not show any changes :) >> >> So I redownloaded the latest version of tried >> >> - changes something >> >> - exist without saving >> >> - reopening the image >> >> And I could not reproduce the bug.... Shit. >> >> So I lost my time. >> >> Stef >> >> >> >> >> >> Hi >> >> i introduced a loop (yes totally stupid) in menu morph icon :) >> so I had to quit my image. >> I thought that epicea would show me all the changes and I could not find how to do it. >> I do not know how to invoke the old recover lost changes... so so far I lost 40 min of dev :( >> >> I have no idea what is monitor vs log set in Epicea. >> And log set is just with the changes I'm doing :( not the ones I lost :( >> >> In cutting alpha image it would be good to make sure that we cannot lose our work :( >> Stef >> >> >> >> >> >> >> <epiceaLogSet.jpg> >

Sept. 22, 2016

Re: [Pharo-dev] How do recover change with epicea?

by stepharo

Hi norbert I like your names better than mine. It took me some times to understand the monitor and others. Stef Le 21/9/16 Ã 09:51, Norbert Hartl a Ã©crit : > > > Am 21.09.2016 um 08:02 schrieb stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > >> >> >> Le 21/9/16 Ã 06:50, Martin Dias a Ã©crit : >>> Hi Stef, âNo idea why Epicea didn't log your changes. >> >> Me neither I tried to reproduce it and I could not. >> Still I lost 40 min deep hacking. >>> >>> About "monitor vs. log set"... the two new entries in World Menu > >>> Tools > Epicea... I'd like user opinions to improve naming and UI. I >>> can tell some things introduced in the latest integration. >>> >>> - The Log Set >>> As you know, Epicea Monitor logs code changes (and some IDE events >>> such as MC load/save and refactorings). Such data is placed in .ombu >>> files in a local directory. Each time a Pharo image opens, Epicea >>> Monitor logs code changes into a new ombu file. Those ombu files in >>> the local directory is what is currently called "Log Set". >> >> Session Set > > Session changes > or > Last session changes > > It is in the text. It writes changes since image start (=session) >>> >>> - The Monitor UI shows the code changes since Epicea started to log. >>> ===> This means it shows changes placed in potentially several ombu >>> files. >> >> Full Log Set >> > All changes > > Why so complicated names? Why so different to before? > > Norbert >> >>> >>> - The Log Set UI shows: >>> -- all the logs in the local directory on the left panel, and >>> -- the content of the selected log in the right panel. >>> ===> This UI visually connects the logs to help user to understand >>> how the ombu files are related. Note that the code changes displayed >>> on the right panel belong to only one log (different than in the >>> Monitor UI, that might show changes in several logs). >>> >>> Cheers, >>> Martin >>> >>> On Tue, Sep 20, 2016 at 4:57 PM, stepharo <stepharo(a)free.fr >>> <mailto:stepharo@free.fr>> wrote: >>> >>> even better >>> >>> Smalltalk tools changeList browseRecentLog >>> >>> does not show any changes :) >>> >>> So I redownloaded the latest version of tried >>> >>> - changes something >>> >>> - exist without saving >>> >>> - reopening the image >>> >>> And I could not reproduce the bug.... Shit. >>> >>> So I lost my time. >>> >>> Stef >>> >>> >>> >>> >>> >>> Hi >>> >>> i introduced a loop (yes totally stupid) in menu morph icon :) >>> so I had to quit my image. >>> I thought that epicea would show me all the changes and I >>> could not find how to do it. >>> I do not know how to invoke the old recover lost changes... >>> so so far I lost 40 min of dev :( >>> >>> I have no idea what is monitor vs log set in Epicea. >>> And log set is just with the changes I'm doing :( not the >>> ones I lost :( >>> >>> In cutting alpha image it would be good to make sure that we >>> cannot lose our work :( >>> Stef >>> >>> >>> >>> >>> >>> >>

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Nicolas Passerini

Hi Norbert, I am failing to reproduce this issue, I would need more info. What I did is: - create a git repository with git file tree and load some package into a clean Pharo 6 Image with the stable version of Iceberg - add a local iceberg repository pointing to the same directory where the gitfiletree repository resides - open an Iceberg repository synchronizer for that project. ... and it seems to work, so I must be missing something. On Thu, Sep 22, 2016 at 12:38 PM, Nicolas Passerini <npasserini(a)gmail.com> wrote: > Yes, I do not know exactly why, but Metacello will not update your > packages if you do that. > > On Thu, Sep 22, 2016 at 12:27 PM, Norbert Hartl <norbert(a)hartl.name> > wrote: > >> >> Am 22.09.2016 um 11:56 schrieb Nicolas Passerini <npasserini(a)gmail.com>: >> >> >> On Thu, Sep 22, 2016 at 11:43 AM, Norbert Hartl <norbert(a)hartl.name> >> wrote: >> >>> I'm using stable, sorry for not saying. >>> >> >> No worries. >> >> I think it is fixed in the newer development version, but let me check it >> and I will come back to you. >> >> I loaded >> >> Metacello new >> baseline: 'Iceberg'; >> repository: 'github://npasserini/iceberg:master'; >> load. >> >> but the problem still exists. I must confess that I struggle to use this >> properly. By executing the expression above I cannot see what I really >> updated. Monticello browser is not of any help. I can see Iceberg.package >> which is bold. Loading the package does not seem to do anything and the >> package stays bold. >> >> Norbert >> >> >

Sept. 22, 2016

Re: [Pharo-dev] Better diffs

by Yuriy Tymchuk

I want to add my 2 cent: we need a nice diff model. Because now we have about 3-4 models used by visual tools, metacello, refactoring, etcâ¦ and all suck in one way or another. It would be nice to have a unified model (maybe epicea?) and build on top of it, so if we need to improve, there will be one place to work on. Uko > On 22 Sep 2016, at 11:49, Nicolas Passerini <npasserini(a)gmail.com> wrote: > > I am not happy with Iceberg diffs so I wonder if there is a better diff morphs around. > > Currently I am using a GLMDiffPresentation, which gives an easy way to show a diff, but is not much flexible. Some requirements I have are: > a. Configure coloring (currently changes are always shown in red for the left version and in green for the right version). > b. Provide a title for each side of the diff > c. (more difficult) Show three way diffs. > > Also highlighting is just not right in current version, several times it does not highlight correctly the changed code. > > So, do you know if there is a better way to show diffs? > > Thank you. > Nico

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Nicolas Passerini

Yes, I do not know exactly why, but Metacello will not update your packages if you do that. On Thu, Sep 22, 2016 at 12:27 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 22.09.2016 um 11:56 schrieb Nicolas Passerini <npasserini(a)gmail.com>: > > > On Thu, Sep 22, 2016 at 11:43 AM, Norbert Hartl <norbert(a)hartl.name> > wrote: > >> I'm using stable, sorry for not saying. >> > > No worries. > > I think it is fixed in the newer development version, but let me check it > and I will come back to you. > > I loaded > > Metacello new > baseline: 'Iceberg'; > repository: 'github://npasserini/iceberg:master'; > load. > > but the problem still exists. I must confess that I struggle to use this > properly. By executing the expression above I cannot see what I really > updated. Monticello browser is not of any help. I can see Iceberg.package > which is bold. Loading the package does not seem to do anything and the > package stays bold. > > Norbert > >

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Norbert Hartl

> Am 22.09.2016 um 11:56 schrieb Nicolas Passerini <npasserini(a)gmail.com>: > > > On Thu, Sep 22, 2016 at 11:43 AM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > I'm using stable, sorry for not saying. > > No worries. > > I think it is fixed in the newer development version, but let me check it and I will come back to you. I loaded Metacello new baseline: 'Iceberg'; repository: 'github://npasserini/iceberg:master'; load. but the problem still exists. I must confess that I struggle to use this properly. By executing the expression above I cannot see what I really updated. Monticello browser is not of any help. I can see Iceberg.package which is bold. Loading the package does not seem to do anything and the package stays bold. Norbert

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Nicolas Passerini

On Thu, Sep 22, 2016 at 11:43 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > I'm using stable, sorry for not saying. > No worries. I think it is fixed in the newer development version, but let me check it and I will come back to you.

Sept. 22, 2016

Better diffs

by Nicolas Passerini

I am not happy with Iceberg diffs so I wonder if there is a better diff morphs around. Currently I am using a GLMDiffPresentation, which gives an easy way to show a diff, but is not much flexible. Some requirements I have are: a. Configure coloring (currently changes are always shown in red for the left version and in green for the right version). b. Provide a title for each side of the diff c. (more difficult) Show three way diffs. Also highlighting is just not right in current version, several times it does not highlight correctly the changed code. So, do you know if there is a better way to show diffs? Thank you. Nico

Sept. 22, 2016