Closed dberlow closed 5 years ago
ghost
commented
5 years ago Generally I believe this can be done quickly for most of the examples. Interactive ones like PARTICIPATION and the text-on-arc are trickier because they involve Javascript, which I haven't taken into account for the playground (unlike the real Codepen, which has three editing panes).
I threw this whole playground UI together in an hour, and would be happy for an actual designer to sketch up a better one.
ghost
commented
5 years ago To answer your question, I can probably come up with a stretchable "window in window" preview that starts at the same width as the example was when clicked, in a few hours.
dberlow
commented
5 years ago I did a quick survey and they are much better than I thought, in fact most of them are perfectly expectable. It’s just this one was really really undone.
On Mar 19, 2019, at 7:53 PM, Chris Lewis notifications@github.com wrote:
To answer your question, I can probably come up with a stretchable "window in window" preview that starts at the same width as the example was when clicked, in a few hours.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
ghost
commented
5 years ago This is working pretty well, feel free to reopen or start a new ticket if I've missed anything.
When the user selects to use these, the default they start with must be as close to the example in appearance as possible.
I show what the current default is for an example in the enclosed PDF, Topics/Styles/Example 1, and it's code playground defaults as seen on my desktop, iPad and phone.
Below that, I show what a more accurate default would be, and I include the code for each below that.
I'm interested in a time and cost estimate to make it so every playground so far defined based on an example, has reasonable “portal-responsive” type and typographic defaults.
Playground Defaults.pdf I can also email the Sketch file.