http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14224 --- Comment #5 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to Martin Stenberg from comment #4)
Hi Jonathan,
Do you think it's worth adding a new subroutine GetIssue for this special case of GetIssues? GetIssues will still return an arrayref when called with issue_id, so the return type matches the plural "s" at least.
GetIssue would not return an array, but the matching issue.
I'm doing an ajax request to minimize overhead when sending the request (i.e. no need to send note data for all issues when only one has been changed) and when recieving (i.e. no need to render a new template and send a whole document when only an "ok" or "nok" is needed). And as a bonus it allows the user to write a second note while the first one is beeing sent/processed to the server.
To be honest I thought javascript was concidered a requirment for Koha. I'm using NoScript myself, and am always positivly surprised when a page works without having to enable javascript.
How about keeping the ajax-version and adding a fallback for browsers without javascript?
You can add 2 forms in the page, the one needing JS can be hidden with a css rule. When the page is loading, a JS code could hide one and display the other one. I suppose it's the way to go. -- You are receiving this mail because: You are watching all bug changes.