- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Changes Browser is broken

by Peter UhnÃ¡k

Actually the thanks here goes to Latsabben ( that fixed most of it before I could even start looking at the code. :) Peter On Fri, Mar 18, 2016 at 12:30 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > THANK YOU !! > > (but you had a secret French special agent, right ;-) > > > On 18 Mar 2016, at 12:26, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > 12 hours later all the bugs are fixed. > > > > And that's why I love Pharo and everyone here. :) > > > > Thanks! > > > > On Fri, Mar 18, 2016 at 10:53 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > On Fri, Mar 18, 2016 at 8:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > yes, Epicea will be integrated âfirst week of Pharo 6â, so we can > iterate and > > > > Well we still need to fix it, we can't leave Pharo 5 for a year without > a proper recovery. > > We'll try to fix something today with Stef. > > > > Peter > > > > >

March 18, 2016

Re: [Pharo-dev] Changes Browser is broken

by Sven Van Caekenberghe

THANK YOU !! (but you had a secret French special agent, right ;-) > On 18 Mar 2016, at 12:26, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > 12 hours later all the bugs are fixed. > > And that's why I love Pharo and everyone here. :) > > Thanks! > > On Fri, Mar 18, 2016 at 10:53 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > On Fri, Mar 18, 2016 at 8:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yes, Epicea will be integrated âfirst week of Pharo 6â, so we can iterate and > > Well we still need to fix it, we can't leave Pharo 5 for a year without a proper recovery. > We'll try to fix something today with Stef. > > Peter >

March 18, 2016

Re: [Pharo-dev] Changes Browser is broken

by Peter UhnÃ¡k

12 hours later all the bugs are fixed. And that's why I love Pharo and everyone here. :) Thanks! On Fri, Mar 18, 2016 at 10:53 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > On Fri, Mar 18, 2016 at 8:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> yes, Epicea will be integrated âfirst week of Pharo 6â, so we can iterate >> and > > > Well we still need to fix it, we can't leave Pharo 5 for a year without a > proper recovery. > We'll try to fix something today with Stef. > > Peter >

March 18, 2016

Re: [Pharo-dev] Changes Browser is broken

by Peter UhnÃ¡k

On Fri, Mar 18, 2016 at 8:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yes, Epicea will be integrated âfirst week of Pharo 6â, so we can iterate > and Well we still need to fix it, we can't leave Pharo 5 for a year without a proper recovery. We'll try to fix something today with Stef. Peter

March 18, 2016

[pharo-project/pharo-core]

by GitHub

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

March 18, 2016

[pharo-project/pharo-core] 127c6b: 50652

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 127c6b0286f217e1aea290541a6a21027e161d1c https://github.com/pharo-project/pharo-core/commit/127c6b0286f217e1aea29054… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-18 (Fri, 18 Mar 2016) Changed paths: A NewValueHolder.package/CollectionValueHolder.class/instance/announcements/whenAddedDo_.st A NewValueHolder.package/CollectionValueHolder.class/instance/announcements/whenRemovedDo_.st A NewValueHolder.package/CollectionValueHolder.class/instance/announcing/valueAdded_.st A NewValueHolder.package/CollectionValueHolder.class/instance/announcing/valueRemoved_.st M NewValueHolder.package/CollectionValueHolder.class/instance/override/at_put_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/addAllFirstUnlessAlreadyPresent_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/addAllFirst_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/addAllLast_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/addAll_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/addFirst_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/addLast_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/add_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/add_afterIndex_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/add_after_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/add_beforeIndex_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/add_before_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/atAllPut_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/atAll_putAll_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/atAll_put_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/atLast_put_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/atWrap_put_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/at_ifAbsentPut_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/insert_before_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/removeAll.st A NewValueHolder.package/CollectionValueHolder.class/instance/protocol/removeAll_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/removeAt_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/removeFirst.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/removeFirst_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/removeIndex_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/removeLast.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/removeLast_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/remove_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/remove_ifAbsent_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/replaceAll_with_.st M NewValueHolder.package/CollectionValueHolder.class/instance/protocol/replace_.st A NewValueHolder.package/CollectionValueHolderTest.class/README.md A NewValueHolder.package/CollectionValueHolderTest.class/definition.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/running/setUp.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/tests/testAddMany.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/tests/testAddOne.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/tests/testChangeAddMany.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/tests/testChangeAddOne.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/tests/testChangeRemoveMany.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/tests/testChangeRemoveOne.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/tests/testRemoveMany.st A NewValueHolder.package/CollectionValueHolderTest.class/instance/tests/testRemoveOne.st M NewValueHolder.package/NewValueHolder.class/README.md M NewValueHolder.package/NewValueHolder.class/instance/announcements/whenChangedDo_.st A NewValueHolder.package/NewValueHolderTest.class/README.md A NewValueHolder.package/NewValueHolderTest.class/definition.st A NewValueHolder.package/NewValueHolderTest.class/instance/tests/testChange.st A NewValueHolder.package/NewValueHolderTest.class/instance/tests/testValuesInBlock.st A NewValueHolder.package/ValueAdded.class/README.md A NewValueHolder.package/ValueAdded.class/class/instance creation/newValue_.st A NewValueHolder.package/ValueAdded.class/definition.st A NewValueHolder.package/ValueAdded.class/instance/accessing/newValue.st A NewValueHolder.package/ValueAdded.class/instance/accessing/newValue_.st A NewValueHolder.package/ValueRemoved.class/README.md A NewValueHolder.package/ValueRemoved.class/class/instance creation/oldValue_.st A NewValueHolder.package/ValueRemoved.class/definition.st A NewValueHolder.package/ValueRemoved.class/instance/accessing/oldValue.st A NewValueHolder.package/ValueRemoved.class/instance/accessing/oldValue_.st R NewValueHolder.package/extension/Object/class/selectionReactiveVariable.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50651.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50652.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50651.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50652.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/DropListModel.class/instance/initialization/initialize.st A Spec-Core.package/ListModel.class/instance/api/selectedItemsSorted.st M Spec-Core.package/ListModel.class/instance/initialization/initializeValueHolders.st M Tool-ExternalBrowser.package/ExternalChangesBrowser.class/instance/initialization/initializePresenter.st Log Message: ----------- 50652 17843 Changes Browser doesnt recover changes in correct order https://pharo.fogbugz.com/f/cases/17843 17750 Extend CollectionValueHolder with ValueAdded/Removed/Changed https://pharo.fogbugz.com/f/cases/17750 http://files.pharo.org/image/50/50652.zip

March 18, 2016

Re: [Pharo-dev] Changes Browser is broken

by Esteban Lorenzano

yes, Epicea will be integrated âfirst week of Pharo 6â, so we can iterate and fix :) > On 18 Mar 2016, at 08:52, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > On Fri, Mar 18, 2016 at 7:45 AM, stepharo <stepharo(a)free.fr> wrote: >> Yes because we have epicea to replace it but epicea shows us some nice bugs >> underneath. >> So we decided to postpone. > > Postpone after 5.0 ? > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

March 18, 2016

Re: [Pharo-dev] Changes Browser is broken

by Serge Stinckwich

On Fri, Mar 18, 2016 at 7:45 AM, stepharo <stepharo(a)free.fr> wrote: > Yes because we have epicea to replace it but epicea shows us some nice bugs > underneath. > So we decided to postpone. Postpone after 5.0 ? -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

March 18, 2016

Re: [Pharo-dev] Changes Browser is broken

by stepharo

thanks for the report. We should fix them. We can try to fix one together today. Le 17/3/16 23:30, Peter UhnÃ¡k a Ã©crit : > Today I learned that you can actually lose code in Pharo because the > record is not always added to the changes file. > > Also using the tool is quite a lot of pain, so if you want to recover > your changes you have to do a lot of archaeology. > > I've added several issues and marked most of them as '2 - Really > Important', because I think they are (especially for students etc that > like to break things), but maybe you don't want it for Pharo 5. > > https://pharo.fogbugz.com/f/cases/17840/ChangesBrowser-selectAll-DNU > https://pharo.fogbugz.com/f/cases/17841/Creating-a-class-from-a-debugger-du… > https://pharo.fogbugz.com/f/cases/17842/Recover-lost-changes-doesn-t-recove… > https://pharo.fogbugz.com/f/cases/17843/Changes-Browser-doesn-t-recover-cha… > > Peter > >

March 18, 2016

Re: [Pharo-dev] Changes Browser is broken

by stepharo

Yes because we have epicea to replace it but epicea shows us some nice bugs underneath. So we decided to postpone. Now this is just that maintaining two systems is always a pain and we are sorry. Stef Le 18/3/16 00:33, Ben Coman a Ã©crit : > I hadn't used Recover Changes for a while, but recently found that it > had lost a lot of power. Particularly not being able to filter to > show only the most recent updates. Its tedious to manually search for > the latest version of several methods. > > cheers -ben > > On Fri, Mar 18, 2016 at 6:30 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> Today I learned that you can actually lose code in Pharo because the record >> is not always added to the changes file. >> >> Also using the tool is quite a lot of pain, so if you want to recover your >> changes you have to do a lot of archaeology. >> >> I've added several issues and marked most of them as '2 - Really Important', >> because I think they are (especially for students etc that like to break >> things), but maybe you don't want it for Pharo 5. >> >> https://pharo.fogbugz.com/f/cases/17840/ChangesBrowser-selectAll-DNU >> https://pharo.fogbugz.com/f/cases/17841/Creating-a-class-from-a-debugger-du… >> https://pharo.fogbugz.com/f/cases/17842/Recover-lost-changes-doesn-t-recove… >> https://pharo.fogbugz.com/f/cases/17843/Changes-Browser-doesn-t-recover-cha… >> >> Peter >> >> >

March 18, 2016