Skip to content
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

Circle Sticker Standard #1

Open
DeMarko opened this issue May 7, 2014 · 6 comments
Open

Circle Sticker Standard #1

DeMarko opened this issue May 7, 2014 · 6 comments

Comments

@DeMarko
Copy link

DeMarko commented May 7, 2014

In the same way there are hexagonal and square standards, I feel there should also be a circular standard. It's a pretty common design pattern for illustrations (in the way that hexagons and squares fit logos very well)

@terinjokes
Copy link
Owner

Sorry, circles don't allow for the same highly optimized use of space, as there will be extra space between circles.

It was a deliberate design decision of this working group to consider circles a legacy sticker design.

Well have more information on handling legacy sticker designs in a future draft.

@terinjokes
Copy link
Owner

I originally closed this request back when the Sticker Standard was supposed to be a joke. Reopening now that I've gotten a few more requests for it.

@terinjokes terinjokes reopened this Nov 18, 2016
@junosuarez
Copy link

circle packing though

@terinjokes
Copy link
Owner

@jsdnxx It's still a valid complaint, but think it's something worth having a discussion over. As noted in 2014, perhaps we should document non-tessellating "legacy" shapes somewhere.

@gamesbook
Copy link

gamesbook commented Apr 8, 2018

I'd support this; also an octagonal sticker (some road-signs are octagonal in shape) as its slightly more efficient for packing and produces a pleasing tessellation.

@Potherca
Copy link

Potherca commented Apr 4, 2024

I think a valid use case has been overlooked for circular (or even elliptical) stickers... Filling in an empty space!

Hex circle

The specification would be simple, it should not exceed the existing boundaries of the current spec.

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants