Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
redox
redox
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 211
    • Issues 211
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • 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
  • redoxredox
  • Issues
  • #615

Closed
Open
Opened Apr 17, 2016 by Jeremy Soller@jackpot51Owner

[question] servo as a desktop UI/UX layer?

Created by: leeoniya

Hey guys,

Sorry if this is a dumb question/idea, as I know very little about servo's OS-level dependencies.

Is something like utilizing servo for a desktop/ui layer in Redox even feasible (similar to what gaia is for b2g [1] or Electron [1])? I imagine it would be a huge amount of work, but it would eliminate the need to re-invent or reimplement flexbox (eg for window tiling), CSS animations/transitions, shadows, etc. You could potentially offload the entire UI design to designers and quickly spawn a theming community. An OS where the UI/UX is 100% styleable with little friction would be incredibly cool.

WebRender is already highly parallelized and GPU accelerated: https://news.ycombinator.com/item?id=11175258

[1] https://github.com/mozilla-b2g/gaia [2] http://electron.atom.io/

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: redox-os/redox#615