155554 - Suggestion for redesign of AB properties, separating visiting & mailing address

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Address Book & Contacts, enhancement)

Description

[Hakon]

Just a suggestion for the Address Book ui, focusing on the Properties window...
I think it would be neat to separate mailing address and visiting address,
that would also allow insertion of some new items withoug bloating.
I think it would be more user-friendly to have the tabs like this:
 .............. ............. ..............
:   Contact   :   Location   :   Personal   :

-- Phone numbers, mailing address, email addresses; would be at -> Contact
-- Visiting address would go to -> Location - including new items:
neighbourhood; county/municipality; storey/floor #; (maybe some extra info like)
"take the stairs; at the backyard"
-- The "Other" information would be at -> Personal, along with name, nickname etc.

...because you choose a tab based on what you want to do.
The current design is a little unclear. For example "Name" contains more than
names, email addresses and phone numbers. And email address is indeed also an
"Address", so that's just a little confusing.

Comments please.:)

Comment 1

[Hakon]

Okay, one downside with this would be that since visiting address and mailing
address is mostly similar (regarding street address), it would be awkward to
enter that information twice.
Maybe there should me some convenient copy-function for that, without forcing a
copy.
I forgot to mention why I fancied a separation of mailing and visiting address.
Well because then the display would be more "clean", if you could sort it like this.
 .............
:   Contact   :

Street:
P.O. Box: (*new*)
City:
Zip Code:

 ..............
:   Location   :

Street:
Storey/Floor:
Neighbourhood:
City/county/municipality:

[Map button]

Comment 2

[Alex Bishop]

Moving to Browser/User Interface Design, marking NEW and CC'ing jglick.

This should probably be discussed in n.p.m.ui.

Comment 3

[Michael Lefevre]

guess Alex's confirmation didn't happen because of the bugzilla bug that existed
with reassigning and confirming at the same time...

really confirming.

Comment 4

[timeless]

uid is being phased out.

Comment 5

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420