Re: [Koha-devel] Getting rid of YUI ?
On Tue, Nov 2, 2010 at 11:02 AM, Vincent Danjean wrote: > On 02/11/2010 14:32, Tomas Cohen Arazi wrote: >> On Tue, Nov 2, 2010 at 10:24 AM, Galen Charlton wrote: >>> Other question : should we have jquery code inside koha (and thus having to take care of the updates) or should we use an external source ? (does this exist ? for yui it does, see yuipath syspref in koha) >>> >>> I agree with Chris that we need to provide options for both an >>> external and internal source. >> >> I think Koha shouldn't depend on external libraries release cycles and >> provided API stability. We should depend on included and tested >> version of the libraries and backport security fixes from upstream. > > When Koha is packaged into a distribution (Debian for example), embedding > copies of external libraries is always a bad point. So, you should > prepare the code to use another (local) copy of this library. > > IMHO, the best way is to provide a copy of the external libraries with > the Koha code (so that users that download directly Koha can easily use > it) but to put it in a separate directory so that packagers can > remove it and replace it with symlinks to the system-wide library > (such as the contents of the libjs-jquery-ui package in Debian for > example) IMHO, it will always depend on the API stability of the libraries in use and, in the case you use as an example, the politics of the Linux distribution in question. As a maintainer of debian packages for Koha I'm sure you're confident about that in this specific distribution. Also, I'm not a jquery expert so I'm not aware of any non-stability on its API, so take my comments as mere questions. To+ ___ 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] Getting rid of YUI ?
On 02/11/2010 14:32, Tomas Cohen Arazi wrote: > On Tue, Nov 2, 2010 at 10:24 AM, Galen Charlton wrote: >> >>> Other question : should we have jquery code inside koha (and thus having >>> to take care of the updates) or should we use an external source ? (does >>> this exist ? for yui it does, see yuipath syspref in koha) >> >> I agree with Chris that we need to provide options for both an >> external and internal source. > > I think Koha shouldn't depend on external libraries release cycles and > provided API stability. We should depend on included and tested > version of the libraries and backport security fixes from upstream. When Koha is packaged into a distribution (Debian for example), embedding copies of external libraries is always a bad point. So, you should prepare the code to use another (local) copy of this library. IMHO, the best way is to provide a copy of the external libraries with the Koha code (so that users that download directly Koha can easily use it) but to put it in a separate directory so that packagers can remove it and replace it with symlinks to the system-wide library (such as the contents of the libjs-jquery-ui package in Debian for example) Regards Vincent > To+ -- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11ENSIMAG - antenne de Montbonnot Fax:+33 4 76 61 20 99ZIRST 51, avenue Jean Kuntzmann Email: vincent.danj...@imag.fr 38330 Montbonnot Saint Martin ___ 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] Getting rid of YUI ?
On Tue, Nov 2, 2010 at 10:24 AM, Galen Charlton wrote: > > > Other question : should we have jquery code inside koha (and thus having > > to take care of the updates) or should we use an external source ? (does > > this exist ? for yui it does, see yuipath syspref in koha) > > I agree with Chris that we need to provide options for both an > external and internal source. I think Koha shouldn't depend on external libraries release cycles and provided API stability. We should depend on included and tested version of the libraries and backport security fixes from upstream. To+ ___ 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] Getting rid of YUI ?
Hi, On Mon, Nov 1, 2010 at 11:07 PM, Paul Poulain wrote: > I think jquiry-ui (http://jqueryui.com) is good enough to decide to get > rid of YUI. I am in favor of this. > Other question : should we have jquery code inside koha (and thus having > to take care of the updates) or should we use an external source ? (does > this exist ? for yui it does, see yuipath syspref in koha) I agree with Chris that we need to provide options for both an external and internal source. Regards, Galen -- Galen Charlton gmcha...@gmail.com ___ 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] Getting rid of YUI ?
Another upvote for jQuery. I'm using it for Libki now. I find it far more elegant to work with than YUI. Kyle http://www.kylehall.info Mill Run Technology Solutions ( http://millruntech.com ) Crawford County Federated Library System ( http://www.ccfls.org ) Meadville Public Library ( http://www.meadvillelibrary.org ) On Tue, Nov 2, 2010 at 8:59 AM, Owen Leonard wrote: > > I think jquiry-ui (http://jqueryui.com) is good enough to decide to get > > rid of YUI. > > I think this is a good goal. I agree that JqueryUI is mature enough to > start using. > > > Cons: > > ? (Anyone want to argue ?) > > Not a con, but a difficulty: We need to choose a good jquery-based > menu system to replace the YUI one. This is something JqueryUI doesn't > offer. > > > -- 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] Getting rid of YUI ?
> I think jquiry-ui (http://jqueryui.com) is good enough to decide to get > rid of YUI. I think this is a good goal. I agree that JqueryUI is mature enough to start using. > Cons: > ? (Anyone want to argue ?) Not a con, but a difficulty: We need to choose a good jquery-based menu system to replace the YUI one. This is something JqueryUI doesn't offer. -- 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] Getting rid of YUI ?
On Mon, Nov 1, 2010 at 11:07 PM, Paul Poulain wrote: > > > Other question : should we have jquery code inside koha (and thus having > to take care of the updates) or should we use an external source ? (does > this exist ? for yui it does, see yuipath syspref in koha) > I have no problem with changing to something better than yui. Regarding the location of the source: I think that if we use an external source, we *must* include an internal version/option for those who are bandwidth challenged as well as in a preemptive protection against data link outages on local installations. Koha tends to bork if the yui source is external and the link to the internet dies. In this regard, we should also consider some fail over mechanism if we continue to use an external source so when the external source is unavailable for whatever reason, Koha drops back to the internal source. my $0.02 worth. Kind Regards, Chris ___ 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] Getting rid of YUI ?
Paul Poulain schreef op di 02-11-2010 om 04:07 [+0100]: > Other question : should we have jquery code inside koha (and thus > having > to take care of the updates) or should we use an external source ? > (does > this exist ? for yui it does, see yuipath syspref in koha) It would definitely have to be optional if it were made possible to use the hosted version, for people on non-internet-connected machines. However, this would encourage bringing the support up to modern jquery levels. There are currently issues in places when you use a current version (and this affects the packages which originally tried to use the debian packaged version.) -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D signature.asc Description: This is a digitally signed message part ___ 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] Getting rid of YUI ?
Hi world, As you know, we are using both YUI and jquery javascript libraries in Koha. That's too much ! I think jquiry-ui (http://jqueryui.com) is good enough to decide to get rid of YUI. Pro: * jquery much more developed * yui & webdev have problems working together * a lot of informations are available for jquery, including tutorials and books * http://jqueryui.com/docs/Theming/API seems much more clear & easy to use to me than yui css (is it just me ?) * jqueryui comes with (a themable) complete set of icons Cons: ? (Anyone want to argue ?) So, I propose the following roadmap : * new templates should be developed using jquery, not yui * 3.4 would still have both * in 3.6, we get rid of yui Other question : should we have jquery code inside koha (and thus having to take care of the updates) or should we use an external source ? (does this exist ? for yui it does, see yuipath syspref in koha) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 ___ 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/
