Sounds familiar. For my part, I don't know if we need to keep bolting on more new and shiny to Koha. ElasticSearch makes sense. A REST API makes sense. Fixing broken things or adding missing essential functionality. Also, how would this React POC go in terms of translations? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Owen Leonard Sent: Monday, 19 September 2016 11:33 PM To: Koha Devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] To React or not to React
Another thing is that you need nodejs to compile it so is another thing to throw on the stack.
Isn't this the kind of dependency requirement that killed my request to introduce a front-end build tool like Grunt or Gulp?
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha- community.org/ bugs : http://bugs.koha-community.org/