[Koha-devel] To React or not to React

[Kyle Hall]

I think I covered everyones questions. If I missed any or anyone has
followups to my replies, please keep them coming! Koha *needs* a way for us
to develop and use modern web practices. Koha has always evolved as the web
has evolved. If it didn't, we'd still be using pure cgi-script with no
javascript or ui layout framework! It's time for Koha to evolve a again,
and it's a very small step compared to say the introduction of Bootstrap.
React will just be another tool we can use to make Koha even better than
before, and will not require changing much code at all to add, and does not
affect any currently submitted patches.

Again, please keep the questions and suggestions coming! Thanks to everyone
who has joined in the discussion so far!

Kyle

<https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Tue, Sep 20, 2016 at 1:30 AM, Kyle Hall <kyle.m.hall at gmail.com> wrote:

> 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.
>>
>
> I'm not sure how this differs from Koha adding Zebra, adding Elastic or
> adding a restful api. To me, this is not a matter of adding new for the
> sake of new ( React isn't even new at this point ) but of adding something
> that is necessary and long overdue. The question isn't about needing React
> or not, it's about the need for a modern JS UI toolkit to take advantage of
> our svc and rest api's without the need to write crazy amounts of code to
> make it work with just jQuery. Take a look at the javascript file for the
> holds table and you'll see what I mean. A React implementation of it would
> be *so* much cleaner and easier to understand for everyone. Please don't
> ask me to rewrite it as a poc though ; ) I *will* be happy to rewrite it
> post-adoption.
>
>
>>
>> Also, how would this React POC go in terms of translations?
>>
>
> React is just Javascript, and is translated the same way translate all our
> other js files.
>
>
>>
>> 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 at lists.koha-community.org [mailto:koha-devel-
>> > bounces at lists.koha-community.org] On Behalf Of Owen Leonard
>> > Sent: Monday, 19 September 2016 11:33 PM
>> > To: Koha Devel <koha-devel at 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 at 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/
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20160920/b28fc608/attachment.html>