Re: [Koha-devel] To React or not to React

[Katrin]

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.
We don't translate js files at the moment - which may be debatable. One 
benefit at the moment of keeping the strings only in the templates is 
that we don't copy the js files as we do with the template files. I 
think this should be solvable, but it's something to keep in mind.



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-boun...@lists.koha-community.org

[mailto:koha-devel- 
> boun...@lists.koha-community.org
] On Behalf Of Owen Leonard
> Sent: Monday, 19 September 2016 11:33 PM
> To: Koha Devel >
> 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/ 





___
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/


___
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/

Re: [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



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  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-boun...@lists.koha-community.org [mailto:koha-devel-
>> > boun...@lists.koha-community.org] On Behalf Of Owen Leonard
>> > Sent: Monday, 19 September 2016 11:33 PM
>> > To: Koha Devel 
>> > 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/
>>
>>
>>
>
___
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/

Re: [Koha-devel] To React or not to React

[Kyle Hall]

>
> 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-boun...@lists.koha-community.org [mailto:koha-devel-
> > boun...@lists.koha-community.org] On Behalf Of Owen Leonard
> > Sent: Monday, 19 September 2016 11:33 PM
> > To: Koha Devel 
> > 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/
>
>
>
___
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/

Re: [Koha-devel] To React or not to React

[Kyle Hall]

I did much research on that particular issue and it was put to rest when
Facebook updated it's license for React. It looks like the Wikipedia page
only has the vaguest reference to that ; )


> Regarding licensing:
>
> https://en.wikipedia.org/wiki/React_(JavaScript_library)
>
> See part "Patents clause controversy"
>
>
___
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/

Re: [Koha-devel] To React or not to React

[Kyle Hall]

>
>
> 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.
>

I must disagree. Ajax Koha features powered by javascript are far faster
then the traditional cgi-powered equivalents. Another powerful speed factor
is "just in time" loading. Consider all the data loaded in tabs they may
only be viewed once every dozen or more views. The prime example I can
point to is the holds tab. In the past we had to process and load the holds
data for a patron on every checkout. Now we only load that data when the
tab is clicked on, thus saving many wasted cpu cycles!


>
> 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?)
>

This discussion is not really about this particular feature or what it
does, but about the architecture that it uses. This is my second iteration
of the feature. The first version I wrote used Angular which gives me a
good perspective on the use of both in Koha, which is why I started this
discussion ; )

The short answer is yes, it's definitely optional and the feature can be
safely ignored if you aren't interested in it.


>
> 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...
>

Getting proper tools in Koha will have a great impact on *reducing* bloat
rather than adding to it. When we make requests via our services we bypass
all the ui processing that is needed the redisplay the page. Koha has
suffered from bloating in the last few years of releases, but they had
nothing to do with javascript or restful services ( thanks again to
Jonathan for doing so much work de-bloating Koha! )

Kyle


>
> 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 
> wrote:
> My +1 for React. Angular requires a specific skill, other than Javascript.
> Stefano
>
> On 15 set 2016, at 19:22, Kyle Hall  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
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.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/
>
>
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> 

Re: [Koha-devel] To React or not to React

[Kyle Hall]

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 
> wrote:
> My +1 for React. Angular requires a specific skill, other than Javascript.
> Stefano
>
> On 15 set 2016, at 19:22, Kyle Hall  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
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.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/
>
>
>
> ___
> 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/
>
>
> ___
> 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/
>
> ---
> Maritime heritage and history, preservation and conservation,
> research and education through the written word and the arts.
> > and <
> http://UltraMarine.ca >
>
> ___
> 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/
>
___
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/

Re: [Koha-devel] To React or not to React

[Kyle Hall]

Yes, I definitely want to complete the backend and make this a fully
functioning submission before long. I decided to get it out as early as
possible just to get this discussion rolling!



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 Mon, Sep 19, 2016 at 10:18 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi Kyle;
>
> Thanks for this example.
> Would it be possible to see a working example to fully understand what
> you have in mind?
>
> Cheers,
> Jonathan
>
> 2016-09-15 19:22 GMT+02:00 Kyle Hall :
> > 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
> > ByWater Solutions ( http://bywatersolutions.com )
> > Meadville Public Library ( http://www.meadvillelibrary.org )
> > Crawford County Federated Library System ( http://www.ccfls.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/
> ___
> 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/
>
___
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/

Re: [Koha-devel] To React or not to React

[Kyle Hall]

Owen, I didn't know that proposal had been shut down! I find it especially
odd since we already require nodejs for converting our less files to css.
We already have leaped the bar of needing to use nodejs as Koha developers,
so I see no reason why cannot just use grunt or gulp via npm as we do the
less complier.



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 Mon, Sep 19, 2016 at 9:32 AM, Owen Leonard  wrote:

> > 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/
>
___
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/

Re: [Koha-devel] To React or not to React

[Kyle Hall]

On Mon, Sep 19, 2016 at 8:33 AM, Philippe Blouin <
philippe.blo...@inlibro.com> wrote:

> Can I not be against, yet still have concerns?  :)
>
> I'm glad you so gallantly dumped Angular, which I would have raised my
> hand Against since that thing obsolete past code every 6 months.  But I do
> not know React.  Could you sell me more the big plusses to do that.  What
> will it replace, do you have an example?  What about all the code waiting
> approval right now, will it become obsolete because non-Reactive ?
>

The big plus of React is that it really does allow quick development of
very nice widgets that can be used and re-used. React is also a view layer
only and does not throw everything and the kitchen sink in like Angular
does. React does not obsolete any existing code, but it can be used to
augment existing features and for new features wherever we want to use it!

>
> All the big previous changes (bootstrap, dbix...) were not without pain,
> espeicially for those outside the core, not coding these technologies 24/7.
>
> And how do you see React evolving in the next 5 years?  Keeping up with
> bootstrap requires huge effort (if/when we upgrade).
>

React has a nice simple, stable api at this point. I cannot say what it
will be in 5 years, but I can say that what is now will not limit us in the
future. It does what we need it to do right now.


>
> Again, I know little.  Please don't ask me if I'm against, but give me
> your big sales pitch. :)
>

Of course! I have learned how to use React and Angular both just as for
potential use in Koha. A direct comparison of them *for Koha* tells me that
React is far better suited for our uses.

Kyle


>
> Cheers,
>
> Philippe Blouin,
> Responsable du développement informatique
>
> Tél.  : (888) 604-2627
> philippe.blo...@inlibro.com
> inLibro | pour esprit libre | www.inLibro.com
> On 09/19/2016 08:18 AM, Kyle Hall wrote:
>
> Thanks for the feedback Stefano!
>
> Please, if anybody is *against* the use of React in Koha, please voice
> your concerns!
>
> 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 < 
> bargi...@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.h...@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
>> ByWater Solutions ( 
>> http://bywatersolutions.com )
>> Meadville Public Library ( 
>> http://www.meadvillelibrary.org )
>> Crawford County Federated Library System ( 
>> http://www.ccfls.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/
>>
>>
>>
>> 

Re: [Koha-devel] To React or not to React

[David Cook]

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-boun...@lists.koha-community.org [mailto:koha-devel-
> boun...@lists.koha-community.org] On Behalf Of Owen Leonard
> Sent: Monday, 19 September 2016 11:33 PM
> To: Koha Devel 
> 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/


___
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/

Re: [Koha-devel] ILSDI - GetAvailability

[David Cook]

Yeah, the documentation is wrong, if I recall correctly. Hurray for opening
a bug report!

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-boun...@lists.koha-community.org [mailto:koha-devel-
> boun...@lists.koha-community.org] On Behalf Of SUZUKI Arthur
> Sent: Monday, 19 September 2016 6:53 PM
> To: Julian Maurice ; koha-de...@lists.koha-
> community.org
> Subject: Re: [Koha-devel] ILSDI - GetAvailability
> 
> Hello Julian,
> 
> Thanks for your reply!
> 
> I've opened a bug report here :
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17317
> 
> Arthur
> 
> Le 16/09/2016 à 11:08, Julian Maurice a écrit :
> > Hello Arthur,
> >
> > You're not doing anything wrong. The GetAvailability implementation in
> > Koha works only when id_type=item. And I believe the parameter
> > 'return_type' is not used at all.
> >
> > Please open a bug report on https://bugs.koha-community.org/
> >
> > On 16/09/2016 10:45, SUZUKI Arthur wrote:
> >> Hello people,
> >> First of all I wishes everyone have spent a nice summer!
> >>
> >> At my work we're trying to use ILSDI to get availability of all items
> >> for a biblionumber.
> >>
> >> Thanks to Julian we were able to use the GetAvailability method to
> >> get availability for one item at a time.
> >>
> >> https://catalogue.univ-lyon3.fr/cgi-bin/koha/ilsdi.pl?service=GetAvai
> >> lability=510054_type=item
> >>
> >> According to the documentation it is possible to query this script
> >> with biblionumber rather than itemnumber to get availability of all
> >> items in one shot.
> >>
> >> https://catalogue.univ-lyon3.fr/cgi-bin/koha/ilsdi.pl?service=GetAvai
> >> lability=334726_type=bib_type=item
> >>
> >> The late query is then supposed to work but it doesn't.
> >> Am I doing something wrong?
> >>
> >> Thanks in advance for your wisdom and enlightenment!
> >> Best regards,
> >>
> >> Arthur Suzuki
> >> University Jean Moulin Lyon 3
> >>
> >
> 
> --
> Arthur SUZUKI
> Service informatique des bibliothèques
> BIBLIOTHÈQUES UNIVERSITAIRES
> Université Jean Moulin Lyon 3
> 6 Cours Albert Thomas - B.P. 8242 – 69355 Lyon Cedex 08 ligne directe :
+33
> (0)4 78 78 79 16 | http://bu.univ-lyon3.fr L'Université Jean Moulin est
> membre fondateur de l'Université de Lyon
> 
> ___
> 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/


___
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/

Re: [Koha-devel] To React or not to React

[Marc Véron]

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 > wrote:


My +1 for React. Angular requires a specific skill, other than
Javascript.
Stefano


On 15 set 2016, at 19:22, Kyle Hall > 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 
ByWater Solutions ( http://bywatersolutions.com
 )
Meadville Public Library ( http://www.meadvillelibrary.org
 )
Crawford County Federated Library System (
http://www.ccfls.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/ 



___
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/


___
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/ 


---
Maritime heritage and history, preservation and 

Re: [Koha-devel] To React or not to React

[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 
<bargi...@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.h...@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
ByWater Solutions ( 
http://bywatersolutions.com )
Meadville Public Library ( 
http://www.meadvillelibrary.org )
Crawford County Federated Library System ( 
http://www.ccfls.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/



___
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/


___
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/


---
Maritime heritage and history, preservation and conservation,
research and education through the written word and the arts.
 and 
___
Koha-devel 

Re: [Koha-devel] [Koha::Object] Related records and calling methods from templates

[Jonathan Druart]

2016-09-15 13:03 GMT+02:00 Marcel de Rooy :
> Hi devs,
>

Hi :)

> I am seeing more Koha objects that include methods for related records like
> Koha::Patron, sub image referring to Koha::Patron::Images.
>
> As a second example, on bug 14610 (article requests), a biblio, item, branch
> and borrower method is added to Koha::ArticleRequest.

These methods should highlight the relationships (fk or missing fk at
DB level) between objects. They make sense to me as long as we want to
manipulate Koha::Objects.

Note that branch should be replaced with library ;)

> Obviously, they all follow the same pattern.
>
> Could we generalize that, and keep our code cleaner?
>
>
>
> And do we always need the full Koha object? For use in a template we may
> need only a few columns.

What do you suggest? It's much easier to always get and pass a full
object than sometimes a smaller one without knowing exactly what it
represents (which methods you can call on it).
I don't think it will hurt perfs too much.
Of course there will certainly be some rooms for improvements here, it
should not be a rule written in stone.

> We start passing these objects to the templates now too, making it possible
> to call methods from the template. It is possible, but do we really want
> that? More code ends up in the template, maybe harder to find since you now
> use borrower.method instead of borrower->method etc. Secondly, reading
> borrower.something might not immediately tell you that something is a method
> instead of a column.

Yes, I don't think it's a good thing. We should avoid calling methods
in template, only accessors. If the method is trivial, I'd say it
could be ok.

> In other cases we have added a sort of wrapper like Branches.GetName from
> the Branches plugin.

That was to help us, and that will continue to help us, because the fk
don't always exist.
If should not hurt perf neither.

> I am interested to know if we want to enforce this wrapper approach for
> instance, or just continue on the current road.

Where and why? :)

Usually I don't think TT plugins should be used for such things. In an
ideal world, we would manipulate objects in templates and
library.branchname would display the library name (in a ideal world it
would be library.name...).
Or patron.library.branchname, but we should not need a plugin for
that: Branches.GetName( patron.branchcode )

Cheers

> Thx,
>
>
>
> Marcel
>
>
>
>
> ___
> 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/
___
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/

Re: [Koha-devel] To React or not to React

[Jonathan Druart]

Hi Kyle;

Thanks for this example.
Would it be possible to see a working example to fully understand what
you have in mind?

Cheers,
Jonathan

2016-09-15 19:22 GMT+02:00 Kyle Hall :
> 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
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.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/
___
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/

Re: [Koha-devel] To React or not to React

[Owen Leonard]

> 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/

Re: [Koha-devel] To React or not to React

[Rodrigo Santellan]

Arthur,

I believe that foundation is an alternative to bootstrap. React JS is on
the league of backbone, angular and ember.

I have use React JS on a project and the best thing about it is the
possibility of rewrite really small parts of the page. Create small widget
to increase the functionality and keep turning the old page in a new way.
One of the best thing for me about react is that is only frontend
development so it has less impact on a migration and you can really
decouple the backend.

My cons are that the documentation is not that good, they want you to write
the new code on ES6 but there is not that much documentation on that.
Another thing is that you need nodejs to compile it so is another thing to
throw on the stack.

Just my grain of sand!

Cheers!

On Mon, Sep 19, 2016 at 9:59 AM, SUZUKI Arthur 
wrote:

> Since you're talking about JS/CSS Frameworks, what about Foundation?
> http://foundation.zurb.com/
> This one is cool too!
> Best regards,
> Arthur Suzuki
> University Jean Moulin Lyon 3
>
>
> Le 19/09/2016 à 14:33, Philippe Blouin a écrit :
>
> Can I not be against, yet still have concerns?  :)
>
> I'm glad you so gallantly dumped Angular, which I would have raised my
> hand Against since that thing obsolete past code every 6 months.  But I do
> not know React.  Could you sell me more the big plusses to do that.  What
> will it replace, do you have an example?  What about all the code waiting
> approval right now, will it become obsolete because non-Reactive ?
>
> All the big previous changes (bootstrap, dbix...) were not without pain,
> espeicially for those outside the core, not coding these technologies 24/7.
>
> And how do you see React evolving in the next 5 years?  Keeping up with
> bootstrap requires huge effort (if/when we upgrade).
>
> Again, I know little.  Please don't ask me if I'm against, but give me
> your big sales pitch. :)
>
> Cheers,
>
> Philippe Blouin,
> Responsable du développement informatique
>
> Tél.  : (888) 604-2627
> philippe.blo...@inlibro.com
> inLibro | pour esprit libre | www.inLibro.com
> On 09/19/2016 08:18 AM, Kyle Hall wrote:
>
> Thanks for the feedback Stefano!
>
> Please, if anybody is *against* the use of React in Koha, please voice
> your concerns!
>
> 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 
> wrote:
>
>> My +1 for React. Angular requires a specific skill, other than Javascript.
>> Stefano
>>
>> On 15 set 2016, at 19:22, Kyle Hall  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
>> ByWater Solutions ( http://bywatersolutions.com )
>> Meadville Public Library ( http://www.meadvillelibrary.org )
>> Crawford County Federated Library System ( http://www.ccfls.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/
>>
>>
>>
>> 

Re: [Koha-devel] To React or not to React

[SUZUKI Arthur]

Since you're talking about JS/CSS Frameworks, what about Foundation?
http://foundation.zurb.com/
This one is cool too!
Best regards,
Arthur Suzuki
University Jean Moulin Lyon 3

Le 19/09/2016 à 14:33, Philippe Blouin a écrit :

Can I not be against, yet still have concerns?  :)

I'm glad you so gallantly dumped Angular, which I would have raised my 
hand Against since that thing obsolete past code every 6 months.  But 
I do not know React.  Could you sell me more the big plusses to do 
that.  What will it replace, do you have an example?  What about all 
the code waiting approval right now, will it become obsolete because 
non-Reactive ?


All the big previous changes (bootstrap, dbix...) were not without 
pain, espeicially for those outside the core, not coding these 
technologies 24/7.


And how do you see React evolving in the next 5 years?  Keeping up 
with bootstrap requires huge effort (if/when we upgrade).


Again, I know little.  Please don't ask me if I'm against, but give me 
your big sales pitch. :)


Cheers,

Philippe Blouin,
Responsable du développement informatique

Tél.  : (888) 604-2627
philippe.blo...@inlibro.com 

inLibro | pour esprit libre | www.inLibro.com 
On 09/19/2016 08:18 AM, Kyle Hall wrote:

Thanks for the feedback Stefano!

Please, if anybody is *against* the use of React in Koha, please 
voice your concerns!


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  
wrote:


My +1 for React. Angular requires a specific skill, other than
Javascript.
Stefano


On 15 set 2016, at 19:22, Kyle Hall  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 
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.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/




___
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/





___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website 

Re: [Koha-devel] To React or not to React

[Philippe Blouin]

Can I not be against, yet still have concerns?  :)

I'm glad you so gallantly dumped Angular, which I would have raised my 
hand Against since that thing obsolete past code every 6 months. But I 
do not know React.  Could you sell me more the big plusses to do that.  
What will it replace, do you have an example?  What about all the code 
waiting approval right now, will it become obsolete because non-Reactive ?


All the big previous changes (bootstrap, dbix...) were not without pain, 
espeicially for those outside the core, not coding these technologies 24/7.


And how do you see React evolving in the next 5 years?  Keeping up with 
bootstrap requires huge effort (if/when we upgrade).


Again, I know little.  Please don't ask me if I'm against, but give me 
your big sales pitch. :)


Cheers,

Philippe Blouin,
Responsable du développement informatique

Tél.  : (888) 604-2627
philippe.blo...@inlibro.com 

inLibro | pour esprit libre | www.inLibro.com 
On 09/19/2016 08:18 AM, Kyle Hall wrote:

Thanks for the feedback Stefano!

Please, if anybody is *against* the use of React in Koha, please voice 
your concerns!


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 > wrote:


My +1 for React. Angular requires a specific skill, other than
Javascript.
Stefano


On 15 set 2016, at 19:22, Kyle Hall > 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 
ByWater Solutions ( http://bywatersolutions.com
 )
Meadville Public Library ( http://www.meadvillelibrary.org
 )
Crawford County Federated Library System ( http://www.ccfls.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/




___
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/





___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : 

Re: [Koha-devel] To React or not to React

[Kyle Hall]

Thanks for the feedback Stefano!

Please, if anybody is *against* the use of React in Koha, please voice your
concerns!

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  wrote:

> My +1 for React. Angular requires a specific skill, other than Javascript.
> Stefano
>
> On 15 set 2016, at 19:22, Kyle Hall  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
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.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/
>
>
>
> ___
> 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/
>
___
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/

Re: [Koha-devel] ILSDI - GetAvailability

[SUZUKI Arthur]

Hello Julian,

Thanks for your reply!

I've opened a bug report here : 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17317


Arthur

Le 16/09/2016 à 11:08, Julian Maurice a écrit :

Hello Arthur,

You're not doing anything wrong. The GetAvailability implementation in
Koha works only when id_type=item. And I believe the parameter
'return_type' is not used at all.

Please open a bug report on https://bugs.koha-community.org/

On 16/09/2016 10:45, SUZUKI Arthur wrote:

Hello people,
First of all I wishes everyone have spent a nice summer!

At my work we're trying to use ILSDI to get availability of all items
for a biblionumber.

Thanks to Julian we were able to use the GetAvailability method to get
availability for one item at a time.

https://catalogue.univ-lyon3.fr/cgi-bin/koha/ilsdi.pl?service=GetAvailability=510054_type=item

According to the documentation it is possible to query this script with
biblionumber rather than itemnumber to get availability of all items in
one shot.

https://catalogue.univ-lyon3.fr/cgi-bin/koha/ilsdi.pl?service=GetAvailability=334726_type=bib_type=item

The late query is then supposed to work but it doesn't.
Am I doing something wrong?

Thanks in advance for your wisdom and enlightenment!
Best regards,

Arthur Suzuki
University Jean Moulin Lyon 3





--
Arthur SUZUKI
Service informatique des bibliothèques
BIBLIOTHÈQUES UNIVERSITAIRES
Université Jean Moulin Lyon 3
6 Cours Albert Thomas - B.P. 8242 – 69355 Lyon Cedex 08
ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr
L'Université Jean Moulin est membre fondateur de l'Université de Lyon

___
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/