About Features Downloads Getting Started Documentation Events Support GitHub

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
developers_call:minutes20190312

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
developers_call:minutes20190312 [2019/03/12 12:59] – [VuFind Developers Call Minutes: March 12, 2019] demiankatzdevelopers_call:minutes20190312 [2019/03/12 13:21] (current) – [3. Other Topics?] demiankatz
Line 29: Line 29:
  
 ==== 2. Development Planning ==== ==== 2. Development Planning ====
 +
 +=== Development Planning ===
 +
 +There was some discussion of [[https://github.com/vufind-org/vufind/pull/1335|PR #1335]]. Ere pointed out that it's important to allow the user to override the default pickup location when placing requests, since users sometimes have good reasons to do this (i.e. they are member of main library but live closer to branch library). He will review whether his instance is using any custom code around pickup locations, or whether the existing default VuFind logic is meeting local needs.
 +
 +Demian plans to investigate refactoring pickup-related logic to a service for centralization, unless someone objects.
  
 === Browse Handler Optimizations === === Browse Handler Optimizations ===
Line 44: Line 50:
 ==== 3. Other Topics? ==== ==== 3. Other Topics? ====
  
 +=== Future of LESS / SCSS ===
 +
 +Chris inquired whether there was a desire to move to a single CSS-related language, since the current system uses LESS as a primary option but also ports to SCSS for flexibility, and this requires some extra maintenance work. It seems that there are still significant needs for both formats, and taking either one away would cause significant inconvenience for someone. Demian suggested that it may be best to stick with the status quo for now, especially since recent SCSS work has introduced a more flexible mechanism for working around limitations of the automatic conversion. If we are going to make a drastic change, rather than choosing between one of two fairly contemporary technologies, it may be better to wait until there is something substantially better (such as a future hypothetical development that leverages native browser support more effectively) before investing effort in this.
 ===== Next Call ===== ===== Next Call =====
  
Line 49: Line 58:
  
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
developers_call/minutes20190312.1552395595.txt.gz · Last modified: 2019/03/12 12:59 by demiankatz