Community design crit - February 6, cancelled

[Hung, Jonathan]

Hi everyone,

Currently there isn't a topic scheduled for tomorrow's design crit, so there 
will not be a meeting for Tuesday February 6.

If anyone has a design they would like to share in the future please let me 
know.

Thanks!

- Jon.


---
Jonathan Hung, Inclusive Designer
Email: jh...@ocadu.ca
OCAD University
Inclusive Design Research Centre

___
fluid-work mailing list - fluid-work@lists.idrc.ocad.ca
To unsubscribe, change settings or access archives,
see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

Re: Icon font building

[Justin Obara]

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 February 2, 2018 at 7:18:24 AM, Justin Obara (obara.jus...@gmail.com)
wrote:

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 succeeded, and
have the fonts available as an artefact associated with a successful build.


I’m not sure if that would work in the process I described, but I guess we
can touch base on it once there’s something in place to work from.

Thanks
Justin

On February 2, 2018 at 4:57:26 AM, Tony Atkins (t...@raisingthefloor.org)
wrote:

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:

> I’ve filed a FLUID-6244
>  to address this, at
> least as an initial step, by adding a grunt build process to the
> Infusion-Icons  repo.
>
> Here's the suggestion for the new process:
>
>- In Infusion-Icons add a grunt task to generate an icon font that
>includes all of the icons
>- In Infusion-Icons add a grunt task for building a custom icon font
>based on a config file
>-
>   - The config file will be versioned in the project's repo (e.g.
>   Infusion), and include the paths to the SVGs to use, and their 
> codepoints
>   - The config file would be able to contain any configuration that
>   is valid for grunt-webfont task
>- After an icon font is generated, the implementor will need to
>manually place it in the specific project repo
>
> Example Config:
> {
> src: [
> "svg/contrast.svg",
> "svg/reset-undo-arrow.svg",
> "svg/line-space-expanded.svg",
> "svg/line-space-condensed.svg",
> "svg/line-space.svg"
> ],
> options: {
> font: "custom-icons",
> codepoints: {
> "contrast": 0xE005,
> "reset-undo-arrow": 0xE008,
> "line-space-expanded": 0xE009,
> "line-space-condensed": 0xE00a,
> "line-space": 0xE00b
> }
> }
> }
>
> I understand this isn’t the most elegant solution, but I think it will at
> least, in the short term, provide a workable solution that still preserves
> the configuration for generating the icon font and make it easier to see
> which icons are included at which codepoints. As we have time in the
> future, I think we should look for ways to improve this workflow, including
> adding the VM option to remove the need to manually install fontforge and
> ttfautohint.
>
> Thanks
> Justin
>
> On February 1, 2018 at 12:50:44 PM, Justin Obara (obara.jus...@gmail.com)
> wrote:
>
>
> 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 and
> bridging across a host and vm. We use grunt for other build tasks that have
> been run on the host machine and probably won’t want to force anyone to
> have to use the vm.
>
> I’m wondering now if we just add something to the Infusion-Icons repo for
> building fonts. We could require that fontforge and ttfautohint are
> installed, or setup a vm option. Any thoughts?
>
> Thanks
> Justin
>
> On January 26, 2018 at 8:13:45 AM, Justin Obara (obara.jus...@gmail.com)
> wrote:
>
> 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 easier to update the icons if the build process is
> colocated, and it should be fine to version the icons alongside Infusion. I
> suppose if we break Infusion out into a monorepo we could explore
> separating the icons into their own package(s) (there will likely be
> separate fonts for each component that uses icons in order to keep file
> sizes to a minimum). I’m open to other ideas though.
>
> Thanks
> Justin
>
>
> On January 26, 2018 at 3:38:36 AM, Tony Atkins (t...@raisingthefloor.org)
> wrote:
>
> Thanks for the writeup, Justin.
>
> I think the obvious solution here is to use our