Re: [Koha-devel] API use in intranet and OPAC

2019-10-14 Thread dcook
Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -Original Message- From: Koha-devel On Behalf Of Fridolin SOMERS Sent: Monday, 14 October 2019 6:24 PM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] API use in intranet and OPAC

Re: [Koha-devel] API use in intranet and OPAC

2019-10-14 Thread Fridolin SOMERS
+1 for me. I'm sure modern web-browsers can provide a good accessiblity even with JS/Ajax. Le 07/10/2019 à 13:28, Kyle Hall a écrit : I think it's pretty practical at this point in time to agree that if we are to continue making a modern web app, we need to require javascript. --- http://www.

Re: [Koha-devel] API use in intranet and OPAC

2019-10-08 Thread Indranil Das Gupta
Hi, On Tue, 8 Oct 2019 at 06:17, wrote: > I suppose one downside could be the Koha OPAC website could become > neglected, if everyone was just maintaining their own user interfaces. But > I imagine a lot of people would still want to use the Koha OPAC website too. > (After all, integrating with

Re: [Koha-devel] API use in intranet and OPAC

2019-10-07 Thread dcook
Direct: 02 8005 0595 From: Arthur Suzuki Sent: Tuesday, 8 October 2019 11:17 AM To: koha-devel@lists.koha-community.org; dc...@prosentient.com.au; 'Katrin Fischer' Subject: Re: [Koha-devel] API use in intranet and OPAC One but not least issue with JavaScript, how do we test thi

Re: [Koha-devel] API use in intranet and OPAC

2019-10-07 Thread Arthur Suzuki
> >David Cook > >Systems Librarian > >Prosentient Systems > >72/330 Wattle St > >Ultimo, NSW 2007 > >Australia > > > >Office: 02 9212 0899 > >Direct: 02 8005 0595 > > > >From: Koha-devel On >Behalf Of Katrin Fischer >Sent: Tuesd

Re: [Koha-devel] API use in intranet and OPAC

2019-10-07 Thread dcook
72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel On Behalf Of Katrin Fischer Sent: Tuesday, 8 October 2019 7:31 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] API use in intranet and OPAC If we decide to

Re: [Koha-devel] API use in intranet and OPAC

2019-10-07 Thread Katrin Fischer
If we decide to require JavaScript for the OPAC we should be careful to do it in a way that is accessible. Accessibility can even be a legal requirement in some countries for websites of public institutions like libraries. Katrin On 07.10.19 13:28, Kyle Hall wrote: I think it's pretty practical

Re: [Koha-devel] API use in intranet and OPAC

2019-10-07 Thread Kyle Hall
I think it's pretty practical at this point in time to agree that if we are to continue making a modern web app, we need to require javascript. --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County

Re: [Koha-devel] API use in intranet and OPAC

2019-10-07 Thread Marcel de Rooy
Yeah I guess we reached the point that we just need javascript in OPAC ? ​Museumstraat 1 Postbus 74888 1070 DN Amsterdam Rijksmuseum.nl ​ ​Nu te zien: ​​​Louise Bourgeois in de Rijksmuseumtuinen ​Operatie Nachtwacht ​ ​Verwacht: ​Rembrandt-Velázquez. Nederlandse & Spaanse meesters ​ ​ ​T/m 18 j

Re: [Koha-devel] API use in intranet and OPAC

2019-10-07 Thread Kyle Hall
I'm going to go out on a limb and say it will indeed require javascript. There are a number of OPAC features ( though non-essential ) that don't function without javascript. Is this still a requirement for the OPAC? Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com

Re: [Koha-devel] API use in intranet and OPAC

2019-10-07 Thread Marcel de Rooy
We found a few other intranet places as well (thx Katrin). The first comes from bug 8030, august 2016. root@master:/usr/share/koha/koha-tmpl/intranet-tmpl/prog# git grep -l "/api/v1/" [Bug 15496 12-04-19] en/modules/cataloguing/moveitem.tt [Bug 23710 01-10-19] en/modules/reserve/request.tt [FIRST

Re: [Koha-devel] API use in intranet and OPAC

2019-10-04 Thread Owen Leonard
> I think it best to move OPAC to use the API, but this time I'm going to hear > you first. Would this make the holds process dependent on JavaScript? Owen -- Web Developer Athens County Public Libraries https://www.myacpl.org ___ Koha-devel mailing