edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] Gopher item type 7
Date: Thu, 22 Aug 2019 18:46:28 +0100	[thread overview]
Message-ID: <20190822174628.GE16219@toaster> (raw)

Hi,

On the gopher users mailing list someone was asking about clients so, of
course, I suggested adding edbrowse to the list.  This prompted me to refresh my
memory of our gopher support.  It looks like it works relatively well apart
from item type "7".  This should be a form which allows one to enter keywords
which are passed like a get query to the relevant selector.  However, in
edbrowse these are rendered as hyperlinks like all other item types (with
the exception of "3" and "i").  I had a brief go at fixing this but ran
into a couple of issues:
- When entering keywords in the newly rendered form they vanished after a
  rerender event.
- The form wouldn't submit as, apparently, edbrowse only supports form
  submission via http and https.

In addition, I still need to check how edbrowse would submit the form as I
think the rules may be a bit different, i.e.  I think there shouldn't be a
field name in the query (search) string.

As an example of where this functionality is needed:
gopher://gopher.floodgap.com/1/v2

The "Search Veronica-2" link is actually supposed to either render as a form
to submit the search or, in some clients, an item which then brings up a
form which you can then use to submit the query (but I think the former
option of just rendering the form may well be a nicer UI).

I'm not sure how difficult making this work will prove to be but am happy to
help where I can.

Cheers,
Adam.

             reply	other threads:[~2019-08-22 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 17:46 Adam Thompson [this message]
2019-08-22 19:55 ` Karl Dahlke
2019-08-22 20:10 ` Karl Dahlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190822174628.GE16219@toaster \
    --to=arthompson1990@gmail.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).