Comentários (40)

1 localhost comentou às Link permanente

also the easiest way is. select contacts. drag to desktop and there is the vcard file. BOOM you'r done. see apple's address book aplication. make it dead easy. give multiple dialog boxes to the propeller heads!

2 localhost comentou às Link de Retorno

"Pick a default and move on" and "UTF-8" is the answer for all three as the end user should never be asked something that will only generate support calls.

On 2, also include view titles, vaD quv vo''oH.

3 localhost comentou às Link permanente

I agree with the others, these questions only confuse people.However, you should provide a dialog box with these options that you can change somewhere, i.e. an "Advanced Options" checkbox, or something in properties to allow a change, make it hidden from initial view. Please do not make it too deep however.Regarding 3, please take a leaf from DB2, and allow the user/operator to type in a letter and/or a dialog box instead of just character code. Yes character code is useful, but so would something simple, as not everyone I talk to has ASCII codes memorized.

4 localhost comentou às Link permanente

1. Pick a sensible default AND leave the option there--or at least, make this configurable somewhere/somehow. I'm not sure which makes more sense, but I'm thinking "native." BTW, I'm surprised "native character set" doesn't isn't "default character set" like in #2; shouldn't it be?

2. Last I checked, UTF-8 was an encoding for Unicode; so if I select Unicode, what character set do you use?! Again, I dislike removing options; leave the sensible default you have there ("default character set"). BTW, Ted's slightly more likely to change the 'details' checkbox than the character set, so why not make the 'details' portion first? That makes it easier to ignore the character set.
3. It's tough to imagine "Ted" exporting contacts to structured text at all; I expect developers & admins to be more likely to do this. So, please don't remove options here. Again, put the word wrap option first, since it's more likely to be changed.

5 localhost comentou às Link de Retorno

Why the inconsistency between "Native character set" and "Default character set"? Is there a difference? I suspect not. I suspect that both are trying to express "Use the character set supported by my computer's OS". But if there is a difference, it's a really, really subtle difference. Ted surely doesn't understand that level of subtlety. Either way, he's headed for confusion.

And as Kendall has already noted, UTF-8 is an encoding of Unicode. And UTF-8 and Unicode both equally deserve to be described as "International". The choice you are most likely trying to convey is between "International - Unicode (UTF-8)" and "International - Unicode (UTF-16)". Seems to me that if the designer of the dialog doesn't understand how to express this choice precisely, that proves that Ted doesn't stand a chance.
There is hardly ever any reason why you need control over character set choice for an export, but never say never. The choice can be hidden behind an "Advanced Options" button, but not removed.

6 localhost comentou às Link permanente

If Ted is like the average Notes user I support he will be so confused/afraid of these questions he will convince himself he probably doesn't need that export after all.

7 localhost comentou às Link permanente

Ted wouldn't know and neither would most Domino Admins (if they were honest). It's time to make things easy for the Notes users; They don't want multiple ways of doing the same thing with more options than you could shake a stick at - they just want to do it quickly and easily.

I know this is heresy but one of the reasons people like Outlook is because it's easier to use and has less options to confuse the user.
Please make Notes easy to use, keep the "advanced" stuff behind a button for the adventurous.

8 localhost comentou às Link de Retorno

No user should have to deal with codesets unless something goes wrong. If it does they'll find out why. Go with UTF-8 as standard.

9 localhost comentou às Link de Retorno

Mikkel - Why UTF-8? IMHO, the correct behavior for each one is the "most compatible". For VCard, what do the most popular programs that import/export that format use? For CSV and Structured Text, what is the default encoding used by the native text editor of the client platform? (In the event that the native text editor auto-detects character encoding, which I believe is true of Notepad on Windows, then the best auto-detected encoding -- probably UTF-16 -- should be used.)

10 localhost comentou às Link permanente

I think the default in these dialogs should be the default (not Unicode), otherwise why have a Notes-wide preference for import/export character set that doesn't really WORK Notes-wide. ;-)

Also, hide the character set in a collapsible section in ALL dialogs--not just for contacts. Most users will ignore it; those who know what it is can click to expand and change the option. In terms of dialog complexity versus flexibility, IMHO this is a good compromise.

11 localhost comentou às Link permanente

My users import/export contacts for various reasons:- They're a new hire and need to import their Outlook contacts.- They're leaving the company and need to export their personal Lotus Notes contacts to Outlook.- 3rd party app does not support Lotus Notes, so they need to keep their local Outlook address book updated. For example, mobile phones.- And a recent FAQ: they want to update their GMail contacts, and then push to social networks.

So in most cases they'd like an Outlook specific button.

12 localhost comentou às Link permanente

I agree with all above. The handiest thing for my users would be the option of importing outlook contacts as they often come from another business that uses outlook and wants to add their contacts.

13 localhost comentou às Link de Retorno

As per a previous comment, drag and drop contacts in and out using common contact formats..

Or, give a list of specific applications to import/export as, e.g Outlook, Gmail, etc... then if they do not pick those give them the options you are suggesting.
Notes really needs to start hiding this complexity, so ideally the drag and drop option would be best

14 localhost comentou às Link permanente

Advanced Options should be hidden with a button on the export or "Export" and "Export Advanced". The more important issue is what you are exporting to. Excel or at least the Symphony product. And make it so you don't have to create a view that represents the entire Contact form/fields to get a "complete" export of Contacts.

15 localhost comentou às Link permanente

Hi Neil,

The drag and drop got me thinking. It would be nice to be able to drag a vcf and other 'contact' files onto Notes and it would allow you to view/import them seamlessly.
At the very least, I'd like Notes to allow me to have one (1) contact document and multiple email addresses for the one person !

Incluir um Comentário Incluir um Comentário