if under ~150 contacts, people index page is too many divisions

[rejon]

If < ~150 public profiles, then the tri-column list should not have alphabetical divisions and just be solid....

150 might not be enough...the goal is that most will have less than 150-200 and that should try to fit in the main window.

after that number, then we should switch to the alphabetical section headers...

is that enough info to conquer this?

[Brad Phillips (brad-bradphillips)]

I think that's doable, but what about sorting the usernames?

The current alphabetical by last name solution isn't ideal, as in yumumu, because the full_name field contains both first names, last names, and other times they aren't names at all. Currently, any "full_name" entries with numbers or non-alphanumeric characters as the first character in the last string (i.e. my twitter 2007, or Brad Phillips .ORG) aren't included in the public list. Also if their full_name is only 1 string including no spaces (i.e. Brad), they aren't listed here either.

I did this as temporary solution just to get a visual setup. I can arrange to have these other conditions included, but I think we should tackle a better method of sorting the users (separating out full_name would be better solution, I think) before determining further conditions on the sorting.

[Christopher Adams (christopheradams)]

I agree we should deal with handling names before the exact type and
arrangement on the index. This would need a new bug.

On Sat, Jan 29, 2011 at 3:57 AM, Brad Phillips <email address hidden>wrote:

> I think that's doable, but what about sorting the usernames?
>
> The current alphabetical by last name solution isn't ideal, as in
> yumumu, because the full_name field contains both first names, last
> names, and other times they aren't names at all. Currently, any
> "full_name" entries with numbers or non-alphanumeric characters as the
> first character in the last string (i.e. my twitter 2007, or Brad
> Phillips .ORG) aren't included in the public list. Also if their
> full_name is only 1 string including no spaces (i.e. Brad), they aren't
> listed here either.
>
> I did this as temporary solution just to get a visual setup. I can
> arrange to have these other conditions included, but I think we should
> tackle a better method of sorting the users (separating out full_name
> would be better solution, I think) before determining further
> conditions on the sorting.
>
> --
> You received this bug notification because you are a member of PPL
> Developers, which is subscribed to PPL.
> https://bugs.launchpad.net/bugs/709437
>
> Title:
> if under ~150 contacts, people index page is too many divisions
>
> Status in PPL:
> Confirmed
>
> Bug description:
> If < ~150 public profiles, then the tri-column list should not have
> alphabetical divisions and just be solid....
>
> 150 might not be enough...the goal is that most will have less than
> 150-200 and that should try to fit in the main window.
>
> after that number, then we should switch to the alphabetical section
> headers...
>
> is that enough info to conquer this?
>
>
>

[Christopher Adams (christopheradams)]

Brad, just keep the list alphabetical by the first character in the
full_name. Don't bother trying to parse it to first name and last name.

On Sat, Jan 29, 2011 at 5:04 PM, Christopher Adams <email address hidden>wrote:

> I agree we should deal with handling names before the exact type and
> arrangement on the index. This would need a new bug.
>
> On Sat, Jan 29, 2011 at 3:57 AM, Brad Phillips <email address hidden>wrote:
>
>> I think that's doable, but what about sorting the usernames?
>>
>> The current alphabetical by last name solution isn't ideal, as in
>> yumumu, because the full_name field contains both first names, last
>> names, and other times they aren't names at all. Currently, any
>> "full_name" entries with numbers or non-alphanumeric characters as the
>> first character in the last string (i.e. my twitter 2007, or Brad
>> Phillips .ORG) aren't included in the public list. Also if their
>> full_name is only 1 string including no spaces (i.e. Brad), they aren't
>> listed here either.
>>
>> I did this as temporary solution just to get a visual setup. I can
>> arrange to have these other conditions included, but I think we should
>> tackle a better method of sorting the users (separating out full_name
>> would be better solution, I think) before determining further
>> conditions on the sorting.
>>
>> --
>> You received this bug notification because you are a member of PPL
>> Developers, which is subscribed to PPL.
>> https://bugs.launchpad.net/bugs/709437
>>
>> Title:
>> if under ~150 contacts, people index page is too many divisions
>>
>> Status in PPL:
>> Confirmed
>>
>> Bug description:
>> If < ~150 public profiles, then the tri-column list should not have
>> alphabetical divisions and just be solid....
>>
>> 150 might not be enough...the goal is that most will have less than
>> 150-200 and that should try to fit in the main window.
>>
>> after that number, then we should switch to the alphabetical section
>> headers...
>>
>> is that enough info to conquer this?
>>
>>
>>
>

[Brad Phillips (brad-bradphillips)]

Ok, the sql has been altered to line everything up by first character of full_name field & is working as expected now.

[Brad Phillips (brad-bradphillips)]

Cool, so I've restructured the people widget to inherit 1 of 2 possible content widgets: "people_list_alphabetical" or "people_list_combined". Via some of that <php php> in the people widget, If the SQL pulls in less than 150 results (public profiles), then the list is displayed combined, while the alphabetical list is employed in the other case. I don't have 150 contacts, but it worked as expected when testing with a lower number.

[rejon (rejon)]

You rule! Awesome!

On Sun, Jan 30, 2011 at 6:44 AM, Brad Phillips
<email address hidden> wrote:
> Cool, so I've restructured the people widget to inherit 1 of 2 possible
> content widgets: "people_list_alphabetical" or "people_list_combined".
> Via some of that <php php> in the people widget, If the SQL pulls in
> less than 150 results (public profiles), then the list is displayed
> combined, while the alphabetical list is employed in the other case.  I
> don't have 150 contacts, but it worked as expected when testing with a
> lower number.
>
> ** Changed in: ppl
>       Status: Confirmed => Fix Released
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/709437
>
> Title:
>  if under ~150 contacts, people index page is too many divisions
>

--
Jon Phillips
http://rejon.org/ | http://fabricatorz.com/
chat/skype: kidproto | irc: rejon
+1.415.830.3884 (sf/global) | [phone] (berlin)