Skip to content

Web Browser #145

@toncho11

Description

@toncho11

In general we could have a Nano-X compatible browser (that uses Nano-X API) that executes on a contemporary machine, but is displayed on a Nano X server running under ELKS. So you:

  • telnet to a modern computer or Rasberry PI
  • you configure the a Nano-X browser to use the network IP of the Nano X server running under ELKS
  • you start the browser over telnet on the remote computer, it shows on ELKS and Nano X

So it is like finally using the advantages of the client/server architecture of the X graphical systems. I used to do a lot of X server ssh port forwarding.

Also the browser needs to compile on contemporary systems, not ELKS, which probably makes it easier to develop.
We could say that it is not limited by the memory available to ELKS, but indeed it is. Showing an image on the X server under ELKS will still consume a lot of memory.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions