Font Awesome 4.6.0

  • oh, a new version released? that's great 2 know.

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.

  • @SoftCreatR is it possible to "replace" that stuff with a plugin

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.

  • I didnt ask you to do it just wondering about whether it's possible or not.

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.

  • okay... didnt know that one. but well a patch that updates WCF to latest font awesome would be epic.

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.

  • aside from testing only some font and css files have to be swapped, theoretically not much and could even be done with WCF2.1

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.

  • well I did say in theory. it depends what customizations are done in WCF with fontawesome. if the fonts and CSS are more or less seperate from the WCF and just included it would work as I said.
    but when they have customized some stuff it wont be that easy,

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.

  • well I did say in theory. it depends what customizations are done in WCF with fontawesome.

    By knowing that you don’t know what customization has to be make to update the font, you shouldn’t post any thought about it.
    Just stay calm and keep your fingers from writing if you don’t know the answer.

  • well I did check an fa update commit from wcf2.1 (or rather the 2 of them) and it doesnt look THAT hard
    step 1. replace the binaries.
    step 2. icons.less from fontawesome, replace every instance of {fa-css-prefix} with fa and copy the whole icon block into the fontawesome icon block of wcf's icons.less while replacing that block of the wcf file.
    step 3. copy all lines in variables.less that start with @fa-var into the variables.less from wcf while replacing that block of the wcf file.


    I am not exactly sure how to update the binaries with browser github but I could make the less files, albeit that you will have probably multilple commits to pull...

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.

  • Would be nice for users to decide the version of font awesome. Like adding a box in ACP where we can input the Font Awesome CDN link. The box can have a default value ( and even " reset to default " option ).

    Smile , it's good for health

  • well the Idea would be great but since different fontawesome levels have different LESS/CSS and the fa less in in the wcf less, that one has to be modified and cannot be loaded from CDN so strightly.

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.

  • well the technical side of updating fa in wcf2.1 is explained a post further above. maybe I can make a request for chaning in github

    aus angst vor Capslock nutze ich selten shift.


    in fear of capslock I rarely use shift.