> Koha throws a fatal error, which can only be resolved by deleting the
> problematic session from the table.
Did the error look like this? https://paste.koha-community.org/37943
If so then yes I've seen it! But I don't know what happened to trigger
it. I was able to resolve it by deleting
> Maybe just write Tim a mail and ask him to put us on his cloudflare allowlist.
I have sent a message to Tim. I'll pass on what I find.
-- Owen
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
I noticed recently that requests to LibraryThing's ThingISBN service
are being blocked. Koha tries to access a url like this:
https://www.librarything.com/api/thingISBN/0439139600
...which opens fine in a browser, but triggers the response "WARNING:
URL Request Failed 403 Forbidden" when Koha
> I’ll raise an issue with them. The git repo hasn’t been updated in over 2
> years but fingers crossed.
I'm not optimistic based on the lack of activity in other issues
raised there. At the very least we can patch our copy of the library
with a simple fix to remove the onclicks.
The bigger
> I'd like to propose replacing .scss-lint.yml with .stylelintrc.json,
> transferring
> most of the same rules.
Thanks for the feedback everyone. I'll work on a patch for the lint
config and also one to add stylelint to the CSS build workflow.
-- Owen
Hi all,
Back when we switched from LESS to SCSS in the OPAC (Bug 20427) I
added a linting configuration, .scss-lint.yml. I've always configured
my editor to automatically lint SCSS using this configuration. I don't
know if anyone else does this too.
In VS Code I was using scss-lint for this, but
> Microsoft has EOLed Internet Explorer.
In that case, when my corpse has been in the ground for a minimum of
six months you can start calling me EOLed
> I think we use a mix of jQuery date picker and Flatpickr
All dependencies on Bug 29239, "[OMNIBUS] Replace jQueryUI's
timepicker with
> An alternative could be to add the following to the dropdown in question:
>
> max-height: 33vh;
> overflow-y: auto;
This seems to work well. I think the only disadvantage to adding this
globally would be that there is an empty scrollbar if the menu doesn't
overflow.
On the library groups page
> Is it just me or is the CSS on the OPAC not using Bootstrap CSS?
It is. Bootstrap 3 or 4 depending on your Koha version. I think maybe
it looks like it isn't because we're now compiling Bootstrap from SCSS
directly into opac.css.
-- Owen
___
> Does anyone else have an issue with the OPAC search results not displaying
> correctly on smaller device screens?
Are you seeing it in master? Sounds like Bug 29603.
-- Owen
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
Hi everyone,
I've got a few patches awaiting signoff which I'd love to see make it
into 22.05. They're minor issues but I think they'd be good to have:
30388 -- Fix some errors in the template for ordering from a MARC file
30422 -- Authorities editor update broke the feature added by Bug 20154
> * April 29 - "Soft" feature freeze : nothing big or with high risk of
> side-effects will be included into the final release if not marked as
If I may make a request, I'd love to see Bug 29155 make it in: Upgrade
jquery version. This patches some known vulnerabilities in the jQuery
version we
On Thu, Feb 10, 2022 at 3:27 PM Fridolin SOMERS
wrote:
> Hi devels.
> I've changed next dev IRC meeting hour from 15 UTC to 10 UTC.
> https://wiki.koha-community.org/wiki/Development_IRC_meeting_16_February_2022#Time
I have added an item to the agenda: Share proposal for staff interface
There has been some discussion on Bug 26019 about how to handle the
changing ways browsers are handling the "SameSite" attribute in
cookies:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26019
There doesn't seem to be a consensus on how to proceed, and I guess
part of the question is
As Paul announced in December
(https://lists.koha-community.org/pipermail/koha-devel/2021-December/046841.html)
Biblibre is sponsoring a refresh of the staff interface design. They
have hired a graphic designer, Thibaud Petit, to create some
proposals, and will have an intern starting in February
> Is there a way to use a barcode multiple time
Koha expects items to have unique barcodes. I don't think what you're
describing is possible.
Owen
--
Web Developer
Athens County Public Libraries
(740) 737-6006
https://www.myacpl.org
___
Koha-devel
> And also, what's on your list for 22.05?
Some larger things I'm working on:
- Upgrading jQuery in the OPAC and staff client. This depends on
upgrading jQueryUI which depends on getting the last of the Flatpickr
patches in.
- Continue to replace jQueryUI widgets with alternatives, starting
with
> often by users still on Windows 7 boxes (msft eoled Win7 in Jan 2020 iirc)
For those users there is a Windows application:
https://github.com/bywatersolutions/koha-offline-circulation/releases/tag/v1.3.2
Is that a feasible alternative?
-- Owen
--
Web Developer
Athens County Public
> Does anyone use it? The one enabled by the AllowOfflineCirculation
> system preference.
This question elicited a flood of zero responses, and I'm not sure
what that means!
In any case, I've looked at this issue again and discovered that the
feature is broken in up-to-date browsers. It depends
Does anyone use it? The one enabled by the AllowOfflineCirculation
system preference. I don't think the core functionality of the feature
has been touched since its original introduction and I'm concerned
that it either doesn't work or is too fragile to be used in
production.
I'm not asking
We're making progress towards a replacement for the jQueryUI
datepicker component: Bug 28376, "Replace obsolete
jquery-ui-timepicker-addon"
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28376
I think it would be a good idea to look at replacing the rest of the
jQueryUI components we
> Just a side note: jQuery UI hasn't seen much development lately. I
> wouldn't build new functionality on top of it.
I agree 100%. Although it continues to work well for us, I'm concerned
about its long-term health.
-- Owen
--
Web Developer
Athens County Public Libraries
(740) 737-6006
> Does anyone know why #wrap in
> koha-tmpl/opac-tmpl/bootstrap/css/src/_common.scss has padding-left: 40px and
> padding-right: 40px?
Because the OPAC was designed to have 40 pixels of padding on either
side of the main content.
> It makes adding full-width headers/footers impossible without
On Wed, Jul 15, 2020 at 10:41 PM wrote:
>
> Yeah, I'm not a fan of a single big file either.
...
> It looks like that 1 file is 764 lines long
For comparison, columns_settings.yml is currently 1434 lines long.
-- Owen
--
Web Developer
Athens County Public Libraries
(740) 737-6006
> Does anyone use Safari with Koha? I had someone using it the other day and
> they weren’t able to upload a MARC file to the Staged MARC Management.
In what way were they not able to upload?
I think we should do our best to support Safari.
-- Owen
--
Web Developer
Athens County Public
> this looks good to me - why do you think it might not be worth pursuing?
No particular reason, I just wanted to get some opinions in case there
was a downside I wasn't seeing.
Also: Julian is right, the t() macro works perfectly, I was just
looking at the wrong po file!
Thanks,
Owen
--
I've posted a work in progress here:
https://gitlab.com/koha-dev/koha-dev/-/tree/wip-2020-07-08-combine-header-searches
Katrin I liked your idea about defining the labels, but I'm not sure I
did exactly what you were suggesting. Even with the t() macro the
labels are still not picked up for
I'm playing around with the idea of eliminating all the many search
form include files (serials-search.inc, cat-search.inc,
checking-search.inc, etc.) and replacing them with a single template
which can be processed in different ways.
For instance, in the circulation-home.tt template, "[% INCLUDE
> Can you expand more on that?
Yes. Bootstrap assets would be downloaded in a dev environment during
"yarn install" as we do other npm packages. In the OPAC SCSS we can
then reference those files when we build the OPAC CSS:
/* Bootstrap imports */
@import
Hi all,
I've been working on a Bootstrap 4 upgrade to the OPAC (Bug 20168,
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20168).
My work in progress is here:
https://gitlab.com/koha-dev/koha-dev/-/tree/wip-2020-05-14-opac-bootstrap-4
One of the differences between this version and
> In the past, I have wondered if we could get rid of “/cgi-bin/koha” as a path
> prefix all together
No idea what that would involve (other than search-and-replace in the
templates), but from the user's point of view I think it would be a
nice improvement.
-- Owen
--
Web Developer
Athens
> yes, you'r right it is working with newer versions of koha, my fault...
There's certainly nothing wrong with asking about bugs with older
versions assuming they're still maintained!
-- Owen
--
Web Developer
Athens County Public Libraries
(740) 737-6006
https://www.myacpl.org
> we have realized that chrome is not printing (I think safari neither) any
> more list or carts from koha
It's working for me in Chrome and Safari on OS 10.15.4 in both master
and 19.05.x. What version are you testing in? What are the specific
symptoms of the problem?
-- Owen
--
Web
> The role proposals page for the upcoming 20.11 development cycle is now
> available
Corrected link for the 20.11 page:
https://wiki.koha-community.org/wiki/Roles_for_20.11
-- Owen
--
Web Developer
Athens County Public Libraries
(740) 737-6006
https://www.myacpl.org
> That said, I feel like Owen Leonard might be re-engineering that system
> currently?
Not me! I think Bug 15522, "New interface for revamped circulation
rules" is what you're thinking of.
-- Owen
--
Web Developer
Athens County Public Libraries
(740) 737-6006
https:
> It shows a table with users and there permissions.
> JS Datatable is OK with Koha 18.11 but not with master.
This didn't work for me in my test using master but my database has a
LOT of borrowers. Is the plugin trying to load all borrowers at once?
-- Owen
--
Web Developer
Athens County
Looks like this was the solution I used before. Thanks to whichever
person or search engine helped me with it. Sorry I don't remember. I
know I didn't come up with it myself.
Running this shell script worked for me today:
#! /bin/sh
export FIRST_RUN='true'
vagrant up --no-provision
vagrant ssh
I used koha-testing-docker on Windows 10 for a while and then it
stopped working for me altogether:
https://gitlab.com/koha-community/koha-testing-docker/issues/140
> 1. I had to switch the distribution to
> https://app.vagrantup.com/digital-port/boxes/debian-stretch64
> because otherwise I was
> (Historically, we’ve used our own custom desktop application to fill this
> niche.)
Your own custom super-secret desktop application!
-- Owen
--
Web Developer
Athens County Public Libraries
(740) 737-6006
https://www.myacpl.org
___
Koha-devel
> > Does anyone know if there was a reason the change made in Bug 19298
> > wasn't made to the OPAC search results page?
>
> I am not sure we are ready for that, it could impact performance if
> several records have a lot of items.
I certainly understand this concern. I think it's important to
Bug 19298, "allow_onshelf_holds is not calculated correctly in
opac-shelves" added a check of circulation rules to control whether
the "Place hold" button should appear on the OPAC list contents page.
I'm trying to restart my work on Bug 13121, "Move search results
"action" links ("Place hold,"
Bug 15522, "New interface for revamped circulation rules"
(https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15522) has
been in limbo for a long time. It's a big change that relies on a
patch that makes a big change: Bug 18936 - Convert issuingrules fields
to circulation_rules
> 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
I would love to get some help testing a patch I wrote which upgrades
the DataTables plugin in the staff client and adds some new style to
the default DataTables toolbar.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23013
The patch is too big to post on Bugzilla, so I created a
> Do we have a standard way of dealing with radio buttons mixed with other
> input types?
I've submitted a patch for Bug 21751 which I hope solves that
particular problem. There are several ways to handle radio buttons and
checkboxes, and the CSS can probably be consolidated somewhat. I'll
> this
>
> To 500$a for that record and save it.
>
> Now go view ‘Title notes’ in the OPAC for this record.
> Ugly HTML mess.
This is how I would expect it to work. MARC isn't intended to have
HTML markup in it.
-- Owen
--
Web Developer
Athens County Public Libraries
https://www.myacpl.org
> I'm starting with looking for instances of 'biblio', which should be
> 'Bibliographic record'.
Hopefully Bug 19833 took care of (most of?) them.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19833
> I'm wondering about instances of "Biblio number" in the text... I think that
>
> I've noticed that there's a translation too long in french in
> catalogue/moredetail.pl so it's unreadable. Cf image.
This is a problem with the page's stylesheet which can be corrected
immediately by adding some CSS to your intranetUserCSS system
preference:
ol.bibliodetails li {
clear:
> > Bit late in the project to make this change imo? But yes, our
> > interpretation is quite different ;)
> But it's never too late to make a positive change, right ? :)
I agree that it's not too late to make useful changes to our workflow.
There was a time when we didn't even sign off patches!
> I haven’t checked master yet, but in the 17.xx versions, I’m noticing it is
> really difficult to click the dropdown for “List prices are:” in “Ordering
> information” on /cgi-bin/koha/acqui/supplier.pl.
David did you create a bug report for this? If no, please do so.
-- Owen
--
Web
If there is consensus that the add/edit buttons should be in line with
the section headings:
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75780
-- Owen
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
I've submitted a patch on Bug 20779 to refresh the style of the patron
detail page, and I'd like to get some feedback on my proposal. Compare
this "before" image:
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75434
...with this screenshot after the patch has been applied:
> My +1, but only for the staff interface.
Yes, this proposal is limited to the staff client.
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
> I think most of our libraries are on modern browsers now, but for those that
> aren't...
I'll let the users of Internet Explorer 6, 7, and 8 come up with their
own solutions :P
> > https://caniuse.com/#search=main
-- Owen
--
Web Developer
Athens County Public Libraries
> Instead of class names, why not use the "new" HTML 5 elements, like
> , , and the others ?
https://caniuse.com/#search=main
Great idea Julian, I agree.
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha-devel
In case people have feelings about markup, I wanted to share Bug
20670, "Bug 20670 - Add markup and standard classes for sidebars and
main content areas."
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20670
The conversion of staff client templates to Bootstrap grids is
continuing,
> Great, too bad at my company almost everyone is at least partly a remote
> worker.
Yes, those of us who work solo do just fine with self-recrimination!
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha-devel
Hello all,
This is a reminder that there will be a Koha general IRC meeting in
about 24 hours, 4 April at 14UTC.
Please add anything you want to discuss to the agenda.
Please add your apologies if you can't make the meeting.
Local time conversion:
> Same goes for me - cait. You can find a lot of the devs are in the IRC
> channel
See here for a list of IRC regulars:
https://wiki.koha-community.org/wiki/IRC_Regulars
-- Owen (oleonard)
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
> According to https://stackoverflow.com/a/574698 the maximum length of an
> email address is 254 characters, so VARCHAR(255) should be enough.
> Do you know if there is any reason why we use mostly TEXT and MEDIUMTEXT
> for these columns ?
Is there ever a situation where we want to allow
> I've filed two bugs - 20053 and 20054 for these respectively. What do you
> all think? Should we fix this OR should be let things be as they are, for
> now?
I've been wanting to make the same change, so I'm all for fixing it.
-- Owen
--
Web Developer
Athens County Public Libraries
Is anyone currently working on, or have plans to work on Bug 19736,
"Add a digest option for AUTO_RENEWALS Notice?"
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19736
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
> It looks like opac-serial-issues.pl is linked at the bottom of the
> Subscriptions tab in the OPAC detail view.
Agreed. I won't be touching that one.
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha-devel
Hello everyone,
The deadline to submit proposals to host Kohacon 2018 has been
extended to 17 October 2017.
We currently have only one proposal from the United States.
Please add your proposal to the Koha Wiki
(https://wiki.koha-community.org/wiki/KohaCon18_Proposals).
Thanks,
Owen
--
Web
> * 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
The validation error in question is:
"Error: Element option without attribute label must not be empty."
There seems to be little to no human-readable documentation for that
particular error, but it seems to mean that these are invalid:
This is valid for some reason, but doesn't appear to be
> I'd like to add that if anybody would like help in the next few days with a
> testing environment, whether it's a guided tour of the koha-sandboxes, or
> help setting up kohadevbox (see https://github.com/digibib/kohadevbox ),
> feel free to ask me (barton) in IRC. Just mention my name in #koha,
>. I believe the vast majority have P5 priorities & low severity
> (i.e., are "enhancements" rather than critical or major).
Note that the priority scale (P5-P1) is not used. I agree with
Jonathan's process of evaluating the priority of bugs based on
severity. It should also be understood that
I've just started up a new kohadevbox installation on my Mac, and I'm
getting an internal server error message which I've never seen before.
On acqui/neworderbiblio.pl I get a completely blank page with just the
words "Internal Server Error." I've double-checked the DebugLevel
preference ("all")
> The form element is containing the input boxes for username and password.
Have you tried applying your styling to "#auth fieldset.brief" ?
#auth fieldset.brief {
border: 1px solid #CCC;
border-radius: 10px;
padding: 1em;
}
#auth legend {
border: 0;
line-height: 1em;
margin: 0;
}
If you didn't get the plain text version of that announcement you may
end up getting the wrong link for the date and time.
Just in case:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting=20170111T20
-- Owen
--
Web Developer
Athens County Public Libraries
> = Important bugs waiting for love =
I would like to add one to this list:
Bug 16239 - Upgrade Bootstrap in the staff client
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16239
Josef Moravec has contributed a lot of work with this patch, and I've
signed off on all of it, but it has
> However, I would like to know whether there is any way to extract the
> sub-title from the field marc using sql statement ?
Yes. See this example in the SQL reports library:
https://wiki.koha-community.org/wiki/SQL_Reports_Library#Title.2FSubtitle_List
-- Owen
--
Web Developer
Athens
I've been working on an update to the way the OPAC handles JavaScript,
with the long-term goal of being able to consolidate scripts in order
to take advantage of JS concatenation and minification as much as
possible.
Bug 17498 describes what I've been testing:
> let's say I have my PC and I have a windows on it , and I have a virtual
> machine with Debian and koha dev
>
> Check out https://github.com/digibib/kohadevbox
> Its a vagrant-based development-environment which are used by many Koha
> developers.
As far as I know it is not possible to
> The next dev meeting is on November 9th and the time has been set to
> 19UTC but is flexible.
> I'd like to try something new and get an answer to this survey:
> https://framadate.org/3dAEB8zqQLzzTptD
Should we consider the times shown in the survey to be UTC?
-- Owen
--
Web Developer
> The reason I’m asking is: as soon a book with a reservation is returned on
> our selfcheck machines an email is added to the message_queue table with the
> status of pending.
It sounds to me like the problem isn't that the message in the queue
should be marked differently. It sounds like the
On Wed, Mar 2, 2016 at 11:44 AM, Wolfram Schneider wrote:
> how about using webpack?
>
> https://webpack.github.io/docs/
Kyle proposes the use of webpack in his React proof of concept (Bug
17297 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17297).
Since then I've
Sorry folks, but this is pretty long.
> That said, I think it’s a shame that Koha has no priorities. I also want
> Koha to be the fastest, slickest most useful ILS in the world, but I think
> more collaboration and cooperation would help ensure that.
For companies to collaborate and cooperate
> I'm trying to figure out where the field authentication of the borrowers
> table is used?
I don't see borrowers.authentication in the schema:
http://schema.koha-community.org/tables/borrowers.html
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
> 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
> check out, check in, restart mysql server, check out, check in... old_issues
> bug!
What exactly is the bug?
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha-devel mailing list
> Do you have any documentation for preferred use of jQuery tabs?
Hi David,
Sorry to have let your question hang for so long!
If I had to describe how tabs are generally used in Koha I would say
that they are used to present distinct sub-categories of information
about a thing in a way which
> I would love to get help getting that list down to zero. Please take a
> look if you can.
Sorry for the bad link. I guess I don't know how to share a saved
search correctly. Here's a giant link:
Recently I've been going through the list of bugs reports on
unmaintained 3.x versions of Koha. I've closed bugs which I could not
verify and updated to 'master' those which I could reproduce.
The list is down to 45 bugs which I had questions about, didn't
understand, or didn't know how to test.
> Does anyone have any strong objections to shutting down the mailing list?
+1 to shutting down the patches mailing list.
I haven't heard any objections yet, so let's move forward on it.
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
Now that there is a generic file upload tool, could that be used to
offer more customization options in areas where file selections are
used? I'm imagining a system where you define upload categories: CSS,
image, audio file, XSLT. Then wherever a setting allows you to select
a file in that
It sounds like there is no urgent desire to change the workflow, which
is good because I think that means nobody is upset about any recent
interface changes.
I think that maintaining the interface guidelines and pattern
documentation is a good idea, and I will continue to do so. I don't
think
On Thu, Apr 7, 2016 at 3:23 PM, Julian Maurice
wrote:
> jQuery 1.12 seems to be the last release of the 1.x branch.
> What's next ? Should we upgrade to 2.x ? 3.x ?
We can assume that we will upgrade it to something. I don't think we
should complicate this
> I have filed a new bug with a plan for how to move forward on an
> upgrade of jQuery in the staff client.
>
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883
This is stuck, so I need to ask for suggestions on how to proceed.
Jonathan and I have two different proposals. Mine:
-
> I've already been through the schema diagram available on schema spy but I
> still need more clarification.
If you ask a question about the database someone might be able to help you.
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
Sorry for being the guy who thinks way too much about buttons.
I have added a section to the interface guidelines in the wiki all
about buttons:
https://wiki.koha-community.org/wiki/Interface_patterns#Buttons
I think it's an accurate description of how we're doing things now.
Please let me know
The staff client uses (albeit inconsistently) the "accesskey"
attribute in some dialogs where a Yes/No choice is offered:
Yes, delete (Y) / No, don't delete (N)
I've just seen that the addition of the renew tab in the header search
form assigned "Alt-y" to the renew form. These two shortcuts
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883
I've attached a proof-of-concept patch to the bug which does the following:
- Adds jQuery 1.12.0
- Adds jQueryUI 1.11.4
- Adds a new version of doc-head-close.inc,
doc-head-close-jquery-1.12.0.inc, to be included on pages which
Are we at an impasse on this? I think the lack of *something* to
manage front-end assets is making Koha less efficient to use and more
difficult and error-prone to develop for.
-- Owen
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
> and seeing this bugzilla:
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14076
I filed the similar Bug 15747:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15747
Not sure if it should be considered a duplicate?
-- Owen
--
Web Developer
Athens County Public
> Jake [2] *is* packaged for Debian -- would that work for you as an
> alternative, Owen?
After a quick look at Jake I'm concerned that it is not as
fully-featured or well-documented than Grunt or Gulp. The wider
adoption of Grunt and Gulp mean that there is a more vibrant array of
plugins for
> make regeneration of the CSS from the LESS a bit more straightforward, and
> allow us to remove the generated files from Git.
Removing the generated files from git makes sense from a front-end
developer's point of view, but I wonder if that doesn't create too
many problems for
I would very much like to start using some kind of build tool for
front-end assets in Koha. The ones I've encountered are Grunt and
Gulp:
Grunt: http://gruntjs.com/
Gulp: http://gulpjs.com/
I have some experience with Grunt, and have heard good things about
Gulp. Has anyone else used either in
> IRC is flooded with spam.
For reference:
http://irc.koha-community.org/koha/2016-02-05#i_1786129
> It would be nice to have somebody with op rights for EU mornings.
Sounds like a good idea to me.
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
1 - 100 of 223 matches
Mail list logo