I'll look forward to seeing it.  A lot of us want a fast, compact,
stylus-centric UI for use on PDAs, but we don't want to give up being able
to do development on the PDA (e.g., we still want browsers, the compiler,
etc.).

IAE, I'm looking forward to seeing it, although I am still not sure why such
a UI could not be built using MVC interfaces.

The idea of using a state machine caught my attention.  I am currently in
the process of building a project using a general state machine approach.
The current state is encoded in the notion of a Context; the Context holds
the current Actions that can be performed in the Context; the Actions cause
a a transition to another Context.  That is model behavior, but the contexts
can viewed, and a selection of an action made.  Actions are objects, not
methods.  The actual application is hidden within the Actions and the way in
which the context graph is constructed dynamically.

	--- Noel

Tansel Ersavas [Editor, SqueakNews http://www.squeaknews.com] wrote:
> "Noel J. Bergman" wrote:
>> What details are known about this additional UI?  MVC works just fine on
>> PDAs, and is small, fast, rich, and flexible; what does this minimal UI
>> offer to warrant YAUI?

Well, I guess I made a few demos to a few people, but I doubt if anyone can
remember. Apart from that nobody knows much about it. You'll have to wait at
least about a month and a bit to see the full details but I can tell you
this:

It is not actually intended to compete with neither MVC nor Morphic. I guess
it should be called a toolkit rather than "UI" but what the heck, it is a
UI.  It is aimed at minimal machines and works on top of an almost fully
stripped image (no MVC, no Morphic, only sound and basic Blt support, images
under 1M). The goal is to quickly program slick looking PDAs and Kiosk
applications with minimal programming (very narrow focus). Supports sound
and still and animated graphics. It is programmed as a state machine or a
hierarchy of state machines so most of the generation can be automated (You
don't have to, but makes things easier). It works well with stylus and all
requests are point and click, it has its own keyboard layout which is so
flexible it can emulate a keyboard, a pop-up menu or a yes-no answer in
exactly the same way. It is about 10 classes and 190 methods,
semi-commercially tested and working. It was borne out of a need and helped
me to develop a 30+ page full color mostly functioning prototype  on a
Cassiopeia with 16M memory and 10M+ graphics and sound files, all in 3-4
weeks, including the toolkit itself. This was around January 2000 when I was
in a more functioning state, it needs a little dusting.

Cheers