Thanks Tony,
That was really quick. I’ll take a look at it.
Thanks
Justin
On February 8, 2018 at 5:14:57 AM, Tony Atkins (t...@raisingthefloor.org)
wrote:
Hi, All:
As I didn't want to block Justin's work, I went ahead and added the Vagrant
configuration and docs this morning. See my pull
Hi Tony,
I have the grunt tasks working for generating a the icon fonts. You can
either generate a font with all the icons or a custom font based off a
supplied config file.
https://github.com/jobara/infusion-icons/tree/FLUID-6244
Thanks again for the help with the VM setup.
Thanks
Justin
On
Hi Tony,
Thanks for your help. I’ll get the grunt script setup. It will be some
extra work to get things to work with an external config file, but I’m
hoping not much extra. Anyways I’ll check in with you once that’s in place.
We can add the font building to our CI, know that the build
Hi, Justin:
It's incredibly trivial to set up a Vagrantfile with Alfredo's new plugin.
Let me know once you have the grunt script setup and I can submit a pull
against your branch or otherwise assist.
Cheers,
Tony
On 1 February 2018 at 22:10, Justin Obara wrote:
>
Hi, Justin.
I'm definitely a bigger fan of making it possible to use the VM for this,
even if some of us choose to install the libraries and run the commands on
their machine. We can express (in the VM configuration) the dependencies
that are required in a clear way that can be tested. There
Hi Tony,
I was thinking about this more today and I’m not sure it will work in the
same repo. Basically the issue is that it uses a grunt task to do the font
generation while relying on fontforge and ttfautohint installed separately
on the machine. The issue of course is the npm install required
Hi Tony,
Thanks for this suggestion. The VM approach seems like a good option. I
don’t think it will be something that we run that frequently, so the
overhead of the VM shouldn’t be too much to worry about.
Regarding location, I think I’d prefer having it in the main repo. I feel
like it will be
Thanks for the writeup, Justin.
I think the obvious solution here is to use our existing VM infrastructure
to make it easy to build the font regardless of the host platform. There
are fontforge packages for Linux, we just need to have a Vagrant VM that
installs fontforge as part of its setup