[gopher] Proposal for a gopher++ TITLE resource
Cameron Kaiser
spectre at floodgap.com
Thu Apr 1 12:40:12 UTC 2010
> Conforming clients will use the first info resource with the word
> "TITLE" in the selector as the title of the menu. All following TITLE
> resources should be ignored.
[...]
> If a non-conforming client receives a TITLE resouce, it will simply
> render it as informational text. As the TITLE should be on the first
> line of any menu it will look like a title to the user even if the
> client doesn't specifically render it as such.
I think this is fine, except that I don't think there should be any
restriction about where the TITLE resource should occur. It may make
more sense for it to occur lower down on the menu:
1> Back to the previous menu
This is the title. << TITLE resource
This is the text.
2> Some more menu options.
3> Some more menu options.
Myself, I would probably simply have the client *both* print it as an
info text line (for consistent output), and then do whatever it wants to
do with it internally (put it in the window title bar, etc.). I haven't
looked at your code yet to see if this is already what you're doing, so
maybe you already are :)
Seems like this kind of interface could be extended to other kinds of
metadata, too.
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser at floodgap.com
-- FORTUNE: The moon is in Venus' house. Shortly, there will be planetoids. ---
More information about the Gopher-Project
mailing list