Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O orbclient
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • redox-os
  • orbclient
  • Issues
  • #12

Closed
Open
Created Jun 06, 2016 by Jeremy Soller@jackpot51Owner

Re-adding a Image struct.

Created by: ca1ek

I'm wondering if you would be okay with me adding the Image struct back into orbclient.

Why?

Orbimage is a library only to deal with images. I want to add a hardware accelerated image support(with fallback to software in Redox) trough sdl2::render::Texture. That would be totally out of the scope of orbimage.

My current idea is to have SoftwareImage and HardwareImage structs, both implementing Image trait. SoftwareImage being same as orbimages Image.

No image loading functions, the way to load them is still trough orbimage.

What do you think?

Edited Sep 29, 2019 by Coleman McFarland
Assignee
Assign to
Time tracking