Long standing feature request

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Long standing feature request

Youssef Mahmoud
Hey folks,

Does anyone know if any active Evo developers are aware of this bug
report (feature request)?: https://bugzilla.gnome.org/show_bug.cgi?id=2
07624

Youssef
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Long standing feature request

Andre Klapper
Hi Youssef,

On Fri, 2017-05-19 at 10:51 -0400, Youssef Mahmoud wrote:
> Does anyone know if any active Evo developers are aware of this bug
> report (feature request)?:
> https://bugzilla.gnome.org/show_bug.cgi?id=207624

Developers (and anyone else) can be aware of all bug reports, as all
bug reports are public.

As (wo)manpower is very limited it's likely that nobody will work on it
in the foreseeable future. Everybody is free to propose code changes
(providing a software patch) if they want to see that bug fixed.
See https://wiki.gnome.org/Git/Developers for more information.

Thanks,
andre
--
Andre Klapper  |  [hidden email]
http://blogs.gnome.org/aklapper/
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Long standing feature request

Youssef Mahmoud
Alright, some follow-up questions to that:
-Who sets the development priorities for Evolution?
-Are they aware that this is a standard feature of pretty much every
other modern email client in existence, and that this request is 15
years old now?
-Is there a way I can encourage an experienced dev who's already
familiar with the code base to work on this? I currently donate monthly
to the Gnome Foundation, but perhaps an extra donation or a payment
directly to the developer?

-----Original Message-----

Date: Fri, 19 May 2017 19:01:44 +0200
Subject: Re: [Evolution] Long standing feature request
To: [hidden email]
From: Andre Klapper <[hidden email]>
Hi Youssef,

On Fri, 2017-05-19 at 10:51 -0400, Youssef Mahmoud wrote:
> Does anyone know if any active Evo developers are aware of this bug
> report (feature request)?: 
> https://bugzilla.gnome.org/show_bug.cgi?id=207624

Developers (and anyone else) can be aware of all bug reports, as all
bug reports are public.

As (wo)manpower is very limited it's likely that nobody will work on it
in the foreseeable future. Everybody is free to propose code changes
(providing a software patch) if they want to see that bug fixed.
See https://wiki.gnome.org/Git/Developers for more information.

Thanks,
andre


_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Long standing feature request (Undo operation)

Pete Biggs

I've added what the mysterious feature request is to the subject line
since it's not mentioned anywhere ...


> -Are they aware that this is a standard feature of pretty much every
> other modern email client in existence, and that this request is 15
> years old now?

It may be 15 years old, but it's only got 31 comments on it and there's
a massive gap of 5 years 2010-2015 with only 10 comments in the last 10
years. So, TBH, there doesn't really seem to be a massive clamouring
for it.

Yes, it might be a useful thing and I might use it once or twice a
year, but I can see that to do it properly it would have to be built
into every operation and that is a massive task and something that
affects the whole of the gui codebase I presume - possibly even the
other backend components (if, in between deleting and undoing, another
client expunges, then that needs to be handled and involves the
backends).

I don't think it's as easy as some of the bug comments seem to think.

P.
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Long standing feature request (Undo operation)

Youssef Mahmoud
Pete,

> It may be 15 years old, but it's only got 31 comments on it and
> there's
> a massive gap of 5 years 2010-2015 with only 10 comments in the last
> 10
> years. So, TBH, there doesn't really seem to be a massive clamouring
> for it.

Perhaps not, but there are also 6 subsequently filed bugs that were
closed as duplicates, and probably many more people who just don't know
that bug reports can be used to request features in addition to
reporting things that are broken.

> Yes, it might be a useful thing and I might use it once or twice a
> year, but I can see that to do it properly it would have to be built
> into every operation and that is a massive task and something that
> affects the whole of the gui codebase I presume - possibly even the
> other backend components (if, in between deleting and undoing,
> another
> client expunges, then that needs to be handled and involves the
> backends).
>
> I don't think it's as easy as some of the bug comments seem to think.
That's disappointing, but understandable. Do you think the difficulty
of implementing this is unique to Evolution's design, or is it just the
way things are in general? I only ask because of the prevalence of this
feature in other email clients I've used.

Youssef
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Long standing feature request (Undo operation)

Patrick O'Callaghan
On Fri, 2017-05-19 at 14:30 -0400, Youssef Mahmoud wrote:
> That's disappointing, but understandable. Do you think the difficulty
> of implementing this is unique to Evolution's design, or is it just the
> way things are in general? I only ask because of the prevalence of this
> feature in other email clients I've used.

Probably an historical accident. AFAIK Evolution was designed from the
outset with a focus on IMAP mailing, and in an IMAP context an Undelete
feature is redundant since "mark for deletion" can easily be reversed.
IMAP was explicitly designed to work this way, though some
implementations seem to have forgotten it (Gmail for example). I
suspect POP is mainly there for backwards compatibility, while EWS is a
relatively recent addition. An Undelete function would need special-
case code for each one as they all use different storage backends (and
more than one in the POP case).

This is all supposition by the way, but it seems plausible.

poc
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Long standing feature request (Undo operation)

Pete Biggs
In reply to this post by Youssef Mahmoud

> > Yes, it might be a useful thing and I might use it once or twice a
> > year, but I can see that to do it properly it would have to be built
> > into every operation and that is a massive task and something that
> > affects the whole of the gui codebase I presume - possibly even the
> > other backend components (if, in between deleting and undoing,
> > another
> > client expunges, then that needs to be handled and involves the
> > backends).
> >
> > I don't think it's as easy as some of the bug comments seem to think.
>
> That's disappointing, but understandable. Do you think the difficulty
> of implementing this is unique to Evolution's design, or is it just the
> way things are in general? I only ask because of the prevalence of this
> feature in other email clients I've used.
>
I suspect it's something that is "trivial" if it's designed into the
application from the beginning, but distinctly non-trivial to bolt on
afterwards. What I mean is that if it's something that is an intrinsic
part of the application, then whenever a new function is implemented,
some thought is put into the do-undo-redo process, and the way a
function is coded may well be determined by the undo requirements.
However, to retrofit it, that process has to be gone through for
everything - someone has to go through and analyse the code for every
function and action and work out how to do the undo, and it's not
unimaginable that a whole action will have to be re-coded just to
accommodate the requirements of the undo.

P.

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Loading...