https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25870
--- Comment #73 from David Cook <[email protected]> --- Useful features/enhancements being blocked for years is something that frustrates everyone. Perhaps even increasingly so. I'm in the process of trying to think of architectural changes that will make it easier to extend Koha. I think with the slow shift towards using the REST API for the backend and Vue.js for the front-end, it's going to get easier and easier to extend/customize Koha. "Bug 43355 - Add a /search API endpoint for biblios" has been created to add a search endpoint. Whether that's the right answer for bug 27113 - I don't know. I think /api/v1/search/autocomplete or something more to-purpose would make sense, but that's just me. Hence my comment about having a Koha Plugin and a System Preference pointing to an API endpoint. @Katrin: The logic is we make whatever necessary UI changes to Koha, have the system preference or other setting to point to the endpoint, and then backend components can be developed and swapped out easily. So maybe it starts as Koha Plugin, but then everyone really likes it, so we adopt it into core. (For instance, I think that Koha should adopt Bywater's Coverflow into core, as it's such a handy feature for every Koha.) Anyway, just a thought. I by no means am saying that it has to be a Koha Plugin, but I think that would accelerate development and testing. It's an approach I'm increasingly going to try taking with my own enhancements and new features. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
