Replies: 7 comments 7 replies
-
Yes. E.g. If you go to the Layout Video Proof Array under "Family Comparison" you can add a new layer using "+" and then change the "Family". |
Beta Was this translation helpful? Give feedback.
-
Can you please elaborate? I'm not sure why it is needed. Also note, we're going to switch to use Vite soon as implemented in #32 this makes usage of TypeScript and also jsx possible. Probably there's also a way to import files as text. I can speed up the Vite integration if you would prefer it. The #32 PR uses an existing module to integrate the POC for the React bridge, that part should not be as it in the main branch. |
Beta Was this translation helpful? Give feedback.
-
Yes, documentation of these aspects is required indeed! I can answer questions in discussions and we can tailor them to become general documentation. Maybe ask specific questions as new discussions and I will give my best to elaborate. Follow up questions can be answered in further discussions etc. |
Beta Was this translation helpful? Give feedback.
-
I'd like to collect future plans I have in my mind before making big changes here. I wouldn't like to have a big refactoring here before we didn't solve a questions that's looming on the horizon. Probably, your 6. Expand the technical overview in the documentation should also include a "future perspective" which would help a lot to assess the current state as well. That said, general improvements on the CSS and markup shouldn't be a problem to do now, and getting a concept into the handling of styles would also be appreciated by me.
These two would be definitely nice.
I’d like to discuss this further before making a decision. |
Beta Was this translation helpful? Give feedback.
-
A List of missing features would definitely be nice to have. There are features that are missing and have been requested by @dberlow the most prominent in my mind is the design space location label, in light blue, in the legacy app. In the Video Proof layouts, it's located at the top right corner. In the Type Tools layouts it's an option under "Variations -> Show parameters". I expect each layout will require a custom manifestation to this but, I'd still try to create an underlying shared approach. |
Beta Was this translation helpful? Give feedback.
-
For the most part they are pretty separate I believe. We could add a "legacy-" prefix to directories or files that are clearly only legacy. e.g. "lib/js/layouts" could become "lib/js/legacy-layouts" There are also shared files however, e.g. |
Beta Was this translation helpful? Give feedback.
-
|
Another idea I had while working on this demo last week is to have an API to create a "Stages and Actors" animation instead of using the UI to do it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Based on what I've seen so far, here are some ideas for contributions that I could make to the project and also some suggestions for improvements.
@graphicore @dberlow Let me know what you guys think.
Contribution ideas
1. UI/UX improvements
2. Implement Gustavo's proofing tool in Shell
Gustavo's tool requires loading and interacting with 2 variables fonts at the same time. Is this possible with TypeRoof?
3. Port Legacy features to Shell
Is there a list of missing/pending features that needs to be implemented in Shell? If there isn't, I can help creating it.
Suggestions for improvements
4. Have separate folders for Legacy and Shell source files
It would make navigating the codebase easier.
5. Allow loading templates from the HTML file
Implement an option that allows loading templates from the HTML file as an alternative to JS strings containing HTML code. I can work on this later.
6. Expand the technical overview in the documentation
One thing that would make the existing documentation more valuable would be expanding this paragraph.
How does TypeRoof simplify font loading and state sharing? What technical problems does TypeRoof solve? Answering these questions would help developers understand why they should use TypeRoof.
Based on this discussion, it seems TypeRoof does things behind the scenes which aren't noticeable by just using the application. It would be really valuable if this was explained in further detail.
Beta Was this translation helpful? Give feedback.
All reactions