Lists Home |
Date Index |
- From: Len Bullard <firstname.lastname@example.org>
- To: Jelks Cabaniss <email@example.com>
- Date: Fri, 05 Nov 1999 21:41:34 -0600
Jelks Cabaniss wrote:
> Jeffrey E. Sussna wrote:
> > > <ACTION TYPE=ACCEPT TASK=GOSUB VARS=host=$(hostname)
> > Any language that contains a construct called "GOSUB" deserves dustbin
> > status. :-)
<a href= : the great leveler, the chosen symbol, the getItBox.
> Indeed. Check out this little snip from Rohit Khare's "W* Effect Considered
So: in geek
> One way to think of WML is as programming 3270 screens
> with a very simple BASIC.
> An application is delivered to
> the handset as a 'deck', the deck is
> which allocates a corresponding
> pool of storage space for variables.
so that a namespace names
> Individual 'cards'
> are executed on entry and exit
> to render the handset
and binds namespaces
> they can fill in (shared) variables,
> rerender on
> external event notifications (e.g. call completed), and
names bound to controls
> bind further actions to a small set of buttons.
format geometry for interaction, morphs, multiD, aggregate sets
> display calls themselves are essentially character-cell
> oriented, with tab alignment and bold, italic,
> underline, big, and small fonts. Tables, frames, colors,
> and so on are not supported.
binds format. go3D. kids hate buttons. give them personalities
and adventure. the world is not small nor is the reach of our
tools to communicate and be human together. make it more
exciting than windows and win.
> Semantic HTML markup like
> <ADDRESS> must be stripped out. Even simple declarative
> HTML doesn't mean what it used to -- <P> no longer
> begins a new line. 'Graphics' support is intended mainly
> for optional icons in place of text menus; no clickable
> menu maps or such. WML is really a scripting language...
which is what you need for prebinding information to occasionally
The nice thing about lowlyFrame design: the initial allocation of IDs
is clean if the
trees name attribute sets. One id to fetch a subtree.
Give up some semantics in that instance to get more certain binding of
control to value by device.
The next instance is yours to transform as you will. Accumulate
Schemas must be temporally adaptive. That is why XML schema. That is
We do it anyway. How many messages are used in this system which are
timestamped? Can we make schema more adaptive by finding principles for
that timestamping more efficiently? Types aggregate in time.
of named events and types are bound such that when it changes in one
part of the
tree, it changes in all the others at the same time. A variable is
be polite because it is unique so it changes at the same time in any of
dimensions in which it is represented.
> That's just the tip of the iceberg -- check out how they've "reinvented" TCP/IP:
For the protocol gypsies to say. Pre-aggregating trees is a way to make
the pgs work less.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)