The first impl used whatever order the checkboxes are in, but that was even
less readable. One simple solution, i think, would be to keep the sorting
but underline the most recently selected letter. Will try that when i get
home.

----- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity and
typos.
On Sep 30, 2014 4:46 PM, "Andy Bradford" <amb-fos...@bradfords.org> wrote:

> Thus said "Joe Mistachkin" on Sat, 27 Sep 2014 14:43:15 -0700:
>
> > Works great. I  made a couple style tweaks, including  adding some CSS
> > and moving the new  elements out one level. I'm not sure  if my CSS is
> > the best choice, please feel free to enhance the styling.
>
> Looks fine here.
>
> I sometimes find it hard to find the letter that was added to the string
> when checking a new capability and end up toggling the checkbox multiple
> times to watch for  which new letter is being inserted  in the middle of
> the string of letters.
>
> Would it be better to just add  each new capability letter to the end of
> the current string?
>
> Or perhaps instead each Capability should have it's letter next to it?
>
> (s) Setup        (u) Reader       (r) Read Ticket
> (a) Admin        (v) Developer    (n) New Tickets
> (d) Delete       (g) Clone        (c) Append To Ticket
> (e) Email        (j) Read Wiki    (w) Write Tickets
>
> Thanks,
>
> Andy
> --
> TAI64 timestamp: 40000000542ac246
>
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to