[Koha-devel] To React or not to React
Marc Véron
veron at veron.ch
Mon Sep 19 18:06:26 CEST 2016
Regarding licensing:
https://en.wikipedia.org/wiki/React_(JavaScript_library)
See part "Patents clause controversy"
Marc
Am 19.09.2016 um 17:15 schrieb Paul A:
> At 08:18 AM 9/19/2016 -0400, Kyle Hall wrote:
>> Thanks for the feedback Stefano!
>> Please, if anybody is *against* the use of React in Koha, please
>> voice your concerns!
>
> Question: what has Facebook added to js that we could not use as
> "regular" js? Not a show stopper, but our "gut feeling" (not fully
> documented, but more than anecdotal) is that all js code, given its
> standalone capability, has a more than proportional speed downside.
> And I'm not going near the licensing questions.
>
> If I understand this bug 17297 ("low enhancement") correctly, it
> refines itemnotes by adding granularity. If this is a "good thing",
> can the original coding be improved? Add an auth value? If we need js,
> how optional might this be? (do we know how many Koha users are truly
> interested?)
>
> I've always been impressed by Koha core speed, and without using such
> expressions as "mission creep" (or heaven forfend, code bloat) I truly
> recognize that enhancements are a real life necessity. Just wondering
> how and where they are best added while maintaining the KISS principle...
>
> Best -- Paul
>
>
>> Kyle
>>
>>
>>
>> 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 Fri, Sep 16, 2016 at 9:50 AM, Stefano Bargioni <bargioni at pusc.it
>> <mailto:bargioni at pusc.it>> wrote:
>>
>> My +1 for React. Angular requires a specific skill, other than
>> Javascript.
>> Stefano
>>
>>> On 15 set 2016, at 19:22, Kyle Hall <kyle.m.hall at gmail.com
>>> <mailto:kyle.m.hall at gmail.com>> wrote:
>>>
>>> I have my proof of concept for using React within Koha
>>> completed! You can see it here:Â
>>> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17297
>>>
>>> Please give it a try!
>>>
>>> So, I've written this development ( at least in part ) in
>>> both Angular and React. I know Angular 2 is out but here
>>> are my thoughts so far.
>>>
>>> 1) It's much easier to think in React than in Angular.Â
>>> React is for the most part just Javascript. It's far less
>>> opinionated than Angular. They saying goes React is
>>> Javascript and Angular is Angular. I think the flexibility
>>> of React works well within the Koha ecosystem.
>>>
>>> 2) Writing React feels much more like programming. I think
>>> it's much faster to develop reactive and ajax features inÂ
>>> React than it is using jQuery.
>>>
>>> 3) React makes it pretty easy to create widgets that we
>>> can drop in to a given page and have just work. Pretty much
>>> anything that shows up on multiple pages would make for a
>>> good React widget. Think the holds table which is on the
>>> checkouts page and the patron details page. It is ajaxified
>>> now, but a far far cleaner version could be written in React.
>>>
>>> 4) React is just a view layer. Angular is a full MVC
>>> framework with many pieces we don't really need.
>>>
>>> I think React is probably the way to go for Koha. I like
>>> Angular but for Koha in particular, I think React is a
>>> better fit. I think we really need to get this decision made
>>> as soon as possible. If anyone has opinions, please let
>>> everyone know!
>>>
>>> Kyle
>>>
>>>
>>> http://www.kylehall.info <http://www.kylehall.info/>
>>> ByWater Solutions ( http://bywatersolutions.com
>>> <http://bywatersolutions.com/> )
>>> Meadville Public Library ( http://www.meadvillelibrary.org
>>> <http://www.meadvillelibrary.org/> )
>>> Crawford County Federated Library System (
>>> http://www.ccfls.org <http://www.ccfls.org/> )
>>> _______________________________________________
>>> Koha-devel mailing list
>>> Koha-devel at lists.koha-community.org
>>> <mailto: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/
>>
>>
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at lists.koha-community.org
>> <mailto: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/
>>
>>
>> _______________________________________________
>> 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/
>
> ---
> Maritime heritage and history, preservation and conservation,
> research and education through the written word and the arts.
> <http://NavalMarineArchive.com <http://navalmarinearchive.com/>> and
> <http://UltraMarine.ca <http://ultramarine.ca/>>
>
>
>
> _______________________________________________
> 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/20160919/703d85c8/attachment.html>
More information about the Koha-devel
mailing list