Re: comment on templates
- From: Olav Vitters <olav bkor dhs org>
- To: bugzilla-devel-list gnome org
- Subject: Re: comment on templates
- Date: Wed, 5 Oct 2005 02:05:28 +0200
On Tue, Oct 04, 2005 at 07:17:31PM -0400, Luis Villa wrote:
> I'm considering sucking the current b-t.g.o templates into my work
> bugzilla (which is totally stock, look and feelwise, which...
> suckkks.) So I took a look at the current stuff for the first time in
> a while. Some comments:
Note that some template stuff depends on changes I made to Bugzilla,
just do a:
cvs-update-magic/update-from-mozilla-bugzilla-cvs.sh diff
on a checked out bugzilla-newer to see the differences
> * wow these rock. I think it would be sweet to try to get these into
> upstream 2.22.
andreasn from #marketing helped to make some designs. There are various
designs in http://ramnet.se/~nisse/diverse/temp/ (some in a different
directory). Also borrowed some ideas from Red Hat. It could use some
colors other than blue.
Simplifying the show_bug.cgi depends on a patch in main Bugzilla to make
the cookies secure. Currently the cookies are only secure by limiting
them to your IP address. That doesn't work with people behind
transparant proxies with multiple IP addresses. The patch would allow us
to only limit this to a /16. It'll hopefully go in soon. Details are
at: https://bugzilla.mozilla.org/show_bug.cgi?id=119524
(depends on 2 other patches as I found a Bugzilla bug + MySQL bug while
writing it)
It is for Bugzilla CVS HEAD, but I'm porting it to 2.20 as soon as main
Bugzilla accepts what I did (I'll try to push it to 2.20.1 as well).
Without above such users will be constantly logged out, needing the
logged out page to show all options.
> * 'Bugzilla Bug ####' in the topic is probably redundant- you've got
> Bugzilla in big type in the upper right, so maybe just drop Bugzilla
> there, making it 'Bug ####'?
Feel free to commit ;)
> * I'm a little unsure about highlighting the first comment like that-
> I guess it does reinforce the desire to make the first comment useful,
> but if a bug evolves, that first glance is going to be misleading. I'd
> much rather highlight the (editable later) subject, like we do in the
> current templates.
Hey, it looks nice! Well.. if you are using Mozilla based browser
(somehow that first comment does not as good in Opera and terrible in
IE.. ).
PS: I used CSS to change the background color of the form field that has
focus.. With dropdown fields this triggers some bug in Mozilla (try to
change Version, it is annoying). Have to remove that :(
> * similarly, I like the big, bold resolution information in the
> current layout, though I admit that that could be more familiarity
> than anything else. /me thinks... I think maybe with an *open* bug,
> the best thing to highlight in that way is to put the priority there
> (and maybe whether or not it has an unreviewed patch?); otherwise,
> highlight the resolution/status.
Not sure what part you mean.. you mean the 'Resolved: FIXED" in
http://bugzilla.gnome.org/show_bug.cgi?id=163163? It is still shown,
just didn't know what to do with it (layout).
I want the resolution info to be at the top of the topright box (with
the Opened, Product, Component, etc). Maybe different background + span
both columns + be in the center.
> * highlighting 'show' in the header doesn't really make sense, since
> clicking on it does... basically nothing. I assume the missing stuff
I did that to ensure you know where you are. Also, this is the same as
the current bugzilla (Bugzilla being bolded).
> from my admin footer (params, edit*) etc. being missing are a known
> issue.
Nope, done on purpose :)
See Account and Admin at the top. I think those massive list of links
suck. Ok, when you do want to give somebody editbugs this is annoying,
but I like the simpler page.
> Anyway, these rock-
> Luis
--
Regards,
Olav
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]