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

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

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

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

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

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

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

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

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

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

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

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

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

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!

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

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

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

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

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

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

Re: [Koha-devel] ILSDI - GetAvailability

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:

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

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

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

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

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

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,

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

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:

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

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

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

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

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

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

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

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

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

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