Re: [Archivesspace_Users_Group] Rails help for font-awesome classes ?

2018-02-21 Thread Majewski, Steven Dennis (sdm7g)

Just to confirm: 

Production version of v2.3.0 downloaded zip file release from github:

gems/gems/font-awesome-sass-4.7.0/

Development gems, downloaded via ./build/run bootstrap:

build/gems/gems/font-awesome-sass-5.0.6.2/

— Steve. 



> On Feb 21, 2018, at 11:08 AM, Fox, Bobbi <bobbi_...@harvard.edu> wrote:
> 
> Hey, Steve,
>  
> Believe me, I feel you :-(
>  
> Cheers,
> Bobbi
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
> Majewski, Steven Dennis (sdm7g)
> Sent: Wednesday, February 21, 2018 11:07 AM
> To: Archivesspace Users Group 
> <archivesspace_users_group@lyralists.lyrasis.org>
> Subject: Re: [Archivesspace_Users_Group] Rails help for font-awesome classes ?
>  
> Thank you, Bobbi. This one had me scratching my head. 
> I hate finding surprises moving changes from test to production. 
>  
> — Steve. 
>  
>  
> On Feb 21, 2018, at 10:49 AM, Fox, Bobbi <bobbi_...@harvard.edu 
> <mailto:bobbi_...@harvard.edu>> wrote:
>  
> Hi,
>  
> Since I’m the one (for my sins) who implemented the use of Font Awesome icons 
>  (https://fontawesome.com <https://fontawesome.com/>) in the PUI, I did a 
> little digging.
>  
> FontAwesome has both changed what they make available as a free icon, and 
> also is deprecating some of their class names. 
>  
> ‘fa-file-image-o’ produced a “light” version of the file-image icon, and is 
> now no longer available as a free icon.  (This is true for any icon that ends 
> in –o)
>  
> Undoubtedly the reason you see it in the production version is due to the 
> fact that the icons were downloaded and packaged up *before* this change on 
> the part of FontAwesome, while your development mode probably did a download 
> more recently.
>  
> I don’t have an immediate solution to getting the old icons into the 
> development mode; sorry!
>  
> I guess I need to file a JIRA on this, as well.
>  
> --Bobbi
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
> [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>] On Behalf 
> Of Majewski, Steven Dennis (sdm7g)
> Sent: Tuesday, February 20, 2018 7:22 PM
> To: Archivesspace Users Group 
> <archivesspace_users_group@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: [Archivesspace_Users_Group] Rails help for font-awesome classes ?
>  
>  
> I expect that this has something to do with how stylesheet assets are 
> compiled in Rails, but can anyone explain it to me ? 
>  
> Running in development mode, testing changes to digital object views with 
> IIIF plugin, I noticed I was not seeing the font-awesome icon for the 
> 'fa-file-image-o’ class styles.
>  
>  
>  
> After poking around in the browser console and stylesheets, I discovered that 
> by removing the “-o” suffix, it worked again:
>  
>  
>  
>  
> Initially, I thought this may have been a bug introduced in some recent 
> changes to v2.3.0, but git log didn’t show any likely changes and when I 
> deployed my plugin changes to production, they icons were NOT displayed. 
>  
>  
> When I added the “-o” suffix back, they worked on production, but failed 
> running in development. 
> ( development = ./build/run public:devserver ) 
>  
>  
> The badges on the public resource pages use “fa-book” class for citation 
> badge and “fa-file-pdf-o” for print badge.
> Both of those display properly on production site, but the print badge is 
> missing in development mode. 
>  
>  
>  
> BTW: I was attempting to add appropriate icons switched by d_file[‘material’] 
>  
>  
> — Steve Majewski
>  
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



smime.p7s
Description: S/MIME cryptographic signature
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] Rails help for font-awesome classes ?

2018-02-21 Thread Fox, Bobbi
Hey, Steve,

Believe me, I feel you :-(

Cheers,
Bobbi

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 21, 2018 11:07 AM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Rails help for font-awesome classes ?

Thank you, Bobbi. This one had me scratching my head.
I hate finding surprises moving changes from test to production.

— Steve.


On Feb 21, 2018, at 10:49 AM, Fox, Bobbi 
<bobbi_...@harvard.edu<mailto:bobbi_...@harvard.edu>> wrote:

Hi,

Since I’m the one (for my sins) who implemented the use of Font Awesome icons  
(https://fontawesome.com<https://fontawesome.com/>) in the PUI, I did a little 
digging.

FontAwesome has both changed what they make available as a free icon, and also 
is deprecating some of their class names.

‘fa-file-image-o’ produced a “light” version of the file-image icon, and is now 
no longer available as a free icon.  (This is true for any icon that ends in –o)

Undoubtedly the reason you see it in the production version is due to the fact 
that the icons were downloaded and packaged up *before* this change on the part 
of FontAwesome, while your development mode probably did a download more 
recently.

I don’t have an immediate solution to getting the old icons into the 
development mode; sorry!

I guess I need to file a JIRA on this, as well.

--Bobbi

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 20, 2018 7:22 PM
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Rails help for font-awesome classes ?


I expect that this has something to do with how stylesheet assets are compiled 
in Rails, but can anyone explain it to me ?

Running in development mode, testing changes to digital object views with IIIF 
plugin, I noticed I was not seeing the font-awesome icon for the 
'fa-file-image-o’ class styles.

 

After poking around in the browser console and stylesheets, I discovered that 
by removing the “-o” suffix, it worked again:

 


Initially, I thought this may have been a bug introduced in some recent changes 
to v2.3.0, but git log didn’t show any likely changes and when I deployed my 
plugin changes to production, they icons were NOT displayed.


When I added the “-o” suffix back, they worked on production, but failed 
running in development.
( development = ./build/run public:devserver )


The badges on the public resource pages use “fa-book” class for citation badge 
and “fa-file-pdf-o” for print badge.
Both of those display properly on production site, but the print badge is 
missing in development mode.



BTW: I was attempting to add appropriate icons switched by d_file[‘material’]


— Steve Majewski


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] Rails help for font-awesome classes ?

2018-02-21 Thread Majewski, Steven Dennis (sdm7g)
Thank you, Bobbi. This one had me scratching my head. 
I hate finding surprises moving changes from test to production. 

— Steve. 


> On Feb 21, 2018, at 10:49 AM, Fox, Bobbi <bobbi_...@harvard.edu> wrote:
> 
> Hi,
>  
> Since I’m the one (for my sins) who implemented the use of Font Awesome icons 
>  (https://fontawesome.com <https://fontawesome.com/>) in the PUI, I did a 
> little digging.
>  
> FontAwesome has both changed what they make available as a free icon, and 
> also is deprecating some of their class names. 
>  
> ‘fa-file-image-o’ produced a “light” version of the file-image icon, and is 
> now no longer available as a free icon.  (This is true for any icon that ends 
> in –o)
>  
> Undoubtedly the reason you see it in the production version is due to the 
> fact that the icons were downloaded and packaged up *before* this change on 
> the part of FontAwesome, while your development mode probably did a download 
> more recently.
>  
> I don’t have an immediate solution to getting the old icons into the 
> development mode; sorry!
>  
> I guess I need to file a JIRA on this, as well.
>  
> --Bobbi
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
> Majewski, Steven Dennis (sdm7g)
> Sent: Tuesday, February 20, 2018 7:22 PM
> To: Archivesspace Users Group 
> <archivesspace_users_group@lyralists.lyrasis.org>
> Subject: [Archivesspace_Users_Group] Rails help for font-awesome classes ?
>  
>  
> I expect that this has something to do with how stylesheet assets are 
> compiled in Rails, but can anyone explain it to me ? 
>  
> Running in development mode, testing changes to digital object views with 
> IIIF plugin, I noticed I was not seeing the font-awesome icon for the 
> 'fa-file-image-o’ class styles.
>  
>  
>  
> After poking around in the browser console and stylesheets, I discovered that 
> by removing the “-o” suffix, it worked again:
>  
>  
>  
>  
> Initially, I thought this may have been a bug introduced in some recent 
> changes to v2.3.0, but git log didn’t show any likely changes and when I 
> deployed my plugin changes to production, they icons were NOT displayed. 
>  
>  
> When I added the “-o” suffix back, they worked on production, but failed 
> running in development. 
> ( development = ./build/run public:devserver ) 
>  
>  
> The badges on the public resource pages use “fa-book” class for citation 
> badge and “fa-file-pdf-o” for print badge.
> Both of those display properly on production site, but the print badge is 
> missing in development mode. 
>  
>  
>  
> BTW: I was attempting to add appropriate icons switched by d_file[‘material’] 
>  
>  
> — Steve Majewski
>  
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>


smime.p7s
Description: S/MIME cryptographic signature
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] Rails help for font-awesome classes ?

2018-02-21 Thread Fox, Bobbi
A little more information, for those who want to get into the weeds:

As I was writing up the JIRA, I found that FontAwesome has provided a “shim” 
for moving from Version 4 (which is what ArchivesSpace is using) to their 
completely-rewritten Verison 5, which is at 
https://fontawesome.com/how-to-use/upgrading-from-4#v4-shim.

hth,
Bobbi

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Fox, Bobbi
Sent: Wednesday, February 21, 2018 10:49 AM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Rails help for font-awesome classes ?

Hi,

Since I’m the one (for my sins) who implemented the use of Font Awesome icons  
(https://fontawesome.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__fontawesome.com=DwMGaQ=WO-RGvefibhHBZq3fL85hQ=5xWUzLrZrVLeTqs3CDoeRpPtLv1fRM04CCu4TDULrSY=G63kLehFSbGg9UBv6HQ0qxN-k3OLMjl_EwW1_MYtEfY=gEHnWImdoDuc5cn2KvrcwIfpltUNZwv8emcU4kLhX9Q=>)
 in the PUI, I did a little digging.

FontAwesome has both changed what they make available as a free icon, and also 
is deprecating some of their class names.

‘fa-file-image-o’ produced a “light” version of the file-image icon, and is now 
no longer available as a free icon.  (This is true for any icon that ends in –o)

Undoubtedly the reason you see it in the production version is due to the fact 
that the icons were downloaded and packaged up *before* this change on the part 
of FontAwesome, while your development mode probably did a download more 
recently.

I don’t have an immediate solution to getting the old icons into the 
development mode; sorry!

I guess I need to file a JIRA on this, as well.

--Bobbi

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 20, 2018 7:22 PM
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Rails help for font-awesome classes ?


I expect that this has something to do with how stylesheet assets are compiled 
in Rails, but can anyone explain it to me ?

Running in development mode, testing changes to digital object views with IIIF 
plugin, I noticed I was not seeing the font-awesome icon for the 
'fa-file-image-o’ class styles.

 

After poking around in the browser console and stylesheets, I discovered that 
by removing the “-o” suffix, it worked again:

 


Initially, I thought this may have been a bug introduced in some recent changes 
to v2.3.0, but git log didn’t show any likely changes and when I deployed my 
plugin changes to production, they icons were NOT displayed.


When I added the “-o” suffix back, they worked on production, but failed 
running in development.
( development = ./build/run public:devserver )


The badges on the public resource pages use “fa-book” class for citation badge 
and “fa-file-pdf-o” for print badge.
Both of those display properly on production site, but the print badge is 
missing in development mode.



BTW: I was attempting to add appropriate icons switched by d_file[‘material’]


— Steve Majewski


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] Rails help for font-awesome classes ?

2018-02-21 Thread Fox, Bobbi
Hi,

Since I’m the one (for my sins) who implemented the use of Font Awesome icons  
(https://fontawesome.com) in the PUI, I did a little digging.

FontAwesome has both changed what they make available as a free icon, and also 
is deprecating some of their class names.

‘fa-file-image-o’ produced a “light” version of the file-image icon, and is now 
no longer available as a free icon.  (This is true for any icon that ends in –o)

Undoubtedly the reason you see it in the production version is due to the fact 
that the icons were downloaded and packaged up *before* this change on the part 
of FontAwesome, while your development mode probably did a download more 
recently.

I don’t have an immediate solution to getting the old icons into the 
development mode; sorry!

I guess I need to file a JIRA on this, as well.

--Bobbi

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 20, 2018 7:22 PM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Rails help for font-awesome classes ?


I expect that this has something to do with how stylesheet assets are compiled 
in Rails, but can anyone explain it to me ?

Running in development mode, testing changes to digital object views with IIIF 
plugin, I noticed I was not seeing the font-awesome icon for the 
'fa-file-image-o’ class styles.

 

After poking around in the browser console and stylesheets, I discovered that 
by removing the “-o” suffix, it worked again:

 


Initially, I thought this may have been a bug introduced in some recent changes 
to v2.3.0, but git log didn’t show any likely changes and when I deployed my 
plugin changes to production, they icons were NOT displayed.


When I added the “-o” suffix back, they worked on production, but failed 
running in development.
( development = ./build/run public:devserver )


The badges on the public resource pages use “fa-book” class for citation badge 
and “fa-file-pdf-o” for print badge.
Both of those display properly on production site, but the print badge is 
missing in development mode.



BTW: I was attempting to add appropriate icons switched by d_file[‘material’]


— Steve Majewski


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


[Archivesspace_Users_Group] Rails help for font-awesome classes ?

2018-02-20 Thread Majewski, Steven Dennis (sdm7g)

I expect that this has something to do with how stylesheet assets are compiled 
in Rails, but can anyone explain it to me ? 

Running in development mode, testing changes to digital object views with IIIF 
plugin, I noticed I was not seeing the font-awesome icon for the 
'fa-file-image-o’ class styles.

 

After poking around in the browser console and stylesheets, I discovered that 
by removing the “-o” suffix, it worked again:

 


Initially, I thought this may have been a bug introduced in some recent changes 
to v2.3.0, but git log didn’t show any likely changes and when I deployed my 
plugin changes to production, they icons were NOT displayed. 


When I added the “-o” suffix back, they worked on production, but failed 
running in development. 
( development = ./build/run public:devserver ) 


The badges on the public resource pages use “fa-book” class for citation badge 
and “fa-file-pdf-o” for print badge.
Both of those display properly on production site, but the print badge is 
missing in development mode. 



BTW: I was attempting to add appropriate icons switched by d_file[‘material’] 


— Steve Majewski




smime.p7s
Description: S/MIME cryptographic signature
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group