2006-10-16 02:56:09 |
Matthew Paul Thomas |
bug |
|
|
added bug |
2006-10-16 21:38:47 |
Diogo Matsubara |
blueprint: status |
Unconfirmed |
Confirmed |
|
2006-10-16 21:38:47 |
Diogo Matsubara |
blueprint: statusexplanation |
|
|
|
2006-12-07 12:53:39 |
Steve Alexander |
blueprint: importance |
Undecided |
Medium |
|
2006-12-07 12:53:39 |
Steve Alexander |
blueprint: assignee |
|
stevea |
|
2007-05-13 22:30:25 |
Jonathan Lange |
blueprint: importance |
Medium |
High |
|
2007-05-13 22:30:25 |
Jonathan Lange |
blueprint: statusexplanation |
|
Setting to "High". This makes many of our dependency charts useless, which vastly reduces the utility of the blueprint manager. |
|
2008-09-02 22:17:05 |
Christian Reis |
blueprint: assignee |
stevea |
|
|
2008-09-02 22:17:05 |
Christian Reis |
blueprint: statusexplanation |
Setting to "High". This makes many of our dependency charts useless, which vastly reduces the utility of the blueprint manager. |
|
|
2008-09-02 22:19:14 |
Christian Reis |
description |
The dependency chart is unreadable for any specification that has more than about a dozen dependencies. For example, <https://features.launchpad.net/products/launchpad/+spec/1.0-web-interface>.
This could be fixed by making the dependency levels run vertically, rather than horizontally. This would work better because specification names are shorter than they are wide, so they could be packed more closely together. |
The dependency chart is unreadable for any specification that has more than about a dozen dependencies. For example, <https://features.launchpad.net/products/launchpad-foundations/+spec/1.0-web-interface>.
This could be fixed by making the dependency levels run vertically, rather than horizontally. This would work better because specification names are shorter than they are wide, so they could be packed more closely together. |
|
2008-09-02 22:28:46 |
Martin Albisetti |
blueprint: assignee |
|
beuno |
|
2008-09-02 22:28:46 |
Martin Albisetti |
blueprint: statusexplanation |
|
As kiko says, we should look into what dot offers us today, and possibly tweak the page layout a bit so we can use the full width of that part of the screen.
A combination of those two will hopefully be enough until we have the infrastructure for 3.0 in place, and we can start using magic. |
|
2008-09-03 19:03:24 |
Martin Albisetti |
blueprint: status |
Confirmed |
In Progress |
|
2008-09-03 19:03:24 |
Martin Albisetti |
blueprint: statusexplanation |
As kiko says, we should look into what dot offers us today, and possibly tweak the page layout a bit so we can use the full width of that part of the screen.
A combination of those two will hopefully be enough until we have the infrastructure for 3.0 in place, and we can start using magic. |
|
|
2008-09-06 03:27:25 |
Martin Albisetti |
blueprint: status |
In Progress |
Fix Committed |
|
2008-09-06 03:27:25 |
Martin Albisetti |
blueprint: statusexplanation |
|
Committed a partial fix for this in revision 6962.
Showing between 20 and 30 dependencies should look "acceptable".
The long term solution will be using Ajax magic, which we will have soon-ish. |
|
2008-09-06 15:48:15 |
Martin Albisetti |
blueprint: status |
Fix Committed |
Triaged |
|
2008-09-06 15:48:15 |
Martin Albisetti |
blueprint: statusexplanation |
Committed a partial fix for this in revision 6962.
Showing between 20 and 30 dependencies should look "acceptable".
The long term solution will be using Ajax magic, which we will have soon-ish. |
Ah, yes, I forgot about removing the portlet.
The case in this bug now looks a bit better, but still unreadable :(
Opening the bug again |
|
2009-01-12 22:15:15 |
Martin Albisetti |
blueprint: status |
Triaged |
In Progress |
|
2009-01-12 22:15:15 |
Martin Albisetti |
blueprint: statusexplanation |
Ah, yes, I forgot about removing the portlet.
The case in this bug now looks a bit better, but still unreadable :(
Opening the bug again |
Working on removing the actions portlet |
|
2009-04-07 20:10:52 |
Martin Albisetti |
blueprint: status |
In Progress |
Fix Committed |
|
2009-04-27 16:05:15 |
Martin Albisetti |
blueprint: status |
Fix Committed |
Fix Released |
|