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

build xoop for different shaped screens #3

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

mcdamo
Copy link

@mcdamo mcdamo commented Apr 10, 2024

  • refactor to define shape and rules in map_* scripts
  • script to build xoop_* binary based on named map

Create map_* script to define boundaries and warp rules, and build independent xoop binary for any screen map.

Inspired by screen maps in taralli

@m-col
Copy link
Owner

m-col commented Apr 10, 2024

Hey thanks for the PR! This is an interesting idea. I wonder whether it wouldnt be more user-friendly to use a config file to define map rules. It would certainly be less flexible but I suspect it would be more accessible for people who install compiled binaries from a package rather than compile from source. What do you think?

@mcdamo
Copy link
Author

mcdamo commented Apr 10, 2024

Thankyou for this application ^_^

It depends if a user-friendly config can represent the shapes and warps that users might want. I don't know what people want -_-;, but map_beef is a basic example of a non-standard screen layout with custom warps.

For me a config file could not be used, I have a custom layout with various barriers and warp-translations between screens of different sizes.

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

Successfully merging this pull request may close these issues.

2 participants