Hey everyone,I have a question about your specific preferences on how you prefer to gopher around.Do you prefer a traditional gopher client that mimics a modern Web browser, with back/forward buttons and a single page view of individual gopher menu items?In the past there have been some rather interesting gopher clients which displays a tree to represent the gopher menus. There's also hybrid views like we see in OverbiteFF, where we can directly view gopher items by clicking a plus sign in the gopher menu.So, to your preference, do you prefer seeing gopher as a world wide filing system in a unified tree view, or do you prefer gopher to mimic the look and feel of the Web? Or would you rather slap on an oculus rift and browse in Gopher VR?Unlike the Web, gopher has the advantage of being very flexible when it comes to client design. There's even a FUSE module to mount a gopher server as a local file system. Gopher has true structure and content separation.I'm sure I brought this up before, but XMBC/Kodi uses a similar system for it's media centre. Where structure and content is separated in the same way when developing add-ons. I actually created a Gopher browser for XBMC/Kodi, so you can browse gopher from the comfort of your living room couch using nothing more than an IRDA remote. Try browsing websites using a TV browser just using an IRDA remote... it's painful to navigate, and content loads ultra slow.Anyways this email has gone on long enough, so what would your ideal gopher client of the future be like? Browse gopher using an LCARS interface perhaps?Sent from my BlackBerry Priv - the most secure mobile device - via the TELUS Network
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project