Re: [Gramps-devel] gep 21, compound surnames

[Doug B. <dou...@gm...>]

On Mon, Oct 25, 2010 at 7:51 AM, Nick Hall <nic...@ho...> wrote:
>
>
> Benny Malengier wrote:
>>
>>
>> 2010/10/25 jerome <rom...@ya... <mailto:rom...@ya...>>
>>
>>     Benny,
>>
>>     > Is it complexer than before? The original editor shows the same
>>     fields, so it should not be more complex.
>>
>>     Yes editor provides an access to the same fields than before, but
>>     there was also two selectors (prefix/suffix; patronym/title), and
>>     no group (given, surname). So it was a little bit more "ventilated".
>>
>>     I did not tested gep21 before (separated branch), my first
>>     impression after opening the new Editor was like opening a door
>>     with some VIP and you should not be there. My first reflex will be
>>     to close the door and ask for excusing me! Then I re-open the door
>>     because it is the only one door.
>>
>
> I agree with Jerome.  I was a little bit shocked when I first opened the
> new editor.
>
> The fields seemed scattered.  I think that in such an important editor,
> the fields should be in a simple, natural order.  The purpose of each
> field should be immediately obvious even at a first glance.

We all know that creating a pretty good UI is hard to make pretty, and
hard to get right :)

Some ideas comments:

1) Perhaps an expand/collapse would be good here. I was confused that
I couldn't collapse what the "Use Multiple Surnames" expanded. (I
agree with Nick that maybe the columnar table isn't the right thing
here.)

2) Perhaps an "Advanced..." or "More..." button to show more details.
It is pretty over whelming at first glance.

3) The Name Format Editor probably needs a help button. There is a lot
of text there, but I need to read more.

4) Perhaps a config option would be useful to have UI defaults useful
for different cultures. Maybe a "Classic" option would be useful to
hide the complexity if it is not needed.

-Doug

>
>>
>>     I understand the logic for the emplacement and grouping.
>>     But was it not possible to use two "vertical" columns (like
>>     before) for the two groups ? This make one additional row ?
>>
>>
>> This did not work with the size of the picture.  The GUI is not
>> written in stone, but there is little room for maneuvring. I did give
>> it some thought.
>> Eg, for family name we need 3 fields. This does not fit next to the
>> image. Therefore they are under it. Also, surname must be able to hold
>> long surnames, so needs space.
>>
>> Note also how I tweaked resizing the interface, that should be much
>> better than before (all columns expanding, text labels not expanding, ...)
>>
>> I think your main problem is that you are used to the previous editor :-)
>
> I didn't particularly like the previous editor either, but at least it
> was neater.  I think that we have an opportunity now to come up with
> something better.
>
>
>> Anyway, personally I'd like to hide some of the General section.
>> Perhaps tags need not be so long and can fit on the line with Gender?
>
> I tried to make the position of the tags consistent in the four editors
> consistent, but there is no reason why it can't be changed.  If the
> length of the tag list is bigger then the space available they are shown
> with an ellipsis, and the full list can be seen in the tooltip.
>
>>
>>
>>     > People who need compound surname (spain, brazil, ...) will want
>>     quick access.
>>
>
> Yes, people from Spain or Brazil should be equally at home with the
> editor as the English or Americans.
>
>
>>
>>     For the compound surname, this is a new tab and not a field by
>>     default. We are displaying value and need to click on a button for
>>     editing.
>>
>>
>> No, the table is directly editable. Just tab and enter on it. It can
>> be difficult to discover this, but that is a GTK thing I can do little
>> about. The manual will have to explain it carefully. So no need to
>> click the button to edit the compound surname.
>> If you enter after edit, it is stored. I implemented TAB and CTRL+TAB
>> (shift is grabbed by GTK unfortunately) to move between fields and
>> automatically set it editable. Enter is needed after a change to
>> register it though.
>
> This is one case where I don't think a treeview looks right.  Perhaps we
> should consider dynamically building the interface with simple data
> entry fields?
>
>>
>>
>>
>>     To click on name Editor button (with compound surname edition
>>     still active) should be the same as click on current button ?
>>
>>
>> I don't follow. Name editor holds group as, fam nick, sort as, name
>> date.
>>
>>
>>     Compound surname might be displayed on Editor title and set on
>>     display preferences ?
>>
>>
>> What do you mean. Name display is as before. There are only much more
>> options now. See in preferences Display Name Editor, that allows to
>> try out some name formats.
>
> I have a suggestion.  Why don't we have a drop-down with the different
> entry formats listed (e.g. English, Spanish, ...).  When the user
> selects a format then we build the entry form dynamically based upon
> some parameters (such as number of surnames).
>
> For "English" we would have one surname, but for "Spain" we could have
> two (is this correct?).
> We could exclude fields in some formats - Family Nickname and Call Name
> have little use for "English".
> We could change the labels for some formats to make the purpose of the
> fields clearer ("Family Nickname" could become "Farm Name").
> We could combine the Nickname and Call Name fields, but disable the
> validation in some formats.
> We could store a default entry format in the preferences.
>
> I didn't follow the original discussion very carefully because I didn't
> think that it would affect me, so perhaps this idea won't work.  What do
> you think?
>
> Regards,
>
>
> Nick.
>
>
>>
>> Benny
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
>> Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
>> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
>> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
>> http://p.sf.net/sfu/nokia-dev2dev
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Gramps-devel mailing list
>> Gra...@li...
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>