Is it possible to also include the pro version of FontAwesome?

Directory FontAwesome Iron Iconset
1

Is it possible to also include the pro version of FontAwesome?

2

Hello. We don’t have access to the FontAwesomePro sources, but if they include sprite files (such as [this one]
(https://raw.githubusercontent.com/FortAwesome/Font-Awesome/master/sprites/regular.svg)) it would be possible to modify the code generator, so that it generates the enum based on that external provided file.

The actual compilation would be covered under FontAwesomePro license (“creators may make copies of Pro Icons and Pro Software, make changes to Pro Icons, and share their changes with other Creators”), hence we cannot publish it as an open source addon, but we can update the POM file and provide instructions for building it.

3

Thank you for the answer! I figured it out… the only thing missing is the styling possibility for fa-primary and fa-secondary.
This is the first part of the iconset in fad.js:

<iron-iconset-svg name="fad">
   <svg xmlns:svg="http://www.w3.org/2000/svg">
      <defs>
         <g id="abacus">
            <svg viewBox="0 0 576 512">
               <path xmlns="http://www.w3.org/2000/svg"
                     d="M192 440h-32v-48h32zM160 72v48h32V72zm96 160v48h32v-48zm-96 0v48h32v-48zm96 208h160v-48H256zm96-160h128v-48H352zM544 0a32 32 0 0 0-32 32v464a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16V32a32 32 0 0 0-32-32zM416 72H256v48h160zM32 0A32 32 0 0 0 0 32v464a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16V32A32 32 0 0 0 32 0z"
                     class="fa-secondary"/>
               <path xmlns="http://www.w3.org/2000/svg"
                     d="M144 32h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16V48a16 16 0 0 0-16-16zm96 0h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16V48a16 16 0 0 0-16-16zm-96 160h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16v-96a16 16 0 0 0-16-16zm192 0h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16v-96a16 16 0 0 0-16-16zm-96 0h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16v-96a16 16 0 0 0-16-16zM464 32h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16V48a16 16 0 0 0-16-16zM144 352h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16v-96a16 16 0 0 0-16-16zm96 0h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16v-96a16 16 0 0 0-16-16zm224 0h-32a16 16 0 0 0-16 16v96a16 16 0 0 0 16 16h32a16 16 0 0 0 16-16v-96a16 16 0 0 0-16-16z"
                     class="fa-primary"/>
            </svg>
         </g>
		 ...

Where would I define this style to make the secondary part of each icon more transparent?
.fa-secondary { opacity:.4; }

4

Hi Moritz,

Release 2.2.0 adds support for Duotone icons.

There is a [custom web-component]
(https://github.com/FlowingCode/FontAwesomeIronIconset/blob/master/src/main/resources/META-INF/resources/frontend/font-awesome-duotone/duotone.js) that allows injecting CSS variables into the .fa-primary and .fa-secondary CSS classes.

As a special case, the code generator will detect a file named “duotone.svg” and annotate the correspoding Icon class with
@Tag("duotone-icon") @JsModule("./font-awesome-duotone/duotone.js")
Note that neither duotone.svg nor Duotone.Icon are included with the addon.

5

Thank you :)