I dunno if this is appropriate for this community, so mods, please delete if not.

I have been writing a screen clone in rust.

https://github.com/cameroncros/PoorMansScreen/tree/better_screen (The main branch is how I currently use it, not at all screen-like, the better_screen branch is much closer to a screen replacement.)

It all currently works fine, albeit quite simple, and I suspect not following best practices. Please talk shit about my code so I can fix that :D

For my next stage of development, I would like to use some combo of vt100 and ratatui to wrap the shell in a border, or add a menu bar at the top or bottom to make it clear when the user is inside a “screen”. Does anyone have any thoughts on how to go about doing that? I am very unskilled at ratatui.

  • livingcoder
    2·
    3 days ago

    That’s an interesting take. I didn’t know that the tool screen even existed, so I had no idea that it would be nice to have in my toolbelt for future needs. A README also helps those that may already know a lot about screen and want to know the differences between screen and their implementation.

    There is nothing better in open source than a thorough, well-written README at the root of the project. Wanting others who don’t understand the source of the inspiration to be completely clueless is unfriendly (at best).

    • some_guy@lemmy.sdf.org
      1·
      3 days ago

      I’m pointing out that there is information available without asking the creator to explain it rather than suggesting that a readme shouldn’t be created. In software development, one of the primary skills is knowing where to find information yourself before interrupting others. I’m not suggesting that one shouldn’t ask for help; quite the opposite. I’m just trying to provide an answer as a third-party who is not in a position to author a readme. I don’t consider that unfriendly.