[GH-ISSUE #81] Implement support for other line styles #55

Closed
opened 2026-03-03 16:21:59 +03:00 by kerem · 9 comments
Owner

Originally created by @mum4k on GitHub (Jan 19, 2019).
Original GitHub issue: https://github.com/mum4k/termdash/issues/81

Currently only one line style is supported:

https://github.com/mum4k/termdash/blob/master/draw/line_style.go

Originally created by @mum4k on GitHub (Jan 19, 2019). Original GitHub issue: https://github.com/mum4k/termdash/issues/81 Currently only one line style is supported: https://github.com/mum4k/termdash/blob/master/draw/line_style.go
Author
Owner

@nilathedragon commented on GitHub (Jan 23, 2019):

I've implemented a LineStyleDouble which looks like this:

image
<!-- gh-comment-id:456944233 --> @nilathedragon commented on GitHub (Jan 23, 2019): I've implemented a LineStyleDouble which looks like this: <img width="1662" alt="image" src="https://user-images.githubusercontent.com/43315617/51633224-73601700-1f51-11e9-8150-ed90feeb3ce6.png">
Author
Owner

@nilathedragon commented on GitHub (Jan 23, 2019):

I'll open a pull-request as soon as I figured out how to not submit my commits from my other pull-request too...

Edit: Actually, I'll just submit them with the one I opened. I messed this up and should not have worked on the master of my fork. Lesson learned

<!-- gh-comment-id:456945085 --> @nilathedragon commented on GitHub (Jan 23, 2019): I'll open a pull-request as soon as I figured out how to not submit my commits from my other pull-request too... Edit: Actually, I'll just submit them with the one I opened. I messed this up and should not have worked on the master of my fork. Lesson learned
Author
Owner

@mum4k commented on GitHub (Jan 23, 2019):

To send this as a separate PR, I recommend creating a new fork off the devel branch, making the changes and sending a PR against it.

Let me know if you would like to get more details on this.

<!-- gh-comment-id:457003080 --> @mum4k commented on GitHub (Jan 23, 2019): To send this as a separate PR, I recommend creating a new fork off the devel branch, making the changes and sending a PR against it. Let me know if you would like to get more details on this.
Author
Owner

@mum4k commented on GitHub (Jan 25, 2019):

I wonder what you think - are there any other line styles worth adding or do we close this issue ?

<!-- gh-comment-id:457428730 --> @mum4k commented on GitHub (Jan 25, 2019): I wonder what you think - are there any other line styles worth adding or do we close this issue ?
Author
Owner

@nilathedragon commented on GitHub (Jan 25, 2019):

I cant think of any made of ASCII characters (https://theasciicode.com.ar)

If we can use Unicode, I can think of one or two more... I'd have to test that out first though

<!-- gh-comment-id:457485050 --> @nilathedragon commented on GitHub (Jan 25, 2019): I cant think of any made of ASCII characters (https://theasciicode.com.ar) If we can use Unicode, I can think of one or two more... I'd have to test that out first though
Author
Owner

@nilathedragon commented on GitHub (Jan 25, 2019):

This would be my "LineStyleRound" proposal. A bit more modern than the default single-line approach by adding some curves.

image
<!-- gh-comment-id:457493360 --> @nilathedragon commented on GitHub (Jan 25, 2019): This would be my "LineStyleRound" proposal. A bit more modern than the default single-line approach by adding some curves. <img width="1680" alt="image" src="https://user-images.githubusercontent.com/43315617/51733833-f765ec00-2082-11e9-9dbb-944304a21c89.png">
Author
Owner

@mum4k commented on GitHub (Jan 26, 2019):

Looks great, thanks for adding both. We indeed can use unicode, but I think you already know that ;)

I will leave it up to you to close this issue, not sure if you are still working on other line styles.

<!-- gh-comment-id:457806317 --> @mum4k commented on GitHub (Jan 26, 2019): Looks great, thanks for adding both. We indeed can use unicode, but I think you already know that ;) I will leave it up to you to close this issue, not sure if you are still working on other line styles.
Author
Owner

@nilathedragon commented on GitHub (Jan 26, 2019):

Thank you! Currently I am out of ideas for new borders. I will file a pull request if I get more ideas.

<!-- gh-comment-id:457807510 --> @nilathedragon commented on GitHub (Jan 26, 2019): Thank you! Currently I am out of ideas for new borders. I will file a pull request if I get more ideas.
Author
Owner

@mum4k commented on GitHub (Jan 26, 2019):

Sounds good, let's close this for now, we can as well follow the YAGNI principle and add it only once we need it ;)

<!-- gh-comment-id:457809309 --> @mum4k commented on GitHub (Jan 26, 2019): Sounds good, let's close this for now, we can as well follow the YAGNI principle and add it only once we need it ;)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/termdash#55
No description provided.