+ 8

Code fragment fonts

<Suggestion>Using a monospace font for code fragments would be a better approach as it is the industry standart and provides more readable code.</suggestion> If you agree, hit the like and make this suggestion visible. If not, please explain your idea below.

10th Apr 2017, 11:18 PM
BarÄ±ĆŸ Can Ceylan
BarÄ±ĆŸ Can Ceylan - avatar
6 Answers
+ 6
To be honest I'd prefer SL to use mono in the output console - my ASCII constructions would look better ;)
12th Apr 2017, 5:07 PM
Kuba SiekierzyƄski
Kuba SiekierzyƄski - avatar
+ 6
@BarÄ±ĆŸ Can Ceylan - ah, challenges. I was thinking discussions. The render engine isn't (to me) clearly HTML or even BBCode like StackExchange...input accepts some clipboard-origin formatting, but output hasn't rendered anything more interesting for me than unicode. Do you have a specific font in mind?
12th Apr 2017, 8:06 PM
Kirk Schafer
Kirk Schafer - avatar
+ 5
I'm not really a fan; CodePlayground's already fixed-width, it's wider, pinch-to-zoom and linking code (without losing your place) is way easier with the latest update. Personally, I'd rather have a way to mark snippets as related to a question, so that they can be collected together (not only in your own view...but it would be cool to see a list of 'patches' someone offered to the asker).
12th Apr 2017, 4:37 PM
Kirk Schafer
Kirk Schafer - avatar
+ 4
@Kuba YES. That too. I spent so long trying to line up box chars (unicode, ASCII, terminal tricks) and finally went with a set that matched 'space' width.
12th Apr 2017, 5:25 PM
Kirk Schafer
Kirk Schafer - avatar
+ 4
@Kirk Same story here, man. Same story...
12th Apr 2017, 5:26 PM
Kuba SiekierzyƄski
Kuba SiekierzyƄski - avatar
0
The way code blocks look in challenges when you are on clock is messy and hard to read. Sometimes indentation is buggy too. If they are html templates, a simple wrap with <pre> tag or something similar would fix the issue.
12th Apr 2017, 6:15 PM
BarÄ±ĆŸ Can Ceylan
BarÄ±ĆŸ Can Ceylan - avatar