Add separate table for sandbox projects on user-specific project view

Note that the table in question isn't a view, but is hard-coded in project_issue_my_projects_table().

If all else fails, I can probably get to it over the weekend once packaging is done...

I'll work on this today during my break in class. I'll probably be offline. So, just wanted to assign to myself so no one else duplicates the effort. I'll hopefully post a patch late tonight when I'm back online.

Cheers,
-Derek

Here's an initial patch. Still not done, since I really need to talk to someone about the UI for all this. There's currently no exposed filters on the top table at all, only the bottom table (the issues for the given projects). So, I'm not sure where/how to add the exposed filter. The attached patch at least modifies the query based on $_GET['sandbox'], so we could link directly if we wanted, but there's no way to toggle this via the UI itself.

Also, I'm not thrilled with adding a whole new column for the sandbox bit. I'd rather prepend "Sandbox: " to the project titles, maybe with a warning icon. Here's what it looks like in Garland given the current patch:

I think we need to separate "Official projects" from "Sandbox projects", this to make the conceptual separation between the two even more clear. This would mean two tables, one for official projects and one for sandboxes.

Project by a

Table of official projects

Sandbox's by a

Table of Sandboxes.

Right. Bojhan and I had a good IRC UI chat here. The "filter" as such won't exist. But, we'll have a href anchor on the 2nd table so you can link to http://drupal.org/project/user/dww#sandbox or something if you want to jump to the 2nd table from somewhere else. The existing patch is basically useless at this point, so back to active for a whole new approach. ;) I'll work on it later today or this evening. Gotta run for a class right now.

Yay, much better.

The only minor problem here is that drupalorg_crosssite is doing whacky things with the page title and navigation on this page when it's a subtab on your dashboard/profile. See the difference between

http://drupal.org/project/user

and

http://drupal.org/project/user/[your-username]

For example, http://drupal.org/project/user/dww

So, that's going to slightly complicate things in the case where a user is viewing their own page and all they have are sandboxes. There's not going to be anything indicating they're just sandboxes. But, it's only for the user themselves. If someone else is viewing their page, it's going to need the final argument, and then things should work fine. I don't know if we care, but I wanted to raise it for consideration...

Also, tagging for a UX review, although presumably Bojhan will see this since he's already subscribed...

p.s. One thing we could do is use a "Sandbox project" as the column header for the first column in the table for sandboxes. That way, even in the case in #10, we still have a slight hint we're looking at sandboxes.

I don't want to add a whole new column if we don't have to. This table is already a bit cluttered and very full, and we've got a fixed # of pixels to work with. Plus, it's redundant to have the same value in every row in the column for each table. But, I could at least change the column header on the sandbox table as I mentioned.

Dww's screenshot looks good.

Great, hearing no further objections, I committed to project_issue HEAD. This will be live on git-dev on the next rebuild.

Something tells me project_issue hasn't been upgraded and deployed on git-dev.

http://drupal.org/cvs?commit=486278

And lo. The copy of project_issue.module on git-dev is:

// $Id: project_issue.module,v 1.190 2011/01/15 17:59:53 dww Exp $

Not sure why this isn't getting merged and deployed. I thought sdboyer had a script that does that automatically...