Re: [Koha-devel] ES6 usage in the staff client

2017-08-08 Thread David Cook 
I don't know why I didn't see Tomas's email except within this reply... but
I'm typically referring to IE 8-11. I think all my librarians on IE 6-7 have
moved on from those versions.

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 Tajoli
Zeno
Sent: Tuesday, 8 August 2017 9:43 PM
To: Koha Devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] ES6 usage in the staff client

Hi to all,

Il 08/08/2017 12:30, Tomas Cohen Arazi ha scritto:
> When people say IE, what specific version of the product are you all 
> talking about?

in fact rearding https://www.netmarketshare.com/ IE=16% [worldwide on
desktop] The version are:
Microsoft Internet Explorer 11.0 = 13.71% Microsoft Internet Explorer 10 =
0.90 % Microsoft Internet Explorer 9 = 1,14 % Microsoft Internet Explorer 8
= 1,65 %

See: 
https://www.netmarketshare.com/browser-market-share.aspx?qprid=2=0

In fact the problem is the high numbers of IE 11 that doesn't support ES6

Bye

--
Zeno Tajoli
/SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche
Email: z.taj...@cineca.it Fax: 051/6132198
*CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)
___
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] ES6 usage in the staff client

2017-08-08 Thread Tajoli Zeno 

Hi to all,

Il 08/08/2017 12:30, Tomas Cohen Arazi ha scritto:
When people say IE, what specific version of the product are you all 
talking about?


in fact rearding https://www.netmarketshare.com/ IE=16% [worldwide on 
desktop]

The version are:
Microsoft Internet Explorer 11.0 = 13.71%
Microsoft Internet Explorer 10 = 0.90 %
Microsoft Internet Explorer 9 = 1,14 %
Microsoft Internet Explorer 8 = 1,65 %

See: 
https://www.netmarketshare.com/browser-market-share.aspx?qprid=2=0


In fact the problem is the high numbers of IE 11 that doesn't support ES6

Bye

--
Zeno Tajoli
/SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche
Email: z.taj...@cineca.it Fax: 051/6132198
*CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)
___
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] ES6 usage in the staff client

2017-08-08 Thread Tomas Cohen Arazi 
When people say IE, what specific version of the product are you all
talking about?

El mar., 8 de ago. de 2017 12:36 AM, David Cook <dc...@prosentient.com.au>
escribió:

> I can’t attend dev meetings due to being in the wrong timezone, so I’ll
> just speak up here.
>
>
>
> I’d say the circ rules editor is still used by quite a few of our IE using
> librarians. If the circ rules editor is broken for them, they’re going to
> notice. And that would mean either we don’t upgrade them to the version
> where it breaks, or we hack around the use of non-IE supported code. And I
> imagine we wouldn’t be the only people hacking the code to make it work in
> IE.
>
>
>
> If we do go with non-IE supported code, I think we’d want to have some way
> of falling back or degrading to a version that works. I’m 100% in favour of
> modernity, but I’m also 100% in favour of practicality for librarians.
>
>
>
> Looking at
> https://wiki.koha-community.org/wiki/Circulation_Rules_Interface_and_Backend_Revamp_RFC#Frontend
> and none of the mockup image links are working…
>
>
>
> David Cook
>
> Systems Librarian
>
> Prosentient Systems
>
> 72/330 Wattle St
>
> Ultimo, NSW 2007
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Direct: 02 8005 0595
>
>
>
> *From:* Jesse [mailto:pianohac...@gmail.com]
> *Sent:* Tuesday, 8 August 2017 7:09 AM
> *To:* Christopher Davis <cgda...@uintah.utah.gov>
> *Cc:* David Cook <dc...@prosentient.com.au>; Koha Devel <
> koha-devel@lists.koha-community.org>
>
>
> *Subject:* Re: [Koha-devel] ES6 usage in the staff client
>
>
>
> Owen, to answer your question, I'm working on bug 15522 (
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15522), the
> circ rules editor revamp. Hoping to get a very basic prototype out soon.
>
>
> I've added this to the next dev meeting, but I do want to mention
> something; while I have no great love for IE, and would love to encourage
> its abandonment, the circ rules editor is going to be accessed by a small
> subset of the staff. It may be less of a pain point to introduce
> non-IE-compatible code here than, say, the checkout screen.
>
>
>
> 2017-08-07 8:05 GMT-06:00 Christopher Davis <cgda...@uintah.utah.gov>:
>
> Interesting topic!
>
>
>
> Christopher Davis
>
> Systems & E-Services Librarian
>
> Uintah County Library
>
> cgda...@uintah.utah.gov
>
> (435) 789-0091 <14357890091> ext.261
> uintahlibrary.org
> basinlibraries.org
> facebook.com/uintahcountylibrary
> instagram.com/uintahcountylibrary
>
>
>
> On Sun, Aug 6, 2017 at 5:54 PM, David Cook <dc...@prosentient.com.au>
> wrote:
>
> I agree with Michael. While great strides have been made to get people off
> of IE6 and IE7 and Windows XP, there are still a lot of professionals being
> forced by their IT departments to use older versions of Windows and older
> versions of Internet Explorer.
>
> Over the years, I've upstreamed a number of IE fixes and in a sense been a
> de facto Koha IE maintainer, but it sounds like that might not be possible
> in this case. If we go too far away from what users - rather than
> developers - actually use... then I think we have a problem. I think we'd
> be forfeiting users and potential users of Koha to other systems or to
> out-dated versions of Koha.
>
> Maybe this is a crossroads where developing multiple themes again might be
> a good idea. I don't love the idea, but that might be one way of having an
> up-to-date backend with a modern front-end and a legacy front-end for
> people who can't have a modern option. In that case, it would be all the
> more reason for keeping business logic in code rather than templates. But
> that's just one idea.
>
> Then again... maybe completely breaking Koha's staff end for IE users
> would make professionals put more demands on their IT departments. Demands
> such that IT departments were forced to actually support Firefox or Chrome.
> I wouldn't hold my breath, but... you never know. I could see us bending
> over backwards locally to provide an option to IE users though. And off the
> top of my head that would probably mean staying on an older version of Koha
> or trying to create our own theme to work with an upgraded backend or to
> replace the staff client all together with a simplified cross-browser user
> interface.
>
> 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..

Re: [Koha-devel] ES6 usage in the staff client

2017-08-07 Thread David Cook 
I can’t attend dev meetings due to being in the wrong timezone, so I’ll just 
speak up here.

 

I’d say the circ rules editor is still used by quite a few of our IE using 
librarians. If the circ rules editor is broken for them, they’re going to 
notice. And that would mean either we don’t upgrade them to the version where 
it breaks, or we hack around the use of non-IE supported code. And I imagine we 
wouldn’t be the only people hacking the code to make it work in IE. 

 

If we do go with non-IE supported code, I think we’d want to have some way of 
falling back or degrading to a version that works. I’m 100% in favour of 
modernity, but I’m also 100% in favour of practicality for librarians. 

 

Looking at  
<https://wiki.koha-community.org/wiki/Circulation_Rules_Interface_and_Backend_Revamp_RFC#Frontend>
 
https://wiki.koha-community.org/wiki/Circulation_Rules_Interface_and_Backend_Revamp_RFC#Frontend
 and none of the mockup image links are working…

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: Jesse [mailto:pianohac...@gmail.com] 
Sent: Tuesday, 8 August 2017 7:09 AM
To: Christopher Davis <cgda...@uintah.utah.gov>
Cc: David Cook <dc...@prosentient.com.au>; Koha Devel 
<koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] ES6 usage in the staff client

 

Owen, to answer your question, I'm working on bug 15522 
(https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15522), the circ 
rules editor revamp. Hoping to get a very basic prototype out soon.


I've added this to the next dev meeting, but I do want to mention something; 
while I have no great love for IE, and would love to encourage its abandonment, 
the circ rules editor is going to be accessed by a small subset of the staff. 
It may be less of a pain point to introduce non-IE-compatible code here than, 
say, the checkout screen.

 

2017-08-07 8:05 GMT-06:00 Christopher Davis <cgda...@uintah.utah.gov 
<mailto:cgda...@uintah.utah.gov> >:

Interesting topic!




 
Christopher Davis

Systems & E-Services Librarian

Uintah County Library

 <mailto:cgda...@uintah.utah.gov> cgda...@uintah.utah.gov

(435) 789-0091   ext.261
uintahlibrary.org <http://uintahlibrary.org> 
basinlibraries.org <http://basinlibraries.org> 
facebook.com/uintahcountylibrary <http://facebook.com/uintahcountylibrary> 
instagram.com/uintahcountylibrary <http://instagram.com/uintahcountylibrary> 

  
<https://drive.google.com/a/uintah.utah.gov/uc?id=0B3CXDpFsfriXUHpVNjFKZ25QckU=download>
 

 

On Sun, Aug 6, 2017 at 5:54 PM, David Cook <dc...@prosentient.com.au 
<mailto:dc...@prosentient.com.au> > wrote:

I agree with Michael. While great strides have been made to get people off of 
IE6 and IE7 and Windows XP, there are still a lot of professionals being forced 
by their IT departments to use older versions of Windows and older versions of 
Internet Explorer.

Over the years, I've upstreamed a number of IE fixes and in a sense been a de 
facto Koha IE maintainer, but it sounds like that might not be possible in this 
case. If we go too far away from what users - rather than developers - actually 
use... then I think we have a problem. I think we'd be forfeiting users and 
potential users of Koha to other systems or to out-dated versions of Koha.

Maybe this is a crossroads where developing multiple themes again might be a 
good idea. I don't love the idea, but that might be one way of having an 
up-to-date backend with a modern front-end and a legacy front-end for people 
who can't have a modern option. In that case, it would be all the more reason 
for keeping business logic in code rather than templates. But that's just one 
idea.

Then again... maybe completely breaking Koha's staff end for IE users would 
make professionals put more demands on their IT departments. Demands such that 
IT departments were forced to actually support Firefox or Chrome. I wouldn't 
hold my breath, but... you never know. I could see us bending over backwards 
locally to provide an option to IE users though. And off the top of my head 
that would probably mean staying on an older version of Koha or trying to 
create our own theme to work with an upgraded backend or to replace the staff 
client all together with a simplified cross-browser user interface.

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>  
[mailto:koha-devel-boun...@lists.koha-community.org 
<mailto:koha-devel-boun...@lists.koha-community.org> ] On Behalf Of Michael Kuhn
Sent: Friday, 4 August 2017 10:04 PM
To: koha-devel@lists.koha-community.org 
<mailto:koha-devel@lists.koha-community.org

Re: [Koha-devel] ES6 usage in the staff client

2017-08-07 Thread Jesse 
Owen, to answer your question, I'm working on bug 15522 (
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15522), the circ
rules editor revamp. Hoping to get a very basic prototype out soon.

I've added this to the next dev meeting, but I do want to mention
something; while I have no great love for IE, and would love to encourage
its abandonment, the circ rules editor is going to be accessed by a small
subset of the staff. It may be less of a pain point to introduce
non-IE-compatible code here than, say, the checkout screen.

2017-08-07 8:05 GMT-06:00 Christopher Davis <cgda...@uintah.utah.gov>:

> Interesting topic!
>
>
> Christopher Davis
> Systems & E-Services Librarian
> Uintah County Library
> cgda...@uintah.utah.gov
> (435) 789-0091 <14357890091> ext.261
> uintahlibrary.org
> basinlibraries.org
> facebook.com/uintahcountylibrary
> instagram.com/uintahcountylibrary
>
>
> On Sun, Aug 6, 2017 at 5:54 PM, David Cook <dc...@prosentient.com.au>
> wrote:
>
>> I agree with Michael. While great strides have been made to get people
>> off of IE6 and IE7 and Windows XP, there are still a lot of professionals
>> being forced by their IT departments to use older versions of Windows and
>> older versions of Internet Explorer.
>>
>> Over the years, I've upstreamed a number of IE fixes and in a sense been
>> a de facto Koha IE maintainer, but it sounds like that might not be
>> possible in this case. If we go too far away from what users - rather than
>> developers - actually use... then I think we have a problem. I think we'd
>> be forfeiting users and potential users of Koha to other systems or to
>> out-dated versions of Koha.
>>
>> Maybe this is a crossroads where developing multiple themes again might
>> be a good idea. I don't love the idea, but that might be one way of having
>> an up-to-date backend with a modern front-end and a legacy front-end for
>> people who can't have a modern option. In that case, it would be all the
>> more reason for keeping business logic in code rather than templates. But
>> that's just one idea.
>>
>> Then again... maybe completely breaking Koha's staff end for IE users
>> would make professionals put more demands on their IT departments. Demands
>> such that IT departments were forced to actually support Firefox or Chrome.
>> I wouldn't hold my breath, but... you never know. I could see us bending
>> over backwards locally to provide an option to IE users though. And off the
>> top of my head that would probably mean staying on an older version of Koha
>> or trying to create our own theme to work with an upgraded backend or to
>> replace the staff client all together with a simplified cross-browser user
>> interface.
>>
>> 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 Michael Kuhn
>> Sent: Friday, 4 August 2017 10:04 PM
>> To: koha-devel@lists.koha-community.org
>> Subject: Re: [Koha-devel] ES6 usage in the staff client
>>
>> Am 04.08.2017 um 13:48 schrieb Owen Leonard:
>> >>* Use ES6 classes. This will work in Firefox 45+ (which includes
>> >> two ESR releases), Chrome 42+, Edge and Safari 9
>> >
>> > I'm leaning towards this option, but it would be nice to get some
>> > feedback from users (or from support companies who ask their users?)
>> > who might be required by their workplace to use IE.
>> >
>> > What are you working on?
>>
>> In
>> https://koha-community.org/manual/17.05/html/00_intro.html#
>> koha-recommendations
>> the documentation says: "When working in the Koha staff client it is
>> strongly recommended that you use the Firefox browser. Koha’s staff client
>> is not supported in Internet Explorer and has not yet been fully optimized
>> for Google Chrome."
>>
>> Personally I am working with Mozilla Firefox 54.0.
>>
>> But a lot of Koha staff users still work on MS Internet Explorer and
>> usually they are FORCED to do so by their IT departments. Probably many or
>> even most library users are also using the MS Internet Explorer when
>> accessing the OPAC, so I think this unloved webbrowser definitely has to be
>> supported in one way or the other (if not both).
>>
>> Best wishes: Michael
>> --
>> Geschäftsführer · Diplombibliothekar B

Re: [Koha-devel] ES6 usage in the staff client

2017-08-07 Thread Christopher Davis 
Interesting topic!


Christopher Davis
Systems & E-Services Librarian
Uintah County Library
cgda...@uintah.utah.gov
(435) 789-0091 <14357890091> ext.261
uintahlibrary.org
basinlibraries.org
facebook.com/uintahcountylibrary
instagram.com/uintahcountylibrary


On Sun, Aug 6, 2017 at 5:54 PM, David Cook <dc...@prosentient.com.au> wrote:

> I agree with Michael. While great strides have been made to get people off
> of IE6 and IE7 and Windows XP, there are still a lot of professionals being
> forced by their IT departments to use older versions of Windows and older
> versions of Internet Explorer.
>
> Over the years, I've upstreamed a number of IE fixes and in a sense been a
> de facto Koha IE maintainer, but it sounds like that might not be possible
> in this case. If we go too far away from what users - rather than
> developers - actually use... then I think we have a problem. I think we'd
> be forfeiting users and potential users of Koha to other systems or to
> out-dated versions of Koha.
>
> Maybe this is a crossroads where developing multiple themes again might be
> a good idea. I don't love the idea, but that might be one way of having an
> up-to-date backend with a modern front-end and a legacy front-end for
> people who can't have a modern option. In that case, it would be all the
> more reason for keeping business logic in code rather than templates. But
> that's just one idea.
>
> Then again... maybe completely breaking Koha's staff end for IE users
> would make professionals put more demands on their IT departments. Demands
> such that IT departments were forced to actually support Firefox or Chrome.
> I wouldn't hold my breath, but... you never know. I could see us bending
> over backwards locally to provide an option to IE users though. And off the
> top of my head that would probably mean staying on an older version of Koha
> or trying to create our own theme to work with an upgraded backend or to
> replace the staff client all together with a simplified cross-browser user
> interface.
>
> 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 Michael Kuhn
> Sent: Friday, 4 August 2017 10:04 PM
> To: koha-devel@lists.koha-community.org
> Subject: Re: [Koha-devel] ES6 usage in the staff client
>
> Am 04.08.2017 um 13:48 schrieb Owen Leonard:
> >>* Use ES6 classes. This will work in Firefox 45+ (which includes
> >> two ESR releases), Chrome 42+, Edge and Safari 9
> >
> > I'm leaning towards this option, but it would be nice to get some
> > feedback from users (or from support companies who ask their users?)
> > who might be required by their workplace to use IE.
> >
> > What are you working on?
>
> In
> https://koha-community.org/manual/17.05/html/00_intro.
> html#koha-recommendations
> the documentation says: "When working in the Koha staff client it is
> strongly recommended that you use the Firefox browser. Koha’s staff client
> is not supported in Internet Explorer and has not yet been fully optimized
> for Google Chrome."
>
> Personally I am working with Mozilla Firefox 54.0.
>
> But a lot of Koha staff users still work on MS Internet Explorer and
> usually they are FORCED to do so by their IT departments. Probably many or
> even most library users are also using the MS Internet Explorer when
> accessing the OPAC, so I think this unloved webbrowser definitely has to be
> supported in one way or the other (if not both).
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61
> 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
> ___
> 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] ES6 usage in the staff client

2017-08-06 Thread David Cook 
I agree with Michael. While great strides have been made to get people off of 
IE6 and IE7 and Windows XP, there are still a lot of professionals being forced 
by their IT departments to use older versions of Windows and older versions of 
Internet Explorer. 

Over the years, I've upstreamed a number of IE fixes and in a sense been a de 
facto Koha IE maintainer, but it sounds like that might not be possible in this 
case. If we go too far away from what users - rather than developers - actually 
use... then I think we have a problem. I think we'd be forfeiting users and 
potential users of Koha to other systems or to out-dated versions of Koha. 

Maybe this is a crossroads where developing multiple themes again might be a 
good idea. I don't love the idea, but that might be one way of having an 
up-to-date backend with a modern front-end and a legacy front-end for people 
who can't have a modern option. In that case, it would be all the more reason 
for keeping business logic in code rather than templates. But that's just one 
idea.

Then again... maybe completely breaking Koha's staff end for IE users would 
make professionals put more demands on their IT departments. Demands such that 
IT departments were forced to actually support Firefox or Chrome. I wouldn't 
hold my breath, but... you never know. I could see us bending over backwards 
locally to provide an option to IE users though. And off the top of my head 
that would probably mean staying on an older version of Koha or trying to 
create our own theme to work with an upgraded backend or to replace the staff 
client all together with a simplified cross-browser user interface. 

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 Michael Kuhn
Sent: Friday, 4 August 2017 10:04 PM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] ES6 usage in the staff client

Am 04.08.2017 um 13:48 schrieb Owen Leonard:
>>* Use ES6 classes. This will work in Firefox 45+ (which includes 
>> two ESR releases), Chrome 42+, Edge and Safari 9
> 
> I'm leaning towards this option, but it would be nice to get some 
> feedback from users (or from support companies who ask their users?) 
> who might be required by their workplace to use IE.
> 
> What are you working on?

In
https://koha-community.org/manual/17.05/html/00_intro.html#koha-recommendations
the documentation says: "When working in the Koha staff client it is strongly 
recommended that you use the Firefox browser. Koha’s staff client is not 
supported in Internet Explorer and has not yet been fully optimized for Google 
Chrome."

Personally I am working with Mozilla Firefox 54.0.

But a lot of Koha staff users still work on MS Internet Explorer and usually 
they are FORCED to do so by their IT departments. Probably many or even most 
library users are also using the MS Internet Explorer when accessing the OPAC, 
so I think this unloved webbrowser definitely has to be supported in one way or 
the other (if not both).

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin 
Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 
· E m...@adminkuhn.ch · W www.adminkuhn.ch 
___
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] ES6 usage in the staff client

2017-08-04 Thread Paul A 
[apologies for top-posting]  All our cataloguers' work stations use 
Opera (v.44) which (from dev.opera):


"Opera now [version 29] supports ES6 classes in strict mode, providing 
the following features: prototype-based inheritance, constructors, super 
calls, instance methods, and static methods."


Can you confirm that "strict" mode (for whatever values that might have) 
is what you have in mind?


Thanks
--
Paul
Tired old sys-admin

On 2017-08-03 07:23 PM, Jesse wrote:
As part of my work with Preact (and previous work with React), I've been 
unsure what to do about these libraries' enthusiasm for ES6.


If you're not familiar, ES6 (or ES2015) is a recent, major update to the 
JavaScript standard, and brings in a number of improvements to the 
language. Many of these make small parts of JS development a bit more 
pleasant, but the most relevant addition is native class support.


These built-in classes have been embraced by a lot of modern JS 
libraries, including Preact. The commonly accepted way to write code in 
this libraries depends on support for classes, either from the browser 
itself or a transpiler like Babel. To use Preact, we have two options:


   * Use ES6 classes. This will work in Firefox 45+ (which includes two 
ESR releases), Chrome 42+, Edge and Safari 9 [1][2]. I believe this is a 
very reasonable set of browsers, for the staff client.
   * Use a shim for ES3 support (see [3] for an example of how this 
might work). This can be done, but locks us to an older and less-used 
way of developing on Preact/React.


I strongly prefer the first option, but would like your feedback.

[1] http://kangax.github.io/compat-table/es6/#test-class (Check "show 
obsolete platforms", and get ready for your browser to slow down.)
[2] http://caniuse.com/#feat=es6-class (This is pessimistic; FF has had 
support since version 45.)

[3] https://github.com/developit/preact-in-es3/blob/master/index.js

___
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] ES6 usage in the staff client

2017-08-04 Thread Michael Kuhn 

Am 04.08.2017 um 13:48 schrieb Owen Leonard:

   * Use ES6 classes. This will work in Firefox 45+ (which includes two ESR
releases), Chrome 42+, Edge and Safari 9


I'm leaning towards this option, but it would be nice to get some
feedback from users (or from support companies who ask their users?)
who might be required by their workplace to use IE.

What are you working on?


In 
https://koha-community.org/manual/17.05/html/00_intro.html#koha-recommendations 
the documentation says: "When working in the Koha staff client it is 
strongly recommended that you use the Firefox browser. Koha’s staff 
client is not supported in Internet Explorer and has not yet been fully 
optimized for Google Chrome."


Personally I am working with Mozilla Firefox 54.0.

But a lot of Koha staff users still work on MS Internet Explorer and 
usually they are FORCED to do so by their IT departments. Probably many 
or even most library users are also using the MS Internet Explorer when 
accessing the OPAC, so I think this unloved webbrowser definitely has to 
be supported in one way or the other (if not both).


Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
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] ES6 usage in the staff client

2017-08-04 Thread Owen Leonard 
>   * Use ES6 classes. This will work in Firefox 45+ (which includes two ESR
> releases), Chrome 42+, Edge and Safari 9

I'm leaning towards this option, but it would be nice to get some
feedback from users (or from support companies who ask their users?)
who might be required by their workplace to use IE.

What are you working on?

 -- 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] ES6 usage in the staff client

2017-08-04 Thread Tomas Cohen Arazi 
I think ES6 is broadly implemented in browsers (even edge) so it wouldn't
make sense to complicate the dev workflow without an obvious gain.

El jue., 3 de ago. de 2017 8:24 PM, Jesse  escribió:

> As part of my work with Preact (and previous work with React), I've been
> unsure what to do about these libraries' enthusiasm for ES6.
>
> If you're not familiar, ES6 (or ES2015) is a recent, major update to the
> JavaScript standard, and brings in a number of improvements to the
> language. Many of these make small parts of JS development a bit more
> pleasant, but the most relevant addition is native class support.
>
> These built-in classes have been embraced by a lot of modern JS libraries,
> including Preact. The commonly accepted way to write code in this libraries
> depends on support for classes, either from the browser itself or a
> transpiler like Babel. To use Preact, we have two options:
>
>   * Use ES6 classes. This will work in Firefox 45+ (which includes two ESR
> releases), Chrome 42+, Edge and Safari 9 [1][2]. I believe this is a very
> reasonable set of browsers, for the staff client.
>   * Use a shim for ES3 support (see [3] for an example of how this might
> work). This can be done, but locks us to an older and less-used way of
> developing on Preact/React.
>
> I strongly prefer the first option, but would like your feedback.
>
> [1] http://kangax.github.io/compat-table/es6/#test-class (Check "show
> obsolete platforms", and get ready for your browser to slow down.)
> [2] http://caniuse.com/#feat=es6-class (This is pessimistic; FF has had
> support since version 45.)
> [3] https://github.com/developit/preact-in-es3/blob/master/index.js
>
>
> --
> Jesse Weaver
> ___
> 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/

-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
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/