Re: [gopher] Gopher+ support in the community
Kevin Veroneau <kevin@...
2015-04-23 05:03:23 GMT
Okay, so like I said, here's my initial release of a Gopher client for the
It uses an updated version of my gopherlib.py library found here:
To get it up and running, you will need to grab yourself a copy of npyscreen,
either via pip or just download it manually.
It currently doesn't support every standard Gopher type, but all the basics
are there and were tested, namely i, 0, 1, and of course 7. I will add the
other gopher types as I continue working on it. Feel free to contribute if
you wish as well.
There is currently no address entry function, and it will bring you to floodgap
by default. However, feel free to change the initial server within the code
itself. Proper address entry via a dialog box, and via the command line will
be added very soon.
You can access the menu by press Ctrl-X, there you can return to the root of
the current server, or exit the application itself.
Future versions when other Gopher types are supported will introduce a
preferences form, where you can select external applications to launch for
specific gopher types, such as one to display images, or an external HTTP
browser for HTTP links. HTML will be supported in 2 ways, one being a
html2text translation, or the ability to launch an external browser with
On Wednesday, April 22, 2015 06:03:43 PM James Mills wrote:
> Sounds interesting I'll take a look :)
> James Mills / prologic
> E: prologic@...
> W: prologic.shortcircuit.net.au
> On Thu, Apr 23, 2015 at 9:39 AM, Kevin Veroneau <kevin@...> wrote:
> > I was thinking of urwid, but I don't feel it's the perfect match for this
> > type of application. It would require a good amount of work to use urwid
> > for such a simple client. I am planning on using the rather awesome and
> > lightweight "npyscreen" library. It's seems like a match made in heaven.
> > It supports lists(gopher menus) easily, and can easily display prompts
> > from the user in a dialogue box. It also makes it a snap to create
> > context menus(and popup menus in general). It even supports easy to
> > create and manage forms(great for ASK) and for general preference
> > screens/bookmark management. I've built a documentation viewer in it
> > before, which had a nested menu system and was able to show text
> > documents with ease and minimal code. Overall, I see npyscreen and
> > gopher like a marriage made in heaven.
> > http://npyscreen.readthedocs.org/
> > Check out some of their examples and tell me it won't work. :) That's why
> > I noted I could release an initial client this evening due to how easy
> > and powerful this library is. Urwid is great, I made a few apps in it,
> > but it used complex layouts to display the screen. This made debugging a
> > tad difficult, as it took some time to make an app look and function
> > perfectly. Telnet into my profile server to see that urwid app:
> > telnet://
> > veroneau.net:5199
> > Kevin.
> > On April 22, 2015 5:01:54 PM MDT, James Mills <
> > prologic@...> wrote:
> >> On Thu, Apr 23, 2015 at 8:53 AM, Kevin Veroneau <kevin@...>
> >> wrote:
> >>> For a gopher client, I was going to make a console-based one, along
> >>> with a Qt4 WebKit-based one. Qt4 is nicely cross platform, so nobody
> >>> will be left out.
> >> What are you plans here?
> >> I'd be interested in a console client (urwid?)
> >> and QT4 would be nice too :)
> >> cheers
> >> James
> >> James Mills / prologic
> >> E: prologic@...
> >> W: prologic.shortcircuit.net.au
> >> ------------------------------
> >> Gopher-Project mailing list
> >> Gopher-Project@...
> >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
> > --
> > Sent from my Android device with K-9 Mail. Please excuse my brevity.
> > _______________________________________________
> > Gopher-Project mailing list
> > Gopher-Project@...
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project