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

Graphics implementation #7

Open
7 of 8 tasks
czyzby opened this issue Mar 5, 2016 · 2 comments
Open
7 of 8 tasks

Graphics implementation #7

czyzby opened this issue Mar 5, 2016 · 2 comments

Comments

@czyzby
Copy link
Collaborator

czyzby commented Mar 5, 2016

See DragomeGraphics.

  • Reporting application's bounds (width, height, screen w&h).
  • Reporting rendering meta-data: PPI, PPC, density, delta, FPS(), frame ID(). * - implemented by Renderer, might return mock-up values.
  • Fullscreen mode.
  • Orientation lock during fullscreen mode.
  • Non-continuous rendering. Not supported by GWT either. Do we want to support this?
  • Changing title.
  • Changing cursor. Implemented in DragomeGraphics, but DragomeCursor does not work yet.
  • Display modes.
  • Monitors.
@intrigus
Copy link

intrigus commented Mar 5, 2016

It would be very nice to know, which repository is used for developing gdx-dragome!
It would be better to join forces and not implement the same functionality twice i.e. in this repository and that repository !

@czyzby
Copy link
Collaborator Author

czyzby commented Mar 5, 2016

@intrigus To be honest, not much functionality is duplicated. Yet. This repo is kept cleaner and GWT code is actually refactored, rather than just copied.

I wanted to transfer this repo to dragome/libgdx and merge both repositories ASAP, but not counting short talk with Xpe by forum, no further word from him about it. He seems keen on focusing on his repo (duh, who wouldn't be). But, well, for now his repo contains mostly mock-up classes (basically empty classes with implemented interfaces) except for GL20, Graphics, Files implementations.

Since this repo actually uses Gradle to manage dependency and publish artifacts rather than keeping libraries as jars in the repo (sic), this will most likely become the main one. But you're right: no point in reinventing the wheel, Xpe work should be validated and merged. I really don't want to waste time on any conflicts, so it would be best if @fpetrola just decided what we do.

Edit: see #13.

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

No branches or pull requests

2 participants