, but this code // executes before the first paint, when

Â鶹Çø

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); Missing the classics - News & Stories | Â鶹Çø

Â鶹Çø

Skip to main content

Spark

Missing the classics

Wed, Jun 15, 2016

I read the article about the college’s prioritization process in the winter issue of Spark with profound sadness. I graduated from the classics department with a major in Greek. My father, grandfather and great-grandfather also attended Calvin and received degrees in Greek and classical languages.

We all knew that Calvin was undergoing a difficult prioritization process that would see the end of a number of majors. What does surprise me is that only five majors were cut at all, and that three of these five were from the classics department.

Classics must no longer be important to Calvin College, despite our strong heritage as children of the Reformation, historical devotion to equipping students for seminary, and reputation for being careful students of biblical and theological history.

If the committee had looked at the product of various departments— the caliber of students and their contribution to the church and the world—rather than how many tuition dollars they bring in, I think they would have made very different decisions.

John Medendorp ’10, Kitchener, Ontario

Response: Prioritization has been a long and difficult process, and it is most difficult when it affects the disciplines we love and the faculty members who have provided faithful service to the college. It is important to keep in mind that Calvin still offers a classical studies major. I encourage readers who wish to better understand the care and thoroughness of this process to read the documents posted on President Le Roy’s website: .

Cheryl Brandsen
Calvin College Provost