|
Menu content
|
|
Compressed indices
|
ZIP compression can cut typical index size during download
by around 85%.
|
|
Streaming indices
|
This means that to supply enhanced scalability
together with high performance, indices are not
fully downloaded prior to commencement of applet
operation. Parts (even the largest parts) of indices
may remain on the server until needed. Various
technologies control the fetching of new index
segments.
|
|
Dynamic indices
|
This usually means that the menu content is
drawn from a database, possibly a user-specific
conditional subset of the database in response
to a query or granted permissions.
|
|
Multiple command triggers
|
Clicks on IMINT.COM menus can trigger theoretically
unlimited chains of commands, which can even be
ordered and timed. Targetting multiple pages into
multiple frames is just the tip of an iceberg of
possibilities.
|
|
Multi-sourced indices
|
Indices can be drawn from parameters (HTML files),
external static files on the server, or scripts.
|
|
Multi-type commands
|
Clicks on IMINT.COM menus are not restricted
to triggering just hyperlinks. Other possibilities include:
user-defined scripts, audio files, changes to menu
appearance or content.
|
|
Aesthetics
|
|
True type fonts
|
|
|
Background images
|
Usually used to match the menu seamlessly into
your webpage.
|
|
Colour configuration
|
Define any colours for any parts of the interface.
|
|
Total interface control
|
On most menu types, IMINT.COM avoids standard java
AWT controls (which are sometimes resistant to user-configurability)
in favour of in-house controls with 100% user-configurability. This
means that elements such as scrollbars and popup windows are totally
configurable, whether you use colours, images, fonts, etc.
|
|
Stylesheets
|
For efficient formatting of groups of menu items, a stylesheet
consisting of styles may be defined. Each style may comprise
a palette of colours, icons, button images, positioning commands, etc.,
which can then be assigned to any specific entry using
a shorthand notation.
|
|
Line-wrapping
|
A widely available option on many of our menus.
|
|
Internally generated text shadows
|
A widely available option on many of our menus.
|
|
Varying cursors
|
Typically, "hand", "eggtimer" and "arrow" cursors. Not
universally implemented yet, but available.
|
|
Function
|
|
Search interfaces
|
Versatile query boxes which can be used to search
through existing menu content, load new dynamic indices
from the server, target search results into an adjoining
page, or accepts passwords. So far only deployed with
a few applets, but can be customised into more.
|
|
History tracking
|
The ability of a menu to track the "history" of
each menu item - e.g. "highlighted", "active",
"visited", "pressed", "selected", "partially
selected". Usually visualised with user-defined
colours, multi-state checkboxes or multi-state icons.
|
|
Enhanced event handling
|
Attach command actions to mouse-over movements,
right-clicks, double-clicks, etc. Commands such
as onOpen/onClose for folders can be defined. Commands
such as onLoad for the applet's operation can be defined.
|
|
Exposed methods
|
On many applets a variety of exposed methods allows
your scripts to access or control the applet in various
ways. Also known as "remote controls".
|
|
Error and warning codes
|
During development, codes can be returned to you
describing different kinds of configuration error,
cutting down your development time dramatically.
|
|
Error backup system
|
After release, you can define a backup page or
backup behaviour if unforeseen errors occur - your
website user may never realise something went wrong.
|
