On Mon, 21 Mar 2011 09:28:46 -0400 (EDT)
R P Herrold <herr...@owlriver.com> wrote:
> This is harder -- that ',' is a English way of having a
> delendent clause ('After next download') come before the main
> clause ('in %d hours'). As such, that phase could be
> re-written:
> %d hours after next download
> which saves a couple characters.
Still quite long, but better. Thanks again.
>
> >> and the top row probably should not have icons displayed on
> >> the 'header' line, on both screens
> >
> > A colleague suggested to put grayed icons instead.
> > What do you think?
>
> I think that means there is more work designing and carrying
> icons that will never be used. I considered if there would
> ever be a case where 'edit all' would be a valid choice, and
> concluded it was at best a rare situation.
My conclusion exactly, implementing multi-edit in generally not worth it.
I didn't spend much time designing icons however.
I'm leveraging as much as open stuff there is.
The icons I'm using from the screenshot come from
http://p.yusukekamiyamane.com/ which are licensed via CC with attribution.
> I would omit the icons on the column title line because they
> can (almost) never be active. If there is a detail line, it
> will show the permitted actions already [per user ACLs may
> imply a need for greyed out icons here, if the user lacks
> sufficient rights]. If there are no detail lines, probably a
> informational line, indicating there are no tickets of that
> type found [assuming a feature to permit limiting a subset of
> tickets to display, perhaps on the presence of a keyword]
Agreed. Headers icon be-gone(tm)!
> Thank you for the project, and as I look, your other work for
> the FLOSS community
Thanks. It's always appreciated :)
