>From the looks of it, FontAwesome 5 looks like a completely new project with the same name/versioning system.
I say we stick with FontAwesome 4.7 and hence the current Apache friendly licences. FlexJS users can buy fontawesome 5 and easily build their own library out of it. Thanks, Om On Wed, Jan 4, 2017 at 12:19 AM, Harbs <harbs.li...@gmail.com> wrote: > Font Awesome 5 has a different license and I think even the “free” one is > not an Apache-compatible license. > > There’s probably some way to have a optional “opt-in” for Font Awesome 5, > but ultimately the best way to support that might be outside of Apache. > > On Jan 3, 2017, at 10:55 PM, Christofer Dutz <christofer.d...@c-ware.de> > wrote: > > > And eventually over this year FontAwesome 5 will be published with a lot > of OpenSource extensions (because the Kickstarter Campaign went so well) > > https://www.kickstarter.com/projects/232193852/font-awesome-5 > > > > Here the most interesting parts for the “Free” version: > > > > Funded!!! We’ll add our most-awesome Pro-only code features (but not the > Pro icons) to Font Awesome Free! That means we’ll open source our > super-awesome SVG Framework AND we’ll make all of our JavaScript component > packages available as well! More sprinkles for everyone! > > > > Funded! For React, Angular, Ember.js, and Vue.js, we’ll make > framework-native JavaScript components installable through your favorite > package manager (npm, yarn) for FA Pro. Free for all of our Pro backers! > > > > Funded! We'll include basic SVG files for free in Font Awesome 5 Free! > This won't include any of our SVG framework magic, but should make using > Font Awesome Free easier on the desktop and for folks who love SVG! > > > > 46 Icon Packs Funded! For every icon category pack, we'll add 10 more > icons to Font Awesome Free and another 30 more icons to Font Awesome Pro. > These icon packs are available for free for all Pro backers, but will cost > $10 each after the Kickstarter. Support now and save! > > > > Chris > > > > Am 03.01.17, 21:12 schrieb "carlos.rov...@gmail.com im Auftrag von > Carlos Rovira" <carlos.rov...@gmail.com im Auftrag von > carlos.rov...@codeoscopic.com>: > > > > I think that would be a great addition Om. Thanks for working on > that! :) > > > > 2017-01-03 20:00 GMT+01:00 OmPrakash Muppirala <bigosma...@gmail.com > >: > > > >> Just a heads-up, I have started working on a FontAwesome library for > >> FlexJS. Some basic code is here, in case someone wants to take a peek: > >> https://github.com/apache/flex-asjs/tree/feature/fontawesome > >> > >> I needed font awesome icons for the Flex Team Page app I have been > building > >> using FlexJS and MDL. I thought it would be a good addition. > >> > >> Thanks, > >> Om > >> > >> On Fri, Aug 26, 2016 at 7:27 AM, Alex Harui <aha...@adobe.com> wrote: > >> > >>> > >>> > >>> On 8/25/16, 11:56 PM, "OK" <p...@olafkrueger.net> wrote: > >>> > >>>> Got it, thanks for explanation Alex! > >>>> > >>>> But one question is left: > >>>> What is the difference between just loading a font and embedding a > font? > >>>> I thought "embedded" means that the font is delivered with our Flex > >>>> application so that it don't rely to > >>>> the client machine [1]. > >>>> But if we able to just load the font and use it with FlexJS for me it > >>>> seems > >>>> that's pretty ok. > >>>> So what would "embedding" mean in this context and what advantages > would > >>>> font "embedding" have? > >>> > >>> True embedding means that the font data is encoded into the SWF or > >> HTML/JS > >>> file and not a separate request to the server. > >>> Loading means a separate request for the server. It turns out that in > >> our > >>> current loading of a font SWF the font is embedded into the separate > font > >>> SWF. > >>> > >>> HTH, > >>> -Alex > >>> > >>> > >> > > > > > > > > -- > > > > Carlos Rovira > > Director General > > M: +34 607 22 60 05 > > http://www.codeoscopic.com > > http://www.avant2.es > > > > Este mensaje se dirige exclusivamente a su destinatario y puede > contener > > información privilegiada o confidencial. Si ha recibido este mensaje > por > > error, le rogamos que nos lo comunique inmediatamente por esta misma > vía y > > proceda a su destrucción. > > > > De la vigente Ley Orgánica de Protección de Datos (15/1999), le > comunicamos > > que sus datos forman parte de un fichero cuyo responsable es > CODEOSCOPIC > > S.A. La finalidad de dicho tratamiento es facilitar la prestación del > > servicio o información solicitados, teniendo usted derecho de acceso, > > rectificación, cancelación y oposición de sus datos dirigiéndose a > nuestras > > oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la > documentación > > necesaria. > > > > > >
