Epicea - showing latest lost changes

I have one more suggestion for Epicea. When the window pops up I’d like to have a big “RESTORE” button to reapply all the changes. I think it will be also more user friendly, as how should an newcomer know that he has to select all the items in the list and use the context menu.

Cheers.

Uko

On 24 Feb 2017, at 08:33, stepharong <[hidden email]> wrote:

Hi martin

Thanks for our constant improvement of epicea. 

In VW they have a nice way to filter

you can filter the entitiies

 doit or not

 method or not

 packages or not

and you can deselect a selected item. 

this way you can say I do not want any doit except this one. 

On Fri, 24 Feb 2017 06:29:36 +0100, Martin Dias <[hidden email]> wrote:

Hi. Does this report match your idea? 

https://pharo.fogbugz.com/f/cases/19686/Epicea-Filters 

Martin

On Thu, Feb 23, 2017 at 3:35 PM, stepharong <[hidden email]> wrote:

I agree :)

On Wed, 22 Feb 2017 18:10:35 +0100, Ben Coman <[hidden email]> wrote:

One thing I am missing from Epicea that I used to be able to do

is being able to filter out old changes.  If I've been thrashing 

some method back and forth between a few implementations, 

often I don't want to see *all* the old changes,only the latest ones.  

An option to restore old versions would also be nice, but I don't think that feature existed previously.

cheers -ben

--

Using Opera's mail client: http://www.opera.com/mail/

--

Using Opera's mail client: http://www.opera.com/mail/

Of course. For me it’s about 2 things:

1) I usually need to restore 100% of the changes, so having such button is convenient.

2) I think that newcomers will be confused if they just se a list without any hints what to do with it.

Uko

On 27 Feb 2017, at 05:41, Martin Dias <[hidden email]> wrote:

On Fri, Feb 24, 2017 at 12:04 PM, Yuriy Tymchuk <[hidden email]> wrote:

I have one more suggestion for Epicea. When the window pops up I’d like to have a big “RESTORE” button to reapply all the changes. I think it will be also more user friendly, as how should an newcomer know that he has to select all the items in the list and use the context menu.

Uko, maybe it could be an "Apply all" button on top of the list of changes?

 

Cheers.

Uko

On 24 Feb 2017, at 08:33, stepharong <[hidden email]> wrote:

Hi martin

Thanks for our constant improvement of epicea. 

In VW they have a nice way to filter

you can filter the entitiies

 doit or not

 method or not

 packages or not

and you can deselect a selected item. 

this way you can say I do not want any doit except this one. 

On Fri, 24 Feb 2017 06:29:36 +0100, Martin Dias <[hidden email]> wrote:

Hi. Does this report match your idea? 

https://pharo.fogbugz.com/f/cases/19686/Epicea-Filters 

Martin

On Thu, Feb 23, 2017 at 3:35 PM, stepharong <[hidden email]> wrote:

I agree :)

On Wed, 22 Feb 2017 18:10:35 +0100, Ben Coman <[hidden email]> wrote:

One thing I am missing from Epicea that I used to be able to do

is being able to filter out old changes.  If I've been thrashing 

some method back and forth between a few implementations, 

often I don't want to see *all* the old changes,only the latest ones.  

An option to restore old versions would also be nice, but I don't think that feature existed previously.

cheers -ben

--

Using Opera's mail client: http://www.opera.com/mail/

--

Using Opera's mail client: http://www.opera.com/mail/

Uko: OK, added it as: https://pharo.fogbugz.com/f/cases/19768/Epicea-Lost-Changes-Detector-Add-Apply-all-button-on-top-of-the-list-of-change

Stef: I see... each line should have a checkbox. I remember to see in Spec's FastTableModel a method to enable that... I will try.

Ben: I think that's not necessary because the EpLostChangesDetector already opens a browser where only the "lost changes" are visible. Where "lost changes" means everything logged by Epicea after last Image Save. 

On Tue, Feb 28, 2017 at 7:04 AM, Martin Dias <[hidden email]> wrote:

Uko: OK, added it as: https://pharo.fogbugz.com/f/cases/19768/Epicea-Lost-Changes-Detector-Add-Apply-all-button-on-top-of-the-list-of-change

Stef: I see... each line should have a checkbox. I remember to see in Spec's FastTableModel a method to enable that... I will try.

Ben: I think that's not necessary because the EpLostChangesDetector already opens a browser where only the "lost changes" are visible. Where "lost changes" means everything logged by Epicea after last Image Save. 

I paid particular attention this time to starting after a crash and one thing I'm uncertain about.

Its good that the window says "Lost Changes Detected"

but its not clear the meaning at the bottom where it says "22 filtered entries"

Does this mean these 22 entries were not lost?

Or is it some other reason?

Also, I've a (only mild) concern that I can't see what these other entries are, since I don't know if they are important? 

Can you make it more explicit what the filter is?

Oh, after a while I realise there is a tab for this.

Perhaps at the bottom of the changes list

you could say   "22 filtered entries (see Active Filters tab)"

to help slow people like me.

So if 'remove all filters", what is the easy way to return to 

the identical previous "Lost Changes" filter.

I realise now that I've been missing the old "indication of save points"  

Then I guess I'd be able to select that line and filter "afterwards"

cheers -ben