One thing I do love about Gopher is that the protocol is ridiculously simple. There’s a really short tutorial on how to write a Gopher server in Factor, which I love just because the entire codebase is so damn short. (There’s also a a neat little Gopher UI that ships with Factor proper, which, again due to Gopher’s simplicity, can be a great intro to the GUI system if you’re bored.)
I would recommend adding some padding between the text and the border.
I wonder if making it use a variable-width font by default would make longer documents easier to read, while still preserving any ASCII art by detecting blocks of non-alpha chars and spaces and putting those blocks in a monospace font.
I also worked on a Gopher client, for Windows Mobile (!) - I have the binary still here, but forgot where I put the source. The funny part is that .NET Compact Framework stuff usually runs fine on full-size CLRs - this included.
One thing I do love about Gopher is that the protocol is ridiculously simple. There’s a really short tutorial on how to write a Gopher server in Factor, which I love just because the entire codebase is so damn short. (There’s also a a neat little Gopher UI that ships with Factor proper, which, again due to Gopher’s simplicity, can be a great intro to the GUI system if you’re bored.)
[Comment removed by author]
I would recommend adding some padding between the text and the border.
I wonder if making it use a variable-width font by default would make longer documents easier to read, while still preserving any ASCII art by detecting blocks of non-alpha chars and spaces and putting those blocks in a monospace font.
Sounds like that could get messy.
I also worked on a Gopher client, for Windows Mobile (!) - I have the binary still here, but forgot where I put the source. The funny part is that .NET Compact Framework stuff usually runs fine on full-size CLRs - this included.
Tremendously interesting, but I wish there were examples given to back up these claims.