After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 207442 - Finish GalView
Finish GalView
Status: RESOLVED FIXED
Product: GAL
Classification: Deprecated
Component: GalView
trunk
Other All
: Normal enhancement
: 1.1.x
Assigned To: Chris Lahey
Evolution QA team
: 209461 219053 219331 (view as bug list)
Depends on:
Blocks: 216096 219053
 
 
Reported: 2001-08-16 18:34 UTC by Dick Porter
Modified: 2005-11-15 02:22 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Dick Porter 2001-08-16 18:34:34 UTC
Description of Problem:

I wanted to add a 'Size' header for all mails.  I have about 50 folders.  I
have to click and drag to _each and every one_ of them.


Expected Results:

I would have hoped to be able to apply this change to all folders.  I've
also reported that it's impossible to resize the columns in all folders
easily: this is another manifestation of that same usability problem.
Comment 1 Peter Williams 2001-08-16 19:20:11 UTC
But at the same time, you don't necessarily want all of your mailboxes
to have the same column layout. So I'd say that we would actually have
to implement some kind of table-header-editor to implement this correctly.
Comment 2 Dick Porter 2001-08-16 20:20:07 UTC
Personally, my own usage of folders tends to favour the same set of
headers across each.
Comment 3 Peter Williams 2001-08-16 21:10:00 UTC
Mine doesn't :-)

For instance, my bugzilla folder and vfolders don't have the 'From' or
'Attachment' headers, since with bugzilla mails these never change. So
I can have the subject take up almost the entire width of the table.
This, of course, would not be reasonable for a mailing list.
Comment 4 Luis Villa 2001-08-17 20:24:27 UTC
As a result of the UI freeze today, I'm marking all remaining non-1.0 UI bugs to
'future'. Someone reading this should only change the target back to 1.0 under
the following circumstances:
1) The change would not impact documentation. (i.e., 'how to do X' would not
have to be changed in any way.)
2) The change would require trivial work for the programmers involved. Most
likely, only the programmers themselves are able to judge this. So, if you are
not on the evo team, or cannot provide a patch to them for this, you should
probably not make any such changes. 
Sorry that this is going to impact so many irritating bugs, but we have to
prioritize our limited resources.
Comment 5 Nat Friedman 2001-10-12 07:12:22 UTC
Setting this to 1.1 and assigning to Anna to think about how to make
this configurable.  If this proves hard, it may be 1.2.
Comment 6 Not Zed 2001-10-19 02:22:42 UTC
Just a random thought:

Have a 'template' folder layout, that can be:
 1. applied to all existing (or specific) folders
 2. used as a default for any new folders created/opened for the first
time (e.g. imap/maildir/etc)
 3. maybe used always

The last is just opening the same file all the time.
The others are variations of that/copying files about.

Comment 7 Not Zed 2001-10-19 02:23:06 UTC
(and clahey code may be required)
Comment 8 marten ter borgh 2001-11-12 22:06:02 UTC
*** bug 209461 has been marked as a duplicate of this bug. ***
Comment 9 Luis Villa 2001-11-26 17:04:07 UTC
Because of the decision to remap 1.1->1.2 and 1.2->1.4, I'm going to be
moving a large number of bugs around in the bugzilla. You can just
search on 'body contains' 'Because of the decision to remap' and mark
all as read. Please direct all questions about this change to
evolution@ximian.com, not the bug.
Luis

Comment 10 Chris Lahey 2001-12-07 02:14:38 UTC
This is part of GalView.  I'm reassigning and removing the time
estimate since it's a gal thing, not a mail thing.  The design and
most of the code for this is already done.  I just need to finish it.
 It will need to go through some design revisions, but since it's so
close to being coded, I think it makes more sense to do the bit of
work to finish the way it is and work from there than to start from
scratch at this point.
Comment 11 Chris Lahey 2002-01-22 23:08:22 UTC
*** bug 219053 has been marked as a duplicate of this bug. ***
Comment 12 Chris Lahey 2002-01-29 02:10:47 UTC
*** bug 219331 has been marked as a duplicate of this bug. ***
Comment 13 Chris Lahey 2002-02-02 07:25:42 UTC
*** bug 209461 has been marked as a duplicate of this bug. ***
Comment 14 Chris Lahey 2002-02-07 20:41:39 UTC
This is committed and should be pretty usable.  Any bugs or missing
features in the new code should be submitted as separate bugs.