This is a test about what is possible with trac.
This is a draft for the search members application of BW Rox
See also http://www.bevolunteer.org/wiki/Find_members_page
Page context
You can get here by clicking "Members" in main menu (?)
The search generates results and displays the found members on the map and/or in a list. You can then pick a profile to get to a ProfilePage.
People
Matrixpoint Micha (Layout) Matthias (Layout)
Code
On test: http://test.bewelcome.org/searchmembers/index On live site: http://www.bewelcome.org/findpeople.php
Drafts
Newstyle 2 by Micha, 17. November 2007: Description: fullscreen layout (without columns), fullwidth-map, buttons integrated IN google maps, advanced results-list, chosen/marked user feature (group some found members for temporary use)
the draft as .png:
Hey Micha! Nice draft, so far :) maybe we could even use the tech blog to publish and discuss? I think it's the perfect tool for that purpose! Better suited than the forum, because it will be easier to find things later. -> use category "request feedback", and tags "findmembers page" and "graphical draft". Or something in that direction... One thing I would change is replace "search boundaries" by "search in visible map area", or "restrict search to visible area" or "find in visible area".. would make it more obvious, what "boundaries" means.
I agree. Better wording needed. But let's ask John for that. He's the native here ;)
Then the dropdown next to the search field, saying "place". This could have different meanings: (i) the keyword you type is a placename, and the search results will be anything close to / associated with that place. (ii) the keyword you type can be just anything, and the results will be places associated with that keyword. Or even (iii) the keyword means a placename, and the result will again be a location which fits the placename. Of course, one could guess what is meant, but it's better to be leave no doubts.
I really don't think this leads to doubts. But anyway, we could try to make that more clear.
I am sure I will nag around more later ;) Cheers, Andreas (damn there is no comments function in the trac pages !!)
so long, Micha
Hi Micha,
Interesting ideas!
I think I see 4 improvements you are proposing:
1. Full-width map 2. Map boundary search and clear map buttons are on the map. 3. Global search button removed. 4. Input fields combined into one with a pull-down to distinguish search cases: member, keywords, location 5. All help and tips hidden behind a button. 6. Grouping members already viewed.
Comments:
1. I prefer a big map. To me, this is more important than having a few links in the left column as there is now on test.
2. I don't see an advantage to having the boundary search button on the map, and a disadvantage is that it covers the map. I would rather see it close to other buttons with a similar function, namely searching. On the other hand, the 'clear map' button is comparable to the other buttons on the map, and it's directly about managing the map, so that one makes more sense to me to put on the map.
3. I don't think there needs to be a separate global search button. As long as it is clear that searching with the 'place' field blank is a global search by default.
4. Combining the input fields is functionally sound and also an economical use of the space, but the risk is that it becomes less obvious what the options are and the sequence of steps. There is a trade-off between elaborate instructions and step-by-step sequencing (great for the novice but cumbersome for the familiar user) and a condensed, streamlined presentation (great for experts but baffling for newbies).
Our current page definitely leans in the former direction while your proposed layout leans in the latter. Which is best? I think this is something best decided by a focus group that includes non-technical people. Designers and coders often have a different perspective than general users. My inclination is to err on the side of too much visible instruction and obvious sequencing, at least in the beginning.
5. Already addressed in #4, but I would add that there are several compromises that could provide enough help for a novice user but still keeping the design elegant: Context-sensitive help (little question-mark icons that are clicked on or just rolled-over with the mouse to provide context-sensitive help balloons or sidebar help, if a sidebar is used).
6. Grouping members. Seems OK, and wouldn't be too hard to code, but I'm not sure how valuable this one is.
General comment: There are several excellent ideas to work with here, but I really don't think this should be rushed. Compared to the current live version, the version currently on test is a huge improvement and has been waiting to go live (in some form) since August 30. Even though all the changes proposed are doable and manageable, together they represent a significant enhancement and a significant amount of work. Most of the changes impact usability and so I would feel better if they are reviewed and tested thoroughly preferably by a group including ordinary, non-technical members.
Also, there are many other potential improvements to this page that should be brought into the mix, so that that they can be considered in relation to one another and prioritized.
So, my suggestion is, do whatever is necessary to get the current version live, then prepare for the next release.
John
Tickets
- #28
- searchmembers improvements
- #43
- searchmembers: Allow search without restriction on map boundaries
- #44
- searchmembers: Disable map is not working anymore
- #131
- searchmembers, submit by enter not working
- #132
- searchmembers, map not working
- #135
- Preparing searchmembers for release.
- #146
- searchmembers: remember search parameters
- #210
- pictures not found in searchmembers
- #215
- searchmembers: "search using map boundaries" fails in Opera 9.24
- #304
- MOD_layoutbits is breaking searchmembers ajax xml
- #351
- searchmembers ajax not working in Opera / no php closing tag ('?>') in some module files
- #354
- Three possible views + session store of results for searchmembers page
- #361
- searchmembers/ajax in Opera
- #362
- words in searchmembers/ajax XML - quick fix
- #413
- Searchmembers Google map markers -- improve placement
- #492
- searchmembers: no search in german
- #667
- Add contact-indicator to results in searchmembers
(see TracQuery to find out how to create such a list)
