Font builder à la Input

[larsenwork]

Could be cool to to let people customise without having to download first and use font squirrel - anybody with the skill to create the opentype flattening server side ?

Or any other clever idea how to do this?

[larsenwork]

sure, that'd be great!

[larsenwork]

Nice to have(i.e. not needed) - a "normal" suffix where the width is unchanged e.g. "Monoid-Normal-$-*-l.ttf"

[chase]

Alright, I did the cleanup. Make sure to update your local repository to reflect the changes I made in the cleanup:

git branch -m andreas master
git checkout 6898368
git checkout -b master
git cherry-pick --ff 9db7119 a320672
git checkout andreas

That will leave you in your experimental branch to do... experimental things.

[chase]

Regarding the suffix, that's a simple change, but it will have to wait until later. For now, I'm off to bed!

[larsenwork]

cheers, always weird working with people in completely different timezones - I think it's time for some proper breakfast :egg: :coffee:

[chase]

I was about to fall asleep when it hit me, you should also make sure that your local branches track the new remote branches for when you push changes: git branch -u origin/andreas andreas git branch -u origin/master master

Now I'm really off to bed, haha.

[larsenwork]

yep, I have all three branches where I want 'em :sleeping:

[larsenwork]

Could a zip function be added to the script so that all files are zipped individually?

Monoid--large.ttf is 74kb and Monoid--large.ttf.zip is only 31kb

I used this function in shell but don't know any python :wink:

for f in "$@"
do
    zip -j "$f.zip" "$f"
done

[larsenwork]

nevermind about the "normal" suffix - I thought I needed it for the download script on the website but I don't :smile:

[larsenwork]

Good morning! do you prefer linking to your Twitter or GitHub persona from the website? (I'm adding a "made by" section on the webpage) I've played around in Monoid-Andreas and have done manually what wercker can hopefully do in the future. - i.e.:

• building (build.py - ignore "medium" and "normal" - I left them there for better overview)
• zipping files individually (not together with readme/license - forget about that)
• pushed it to the release folder

And everything works - I'm just finishing some text edits for the webpage

[chase]

Let's go with my GitHub persona. I don't really prefer one over the other, but what happens on GitHub stays on Github, right? Haha - okay, bad joke.

Zipping the font files won't be too difficult. That can actually be added as a wercker.yml step.

Also, I think I finally have a realistic solution:

1. Make a base branch named 'release' similar to gh-pages but it only contains the font files.
2. Use RawGit.com's wonderful, free CDN for Github-based content: https://cdn.rawgit.com/andreaslarsen/monoid/release/Monoid-...ttf.zip

[larsenwork]

So it's like the release folder I currently have in Monoid-Andreas only the only content is the zips, right?

[chase]

Exactly! This will make automation simpler and also means you don't need to worry about rebasing and such, since this is a branch dedicated to the Wercker bot's products.

[larsenwork]

Perfect! I "limited" myself to 1600 versions - I can add more if people ask for it but they should cover most user wishes....I guess.

[chase]

The binary object size per file is fairly small and we are using a repository branch, so it shouldn't be too much of an issue to add more options in the future. It won't lock up like GitHub releases, at least.

[larsenwork]

Yep,I didn't really think about file size when I first tried the script this morning - stopped when I saw the folder being >1gb

[chase]

Wercker is giving me difficulties with adding the deploy key for a push, I'm highly considering moving to Travis CI since Wercker hasn't been behaving properly.

[larsenwork]

I can't really say anything as I don't know about either one of them. If it's a matter of the platforms not being "mature" enough then I can get by for the time being with the fontbuilder+build script.

The last step (be it wercker or something else) is the icing on an already delicious cake...

[larsenwork]

and now I'm hungry...

[chase]

Wercker has started to fail silently and sometimes just queues a build for hours and does nothing. Travis CI would be a rather quick transition, they have better integration with Github as well.

Honestly, I'm surprised that Wercker is breaking seemingly randomly. I'm hoping that can turn things around quickly, but if they can't, it is either Travis CI or Circle CI. I'm actually going to try Circle CI first, since it is more flexible like Wercker but battle hardened.

Sorry for all these unexpected blocks in productivity. I swear as soon as I think I have a solution, the provider I'm using breaks, haha.

[larsenwork]

:+1:

[chase]

See #16. I recommend removing the webhook for Wercker :smile: