Skip to content

GitLab

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

Closed
Open
Opened 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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: redox-os/orbclient#12