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

Axes order #4

Open
dberlow opened this issue Aug 3, 2019 · 2 comments
Open

Axes order #4

dberlow opened this issue Aug 3, 2019 · 2 comments
Assignees

Comments

@dberlow
Copy link
Collaborator

dberlow commented Aug 3, 2019

DJR asks:
2) Right now design spaces are in alphabetical order by filename, and sources are in the same order that they appear in the designspace file. The resulting spreadsheet order is odd, but is the correct approach to change the order in the designspace file?

I’m not sure why the designspace file is in a-z order, but there are two possibilities; it was made that way, or it must be made that way;)

In either case UI for the axes order, and that includes the sheets, should match UI in our applications and Google’s if they develop an order.

Dave Crossland can comment on his,ideas for order, i’d Like To follow the mantra, then direction, then a-z. So, for an arbitrary input axes list;

If Opsz, wght, wdth, ital, slnt exist,
Then they are listed first, and that is their order.
If unregistered,
But called GRAD list it after the axes above.
And the axis label starts with Y or X,
Then list this next, Y axes before X.
Or the axis label starts with any other character,
List by letter in alphabetical order before
Any axis that starts with a number, and those can be listed numerically.

I’m bringing Chris in so you can share coding ideas.

Let me know your thoughts

@dberlow dberlow assigned ghost , djrrb and michelleperham Aug 3, 2019
@djrrb
Copy link
Collaborator

djrrb commented Aug 3, 2019

I’m not sure why the designspace file is in a-z order, but there are two possibilities; it was made that way, or it must be made that way;)

AFAIK there are no limitations on the order of <source> tags in the designspace spec.

Will wait for others to contribute ideas. I’d prefer see this stuff sorted in the creation of the designspace file rather than in the spreadsheet, but I’ll do whatever makes sense.

@ghost
Copy link

ghost commented Aug 3, 2019

I take it this would be in a Python build script? Let me know if you need any help implementing the order.

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

3 participants