Mockup Comparison Report #1: Overview Pages
by Máirín Duffy
Hi,
I started digging into documenting fine-grained mockup-to-app
comparisons. Here's the first chunk, and it includes general
observations and comparisons for the overview pages. I'll keep sending
these as I finish them; the next section is "my profile".
I hope this is a useful format; let me know if not. I'm trying to be
careful about checking to make sure a ticket is not already open for an
issue before I open a new ticket but if you know one or more of these
are redundant please let me know and I'll be happy to close the new
redundant one.
These are also documented on this wiki page and I'll be adding more to
the page as I go along as well:
https://fedoraproject.org/wiki/FedoraCommunity/UIReview29Apr2009
~m
******** OVERVIEW *************
= General =
# <title> tag not useful, only says fedora commnunity doesn't say what
section
## ticket 149 https://fedorahosted.org/fedoracommunity/ticket/149
# if not logged in, no right sidebars. probably if not logged in, the
login right sidebar box should be persistent across pages.
## ticket 150 https://fedorahosted.org/fedoracommunity/ticket/150
# tasks widget (currently named quicklinks, should be named tasks)
should be persistent on every page of a logged in user
## ticket 151 https://fedorahosted.org/fedoracommunity/ticket/151
= Overview (logged out) =
# latest rawhide builds in mockup, latest builds in app, is this okay?
# builds and updates grids show "viewing x of y items" - should we pull
this out? it's not in the mockup. right now builds is "Viewing 5 of
100,061 items." not all 100,061 are latest. The 5 shown in the front are
latest.
## ticket 152 https://fedorahosted.org/fedoracommunity/ticket/152
# latest builds widget - is not in my timezone. what timezone? is it
UTC? should be labeled UTC is so.
## ticket 153 https://fedorahosted.org/fedoracommunity/ticket/153
# latest builds widget - status does not have label, only icon. mockup
has labels such as 'success' or 'failure'.
## ticket 154 https://fedorahosted.org/fedoracommunity/ticket/154
# latest builds widget - in mockup, status labels are links. idea for
this could be to have a hover menu or link. if success, link to package
downloads tab or give hover menu downloads tab for rpms. if failure,
hover menu for build error logs or link out to koji page with build
error logs
## ticket 155 https://fedorahosted.org/fedoracommunity/ticket/155
= Overview (logged in) =
# the alerts widget should have two headers, your packages and all
packages. right now it has "this week" and "today" and shows alerts for
all packages only. suggest having two h4 headers, "Your Packages" and
"All Packages" and two h5 headers for each "This Week" and "Today"
## ticket 156 https://fedorahosted.org/fedoracommunity/ticket/156
# s/quicklinks/tasks
## ticket 157 https://fedorahosted.org/fedoracommunity/ticket/157
# quicklinks is missing the search tasks
## ticket 158 #preview
# "my packages" right sidebar widget missing counts in headers
## ticket 159 https://fedorahosted.org/fedoracommunity/ticket/159
# page title missing
## ticket 73 https://fedorahosted.org/fedoracommunity/ticket/73
# grid widgets on page missing display filters "Display: Packages I Own
| Packages I Maintain | All Packages") should be for each latest builds,
latest testing updates, latest stable updates
## ticket 107 https://fedorahosted.org/fedoracommunity/ticket/107
# status column for builds missing labels
## ticket 154 https://fedorahosted.org/fedoracommunity/ticket/154
# "View more" link is labeled, not just "View more" but "View more
updates" "View more builds" etc
## ticket 161 https://fedorahosted.org/fedoracommunity/ticket/161
# by default logging in i see builds for packages i own... not all, in
the mockup
## ticket 162 https://fedorahosted.org/fedoracommunity/ticket/162
14 years, 11 months
update publictest16 (all links now have static versions for opening in a new window)
by John (J5) Palmieri
In order to make this work you need to tag any link in a mako template (or even static html pages) you wish to be transformed with moksha_url="<dynamic|static>". "static" simply rewrites the href to include the csrf token and any other query string variables that are set. "dynamic" does the static rewrite but also sets up an onClick handler so that the csrf token and query string can be updated when the user clicks and not just when the page load. It will also in the future try to determine if a whole page load is unnecessary and simply switch tabs if that is the case.
The only place where you do not add moksha_url is inside of the javascript grid templates since it transforms the template, messing up the final output. The grid will take care of the template links. Come to think of it I still want you to be able to add the markers to the grid template so I am going to look at a way to tell the parser to ignore anything inside javascript templates. For now just assume all links will be transformed to a dynamic url.
--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.
14 years, 11 months
Licensing
by Tom Callaway
We've gotten the goahead to use AGPLv3. We need to have a "Get the
Source" link to our source landing page that tells people how to get the
source (not straight to the git tree) in the footer (it is sufficient
for us to meet the AGPLv3 terms). It is also compatible with the Apache
license, it has the same compatibilities as GPLv3.
~spot
14 years, 11 months
PublicText 16 updates (search and people)
by John (J5) Palmieri
Search is now working. Here are the usecases you want to hit:
* Going to the search tab while not logged in - should show basic instructions and no options for selecting people search
* Doing an unloggedin search (use 'test') - should show package results
* Logging in from the search results using the login button at top right - should bring you back to search with the same search term. you should see a packages and people search results along with check boxes underneath the search bar.
* Uncheck packages and hit the search button - should show only the people search result and packages should remain unchecked
* Uncheck people and hit the search button - should show both the packages and people search result and both should be checked
* Uncheck people again and hit the search button - should show only the packages search result and people should remain unchecked
* Hit the search tab to reset the search term - you should see a more detailed description describing the limitations of the people search
The people/package maint page now shows that persons builds, updates and alerts (updates are broken right now and will show you all updates). Packages is being worked on. To get here click on a user's name in any builds or updates grid and then select teh top Package Maintenance tab.
--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.
14 years, 11 months
update publictest 16 (open in new tab/window)
by John (J5) Palmieri
I've got tabs working as static links when you middle click or use the "open in" context menu item. We basically set the href to be a static link and set a dynamic_href data key to the dynamic address. This makes the dynamic clicks look almost invisible to the user. I still need to do this for other types of links but for now the tabs have this functionality.
--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.
14 years, 11 months
TurboGears2 status
by Luke Macken
I created a TG2 page on the wiki to track the progress of the
TurboGears2 packaging efforts.
https://fedoraproject.org/wiki/TurboGears2
Most of the open bugs just require another pass to fix some minor issues
and bring them up to speed with the latest versions. I'll try and chip
away at these throughout the week, but feel free to poke at them if you
guys are bored.
luke
14 years, 11 months
Navigation Confusion Discussion
by Máirín Duffy
Hi,
In the meeting today Spot brought up a couple of issues with the
navigation design that we've known about for a while and maybe should
address for milestone 1:
- When you're viewing the details of a package, you have three tabs on
top - Overview | Builds | Updates. Builds takes you to a list of ALL
packages' builds, updates takes you to a list of ALL packages updates,
but overview takes you to the overview for the particular package you're
looking at. It's internally inconsistent.
- When you're viewing the details of a user, the tabs across relate to
that single user, not all users. So having tabs that relate to all
packages across the top of a single package is inconsistent and thus
could bring about confusion.
I wrestled with this for much of today and came up with a mockup I'd
like to propose we go with to address this problem. Here is the mockup:
https://fedoraproject.org/w/uploads/2/22/Fedoracommunity-navrethinking-pr...
Here are the changes we'll need to make to do this:
* the tabs on the top of the package details pages should be:
* Overview
* Package Details
* Maintenance Tools
* s/Package Maintenance/Maintenance Tools - for the right nav bar
- I think this wording is more effective at communicating the
differences in the link categories.
* Add the 'All Packages' navigation with links to all packages,
builds, and updates so they are available with only one click.
Add this panel to every package details screen.
We had considered adding the subnav for 'all packages' under the
'package maintenance' tab in the left nav, but it looks a little awkward
(see
https://fedoraproject.org/w/uploads/3/39/Fedoracommunity-navrethinking-1.png ) and I am guessing would be more time-consuming to implement. Adding the 'all packages' little panel on the right-hand side I think helps address the concern about being able to access these screens with one click easily from any single package.
The general pattern we could adopt from this approach:
* Single objects (package details, people profiles) have tabs that
relate only to that single object along the top. If that single
object has more than one level of navigation, the first level of
that object's navigation is represented across the top and
sublevels are represented in a navbar panel on the righthand
side of the page.
* Lists of objects (lists of packages, lists of people) have tabs
that relate only to those lists along the top. For example, an
area of the UI that is primarily used for showing lists of
people would have tabs across the top that were different
configurations of lists of people (e.g., "All People", "New
People", "Package Maintainers" etc). Tabs that relate to any
single object should not be displayed there.
* When a single object is part of a larger collection, there
should be a panel box in all the pages of its details tabs to
link straight out to the relevant collections' navigation. For
example, within the details of any pacakge, you should be able
to link out to a list of all packages. From the details of any
user who is a member of group A, you should be able to link to a
list of all users who are members of group A.
Does this make sense? What do you think?
~m
14 years, 11 months
update publictest16 (People and Profile pages)
by John (J5) Palmieri
Except for some tweaks the people and profile pages are done. I put more links everywhere (missed one I'll get to tomorrow), created the compact info view and cleaned up some of the CSS. Mo the CSS needs to be heavily tweaked for the info stuff as it is not quite like the mockups but about 90% there. The package_maintenance page in people and profiles now have the complete 3rd level nav and look like the mockups. More links link to those pages and switch depending on if you are in people or profile though some links in profile need to be fixed to not link back to people. We also fixed up the live clock to not not display seconds as it was very distracting and having it update once a minute still makes the live clock just as useful without wasting resources both polling and updating the display once a second. I sent a patch upstream which adds the ability to specify the longer timeouts.
--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.
14 years, 12 months
publictest16 update (Yum Package Search)
by John (J5) Palmieri
Yum package search is now operational and populating through a rawhide database which is updated every hour via a cron script. Yum gets many more results because it also lists subpackages which causes a problem since the packages apps only understand parent package names. To get around this I take the srpm, chop off the version and file extensions and compare that to the package name to see if it is the parent. We only link to the parent but I asked Mo to mock up what it should look like if a user clicks on a subpackage.
--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.
14 years, 12 months
publictest16 update: (Package Maintenance overhaul complete)
by John (J5) Palmieri
Package Maintenance overhaul is now complete. The new package details and package maintenance tools tabs now get selected when clicking on any of the links in the category navigation. If we want we can even add the All Packages links to that app or just leave it as a separate app.
--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.
14 years, 12 months
