-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simple Web App UI #1121
Comments
(issue fonttools#1121)
the command line arguments parsing so that we can also invoke it as an imported python module. (issue fonttools#1121)
fontbakery_check_ttf as a python module. It will soon be used also to validate passing font files as in-memory ByteIO objects instead of filepaths.
lots of capabilities are restricted on google app engine though, so I had to disable them when running as a webapp. (issue fonttools#1121)
Felipe wrote me,
Great!
Sounds good
That's fine, I think: lets plan to set up a container based version of the web app with everything (except ftxval which is os x only)
Cool - that's not a very important check :) |
What's with the "App Engine Flexible Environment" https://cloud.google.com/appengine/docs/flexible/ It seems to me it can do all those thing, as they say you can somehow supply your own docker image. |
triggers a server-side fontbakery-check-ttf run and displays the markdown report. It surely still needs to have the UI polished tough. (issue fonttools#1121)
(issue fonttools#1121)
the command line arguments parsing so that we can also invoke it as an imported python module. (issue fonttools#1121)
fontbakery_check_ttf as a python module. It will soon be used also to validate passing font files as in-memory ByteIO objects instead of filepaths.
lots of capabilities are restricted on google app engine though, so I had to disable them when running as a webapp. (issue fonttools#1121)
triggers a server-side fontbakery-check-ttf run and displays the markdown report. It surely still needs to have the UI polished tough. (issue fonttools#1121)
animation attributes. To be used as "loading spinner" in the webapp UI. (issues fonttools#1131 & fonttools#1121)
This is fixed by reseting the check results logger object after outputing each individual report, so that it avoinds accumulating the previous messages. (issues fonttools#1133 & fonttools#1121)
animation attributes. To be used as "loading spinner" in the webapp UI. (issues fonttools#1131 & fonttools#1121)
This is fixed by reseting the check results logger object after outputing each individual report, so that it avoinds accumulating the previous messages. (issues fonttools#1133 & fonttools#1121)
…play only familyname, weigth and style (issue fonttools#1121)
...server-side. (issues fonttools#1121 & fonttools#1131)
(issue fonttools#1121)
the command line arguments parsing so that we can also invoke it as an imported python module. (issue fonttools#1121)
fontbakery_check_ttf as a python module. It will soon be used also to validate passing font files as in-memory ByteIO objects instead of filepaths.
lots of capabilities are restricted on google app engine though, so I had to disable them when running as a webapp. (issue fonttools#1121)
triggers a server-side fontbakery-check-ttf run and displays the markdown report. It surely still needs to have the UI polished tough. (issue fonttools#1121)
animation attributes. To be used as "loading spinner" in the webapp UI. (issues fonttools#1131 & fonttools#1121)
This is fixed by reseting the check results logger object after outputing each individual report, so that it avoinds accumulating the previous messages. (issues fonttools#1133 & fonttools#1121)
…play only familyname, weigth and style (issue fonttools#1121)
...server-side. (issues fonttools#1121 & fonttools#1131)
(We may design a new UI for the webapp later. Step fonttools#2 was initially meant to be for the user to choose whether or not to get hotfixing, but I think that we can always provide hotfixed files via blob-links. The user can choose whether or not to save them simply by clicking the links.) This seems enough for us to merge the webapp into master and then work on gradual improvements here and there... (closes issue fonttools#1121)
Expected behaviour
Many font designers feel uncomfortable using a command line, and expect a drag and drop web app, similar to https://github.com/graphicore/nametableswapper
Observed behaviour
Font Bakery has a command line interface.
How to replicate
Using nametableswapper as a model, make an appengine web app UI for fontbakery, such that:
The first 3 items seem very close to what Lasse has done already; for 4, to start, just printing the MarkDown output as HTML will be sufficient.
The text was updated successfully, but these errors were encountered: