Hipe : HTML Interface Pipe
How Hipe Works  |  Installation  |  Running hiped  |  Hipe API

The Hipe API
Including libhipe
libhipe functions
C++ extensions
Multithreading considerations
Hipe instructions
Interprocess communication
Tags, attributes and styles
Locations
HIPE_OP_ADD_FONT
HIPE_OP_ADD_STYLE_RULE
HIPE_OP_ADD_STYLE_RULE_SRC
HIPE_OP_APPEND_TAG
HIPE_OP_APPEND_TEXT
HIPE_OP_ATTRIBUTE_RETURN
HIPE_OP_AUDIOVIDEO_STATE
HIPE_OP_CANVAS_ACTION
HIPE_OP_CANVAS_QUERY
HIPE_OP_CANVAS_QUERY_RETURN
HIPE_OP_CANVAS_SET_PROPERTY
HIPE_OP_CARAT_POSITION
HIPE_OP_CLEAR
HIPE_OP_CONTAINER_GRANT
HIPE_OP_CONTENT_RETURN
HIPE_OP_DELETE
HIPE_OP_DIALOG
HIPE_OP_DIALOG_INPUT
HIPE_OP_DIALOG_RETURN
HIPE_OP_EDIT_ACTION
HIPE_OP_EDIT_CONTEXT_REQUEST
HIPE_OP_EDIT_STATUS
HIPE_OP_EVENT
HIPE_OP_EVENT_CANCEL
HIPE_OP_EVENT_REQUEST
HIPE_OP_FIFO_ADD_ABILITY
HIPE_OP_FIFO_CLOSE
HIPE_OP_FIFO_DROP_PEER
HIPE_OP_FIFO_GET_PEER
HIPE_OP_FIFO_INFO
HIPE_OP_FIFO_OPEN
HIPE_OP_FIFO_REMOVE_ABILITY
HIPE_OP_FIFO_RESPONSE
HIPE_OP_FILE_RETURN
HIPE_OP_FIND_RESULT
HIPE_OP_FIND_TEXT
HIPE_OP_FRAME_CLOSE
HIPE_OP_FRAME_EVENT
HIPE_OP_FREE_LOCATION
HIPE_OP_GEOMETRY_RETURN
HIPE_OP_GET_ATTRIBUTE
HIPE_OP_GET_AUDIOVIDEO_STATE
HIPE_OP_GET_BY_ID
HIPE_OP_GET_CARAT_POSITION
HIPE_OP_GET_CONTENT
HIPE_OP_GET_FIRST_CHILD
HIPE_OP_GET_FRAME_KEY
HIPE_OP_GET_GEOMETRY
HIPE_OP_GET_LAST_CHILD
HIPE_OP_GET_NEXT_SIBLING
HIPE_OP_GET_PREV_SIBLING
HIPE_OP_GET_RANGE_GEOMETRY
HIPE_OP_GET_SCROLL_GEOMETRY
HIPE_OP_GET_SELECTION
HIPE_OP_GET_STYLE
HIPE_OP_INSERT_TAG
HIPE_OP_GET_X11_XID
HIPE_OP_INSERT_TAG
HIPE_OP_KEY_RETURN
HIPE_OP_LOCATION_RETURN
HIPE_OP_MEASURE_TEXT
HIPE_OP_MESSAGE
HIPE_OP_OPEN_LINK
HIPE_OP_RANGE_GEOMETRY
HIPE_OP_REMOVE_ATTRIBUTE
HIPE_OP_REQUEST_CONTAINER
HIPE_OP_SCROLL_BY
HIPE_OP_SCROLL_TO
HIPE_OP_SERVER_DENIED
HIPE_OP_SERVER_NOTICE
HIPE_OP_SET_ATTRIBUTE
HIPE_OP_SET_CURSOR
HIPE_OP_SET_FOCUS
HIPE_OP_SET_ICON
HIPE_OP_SET_SRC
HIPE_OP_SET_STYLE
HIPE_OP_SET_STYLE_SRC
HIPE_OP_SET_TEXT
HIPE_OP_SET_TITLE
HIPE_OP_SRC_RETURN
HIPE_OP_STYLE_RETURN
HIPE_OP_TAKE_SNAPSHOT
HIPE_OP_TEXT_METRICS
HIPE_OP_TOGGLE_CLASS
HIPE_OP_USE_CANVAS
HIPE_OP_X11_XID_RETURN

Instruction set reference

HIPE_OP_FIFO_INFO

Carries properties of a FIFO relationship: for example, which application has the resource and what the user chose it for, so that an application can tell the user why their file is in use ("notes.txt is open in Appscape"). Properties stated by the framing manager are kept apart from what the application at the other end says about itself.

Properties

Properties are lines of the form key=value, separated by newline characters. The key is everything before the first =; the value is everything after it, as UTF-8 text with no newline characters.

KeyInValue
abilityarg[1]The name of the ability the user chose for this relationship, as the host gave it in HIPE_OP_FIFO_ADD_ABILITY, e.g. Edit in Appscape.
peer-titlearg[1]The title of the application at the other end, as the framing manager shows it to the user.

Who sends it

SenderWhenArguments
The framing managerTo both ends, after relaying a HIPE_OP_FIFO_RESPONSE that gave a resource, and whenever its properties change (e.g. the other end's title changes).arg[1] = its properties, arg[2] empty.
An application at either endWhen something it states about itself becomes known or changes. arg[2] = its properties, arg[1] empty. The framing manager relays it to the other end with arg[2] unchanged and only its own properties (or nothing) in arg[1].
An application at either endTo ask for the framing manager's properties. arg[1] and arg[2] both empty. The framing manager answers that application only, with arg[1], and does not relay the request.

Notes

An application receives this instruction from its parent (location 0), so arg[1] always comes from the framing manager. A framing manager must never copy anything an application sent into arg[1]. arg[2] is only what the other application claims.

Properties describe the other end of the relationship, not "the host" or "the client", so they keep their meaning after the roles are swapped (see "Swapping roles" under HIPE_OP_FIFO_OPEN).

The instruction is optional. A framing manager that doesn't support it sends nothing, and applications that don't support it ignore it, so an application must work without it. An application in a top-level window has no framing manager, and gets no answer.

Like the other FIFO instructions, this one is passed between frames without the Hipe display server interpreting its contents.