Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

Update drag and drop to use fontbakery >= version 0.3.0 #41

Closed
8 of 13 tasks
graphicore opened this issue Aug 15, 2017 · 12 comments · Fixed by #55
Closed
8 of 13 tasks

Update drag and drop to use fontbakery >= version 0.3.0 #41

graphicore opened this issue Aug 15, 2017 · 12 comments · Fixed by #55

Comments

@graphicore
Copy link
Contributor

graphicore commented Aug 15, 2017

Font Bakery now has a new output format, thus, we need to redo the report saving and rendering part. This will improve real time reporting and we also have the opportunity to do parallel execution of tests, which would be nice to have:

Things that need to be done (most "at the same time")

  • update worker to invoke the new Font Bakery
  • change test report format in the database
  • create a new test reporter for the new report format
  • update database report-record on a per test base (or per message?) (== real time pushes to browser)
  • adopt test report rendering (in the browser/javascript) to new style tests
  • We should have just one Font Bakery worker for drag and drop, dashboard etc. so make it reusable
  • enable (worker) distributed/parallel test execution (per process distributed on a multi-core cpu would be awesome as well!)
  • for parallel execution one worker would act as the master and dispatch subset-jobs via AMQP.

Parallel execution can be done after all the other things, when done carefully it'll just work 😄

Other Important

  • all the crazy dependencies need to be in the workers: msfontvalidator, pyfontaine, fontforge, Apple ftxvalidator (use an external OSX-server cloud provider?, ask Apple to make a linux compatible binary 😹 )
  • clean up repository if already possible, better docs
  • begin to plan dashboard (issues has a lot of feature requests)
  • It would be awesome to have self-updating workers 👿 why do a docker push etc.pp if the worker could just run pip install itself (... ok, this is playing the implications down). It would also make it more straight forward to re-run tests. As when the repository changes, we need to re-run when the workers are updated, it's basically both input for us.
  • configuring development/minikube and deployment/gcloud is tortuous
@davelab6 davelab6 modified the milestone: 0.1.0 Aug 16, 2017
@felipesanches
Copy link
Member

The goal should be fontbakery >= 0.3.1 (the 0.3.0 release was broken; the issues were then addressed on a quick follow-up 0.3.1 release)

@graphicore
Copy link
Contributor Author

The APIs didn't change.

@felipesanches
Copy link
Member

I want to showcase the dashboard at ATypI. Can I help with some coding here?

@graphicore Can you please update the check-boxes in the description of this issue in case some of them are already implemented? How do you see a way for me to help here?

@graphicore
Copy link
Contributor Author

Allright, I checked some items and created branches on googlefonts:

@davelab6
Copy link
Member

adopt test report rendering (in the browser/javascript) to new style tests

Could you use https://material.io/components/web/ please?

@graphicore
Copy link
Contributor Author

Could you use https://material.io/components/web/ please?

Yet another material framework?

@felipesanches
Copy link
Member

It seems to be the same one we discussed in the past, if I recall correctly.

@graphicore
Copy link
Contributor Author

There must be even more, but last year Material Design Lite: https://getmdl.io/ was the thing.

@felipesanches
Copy link
Member

I think that any one of these would be great. Unless @davelab6 has some reason to pick a specific one like https://material.io/components/web/ the choice seems to be pretty much up to you.

Even though Font Bakery is not an official/supported Google product, I think the reason why Dave asked for it is to get an elegant look and feel that is familiar to users of Google products (as well as effective in terms of the user experience, off course).

@graphicore
Copy link
Contributor Author

The one thing I don't like about these frameworks is that they seem to have a TTL of less than year. I appreciate not having to write so much style related CSS and HTML though. Oh, yeah, another thing is that the HTML is usually very idiosyncratic. Another attendee could be polymer paper elements, which I also never used and can't say how good it is, but the web components concept could help (or make it worse).

@graphicore
Copy link
Contributor Author

Here's another one: https://material.angular.io/, the older AngularJS has it's own implementation of course: https://material.angularjs.org

@davelab6
Copy link
Member

davelab6 commented Aug 29, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants