Summary: | Making certain alerts stand out | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, kyle.m.hall, lisettepalouse+koha |
Version: | unspecified | Keywords: | Academy |
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Christopher Brannon
2016-03-01 17:14:36 UTC
I think perhaps a better solution is to make sure that messages like this get unique ID atributes so that you can define custom CSS for particular messages which are of higher priority to your library. For example: [% IF ( errmsgloo.badbarcode ) %] <p id="checkin_no_item_with_barcode" class="problem">No item with barcode: [% errmsgloo.msg %]</p> [% END %] That would also allow you to define custom audio alerts for those messages. (In reply to Owen Leonard from comment #1) > I think perhaps a better solution is to make sure that messages like this > get unique ID atributes so that you can define custom CSS for particular > messages which are of higher priority to your library. For example: > > [% IF ( errmsgloo.badbarcode ) %] > <p id="checkin_no_item_with_barcode" class="problem">No item with > barcode: [% errmsgloo.msg %]</p> > [% END %] > > That would also allow you to define custom audio alerts for those messages. +1 I think, in the interest of keeping things simple, and not having programmers hate this, it would be better to have either a brief code, or a numeric problem ID or subclass so people are not having to use #checkin_no_item_with_barcode. As someone that uses jQuery a lot, it would annoy me more than keeping a unique code or number straight. But, that is my personal opinion and not the opinion of programmers. Either way, it would work. HOWEVER, it would be even BETTER, if there were a page that could be dedicated to customizations, and would isolate key alerts and such that people could easily set. Koha is HIGHLY customizable, but not everyone wants the nitty gritty of CSS. Looking things up, possibly mistyping something, trying to figure out what they did wrong. Not everyone wants to keep up on CSS. Keep the ability to customize CSS, but add some basic choices for those who don't CSS. |